SAP ABAP IMG Activity APOCIF_SCOCONF (Process Customer-Specific Structures)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ CA (Application Component) Cross-Application Components
     ⤷ CFD (Package) IMG for APO Core Interface
IMG Activity
ID APOCIF_SCOCONF Process Customer-Specific Structures  
Transaction Code S_AXA_22000013   (empty) 
Created on 20020911    
Customizing Attributes APOCIF_SCOCONF   Process Customer-Specific Structures 
Customizing Activity APOCIF_SCOCONF   Process Customer-Specific Structures 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_SCOCONF    

Use

This Business Add-In (BAdI) is used in the component Sales Scheduling Agreement Processing (SCM-APO-PPS-CDS).

You use this BAdI to enhance or change customer-specific data for confirmations (such as scheduling agreement item, scheduling agreement release header, schedule lines, texts, and partners) that are transferred from SAP APO to the connected ERP system using the APO Core Interface (CIF).

Note
The quantities confirmed in SAP APO are displayed as schedule lines in the JIT/forecast delivery schedule in the sales scheduling agreement in the ERP system.

The BAdI is called in function module CIF_SCOCONF_INBOUND.

The data is formatted here for further processing using the business application programming interface (BAPI) BAPI_SALES_DEL_SCHEDULE_CREATE. Processing occurs on a document by document basis.

You can use this BAdI to enhance or change data:

  • Before the confirmations transferred are updated in the BAPI
  • After the confirmations transferred are updated in the BAPI.

Implementing this BAdI does not have an effect on other IMG activities.

Requirements

You can use the BAdI /SAPAPO/SMOY_PUB_APP APO Publication BAdI for Populating Enhancement Structures in APO and its method APPENDCONFSCHEDAGRMT Enhance Confirmation for Scheduling Agreement in SAP APO to transfer customer-specific data from SAP APO to the ERP system.

You have to create identical or compatible structures in both systems.

The BAdI is called in function module /SAPAPO/DM_CP_PROCESS.

Standard settings

The BAdI is not active in the standard delivery.

The BAdI can be used on multiple occasions.

Activities

After you call the IMG activity, you first see a dialog screen in which you enter a name for the implementation.

If implementations have already been created for this BAdI, you see a dialog window in which the existing implementations are displayed. Choose Create in this dialog window and proceed as follows:

  1. In the Implementation field, enter a name for the BAdI implementation and choose Create.

    The entry screen for creating BAdI Implementations is displayed.

  2. In the entry screen, enter a short text for the implementation in the Short Text for Implementation field.
  3. Choose the Interface tab page.

    The Name of the Implementing Class is automatically filled on this tab page. This is because the system automatically assigns a class name on the basis of the name of your implementation.

  4. Save your entries and make the assignment to a package.
  5. Position the cursor on a method and double-click to navigate to method processing.
  6. Enter the coding you require for the implementation between the instructions method <Interface-Name>~<Method Name> and endmethod.
  7. Save and activate your coding and navigate to the Change Implementation screen.
  8. Save on the Change Implementation screen.

    Note: It is also possible to create an implementation for a BAdI and then activate it at a later point in time. If you want to do this, you should stop now (before activation).

  9. Choose Activate.

    When the application program is executed, the coding you added to the method runs.

See also:

Documentation for method Processing of Customer-Specific Data Before Posting for confirmations/sales scheduling agreement releases (SCOCONF_BEFORE_POSTING)

Documentation for method Processing of Customer-Specific Data After Posting for confirmations/sales scheduling agreement releases (SCOCONF_AFTER_POSTING)

Documentation for interface IF_EX_BADI_SCOCONF

Example

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20020916 
SAP Release Created in 2002_1_470