SAP ABAP IMG Activity BADI_CPE_MAP_BAPI (BAdI: Mapping between BAPIs and CPE Objects)
Hierarchy
☛ PI_BASIS (Software Component) Basis Plug-In
   ⤷ CA-GTF-CPE (Application Component) Commodity Pricing Engine
     ⤷ CPE_DOC (Package) Commodity Pricing: Document Data
IMG Activity
ID BADI_CPE_MAP_BAPI BAdI: Mapping between BAPIs and CPE Objects  
Transaction Code S_BYA_47000047   (empty) 
Created on 20060209    
Customizing Attributes BADI_CPE_MAP_BAPI   BAdI: Mapping between BAPIs and CPE Objects 
Customizing Activity BADI_CPE_MAP_BAPI   BAdI: Mapping between BAPIs and CPE Objects 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BADI_CPE_MAP_BAPI    

Use

This Business Add-In (BAdI) is used in the Commodity Pricing Engine (CA-GTF-CPE) component.

This BAdI enables you to map customer-specific fields in an external BAPI format to internal CPE objects, such as formula records or price quotations. The mapping logic is performed during the outbound and the inbound processing of the data exchange.

Requirements

You have activated the CPE and you use customer-specific fields in price quotations or CPE formulas.

Standard settings

In the standard system, the Business Add-In is not activated. In this state, all customer-specific fields in CPE formulas or price quotations are not considered during data exchange .

The Business Add-In is not reusable.

The Business Add-In is not filter-dependent.

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 also

Methods

PRICEQUOT_FROM_BAPI: Map customer-specific fields of price quotations from BAPI

PRICEQUOT_TO_BAPI: Map customer-specific fields of price quotations into BAPI        

FORMDOC_FROM_BAPI: Map customer-specific fields of formula results from BAPI

FORMINPUT_FROM_BAPI: Map customer-specific fields of formula inputs from BAPI

TERMGRPOUT_FROM_BAPI: Map customer-specific fields of term group results from BAPI

TERMOUT_FROM_BAPI: Map customer-specific fields of term results from BAPI

TERMINPUT_FROM_BAPI: Map customer-specific fields of term inputs from BAPI

FORMDOC_TO_BAPI: Map customer-specific fields of formula results into BAPI

FORMINPUT_TO_BAPI: Map customer-specific fields of formula inputs into BAPI

TERMGRPOUT_TO_BAPI: Map customer-specific fields of term group results into BAPI

TERMOUT_TO_BAPI: Map customer-specific fields of term results into BAPI

TERMINPUT_TO_BAPI: Map customer-specific fields of term inputs into BAPI

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 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BADI_CPE_MAP_BAPI 0 BYA3000001 Commodity Pricing Engine 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20060209 
SAP Release Created in