IDoc Inbound Processing

EDI Inbound: Import and Edit Delivery Schedule Data

You can use the BAdI /SAPAPO/EDI_SCHED_AG to change or add to the data of the selected scheduling agreements after IDoc inbound processing has taken place. For example, you can change or fill the user fields USR01 to 05 or change the status of the scheduling agreement.

Edit IDoc Data

You can use the BAdI /SAPAPO/MOD_EDI_DATA, to change the IDoc data before IDoc Inbound Processing or, for example, add additional values.

Inbound Processing of Forecast/Planning Delivery Schedules with Test Run Indicator

You can use the BAdI /SAPAPO/MSG_TYP_1 to control that an IDoc from a sold-to party, for which you have defined test run in Customizing for the SAP APO is processed in the APO system anyway. ( Supply Chain Planning → Delivery Schedule Processing for Sales Scheduling Agreement → Set IDoc Processing of Scheduling Agreement Releases )

Inbound Processing of Operative Delivery Schedules with Test Run Indicator

You can use the BAdI /SAPAPO/MSG_TYP_2 to control that an IDoc from a sold-to party, for which you have defined test run in Customizing for the SAP APO is processed in the APO system anyway.

A new sold-to party should only be able to send IDocs from a certain date. Therefore, you have determined the test run for this sold-to party. Using these BAdIs you can control that these IDocs are processed in the APO system anyway.

Activate Enhanced Odette Processing Logic

You can use the BAdI /SAPAPO/ODETTE_FLAG to enhance the previous Odette logic so that, if it is necessary to create additional schedule lines on the basis of planned dates and planned cumulative quantity, then a date that lies in the past is assigned to these schedule lines. This means that the schedule lines to be created are created for this date on which a schedule line already exists.

In comparison, in ‘traditional’ Odette logic, the release date transmitted in the IDoc has been used for the creation of schedule lines.

See also Inbound Processing of Scheduling Agreement Releases

Delivery Schedule Split and Due Delivery Schedule

Edit User-Defined Period Formats

You can use the BAdI /SAPAPO/CMDS_SL_DATE to define your own periods (for example, industry months) for sales scheduling agreement schedule lines.

(See Sales Scheduling Agreement with Industry Month Schedule Lines )

Modify Delivery Schedules

You can use the /SAPAPO/CMDS_DS_MOD to influence the way the system splits forecast/planning delivery schedules (for example by specifying a calendar for the delivery schedule split) and how the system generates due delivery schedules.

See Delivery Schedule Split and Due Delivery Schedule

Transportation lane

Prioritization of Sources of Supply and Means of Transport

You use the method SOS_COST_DEST_SORT of the BAdI /SAPAPO/SOS_COST to influence the way in which the system determines the most suitable means of transport for sales scheduling agreements.

IDoc Outbound Processing (Confirmations)

Generate IDoc for Confirmation

You can use the BAdI /SAPAPO/CMDS_CONFOUT to influence the way confirmations are sent to partners, for which you have defined the medium XML in the sales scheduling agreement master data.

Generate Confirmation

You can use the BAdI /SAPAPO/CMDS_SD_CONF to change confirmations and add your own data before confirmations are generated, saved or sent to the customer.

You can also change all the data for transferred items from sales scheduling agreements using the enhancement APOCF060 you can. You can also assign control profiles and confirmation profiles to the scheduling agreement item.

See also Confirmations

Sales Scheduling Agreement Release

Compare Two Time Series

You can use the BAdI /SAPAPO/COMPSCHEDLIN to enhance the standard comparison of two time series by adding further time intervals that you define yourself (for example, weekly or monthly intervals) for variance calculation.

This means that you can, for example, define your own intervals and check whether schedule lines (from confirmations and due delivery schedules) lie within the interval you have defined.

Confirmation

Enhance the Confirmation for the Sales Scheduling Agreement

You can use the method APPENDCONFSCHEDAGRMT Enhance Confirmation for Sales Scheduling Agreement of BAdI /SAPAPO/SMOY_PUB_APP to enhance customer-specific data or data about confirmations (for example, scheduling agreement item, release header, release data, schedule lines, texts and partner), which is send from the SAP APO system to the linked SAP R/3 system via the APO Core Interface (CIF).

Confirmation Status Determination

You can use the BAdI /SAPAPO/CMDS_STATDET to implement your own confirmation status determination process. When you manually create confirmations in the product view, product planning table or in interactive backorder processing, the Current Status of a sales scheduling agreement item is determined on a to-the-second, to-the-minute, to-the-hour or to-the-day basis, depending on the setting you have made in the confirmation profile.

Under/Overconfirmation Alerts

You can use the BAdI /SAPAPO/AM_CNF_ALERT BAdI: Under/Overconfirmation Alerts to influence the way in which the system generates Under- and Overconfirmation Alerts.

See Under- and Overconfirmation Alerts

Fiscal Year Change

Control the Fiscal Year Change

You can use the BAdI /SAPAPO/CMDS_RES_CDQ to check whether (or on what criteria) a fiscal year change is necessary for sales scheduling agreements with manual fiscal year change.

See Manage Fiscal Year

Compare/Reconcile Function

You can use the BAdI /SAPAPO/CIF_DELTA3 to exclude certain fields from the comparison.

See Compare Sales Scheduling Agreements

Activities

These BAdIs can be found in Customizing for Supply Chain Planning under Delivery Schedule Processing for Sales Schedule Agreement → Business Add-Ins (BAdIs) for Sales Scheduling Agreement Processing .

You can also use the Customer Exit APOBO010 to exclude sales scheduling agreement items with the current status Admissibility not ok from backorder processing, for example.