SAP ABAP IMG Activity WRF_PRC_POHF_BADI_06 (BAdI: Conversion of Customer Data)
Hierarchy
☛ EA-RETAIL (Software Component) SAP Enterprise Extension Retail
   ⤷ MM-PUR (Application Component) Purchasing
     ⤷ WRF_PRC_POHF_DDIC (Package) Seasonal Procurement: DDIC Objects PO Processing
IMG Activity
ID WRF_PRC_POHF_BADI_06 BAdI: Conversion of Customer Data  
Transaction Code S_P7R_06000003   (empty) 
Created on 20051206    
Customizing Attributes WRF_PRC_BADI   BAdI Enhancements for Seasonal Procurement 
Customizing Activity WRF_PRC_POHF_BADI_06   BAdI: Conversion of Customer Data 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name WRF_POHF_X_ENHANCEMENT_E    

Use

Mapping of customer-specific data to BAPI structures, in order to process the data.

This BAdI is required for using customer enhancement SAPL2012. The BAdI enables you to enhance the purchase order BAPIs (for header, item, and account assignment data) as follows:

  • Adjustment of existing SAP database tables
    • Attaching customer-specific fields to SAP tables
    • Incorporating existing database fields
  • Incorporation of additional customer-specific database tables

The following BAPI table enhancements are available in the seasonal procurement:

  • BAPI_TE_MEPOHEADER
  • BAPI_TE_MEPOHEADERX
  • BAPI_TE_MEPOITEM
  • BAPI_TE_MEPOITEMX

Requirements

Standard settings

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

See example implementation of inbound and outbound methods in the example implementation class CL_EXM_IM_WRF_POHF_X_ENH_E.

See also

Methods

Inbound

Outbound

Interface

IF_EX_WRF_POHF_X_ENHANCEMENT_E

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
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  20051206 
SAP Release Created in