Sales Order Input File - Other XML Associated Files
Datafile Software
Sales Order Input File - Other XML Associated Files
This database is an intermediate file between the XML order and SOP batch update utility. The data is split across three major headings:
Data from the XML file envelope, where orders are batched into single XML files. The envelope data appears in every record created from that XML file)
Data from the order header for an order. The order header data appears in every record created for the order. If there is an order trailer, then that data also is copied into every record created.
Data from order detail lines. It is these that trigger the creation of records in the file
Item Name Type Size Description
1 ENV_MSG-ID X 12 Unique message number from envelope header
2 ENV_VER N 4
3 ENV_DATE E 10
4 ENV_TIME N 4
5 ENV_TYPE X 10
6 ENV_FROM X 14 ) Typically EAN or mailbox codes
7 ENV_TO X 14 )
9 ORH_FLGN N 4 File generation number, usually same for each order in file
10 ORH_VER N 4
11 ORH_DATE E 10
12 ORH_TIME N 4
13 ORH_TYPE X 10
14 ORH_TYPEDESC X 30
15 ORH_FROM X 14 Typically an EAN code
16 ORH_FROM-CODE X 10 Own customer code, looked up in GLU file
17 ORH_FROM-NAME X 35 Also from GLU file
18 ORH_TO X 14 Typically EAN code. Necessary to store only if operating
in a multi-company environment
19 ORH_TO-CODE X 10
20 ORH_TO-NAME X 30
21 ORH_DELY X 14 EAN or location code for delivery location
22 ORH_DELY-CODE X 10 Own delivery location code, looked up in GLU
23 ORH_DELY-NAME X 40 )
24 ORH_DELY-ADD1 X 40 ) These are necessary for one-off deliveries where no
25 ORH_DELY-ADD2 X 40 ) delivery address code given. The ORH-DELY-CODE
26 ORH_DELY-ADD3 X 40 ) could be that of a customer branch, and this the
27 ORH_DELY-ADD4 X 40 ) address for the final delivery (e.g. building site)
28 ORH_DELY-PC X 35 )
29 ORH_BUYR X 14 ) Customer’s buyer placing the order
30 ORH_BUYR-CODE X 10 )
31 ORH_CREF X 17 Customer’s reference number
32 ORH_SREF X 17 For own order reference
33 ORH_ODATE E 10 Order date
34 ORH_RDATE E 10 Date received (today)
35 ORH_EDAT E 10 Earliest delivery date (date required)
36 ORH_LDAT E 10 Latest delivery date (cancel if not met)
37 ORH_DINS-CODE X 4 Delivery instructions, sometimes coded…
38 ORH_DINS-1 X 40 ) … otherwise given explicitly here
39 ORH_DINS-2 X 40 )
40 ORH_DINS-3 X 40 )
Item Name Type Size Description
41 ORH_DINS-4 X 40 )
42 ORH_CONTRACT X 17 Any contract reference number to be quoted
43 ORH_CNTC-DATE E 10 Date of contract
44 ORH_SUPPLIER X 14 14
45 ORH_SUPP-CODE X 10 10
80 ORD_ORD-LINE N 4 Line number
81 ORD_PRD-EAN X 14 Product code, usually an EAN code
82 ORD_PRD-CUST X 20 Customer’s own product code
83 ORD_PRD-SUPP X 14 Own product code (looked up via GLU)
84 ORD_DESCR1 X 40 ) Product description
85 ORD_DESCR2 X 40 )
86 ORD_NARR1 X 40 ) Additional order narrative
87 ORD_NARR2 X 40 )
88 ORD_QTY K 10 Quantity (of trading units, see above) ordered
89 ORD_UNIT X 6 Text, like "EACH” or "BOX”
90 ORD_PACK N 4 Number of consumer units in trading unit
91 ORD_PRICE K 10 Price expected
92 ORD_CONTRACT X 17 Any contract reference (if applied at line level)
93 ORD_DELY-DATE E 10 Delivery date required (overrides order header)
94 ORD_OWN-CODE X 14
156 SOP-UPD? ? 1 Tagged when SOP batch update has processed it
157 SOP-ERROR X 10 For error noted in SOP batch update
158 ADD-USER X 6
159 ADD-DATE E 10
160 ADD-TIME N 4
Article ID: 1894 Created On: Tue, Jul 10, 2012 at 4:05 PM Last Updated On: Thu, Jun 22, 2023 at 4:31 PM