The mapping attributes are where you actually link the outside XML elements to inside JD Edwards data elements.
Any data elements used in a mapping needs to be present in the appropriate UDC setup. Refer to this section before you begin.
Depending on the place and semantic of the external data element, the attribute is mapped in one of three mappings:
- Header attributes
- Detail Attributes – Repetitive
- Detail Attributes – Non Repetitive
Samples of header attributes include any Receiver and sender detail, or total details; Basically anything you see in a paper invoice in the Header or Total section.
Non Repetitive Detail
Any XML header data that needs to be stored on detail invoice data in JD Edwards is called Non Repetitive Detail: Header data that is still stored on detail line level for reference purposes. The most obvious example of such data elements is the Order Reference in the UBL definition.
Repetitive Detail data relates to the true invoices lines as present in the inbound XML structure as indicated in the above example, for instance with the TaxableAmount inbound data elements.
To start maintaining attributes, choose the Details row exit from your Template Definition.
In the next screen, use the correct attribute type radio button to indicate whether to maintain the header – or detail mapping.
When enabling the detail mapping, ensure to indicate whether repetitive or not and indicate the inbound XML tag which signals the detail section (this is cac:InvoiceLine) in the UBL standard.
Direct mappings can be made for elements where a direct relationship exists between the inbound XML data element and a corresponding JD Edwards data element.
Start by selecting the Attribute type in the Attribute column. Attributes have to be available in the proper UDC to be selectable. The system will show the data table and data item in JD Edwards.
The attribute table link flag indicates whether the attribute is actually to be stored in the associated (header or detail) file or just needs to be stored for further evaluations in downstream mappings.
Map the JD Edwards attributes in the XML tag columns to the correct header- and XML tag.
In the last section of the direct mapping, ensure to set the right values in each format column to map the inbound formats to the ones used in your JD Edwards system. This is mandatory for each date- and numeric format.
Dynamic Cross Reference Mapping
Whenever the inbound XML value does not directly translate to the same data element value in JD Edwards but needs to go through a simple translation, the Dynamic Cross Reference subform can be used.
Imagine in the example used earlier, the XML tag for Tax Y/N contains a value of ‘S’ or is blank (for taxable or not). In JD Edwards that would have to translated to a data element Taxable Y/N which is ‘Y’ or ‘N’.
The Dynamic Cross reference subform should contain the following to ensure the ‘S’ is translated to ‘Y’:
The comparison type can handle =, >=, >, <, <= and !=.
Enriched Mapping – Composite Attributes
Enriched mapping is used in cases that data will have to be present in the JD Edwards system to be able to process the invoice correctly, but there is no directly associated data element present in the source XML.
Composite attributes can use other attribute values, but also use any data element in JD Edwards to calculate attribute values and populate these into the Header- or Detail files.
This is best explained using an example: Tax Rate Area is an important field in JD Edwards invoices, but never present in inbound XML files. Tax Rate Area in JDEdwards is defined by the values of the following:
- Item & Purchase Order Detail Level
- Order Detail Level
- APA Supplier Cost Account Setup (additional possibility in APA)
- Supplier Master
In the row for the Tax Rate Area mapping, select the exit Composite to access the Enriched Mapping:
In the Composite Mapping, three rows have been defined accessing the different JD Edwards data elements to finally come up with the correct Tax Rate Area code for the detail Invoice line being mapped.
UMapper is able to use previously mapped Attributes in Composite Attribute lookups. A mapped supplier number can be used to fetch the payment terms form JD Edwards rather than the one on the invoice for instance using this technology.