Ansicht
Dokumentation

EXIT_/SAPAPO/SAPLBOP_040 - Obsolete - ATP, BOP: Scope of Check for Backorder Processing

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Functionality

The user exit is called in backorder processing before the availability check is called.

The requirements to be checked and the correction quantities of the separate basic methods are transferred to the function module.

Depending on the settings for backorder processing, the requirements to be checked are either the original requirement (requirement check) or the current confirmation of the document (confirmation check). Scheduling has already been performed (according to the settings for the check parameters).
The requirements are transferred into four tables. The contents of these tables are linked to each other by indexes.
The requirements to be checked can be changed, for example, if you want to implement a fair share logic. Changing the requirements has no effect on the quantities originally required in the documents. The change only limits the maximum quantity you can allocate to a document.

The correction quantities are determined for each basic method. By reducing the correction quantities you can prevent the total quantity being divided between the documents to be checked.
You must not change the adjustment entries for planning.

Example

Notes

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

Further information

Enhancement APOBO040

Parameters

CT_CORR_ALL
CT_CORR_CMP
CT_CORR_PAC
CT_CORR_PLN
CT_HOWTOCHK
CT_INTREF
CT_ITMREF
CT_REQ
CT_REQGRP
CT_REQITM
CT_RES
CT_SUBGRP

Exceptions

Function Group

XBOPUSER

General Data in Customer Master   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 2483 Date: 20240604 Time: 022147     sap01-206 ( 25 ms )