Kontakt

Ansicht
Dokumentation

SAPAPO/CMDS_STATDET - BAdI: Determine Confirmation Status

SAPAPO/CMDS_STATDET - BAdI: Determine Confirmation Status

BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used in the component Production Planning and Detailed Scheduling SCM-APO-PPS.

You can use this BAdI to implement your own process for determining confirmation status.

When you create confirmations in the product view, product planning table or in backorder processing the current status of a sales scheduling agreement item is determined according to the setting in the confirmation profile on a to-the-second, -minute, -hour or -day basis.

Either you or the system can confirm the requested quantities, either partially or fully.

You can use this BAdI to save your own determination if, for example, you want to use an up-to-the-week check or a different determination type for different customers.

This BAdI is called up in the function module /SAPAPO/CMDS_CALCULATE_STATUS.

Before you can assign your own determination type for the confirmation status in the confirmation profile, you must create or define a new determination type:

  1. In the table /SAPAPO/DETSTATB for the calling application (APPLICATION_KEY) define a new determination type.
    In the field DETSTAT_BASE enter any two digit abbreviation not used by the application.
    The key of the calling application must be 1 (Confirmation Status Determination). You can also enter additional determination types.
  2. In the text table /SAPAPO/DETSTATT enter a language-specific description for this determination type if necessary.
  3. In the confirmation profile, choose the newly created determinationtype. (Execute Function)
  4. If you use the BAdI then you must implement the CALCULATE_STATUS for every additional determination type.

This BAdI is not active in the standard system.
This BAdI is filter-dependent. For each combination of application and determination type you must create an implementation.

After you have called the IMG activity, proceed as follows:

  1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
  1. In the corresponding field, enter a short text for implementation .
  2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
  3. Choose the tab Interface.
The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
  1. Save your entries and assign a package.
  2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
  3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
  4. Save and activate your coding, and navigate back to the screen Change Implementation.
  5. Save on the screen Change Implementation.
Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
  1. Choose Activate.
When the application program is executed, the coding you have created will be run.

Method
Determine Confirmation Status






Vendor Master (General Section)   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 4737 Date: 20240523 Time: 193818     sap01-206 ( 59 ms )