cancel
Showing results for 
Search instead for 
Did you mean: 

BADI /SAPAPO/ATP_CHKHOR not called from CO09 or /SAPAPO/RRP3 ATP tab

SAPSupport
Employee
Employee
0 Kudos


Dear SAP support,

We have implemented BADI /SAPAPO/ATP_CHKHOR.
This BADI allows to adjust the end timestamp of the checking horizon.

Although the BADI is correctly working for the online ATP check and backorder processing, we observe that it is not called from transaction CO09 - which is the same as the ATP tab in transaction /SAPAPO/RRP3. In that transaction, the ATP checking horizon is still the "standard" one.

In debugging, we observe that the checking horizon is calculated using include /SAPAPO/LATP4FC3, form CHECK_DETAILS_GET, by doing the following call : CALL METHOD p_logpr->get_end_of_check_horizon

In this method, the BADI is not called, which is incorrect.
The situation now is misleading, since an actual ATP check will provide a different outcome.

Thank you in advance for having a look at this issue.

Kind regards,


------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

Accepted Solutions (1)

Accepted Solutions (1)

SAPSupport
Employee
Employee
0 Kudos

The badi method you selected is very technical and should be used only for adjustments of the check horizon linked to the ATP check itself. It was actually designed to overcome a specific requirement in case a special confirmation behaviour was requested.

If you want a more global adjustment of the check horizon you should check note number 2421298 which introduces another badi with the same method name. Since it is located in a more central place the changes should be exposed to the HORDAT as requested.

best regards,

SAP Support

Answers (0)