Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata


ATP BAdI /SAPAPO/PDEM_ATP_CHECK_IF is used only for OEMMI scenario  


The PDEM ATP BAdI was introduced with note 1666495 for the OEMMI scenario.
It was not meant to be used for a regular DTP Upload from CRM or ERP SD, it is only enabled for a B2B scenario.

Calling BADI for OEMMI Scenario

ATP BAdI /SAPAPO/PDEM_ATP_CHECK_IF is  not useful for a regular DTP Upload from CRM or ERP SD. 

METHOD atp_location_fill.
* Only deal with CRM or B2B data
CASE mv_infosource_type.
* WHEN mc_crm_salo.
* lv_r3obj = /sapapo/cl_c=>customer_order.
WHEN mc_b2b_sd. <-- B2B Scenario
lv_r3obj = /sapapo/cl_c=>customer_order.
RETURN. <-- Badi is not called for CRM or ERP SD
CALL BADI mo_pdem_atp_badi->atp_check_if_modify


The BADI documentation (SE18 - Enter BADI Name - Documentation) tells that the BADI is in use for
-if an active supersession chain exists during historical data capture
-for the planning services for the realignment of demand history


There was an attempt to use this BADI for the general DTP upload with note 1822983 but this was reverted back with note 1847654.
The implementation will not be executed for data that comes from ERP SD or CRM.

It is expected that the ATP logic is executed already in these source systems.
Only alternative I see is that you do a custom enhancement or place your ATP determination logic in your Start Routine of the CPD Data Upload.

Related Content

Related Documents

Example ATP BAdI Implementation for Realignment Services

Related SAP Notes/KBAs

SAP Notes: 

1833373   Implementation is missing for /SAPAPO/CL_EX_PDEM_ATP_CHECK

2582165   Trigger SPP_NON_ST_DEMAND not set automatically for locations determined in GATP BAdI



Use this structure to help you compose your contributions for WIKI and at the same time will ensure spelling and grammar.

  • No labels