Ansicht
Dokumentation

Business Add-Ins (BAdIs) for Collaborative Management of Delivery Schedules (New) ( RELNAPO_401_PPS_CDS_BADI )

Addresses (Business Address Services)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Short text

Business Add-Ins (BAdIs) for Collaborative Management of Delivery Schedules (New)

Use

As of SAP APO 4.0 you can use the following BAdIs:

• /SAPAPO/CMDS_STATDET BAdI: Determine Confirmation Status,
  to implement your own confirmation status determination process.
  See release notes More Flexible Determination of the Confirmation Status

• /SAPAPO/COMPSCHEDLIN BAdI: Compare Two Time Series,
  to enhance the standard comparison of two time series by adding time intervals that you define yourself (for example, weekly or monthly intervals) for variance calculation.

• /SAPAPO/CMDS_CONFOUT BAdI: Generate IDoc for the Confirmation,
  to change confirmation data before it is sent as an IDoc.

• /SAPAPO/CMDS_SD_CONF BAdI: Generate Confirmation,
  to change confirmation data, add to it or to control the way confirmations are sent.

• /SAPAPO/CMDS_RES_CDQ BAdI:Control the Fiscal Year Change,
  to define under what circumstances a fiscal year change is necessary and to check whether a fiscal year change is necessary, for sales scheduling agreements for which you have defined that the change should be carried out manually.

• /SAPAPO/CMDS_SL_DATE BAdI: Edit User-defined Period Formats,
  to define and use your own periods (for example, industry months) for sales scheduling agreement schedule lines.
  
  

As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) with Plug-In PI 2002.1 (2002_1_470) you can use the following Business Add-Ins (BAdIs):

For sales scheduling agreement items that are to be sent by APO Core Interface (CIF) (SAP R/3 -> SAP APO):

• CIF_SDLSE_001 BAdI Transfer Sales Scheduling Agreement Items (CIF Outbound),
  to change the data of selected sales scheduling agreements.
  You can also store the customer-specific information in an additional structure.

• CIF_SDLSE_002 BAdI Filter Object Selection for SSA Items (CIF Outbound),
  to select materials and plants again using additional selection criteria.

If you have an SAP R/3 system with Release DI 4.6C2 then the following Customer Exits are available instead of the BAdIs:

• EXIT_SAPLSDSE_001 (corresponds to the BAdI CIF_SDLSE_001)

• EXIT_SAPLSDSE_002 (corresponds to the BAdI CIF_SDLSE_002)

For confirmations that are to be transferred by CIF (SAP APO -> SAP R/3):

• BADI_SCOCONF BAdI Process customer-specific structures (CIF Inbound),

to add to or change customer-specific data or data for confirmations that is transferred via CIF from the SAP APO system to the linked SAP R/3 system.
(The quantities confirmed in the SAP APO system are displayed as schedule lines in the JIT or forecast delivery schedule in the sales scheduling agreement in the SAP-R/3-System.)

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

ABAP Short Reference   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4604 Date: 20240427 Time: 003430     sap01-206 ( 59 ms )