Ansicht
Dokumentation
NOR3_CTR_CHECK -
Fill RESBD Structure from EBP Component Structure General Data in Customer MasterThis documentation is copyright by SAP AG.
Functionality
The function has to provide the status of the Gloabl outline agreement distribution. As long as the transfer is in process it is called periodically within report CLEAN_REQ_REQ_UP if the distribution status is "error" or "ok" the correct distribution status is set for the global outline agreement. As input parameters the function receives:
- the number of the global outline agreement in EBP (in field IV_BE_CONTRACT_NUMBER)
- a language field for the language the error message texts are provided
- the logical system id of the target system
- the partner id of the purchase organisation the global outline agreement is created for
The function expects as a result in field EV_CTR_CREATION one of the status values for the disrtibution of the global outline agreement itself:
- O for Distribution successful
- E for error in distribution
- P or SPACE for distribution still in process
The function expects as a result in field EV_CND_CREATION one of the status values for the disrtibution of the condition and pricing data of the global outline agreement:
- O for Distribution successful
- E for error in distribution
- P or SPACE for distribution still in process
In case of errors the error messages should be stored in table ET_CTR_DISTR_MESSAGES. These messages are copied to the contract disrtibution log. Please consider that the language parameter is specifing the message text language.
Parameter ET_CTR_MM_ITEM_MAP has to be filled with mapping information for the distributed items. Within the R/3 distribution we structure service items to service packages. We recommend not to use this within the distribution to legacy systems. Due to this reason you can leave the last three fields always blank (BE_PACKNO, BE_SUB_PACKNO, BE_INTROW). The first three fields have to be filled with the logical system id of the source system, with the global outline agreement number and the number of the item. The fields BE_OBJECT_ID and BE_NUMBER_INT have to contain the corresponding contract number in the legacy system as well as the corresponding item number. These corresponding numbers are considered within the call of idoc document. This means the call of idoc document can contain the numbers from the legacy system.
Further information
Please have additionally a look to note 646903 for latest information.
Parameters
ET_CONTROL_RECORDET_CTR_DISTR_MESSAGES
ET_CTR_MM_ITEM_MAP
ET_MESSAGES
EV_CND_CREATION
EV_CTR_CREATION
IV_BE_CONTRACT_NUMBER
IV_LANGUAGE
IV_LOGICAL_SYSTEM
IV_PORG_PARTNER_ID
Exceptions
Function Group
BBP_BD_DRIVER_NOR3_PART2PERFORM Short Reference TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 3202 Date: 20240523 Time: 134424 sap01-206 ( 64 ms )
