SAP ABAP IMG Activity VALMAP_005 (Overall Information)
Hierarchy
☛ SAP_BS_FND (Software Component) SAP Business Suite Foundation
   ⤷ CA-MDG-VM (Application Component) Value Mapping
     ⤷ MDG_BS_VALUE_MAPPING_UI (Package) MDG: Value Mapping UI
IMG Activity
ID VALMAP_005 Overall Information  
Transaction Code S_BTD_53000206   (empty) 
Created on 20100226    
Customizing Attributes VALMAP_005   Overall Information for Value mapping 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name VALMAP_005    

Use

You can use value mapping to map the system-internal code values that represent possible entries for a customizing element to the code values of a named external list. The external list can be a global code list or a system-specific code list. The table below shows a use case in which the form of address customizing element uses one set of codes in the Master Data Governance (MDG) hub and a different set of codes in an external code list.

Form of Address            Code Value on MDG Hub                Code Value in External Code List

Mr.            0001                0004

Ms.            0002                0003

Company            0003                0002

Mr. and Ms.            0004                0001

Value mapping is an alternative to synchronizing the customizing entries and their corresponding master data across all systems. We recommend you use value mapping if such synchronization is impractical or impossible.

The approach you take when mapping values of customizing entries depends on whether you implement a global code list or a system-specific code list.

Use of Global Code Lists

We recommend you implement a global code list for inbound and outbound mappings to target systems, if this is possible. For a global code list to work, you must use service communications and the target systems that access the global code list must support value mapping. SAP target systems in releases EHP4 and below and non-SAP target systems only support value mapping with the help of Process Integration (PI) tools or other middleware tools.

Using global code lists ensures consistent mapping between the MDG hub and target systems. It also reduces configuration effort by eliminating the need to create extra mapping configurations for client-to-client communication.

Use of System-Specific Code Lists

You must use a separate code list for a target system if you are using Application Link Enabling (ALE) communications or if the target system is not able to implement value mapping. The minor advantage of this approach is that there is no need to configure value mapping in the target system. The disadvantage is that a separate configuration is required for each target system on the Master Data Governance hub. This greatly increases the overall configuration effort.

Description of Customizing Activities

The following Customizing activities are available:

Requirements

  • You understand the meaning of the code values in the various systems and have agreed mappings with business users.
  • You have determined when to use a global code list by identifying whether target systems support value mapping and whether you are using service communications.
  • SAP elements for which value mapping is supported are part of the standard system supplied.
  • For custom fields, you have defined the elements for which a value mapping is to be carried out. These can be proxy elements or pure ABAP Dictionary objects.
  • You have specified whether the value mapping is to be carried out for client-dependent or client-independent value tables.

Standard settings

Activities

Implementing Value Mapping: Global Code List

The global code list can come from an approved standards agency such as the International Standards Organization (ISO) or from the system landscape.

After setting up the global code list, you configure value mapping to and from the global code list in each system.

  1. Open the Maintain Value Mapping activity. To start assigning code lists to a Customizing element, click the Navigation button beside the Customizing element.
  2. In the Assign Code Lists view, specify the default code list defined in the MDG hub.

    The naming conventions for a global code list from an approved standards agency are as follows:

    • List Agency ID is specified by the United Nations
    • List ID is the official ID supplied from the standards agency.
      • For example ISO 3166-1 is the official list id for country codes.
    • List Version ID is the official ID supplied from the standards agency.

      The naming conventions for a global code list from the system landscape are as follows:

    • List Agency ID is MDG_GLOBAL.
    • List ID matches the element name defined in MDGV_ELEMENT.
      • For example, MDG_FND_PARTY_ROLE_CODE.
    • List Version ID starts at 01.
      • You can add versions as needed.
  3. In the Assign Code Lists view, select the Default for Outbound Mapping checkbox. The global list is always the default.
  4. For the code list you have assigned, open the Map Values view. Map the values, for example map "R" for red to "3000" for flame red.

Implementing Value Mapping: System-Specific Code Lists

  1. In the Assign Code Lists to Elements and Systems activity, define a separate system-specific code list for the data element in the MDG hub configuration and specify the system.

    The naming conventions for a system-specific code list are as follows:

    • List Agency ID uses the syntax for a business system: <System>_<Client>.
      •     For example, QV5_410
    • List ID matches the element name defined in MDGV_ELEMENT.
      • For example, MDG_FND_PARTY_ROLE_CODE.
    • List Version ID starts at 01.
      • You can add versions as needed.
  2. Open the Maintain Value Mapping activity. To start assigning code lists to a Customizing element, click the Navigation button beside the Customizing element.
  3. In the Assign Code Lists view:
  4. For the code list you have assigned, open the Map Values view. Map the values, for example map "R" for red to "01" for red.

Example

The example below shows how to create a system-specific list for the data element MDG_FND_FORM_OF_ADDRESSS_CODE_C which refers to a form of address. The target system is Q35 client 004.

  1. In the Assign Code Lists to Elements and Systems activity, define a separate system-specific code list for the MDG form of address data element in the MDG hub configuration and specify the target system.
  2. Open the Maintain Value Mapping activity. To start assigning code lists, click the Navigation button.
  3. In the Assign Code Lists view:
  4. For the code list you have assigned, open the Map Values view and map the values.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
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 VALMAP_005 0 BTD0000051 Application Framework 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20101004 
SAP Release Created in 702