Ansicht
Dokumentation

EXIT_/SAPAPO/SAPLBOP_052 - Obsolete - ATP, BOP: Results Tranfer of Backorder Processing

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Functionality

In backorder processing, the user exit is called after the availability check. The system has already converted the result into nested tables. After this user exit, the result is copied into backorder processing.

The result of the availability check is transferred to the function module in three tables.

You can change the result of the availability check. When you make changes, you must keep the conditions for the availability check the same in order to prevent extra confirmations. These extra confirmations can cause delivery delays after the document update.

Example

Notes

• Alternatively you can use the function moduleEXIT_/SAPAPO/SAPLBOP_051. The results in the tables are transferred to this function module. This function module is delivered by the ATP controller. The interim results of the separate basic methods are available here.

• If you use parallelizing backorder processing, the system calls this function module in the main process only.

• For a better system performance, the system reuses the ATP scheduling results, and transfers them to the OLTP system. However, if you change the confirmation, you must also delete the corresponding ATP scheduling results, as the system reevaluates the scheduling for the changed items during the update. If you do not delete the scheduling results, the scheduling results transferred to the OLTP system will not correspond to the confirmation situation.

Further information

Enhancement APOBO050

Parameters

CT_BOPCNF
CT_BOPREQ
IT_BOPREQGRP

Exceptions

Function Group

XBOPUSER

RFUMSV00 - Advance Return for Tax on Sales/Purchases   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 2247 Date: 20240523 Time: 055027     sap01-206 ( 54 ms )