TRADACOMS ›
Location Planning › LPRHDR
LPRHDR: Location Planning Report Header
The LPRHDR message is part of the TRADACOMS Location Planning file: location-level planning information.
The Location Planning file contains: LPRHDR → LPRDET → LPRTLR.
Message structure
| Segment | Name | Usage |
|---|---|---|
MHD | Message Header | One message only, at the start of the file |
TYP | Transaction Type | |
SDT | Supplier Details | |
CDT | Customer Details | |
DNA | Data Narrative | Repeat as necessary |
FIL | File Details | |
MTR | Message |
Segments and data elements
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
MSRF | Message Reference | M | V | 9(12) | Consecutive count of messages within the transmission |
TYPE | Type of Message composite | M | 'LPRHDR' '2' for this version | ||
| Type | M | F | X(6) | ||
| Version Number | M | F | 9(1) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
TCDE | Transaction Code | M | F | 9(4) | Code Values List 2 · code list 2 |
TTYP | Transaction Type | C | V | X(12) | Code Values List 3 · code list 3 |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SIDN | Supplier's Identity composite | M | EAN Location Number identifying supplier Supplier's Code as allocated/used by customer | ||
| Supplier's EAN Location Number | C | F | 9(13) | ||
| Supplier's Identity Allocated by Customer | C | V | X(17) | ||
SNAM | Supplier's Name | C | V | X(40) | Supplier's legal name as printed on invoices |
SADD | Supplier's Address composite | C | A maximum of five lines to give the supplier's address | ||
| Supplier's Address Line 1 | C | V | X(35) | ||
| Supplier's Address Line 2 | C | V | X(35) | ||
| Supplier's Address Line 3 | C | V | X(35) | ||
| Supplier's Address Line 4 | C | V | X(35) | ||
| Supplier's Post Code | C | V | X(8) | ||
VATN | Supplier's VAT Registration Number composite | C | Trader's VAT number allocated by HM Customs & Excise Government department or non-UK VAT number | ||
| Numeric VAT Registration Number | C | F | 9(9) | ||
| Alphanumeric VAT Registration Number | C | V | X(17) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
CIDN | Customer's Identity composite | M | EAN Location number identifying the customer Customer's Code as allocated/used by supplier | ||
| Customer's EAN Location Number | C | F | 9(13) | ||
| Customer's Identity Allocated by Supplier | C | V | X(17) | ||
CNAM | Customer's Name | C | V | X(40) | Customer's registered legal name |
CADD | Customer's Address composite | C | A maximum of five lines to give the customer's address | ||
| Customer's Address Line 1 | C | V | X(35) | ||
| Customer's Address Line 2 | C | V | X(35) | ||
| Customer's Address Line 3 | C | V | X(35) | ||
| Customer's Address Line 4 | C | V | X(35) | ||
| Customer's Post Code | C | V | X(8) | ||
VATR | Customer's VAT Registration Number composite | C | Trader's VAT number allocated by HM Customs & Excise Government department or non-UK VAT number | ||
| Numeric VAT Registration Number | C | F | 9(9) | ||
| Alphanumeric VAT Registration Number | C | V | X(17) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First Level Sequence Number | M | V | 9(10) | Starts at 1 and incremented by 1 for each 1st level repeat |
DNAC | Data Narrative Code composite | C | Standard data narrative previously defined and agreed by sender and receiver Number of relevant code list Value from code list · code list 22 | ||
| Code Table Number | C | V | 9(4) | ||
| Code Value | C | V | X(3) | ||
RTEX | Registered Text composite | C | Essential text, where not provided for by specific fields may be communicated using this element. Codes to define the function of the text should be registered with the ANA. The same application code may be repeated up to 4 times, or up to 4 different codes may be used in each repeat of the segment. · code list 24 | ||
| First Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Second Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Third Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
| Fourth Registered Application Code | C | V | X(3) | ||
| Application Text | C | V | X(40) | ||
GNAR | General Narrative composite | C | |||
| General Narrative Line 1 | C | V | X(40) | ||
| General Narrative Line 2 | C | V | X(40) | ||
| General Narrative Line 3 | C | V | X(40) | ||
| General Narrative Line 4 | C | V | X(40) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
FLGN | File Generation Number | M | V | 9(4) | This number is sequential, per file type, per trading partner |
FLVN | File Version Number | M | V | 9(4) | Original (which is always 1) is incremented by 1 for each additional copy created |
FLDT | File Creation Date | M | F | 9(6) | Date the file is created. Format: YYMMDD |
FLID | File (Reel) Identification | C | V | X(6) | Reference on the outside of reel containing the file |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
NOSG | Number of Segments in Message | M | V | 9(10) | Control count of the number of segments comprising message. The count includes the MHD and MTR segments surrounding the message |
Need to exchange TRADACOMS messages with a UK retailer?
SupplyLens connects your ERP, e-commerce or accounting system to any TRADACOMS or EDIFACT trading partner: orders in, invoices out, fully managed.
Book a demo Learn about retail EDI →