EDI Sales Order Import Format
Using the Template TAB delimited format below, you are able to import Sales Orders from an external source.
Instructions
Sales Order Browse Screen
Click on the EDI Import button,
This brings up the Import Customer Order screen
Procedure:-
Click on the File Name look up to bring up the required Import file (obviously this must be accessible by Minder on your server / Sharepoint)
Now Click on Validate.
Vailidate does exactly that, it checks for correct header codes S
Upon a successful validate, you proceed to click on ‘Import.’
This now checks Stock Availability and that the Line Item price presented matches with the rules set within Minder for that Debtor (Contract pricing, Bonus items etc) Any mismatch in pricing, or issues with availability are flagged to you at this point.
Click on Create S/O. This, strangely, creates the Sales Order.
Notes
A browse of all imported fields is accessed from the EDI Imported Log two down from Sales Order Entry in the menu drop-down. You can create sales orders from here if imported but not created due to resolving issues. Likewise, an import file can be lapsed (if no s/o created) and imported again.
Bonus Stock.
Cannot be a route/kit
If parent item is back-ordered then so is its bonus child
Transfers
If there is no free stock of components a transfer back-order is not written to avoid it sitting around without action.
Archive
Imported files are archived to c:\mbs\companyname\archive\xxx (a field setting).
Sales Order Import File Format
Three tab-delimited record types
H | Header |
D | Detail |
E | End of Record Set |
Header Fields
Field | Purpose |
|---|---|
01 | Record Type , the Word (PCXPO) |
02 | The Word (Orders) |
03 | Customer Interchange ID (GLN or Store No) |
04 | Purchase Order Number (required) |
05 | Set purpose code (9) (ignored) |
06 | Test Indicator (P) (ignored) |
07 | Receiver EDI Address |
08 | Sender EDI Address |
09 | Transaction Date (as YYYYMMDD) |
10 | Expected Del Date (as YYYYMMDD) |
11 | Customer ABN (only if not using GLN codes (field 50), GLN will then equal ABN & StoreNo, else blank) |
12 | blank |
13 | blank |
14 | blank |
15 | blank |
16 | blank |
17 | blank |
18 | blank |
19 | blank |
20 | Sender EDI Adr |
21 | Free Text |
22 | blank |
23 | blank |
24 | blank |
25 | blank |
26 | blank |
27 | blank |
28 | blank |
29 | blank |
30 | blank |
31 | Supplier Code (not used) |
32 | blank |
33 | blank |
34 | blank |
35 | blank |
36 | blank |
37 | blank |
38 | blank |
39 | blank |
40 | Delivery Location as a GLN else Consignee if 41 <> '' (required) |
41 | Delivery Adr1 (required if 40 <> a GLN code) |
42 | Delivery Adr2 (ignored if 40 = GLN code) |
43 | Delivery Adr3 (ignored if 40 = GLN code) |
44 | Delivery State (ignored if 40 = GLN code) |
45 | Delivery Post Code (ignored if 40 = GLN code) |
46 | blank |
47 | blank |
48 | blank |
49 | blank |
50 | Customer (Buyer) Code as a GLN) |
Detail Fields
Field | Purpose |
|---|---|
01 | Record Type , the Word (LINEITEM) |
02 | Line No (customer sequence) |
03 | Blank |
04 | Item Bar Code (as per Minder) |
05 | Item Code (as per Minder, will be ignored if 04 <> '') |
06 | Item Description |
07 | Order Qty |
08 | UOM (can be blank) |
09 | Comment field |
10 | Blank |
11 | Item Price |
12 | blank |
13 | blank |
14 | blank |
15 | blank |
16 | blank |
17 | blank |
18 | blank |
19 | blank |
20 | blank |
21 | blank |
22 | blank |
23 | blank |
24 | blank |
25 | blank |
26 | blank |
27 | blank |
28 | blank |
29 | blank |
30 | blank |
31 | blank |
32 | blank |
33 | blank |
34 | blank |
35 | blank |
36 | blank |
37 | blank |
38 | blank |
39 | blank |
40 | blank |
41 | blank |
42 | blank |
43 | blank |
44 | blank |
45 | blank |
46 | blank |
47 | blank |
48 | blank |
49 | blank |
50 | blank |
End Fields
Field | Purpose |
|---|---|
01 | The Word (End) |
| Signifies the End of the Purchase Order, multiple orders can be included on the 1 import file. |
Copyright Programmed Network Management PL 2023