SAP ABAP IMG Activity SIMG_ARC_ORDER (BAdI: Archiving of Additional Data)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ CIIC (Package) CIM integration: Customizing
IMG Activity
ID SIMG_ARC_ORDER BAdI: Archiving of Additional Data  
Transaction Code S_PL0_86000038   (empty) 
Created on 20040211    
Customizing Attributes SIMG_ARC_ORDER   BAdI: Archiving of Additional Data for Process Orders 
Customizing Activity SIMG_ARC_ORDER   Archiving of Additional Data for Process Orders 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ARC_P_ORDER_WRITE    

Use

The Business Add-In (BAdI) ARC_P_ORDER_WRITE is used in the component Order ClosingPP-SFC-CPL (Production Orders) and PP-PI-POR-OCL (Process Orders).

You can use the BAdI to archive additional data when production or process orders are archived. You can also delete additional archived data from the database.

The BAdI is called during the archiving run of the following objects of the archiving class P_ORDER:

  • PP_ORDER: Production orders
  • PR_ORDER: Process orders

Requirements

Standard settings

The BAdI is not active in the standard system.

The BAdI can be reused. All active implementations are called and executed.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Further notes

No system messages can be sent in the method.

The statement COMMIT WORK must not be executed in the method because this leads to inconsistencies in the database.

See also:

Methods

Write Additional Data to the Archive

Delete Additional Data from the database

Business Attributes
ASAP Roadmap ID 255   Create Interfaces 
Mandatory / Optional 3   Nonrequired 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  20040212 
SAP Release Created in 500