Value Mapping: Use of Global Code Lists
You use this process to implement value mapping using global code lists. We recommend you use a global code list for inbound and outbound mapping to target systems if you are using enterprise service-oriented architecture (eSOA) communications or if target systems support value mapping.
The following steps describe value mapping for a selected value when you use a global code list. The selected value is the Company form of address.
Outbound Processing on the MDG Hub
When the MDG hub sends a message that contains the Company form of address, the system converts the internal code defined for the MDG hub (0004) to the code defined for the message (0003). See graphic below.

Use of a Global List: – MDG Hub Configuration
The value mapping configuration information shown in the graphic is summarized in the table below.
Values in the Message |
Internal Values (MDG Hub) |
|---|---|
|
|
Inbound Processing on the Target System
When the target system receives a message that contains the Company form of address, the system converts the internal code defined for the MDG hub (0003) to the code defined for the message (0003). In this case, the values are the same. See graphic below.

Use of a Global List: – Target System Configuration
The value mapping configuration information shown in the graphic is summarized in the table below.
Values in the Message |
Internal Values (Target System) |
|---|---|
|
|