Home > Technical > B2B File layouts > B2B File Formats
Stena GRCSV file – header record followed by item records. Fields ignored by the code are not mentioned – each record must contain at least 11 fields.
Header Record
|
Field Number |
Description |
|
1 |
Value = 122 – identifies the header |
|
2 |
Delivery date |
|
4 |
Trade code |
|
6 |
Supplier code |
|
7 |
Delivery number |
|
8 |
PO number |
|
10 |
Segment count = count of items to follow |
Item Record
|
Field Number |
Description |
|
1 |
Value = 222 – identifies the item record |
|
5 |
Order code |
|
7 |
Quantity ordered |
|
8 |
Quantity received |
Stena PO
ConfirmationCSV file – header record with at least 4 fields.
Header Record
|
Field Number |
Description |
|
1 |
Value = 122 – identifies the header |
|
2 |
Trade code |
|
3 |
Supplier code |
|
4 |
PO number |
ViewPoint
TransferCSV file with at least 11 fields.
|
Field Number |
Description |
|
1 |
Request number |
|
3 |
Request trade code |
|
5 |
Date YYYY-MM-DD or similar format |
|
6 |
Line number |
|
7 |
Order code |
|
9 |
Units received |
|
11 |
Status S = received |
Genting PO
ConfirmationCSV file with 9 fields in each line.
|
Field Number |
Description |
|
2 |
Material number |
|
3 |
SAP supplier code |
|
5 |
Item number (must be numeric) |
|
7 |
SAP trade code |
|
8 |
Quantity ordered (= quantity received) |
Condor PO
ConfirmationCSV file – header record followed by item records. All records expected to have number of fields = 8, 24 or 27. Fields in the file can have “” around the values which will be stripped off.
Header Record
|
Field Number |
Description |
|
1 |
Value = H – identifies the header |
|
3 |
PO number |
|
7 |
Trade code |
Item Record
|
Field Number |
Description |
|
1 |
Value = L – identifies the item record |
|
2 |
Item number |
|
6 |
Case quantity |
|
7 |
Item quantity |
|
8 |
Items per case (carton size) |
MGP Allocation
InvoiceCSV file – header record followed by item records. The header records have ‘[‘ as the first character and they are parsed only to extract comment information – the first, second and ninth fields are concatenated as the comment with line feeds separating them.
Item Record
|
Field Number |
Description |
|
1 |
Item number |
|
2 |
Order code |
|
3 |
Description |
|
4 |
Item quantity |
|
5 |
Cost |
|
9 |
Sales tax |
ALM InvoiceText file – several different types of record; and multiple invoices can be sent in a single file. The lines are apparently strings from which information is picked out – if the information is not used then presumably any filler (0 or space or even a comma) will be OK.
Header Record
Value (or only significant value) = “TH” – must come first or immediately after a trailer record
Trailer Record
Value (or only significant value) = “TT” – must come immediately after the TT header record or after an invoice footer record
Supplier Header Record
Value (or only significant value) = “FHSUPP” – must come immediately after a transaction header
Commodity Header Record
Value (or only significant value) = “FHCOMM” – must come immediately after a transaction header; a supplier header or a supplier detail record.
Invoice Header Record
Value (or only significant value) = “FHCOMM” – must come immediately after a transaction header; a supplier header, a supplier detail record, a commodity header or commodity detail record.
Detail Record
FD indicates a record is a detail record; the type of detail is indicated by the preceding FHxxxx header record.
Invoice Detail Header (following invoice header or invoice footer)
|
Offset |
Length |
Description |
|
1 |
2 |
Value = FD |
|
3 |
5 |
Invoice number |
|
14 |
5 |
00000 |
|
19 |
6 |
Receiver code |
|
155 |
8 |
Invoice date |
Invoice Item Detail (following invoice detail header or invoice detail footer)
|
Offset |
Length |
Description |
|
1 |
2 |
Value = FD |
|
14 |
5 |
Page + line number |
|
42 |
30 |
Item description |
|
75 |
6 |
Order code |
|
87 |
4 |
Carton size |
|
98 |
7 |
Quantity invoiced |
|
147 |
7 |
Unit cost |
|
154 |
9 |
Line cost |
|
174 |
9 |
Line tax |
|
201 |
13 |
EAN |
Invoice Detail Footer (following invoice detail header or invoice item detail)
|
Offset |
Length |
Description |
|
1 |
2 |
Value = FD |
|
14 |
5 |
99999 |
|
45 |
9 |
Freight |
|
64 |
9 |
Total cost |
Supplier and commodity detail records are those FD records following the appropriate FHxxx records – but they are ignored.
MetCash
InvoiceText file – remarkably similar to the ALM invoice files. several different types of record; and multiple invoices can be sent in a single file. The lines are apparently strings from which information is picked out – if the information is not used then presumably any filler (0 or space or even a comma) will be OK.
Header Record
Value (or only significant value) = “TH” – must come first or immediately after a trailer record
Trailer Record
Value (or only significant value) = “TT” – must come immediately after the TT header record or after an invoice footer record
Supplier Header Record
Value (or only significant value) = “FHSUPP” – must come immediately after a transaction header
Commodity Header Record
Value (or only significant value) = “FHCOMM” – must come immediately after a transaction header; a supplier header or a supplier detail record.
Invoice Header Record
Value (or only significant value) = “FHCOMM” – must come immediately after a transaction header; a supplier header, a supplier detail record, a commodity header or commodity detail record.
Detail Record
FD indicates a record is a detail record; the type of detail is indicated by the preceding FHxxxx header record.
Invoice Detail Header (following invoice header or invoice footer)
|
Offset |
Length |
Description |
|
1 |
2 |
Value = FD |
|
3 |
5 |
Invoice number |
|
13 |
5 |
00000 |
|
18 |
6 |
Receiver code |
|
24 |
10 |
PO number |
|
154 |
8 |
Invoice date |
Invoice Item Detail (following invoice detail header or invoice detail footer)
|
Offset |
Length |
Description |
|
1 |
2 |
Value = FD |
|
13 |
5 |
Page + line number |
|
41 |
30 |
Item description |
|
74 |
6 |
Order code |
|
86 |
4 |
Carton size |
|
97 |
7 |
Quantity invoiced |
|
105 |
7 |
Unit cost |
|
112 |
9 |
Line cost |
|
156 |
9 |
Line tax |
|
129 |
13 |
EAN |
|
185 |
9 |
Line service charge |
Invoice Detail Footer (following invoice detail header or invoice item detail)
|
Offset |
Length |
Description |
|
1 |
2 |
Value = FD |
|
13 |
5 |
99999 |
|
34 |
9 |
Freight |
|
54 |
9 |
Total cost |
|
109 |
9 |
Total tax |
|
119 |
9 |
Total service charge |
Supplier and commodity detail records are those FD records following the appropriate FHxxx records – but they are ignored.
EANCOM
FilesThese have a sub-type indicated by the second line in the file. All of these files appear to be obsolete.
|
File Type |
Description |
Identified |
|
BSLVWORDERS |
BSL virtual warehouse order |
Line contains “VWORDERS:D:96A” |
|
EANCOMORDRSP |
Order response |
Line contains “ORDRSP:D:96A” |
|
EANCOMDESADV |
Despatch advice |
Line contains “DESADV:D:93A” |
|
EANCOMINVOIC |
Invoice |
Line contains “INVOIC:D:” |
|
EANCOMVWORDRSP |
VW order response |
Line contains “VWORDRSP:D:96A” |
|
EANCOMCONTROL |
Acknowledgement |
Line contains “CONTRL:2:2” |
| Converted from CHM to HTML with chm2web Pro 2.85 (unicode) |
