eInvoicing Automation uses a dedicated Next Number to track inbound mapping and conversion tasks. Create this next number in the Partner Reserved area “Q46” as follows:
Access the JD Edwards Next Number system by running program P0002 from the fastpath.
Locate the Q46 key. If it does not exist, add it as Q46 with the description “Partner Reserved”.
Create a next number range called “Parsed XML key” and initialize it to 1, as shown in the example.
Any data element that must be read and mapped from source XMLs into JD Edwards needs to be created as an attribute in the correct UDC.
All attributes used in document headers are maintained in UDC Q46|IH.
All attributes used in document details are maintained in UDC Q46|ID. Detail attributes can be repetitive for each invoice line (for instance, Taxable Amount) or non-repetitive (for instance, Purchase Order Number).
Composite attributes are attributes that undergo specific logic after being loaded and mapped. An example is looking up JD Edwards vendor numbers based on an external vendor identifier found in an inbound XML invoice. These are stored in the Composite Attribute UDC as well, Q46|IC.
Composite attributes may use any data present in JD Edwards for validation and to enrich data elements. Tables used need to be set up and present in UDC Q46|IT