TRADACOMS ›
Product Planning › PPRDET
PPRDET: Product Planning Report Details
The PPRDET message is part of the TRADACOMS Product Planning file: product planning and forecast information.
The Product Planning file contains: PPRHDR → PPRDET → PPRTLR.
Message structure
| Segment | Name | Usage |
|---|---|---|
MHD | Message Header | One message for each report |
SFR | Planning Report rules | |
PDN | Product Details | Repeat as necessary |
PLO | Outlet Details | Repeat as necessary |
SFP | Planning Report Data | Repeat as necessary |
SFS | Function Report Data | Repeat as necessary |
RFD | Report References Data | Repeat as necessary |
SFC | Time base control Totals | Repeat as necessary |
SFX | Functional data time base control | Repeat as necessary |
SFL | Planning Report Trailer | |
MTR | Message Trailer |
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 | 'PPRDET' '2' for this version | ||
| Type | M | F | X(6) | ||
| Version Number | M | F | 9(1) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
RTRS | Report time rules composite | M | Date of first record in each row of the report Code which specifies the time period covered by each repeat of data segment. Code Values List 27 Specifies the number of data segments for each product or location Date of last records in each line Indicates the number of periods before the same reporting period repeats, eg the number of working days reported between Mondays, etc · code list 27 | ||
| Date of first entry | M | F | 9(6) | ||
| Report period base | M | V | X(3) | ||
| Number of report segments per row | M | V | 9(3) | ||
| Date at end of period Number of periods in a base | C | F | 9(6) | ||
| cycle | C | V | 9(3) | ||
REPT | Report Type | M | V | X(3) | Indicates whether the data which follows is B = "Budget"; A = "Actual"; or F = "Forecast" |
REPU | Report Function Indicator | C | F | X(3) | Indicates which function is being reported, eg. SALES, ORDERS, STOCK, etc. - Code List 29 · code list 29 |
| 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 segment of this type in the message |
SPRO | Supplier's product number composite | C | Either EAN or supplier's code must be quoted EAN code allocated to the traded unit Supplier's internal reference (non-EAN) identifying the traded unit Code for traded unit allocated under EAN-DUN14 | ||
| EAN-13 Code for the Traded unit | C | F | 9(13) | ||
| Supplier's Code for the Traded unit | C | V | X(30) | ||
| DUN-14 Code for Traded unit | C | F | 9(14) | ||
CPRO | Customer's Product Number composite | C | Can be used for "own label" items allocated a customer's internal number Customer's internal reference for the item (non-EAN) | ||
| Customer's Own Brand EAN Number | C | F | 9(15) | ||
| Customer's Item Code | C | V | X(30) | ||
IDID | EAN/ISSN Number | C | V | 9(18) | EAN/ISSN Number inc. add-on for issue number |
TDES | Traded Unit Description composite | C | Item description as it appears on the item, label or pack | ||
| Traded Unit Description Line 1 | C | V | X(40) | ||
| Traded Unit Description Line 2 | C | V | X(40) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First level sequence number | M | V | 9(10) | Same as preceding PDN segment |
SEQB | Second level sequence number | M | V | 9(10) | Starts at 1 for each sequence of segments |
CLOC | Customer Location composite | M | EAN location number for customer's location Customer's code for the location Supplier's reference for customer's location | ||
| Customer's EAN Location Number | C | F | 9(13) | ||
| Customer's own Location Code | C | V | X(17) | ||
| Supplier's Identity of Customer's Location | 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) | ||
LOCA | Location Activity Indicator | C | V | X(3) | Used to indicate why a location stops activity and is not included in this report. Code List 28 · code list 28 |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First Level Sequence Number | M | V | 9(10) | Takes first level sequence from PDN |
SEQB | Second Level Sequence Number | M | V | 9(10) | Takes second level sequence from PLO |
SEQC | Third Level Sequence Number | M | V | 9(10) | Starts at 1; sequential for each column of data |
REFP | Period Reference composite | M | Use either of the sub-elements not both. Indicates by value: O = opening position or T = line total Indicates the report period to which the data applies Indicates date that period ends | ||
| Summary period | C | F | X(1) | ||
| Report period number | C | V | 9(2) | ||
| Period end date | C | F | 9(6) | ||
QPER | Quantity Data composite | C | Used if REPU specifies the function in SFR otherwise QPER in segment SFS should be used. Number of traded units. Weight or volume or variable unit reported. Must have associated unit of measure reported (Code List 4). Financial amount. Should have currency indicator unless currency already defined. Use Code Values List 31 | ||
| Total Traded units | C | V | 9(15) | ||
| Total Variable units | C | V | 9(10)V9(3) | ||
| Measure Indicator | C | V | X(6) | ||
| Total Financial units | C | V | 9(10)V9(2) | ||
| Currency indicator | C | F | X(3) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First level sequence number | M | V | 9(10) | Takes first level sequence from PDN |
SEQB | Second level sequence number | M | V | 9(10) | Takes second level sequence from PLO |
SEQC | Third level sequence number | M | V | 9(10) | Starts at 1; sequential for each column of data (SFP) |
SEQD | Fourth level sequence number | M | V | 9(10) | Gives individual cell of data by function |
REPU | Report Function Indicator | M | F | X(3) | Note used to indicate the function of the data being reported. Code List 29 · code list 29 |
QPER | Quantity Data composite | M | Number of traded units. Weight or volume or variable unit reported. Must have the associated unit of measure (Code List 4). Financial amount. Should have currency indicator, unless currency is already defined: Use Code Values List 31 | ||
| Total traded units | C | V | 9(15) | ||
| Total variable units | C | V | 9(10)V9(3) | ||
| Measure indicator | C | V | X(6) | ||
| Total Financial units | C | V | 9(10)V9(2) | ||
| Currency | C | F | X(3) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First level sequence number | M | V | 9(10) | Takes first level sequence from PDN |
SEQB | Second level sequence number | M | V | 9(10) | Takes second level sequence from PLO |
SEQC | Third level sequence number | M | V | 9(10) | Starts at 1; sequential for column of data (SFP) |
SEQD | Fourth level sequence number | M | V | 9(10) | Starts at 1; increases for each reference segment |
ORNO | Order number and date composite | M | Used to indicate outstanding order numbers | ||
| Customer's order number | C | V | X(17) | ||
| Supplier's order number | C | V | X(17) | ||
| Date order placed by customer | C | F | 9(6) | ||
| Date order received by supplier | C | F | 9(6) | ||
RDAT | Required Delivery Date | C | F | 9(6) | Date on which delivery is expected or required |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First Level Sequence Number | M | V | 9(10) | Takes value of SEQA from PDN |
SEQB | Second Level Sequence Number | M | V | 9(10) | Starts at 1 and repeats for column of data |
REFP | Period Reference composite | M | Use either of sub-elements not both Maybe O = Opening or T = Total Indicates the report period to which data applies Indicates date that period ends | ||
| Summary Period | C | F | X(1) | ||
| Report period number | C | V | 9(2) | ||
| Period end date | C | F | 9(6) | ||
QPER | Quantity Data composite | C | Totals per time period, reported if REPU used at SFR indicating data of only one function is being reported. If not use QPER in SFX | ||
| Total traded units | C | V | 9(15) | ||
| Total variable units | C | V | 9(10)V9(3) | ||
| Measure indicator | C | V | X(6) | ||
| Total Financial units | C | V | 9(10)V9(2) | ||
| Currency indicator | C | V | X(3) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
SEQA | First level sequence number | M | V | 9(10) | Takes first level sequence from PDN |
SEQB | Second level sequence number | M | V | 9(10) | Either sequential or takes second level sequence from SFC |
SEQC | Third level sequence number | M | V | 9(10) | Starts at 1; sequential for each column/function of data |
REPU | Report Function Indicator | M | F | X(3) | Note: used to indicate the function of the data being reported. Code List 29 · code list 29 |
QPER | Quantity Data composite | M | Totals per time period mandatory if using this segment, reported if REPU used above indicating data of several functions is being reported. If not use QPER in SFC | ||
| Total traded units | C | V | 9(15) | ||
| Total variable units | C | V | 9(10)V9(3) | ||
| Measure indicator | C | V | X(6) | ||
| Total Financial units | C | V | 9(10)V9(2) | ||
| Currency indicator | C | V | X(3) |
| Element | Name | M/C | F/V | Format | Notes |
|---|---|---|---|---|---|
STLD | Data Lines | C | V | 9(10) | Number of SFP or SFS segments in the file |
STLN | Number of Locations Reported | C | V | 9(10) | The number of locations for which data is reported. (PLO segments) |
STPT | Number of Products Reported | C | V | 9(10) | Number of products reported within the file. Count of product reference numbers |
| 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 →