Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-AB (Application Component) Agency Business (Global Trade)⤷
WZRE_XI_PROXY (Package) Agency Business: SOA proxy implementations
IMG Activity
| ID | WLF_SOA_SMT_SC_0008 | BAdI for Mapping of Code Values |
| Transaction Code | S_EBS_44000418 | (empty) |
| Created on | 20110308 | |
| Customizing Attributes | WLF_SOA_SMT_SC_0008 | BAdI for Mapping of Code Values |
| Customizing Activity | WLF_SOA_SMT_SC_0008 | BAdI for Mapping of Code Values |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | WLF_SE_CODE_VALUE_MAPPING |
Use
This Business Add-In (BAdI) is used in the Agency Business component (LO-AB). TThe BAdI is called in field and complex transformation for code value mappings, which allow proprietary code values exclusively or in addition to standard code values. The supplementary fields (ListID, ListVersionID and ListAgencyID) identify the code list from which the code is taken. The transformations and conversions are used in service operations for Agency Business documents.
The BAdI offers two different methods:
- GET_CODE_SUPPL_FIELDS: Provides the supplementary fields for a code GDT (Global Data Type)
- MAP_INBOUND: Provides the code value mapping for incoming messages.
For outgoing messages, the BAdI offers the method GET_CODE_SUPPL_FIELDS to provide the supplementary fields used in the sender system for a concrete code GDT.
For incoming messages, the method GET_CODE_SUPPL_FIELDS is used to compare the supplementary fields used in the receivers systems with those provided by the sender. If they are identical, the code value from the incoming message is accepted, otherwise a more complex code mapping has to be installed, for which the second method MAP_INBOUND is called.
Remark: Unless the supplementary fields are provided by the sender, the receiver side assumes that the corresponding code value in the incoming message belongs to the code list used on the receiver side. The incoming code value is accepted directly.
The constant CO_CODE_GDT_NAMES of the class CL_WLF_INVC_CONSTANTS contains the list of the code GDTs for which this BAdI can be used within Agency Business.
Standard settings
The BAdI defines a filter value that allow you to control at runtime the execution of just the relevant value mapping for a concrete code. The filter value is the name of the code GDT (Global Data Type).
The Business Add-In is multiple-use.
No standard implementation is delivered with this BAdI.
Activities
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
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 | 20110308 |
| SAP Release Created in | 606 |
