<>XML Purchase Order Import
The EDI Solutions XML Purchase Order import uses a template file to translate the XML tags into EDI equivalent information the EDI system can then process the same as if it was processing an EDI formatted document. The format of the template document is a simple text document with one equivalence per line. Each equivalence is <XML Tag>=<EDI Equivalent>, where <XML Tag> is the XML tag used in the import document and <EDI Equivalent> is one of the items from the list below. Some of the equivalences use an second piece of information which is entered after a slash ("/") as part of the equivalence. These secondary pieces of information are generally codes for looking up information in the standard EDI cross-references. These secondary codes do not have to match any standard EDI code. They can be made up by the user, but must exist in the cross-reference.
Equivalence | Definition | Secondary Code |
Document | The start of a new document | |
Header | The start of the header portion of the document | |
PONumber | The customers purchase order number | |
PODate | The customers purchase order date | |
Release | Release number for the purchase order | |
Date | A date - The secondary code will determine the use of the date | A code which can be looked up in the Dare/Time qualifiers cross-reference |
Address | The start of an address - The secondary code will determine the use of the address | "ST" = Ship to address, all other codes are ignored at this time. |
Location | Location ID for an address | |
Name | Company name for an address | |
AddressLine | An address line. There can be multiple tags equivalenced to AddressLine for multi-line addresses | |
City | City for the address | |
State | State for the address | |
PostalCode | Postal/Zip code for the address | |
CountryCode | International country code for the address | |
Detail | Marks the start of the detail area of the document | |
Item | Marks the start on one item in the document | |
Line | Customers line number for the item | |
Product | Product code - The secondary code will determine the use of the information | A code which can be looked up in the product qualifier cross-reference |
Description | Item description | |
Quantity | Quantity ordered | |
UOM | Unit of measure | |
Cost | Price | |
Currency | Currency of the price | |
Retail | Retail price | |
Comment | Comment to be added to the sales order. Multiple tags can be equivalenced to this. |
The document setup for the XML Purchase Order import requests the standard document file and also the name of the template file. The location of the template file will default to in the standard EDI folder or in another folder can be entered.
Sample XML file
<OrderRequest>
<ReferenceID>08acf95a-be05-4681-9484-a355f223ec8e</ReferenceID>
<Header>
<PONumber>PK-eORD</PONumber>
</Header>
<RequestItem>
<RequestID>1</RequestID>
< PartNumber>MS24F750</PartNumber>
<LineCode>MCB</LineCode>
<RequestedQuantity>4</RequestedQuantity>
</RequestItem>
</OrderRequest>
Matching template file
OrderRequest=Document
Header=Header
PONumber=PONumber
RequestItem=Item
RequestID=Line
PartNumber=Product/VN
RequestedQuantity=Quantity
Click here for an EDI XML-In and Generic Output use case overview PDF