SAP ABAP IMG Activity ME_PROCESS_OUT_CUST (BAdI: Processing Options for Contract and Scheduling Agreement BAPIs)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ MM-PUR-OA (Application Component) Vendor Outline Agreements
     ⤷ MMPUR_OUTLINE_AGREEMENT (Package) Purchasing: Outline Agreements
IMG Activity
ID ME_PROCESS_OUT_CUST BAdI: Processing Options for Contract and Scheduling Agreement BAPIs  
Transaction Code S_XC0_18000013   (empty) 
Created on 20050717    
Customizing Attributes ME_PROCESS_OUT_CUST   BAdI: Processing of Outline Agreement: Customer 
Customizing Activity ME_PROCESS_OUT_CUST   BAdI: Processing of Outline Agreement: Customer 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ME_PROCESS_OUT_CUST    

Use

This Business Add-In (BAdI) is used in the component Vendor Outline Agreements (MM-PUR-OA).

The framework program for this BAdI is SAPLMEOUT.

With this BAdI, you can enhance the busines logic of the following BAPIs on an individual basis:

  • BAPIs to create or change a scheduling agreement (BAPI_SAG_CREATE and BAPI_SAG_CHANGE)
  • BAPIs to create or change a contract (BAPI_CONTRACT_CREATE and BAPI_CONTRACT_CHANGE )

Typical applications for this BAdI include:

  • Processing of own objects
  • Processing of additional data on standard objects
  • Implementation of additional validations and derivations
  • Data changes in standard fields
    Note
    Ensure that data integrity is guaranteed.
  • Change in field selection (also relevant to BAPIs)

With its methods, the BAdI covers the entire transaction cycle for the outline agreements, so that you can intervene with an implementation of your own at each stage of the processing. For more information, refer to the interface documentation.

Requirements

You need advanced knowledge of ABAP-OO to implement this BAdI.

Standard settings

  • In the standard system, the BAdI is not active.
  • The BAdI is not filter-independent and cannot be used multiple times.

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.

Example

You will find an example implementation under Goto -> Sample Code.

Further notes

See also:

Methods

Initializations

Opening of an Outline Agreement

Processing of Header Data

Processing of Item Data

Processing of Delivery Schedule Line Data

Processing of Account Assignment Data

Field Selection Reference Key Document Header

Field Selection Reference Key Document Item

Special Field Selection Header

Special Field Selection Item

Closing Check

Post

Closing Processing

Interface
IF_EX_ME_PROCESS_OUT_CUST

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG ME_PROCESS_OUT_CUST 0 HLA0006035 Vendor Outline Agreements 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20090305 
SAP Release Created in 600