Ansicht
Dokumentation

VOFMC_RTN_REG_VC_KOB - Define Requirement in Pricing

CPI1466 during Backup   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Control whether a condition is applicable during pricing.

In pricing, requirements are used for the condition technique. They check various criteria during the execution of pricing. You can enter them in a step of the pricing procedure or in an access of an access sequence.

For pricing, you can implement a requirement for document, for example, as a pre-step; it is then used as a response time improvement that first checks the document fields. Or you can use the requirement for document as a stand-alone check that checks only the header attributes.

In both cases, the document item fields do not have to be checked if the result of the check is negative.

Depending on the implementation type of the process enhancement option task, you must implement the relevant Business Add-In (BAdI) and assign a unique filter value to this implementation. When you register a routine number in a later step, you use this filter value as an enhancement identifier.

• If you want to execute the optional pre-step, you must have implemented the Define Requirement in Pricing for Document custom logic for the Pricing business context. The implementation of the requirement for document is optional.

• If you want to execute the requirement for item, you must have implemented the Define Requirement in Pricing for Document Itemcustom logic for the Pricingbusiness context. You must use this requirement, if item fields are involved.

• You can decide if you want to use either the requirement for document or the requirement for item or both.

• If one of the two requirements has not been implemented, the system sets the result for the respective requirement automatically to fulfilled.

Note: If an implementation is assigned in the registration, but corresponding implementation does not exist an error will be raised in pricing.

Note:

1. Check whether you can use the requirements delivered with the standard system.
2. To register a routine number, define a routine number, for example, routine number 3000001. The system automatically enters the Requirement used in Pricing (PRICING_REQUIREMENT) process enhancement option. You use this routine number in a later step in the pricing procedure or access sequence configuration.

Note: The general number range of the routine number is from 3000000 to 3009999.

1. Assign the filter value of the BAdI implementations to this routine number as an enhancement identifier (ID) for a valid process enhancement option task. For example, for the Requirement for Document Item(PRCG_RQMT_FOR_DOCUMENT_ITEM) process enhancement option task.

Note: Use the field help for the enhancement ID.

Follow up activity:

Enter the routine number in the Requirementfield in the appropriate place of the control data in pricing:

• In the Set Pricing Procedures configuration activity, enter the routine number to a step of your custom pricing procedure.

• In the Set Access Sequences configuration activity, enter the routine number in an access of your custom access sequence.

Note: You can delete your own requirements only, if they are not used in a pricing procedure or access sequence and if the access sequence has not yet been transported to the production system.

A requirement checks whether a condition type is taken into account in the document during pricing. The requirement can define, for example, that a condition type is only taken into account for import and export transactions.

RFUMSV00 - Advance Return for Tax on Sales/Purchases   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 4199 Date: 20240523 Time: 174705     sap01-206 ( 78 ms )