If the Element Mapping tab is not available, it is an indication that you have not completed at least one level mapping in the Level Mapping process.
Once the Level Mapping process is complete, the source definition is presented on the left window and the target definition is presented on the right window. The source and target hierarchies defined in the Level Mapping tab are displayed in bold font. Use the Element Mapping tab to create the message map.
Select the source element and drag it to the target element. Pay special attention to any predefined node conditions (such as Conditional Node Mapping) to ensure that duplicate nodes are mapped to the correct target entities. The source element name and mapped icon will appear next to the target element name indicating the element is mapped.
To unmap a mapped element, select the mapped element on the target window and drag it back to the source element.
Do not map a lower level element to a higher level element. The lower level element values are not available until the header level elements are completely processed.
A higher level element can be mapped to a lower level element. However, you may need to manipulate the higher level element value to make it meaningful in the context of a detail level element.
For example, if the the header level element is invoice total and the line level element is invoice line total, the header invoice total must be distributed across the invoice lines based on the line quantity for it to be meaningful in the context of invoice lines.
One source element can be mapped to multiple target elements.
Review the source elements containing Conditional Node Mapping instructions. Map the source element to the target element associated with the condition.
For the outbound messages (where the source is the database and the target is a DTD) using the OAG standard, map the ECX_OAG_CONTROLAREA_TP_V view (formerly ECX_OAG_CONTROLAREA_V) columns to the DTD CNTROLAREA data type elements. This step is not required for inbound messages (where the source is a DTD and the target is the database) because the content of the DTD CNTROLAREA is not stored in the Oracle E-Business Suite.
Note: The ECX_OAG_CONTROLAREA_TP_V view is an upgraded version of the ECX_OAG_CONTROLAREA_V view. Oracle XML Gateway supports both versions of the database view. For a detailed description of the differences, see the Note presented earlier in this chapter.
The view column names are similar to the DTD CNTROLAREA data type element names, so this is one-to-one mapping. Add the following required Actions to complete the map:
Use the Convert to OAG DATETIME action to convert the Oracle date to the CNTROLAREA DATETIME element.
Use the Append Where Clause action to bind the transaction type and transaction subtype to the ECX_OAG_CONTROLAREA_V view. Or if you are using the ECX_OAG_CONTROLAREA_TP_V view, use the Append Where Clause to bind the transaction type, transaction subtype, party ID, party site ID, and party type to the view.
Note: The ECX_OAG_CONTROLAREA_TP_V view is an upgraded version of the ECX_OAG_CONTROLAREA_V view. Oracle XML Gateway supports both versions of the database view. For a detailed description of the differences, see the Note, presented earlier in this chapter.
Use the Define Transactions form to define the transaction and transaction subtype that represent the Oracle name for the message. Associated with the internal name for the message are the external type and subtype that represent the message name in the XML standard of choice.
For OAG, the external subtype corresponds to the BSR VERB and the external type corresponds to the BSR NOUN. The names entered on the Define Transactions form are stored in the database and accessed by the ECX_OAG_CONTROLAREA_TP_V view. The values are displayed in the Message Designer as default values for the BSR VERB and BSR NOUN elements.
Refer to the Define Transactions Form for the details and observe the recommended naming conventions.
Message Designer uses an icon group to help you determine the status of a map at a glance. The components of the icon group are as follows:
Mapped Element icon.
Action Defined icon.
Code Conversion Enabled icon.
The components will be displayed as on or off (grayed out) within the group icon to indicate if the element is mapped, has an action defined, and/or is enabled for code conversion.
As part of the element mapping process, Actions for data transformation and process control can be defined.
The following three sections are available for your reference. First time users should read all three sections. Experienced users should use the Map Action Editor section and reference the action type of interest.
At the completion of the element mapping process, use the File > Save (Transaction Map) menu option or the Save icon to save the map onto the file system. The name of the map (.xgm) file should be the same as the map name for easy reference. Follow the map naming conventions as follows:
Product mnemonic or user ID
Transaction subtype as entered in the Define Transactions form
XML standard and version used (such as OAG, Rosettanet, iFX)
Outbound or inbound message
Given a map name of:
AR_INVO_OAG70_OUT
the map file name is:
AR_INVO_OAG70_OUT.xgm
Use the File > Properties menu option to change the default directory or map name if necessary.
The transaction map and the associated DTDs are now ready to load into the XML Gateway repository. The message maps will be used by the XML Gateway Execution Engine to create or to consume XML messages.
Refer to How to Load/Delete Message Maps and DTDs for details on loading a message map created by the Message Designer and its associated DTDs into the XML Gateway repository.