Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D97A Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)
Sales data report message
Version: | D |
---|
Release: | 97A |
---|
Contr. Agency: | UN |
---|
Revision: | 3 |
---|
Date: | 96-12-13 |
---|
SOURCE: | Submitted by WEEB-MD1 on behalf of PAEB |
---|
CONTENTS
Sales data report message
- INTRODUCTION
- SCOPE
- Functional definition
- Field of application
- Principles
- REFERENCES
- TERMS AND DEFINITIONS
- Standard terms and definitions
- MESSAGE DEFINITION
- Data segment clarification
- Header section
- Detail section
- Data segment index (alphabetical sequence)
- Message structure
- Segment table
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.6, UN/ECE UNSM General Introduction
|
This message also occurs in the following versions of this standard:
D93A, D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
0. INTRODUCTION
This specification provides the definition of the Sales data report message (SLSRPT) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport.
1. SCOPE
1.1. | Functional Definition
A message to enable the conveyance of product activity related to the sale of products or services, such as the activity location, date, time or period, quantity, pricing, monetary amount, market sector, involved parties and other data enabling various sales analysis processes. Such activity information allows the recipient to perform statistical and quantitative analysis in support of production, planning, marketing, replenishment, and other processes.
1.2. Field of Application
The Sales data report message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry.
1.3. | Principles
This message provides product activity related to the sale of products or services in two mutually exclusive methods. These two methods are represented by segment groups 5 and 9 within the detail area.
- The first method is reporting activity by line item within a specific location, e.g. reporting each product sold within a specific location. This method will utilise segment group 5 and its subordinate groups. If segment group 5 is used segment group 9 shall not be used.
- The second method is reporting activity by location within each line item, e.g. reporting each location and quantity sold for a particular product. This method will utilise segment group 9 and its subordinate groups. If segment group 9 is used segment group 5 shall not be used.
The message may be sent from a buyer, seller, distributor, public warehouse or third party to their supplier, distributor, manufacturer, or other third party. It is assumed the recipient will perform analytical processing of the data in support of other business processes such as marketing, replenishment, or product development.
This message provides the recipient with detailed information relative to a specific product such as:
- Location of the activity, e.g. sale or product movement.
- Specific parties involved, e.g. name of company sold to.
- Date or period of the activity.
- Activity price, e.g. selling price.
- Activity quantity, e.g. quantity sold.
- Promotion in effect.
- Value of the sales.
- Periodical turnover.
- Additional product information, e.g. product groups or id numbers.
- Identification of market segment or channel of distribution.
- Summarisation of information for various locations, e.g. sales for all locations in a region.
2. REFERENCES
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1.
3. TERMS AND DEFINITIONS
3.1. Standard terms and definitions
See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 2.
4. MESSAGE DEFINITION
4.1. Data Segment Clarification
This section should be read in conjunction with the Segment Table which indicate mandatory, conditional and repeating requirements.
The following guidelines and principles apply to the whole message and are intended to facilitate the understanding and implementation of the message:
All specified dates/times should be in the format 'yymmdd'/'hhmm' unless all parties involved in the transaction agree that there is a functional requirement for an alternative format. Periods should be specified as whole numbers representing the required period as indicated in the format qualifier (weeks, months, etc.).
Where a choice of code or text is given only the code element should be used wherever possible. Due to the high volume of data that will be usually transmitted in the Sales Data Report message, it is highly recommended to use codes for products and locations.
Conditional data that is not required in the message should not be included.
Care must be taken that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of a group.
4.1.1. Header section
Information to be provided in the Header section:
0010 UNH, Message header
A service segment starting and uniquely identifying a message. The message type code for the Sales data report message is SLSRPT. Note: Sales data report messages conforming to this document must contain the following data in segment UNH, composite S009:
0020 BGM, Beginning of message
A segment by which the sender must uniquely identify the sales data report by means of its type and number. 0030 DTM, Date/time/period
A segment specifying general dates and, when relevant, times related to the whole message. The sales report preparation date and the sales period covered by the report must be specified using this segment. 0040 Segment Group 1: NAD-SG2A group of segments identifying the parties with associated information. 0050 NAD, Name and address
A segment identifying names and addresses of the parties, in coded or clear form, and their functions relevant to the sales data report. Identification of the sender of the report and the recipient is mandatory for the sales data report message. It is recommended that where possible only the coded form of the party ID should be specified e.g. the sender and receiver of the report are known to each other, thus only the coded ID is required, but when a new address might have to be clearly specified, this should be done preferably in structured format. 0060 Segment Group 2: CTA-COMA group of segments giving contact details of the specific person or department within the party identified in the NAD segment. 0070 CTA, Contact information
A segment to identify a person or department, and their function, to whom communications should be directed. 0080 COM, Communication contact
A segment to identify a communications type and number for the contact specified in the CTA segment. 0090 Segment Group 3: RFF-DTMA group of segments for giving references and where necessary, their dates, relating to the whole message e.g. contract number. 0100 RFF, Reference
A segment identifying the reference by its number and where appropriate a line number within the document. 0110 DTM, Date/time/period
A segment specifying the date/time related to the reference. 0120 Segment Group 4: CUX-DTMA group of segments specifying the currencies and related dates/periods valid for the whole sales data report. The Segment Group 4 may be omitted in national applications but will be required for international exchanges. 0130 CUX, Currencies
A segment identifying the currencies specified in the sales data report e.g. the currency in which the sales amounts or product prices are expressed in. A rate of exchange may be given to convert a reference currency into a target currency. 0140 DTM, Date/time/period
A segment specifying the date/time/period related to the rate of exchange.
4.1.2. Detail section
Information to be provided in the Detail section:
0150 | Segment group 5: LOC-DTM-SG6-SG7 A group of segments providing activity, e.g. sales, data by line item within a specific location. This segment group is mutually exclusive with segment group 9. If segment group 9 is not used, there shall be at least on occurence of segment group 5.
0160 | LOC, Place/location identification
A segment to identify the activity, e.g. sales, the quantity of the activity, and other data related to the specific activity such as buying party, selling price, date sold, etc. 0170 DTM, Date/time/period
A segment identifying the sub-period during which the sales being reported occurred if different than the period specified in the heading section e.g. within a biweekly sales data report as specified in the heading section, sales are reported in sub-periods of one week. 0180 Segment Group 6: RFF-DTMA group of segments giving references at an intermediate level relating to several lines items, e.g. an invoice, shipment, notification, etc. 0190 RFF, Reference
To specify a reference. 0200 DTM, Date/time/period
To specify date, and/or time, or period. SG8 A group of segments to identify the product or service and the activity, e.g. sales, which applies to the product or service. In addition other data related to the activity may 0220 | LIN, Line item
A segment identifying the line item by the line number and configuration level. In addition it may identify the product or service to which the activity, e.g sales is applicable. 0230 PIA, Additional product id
A segment providing either additional identification to the product specified in the LIN segment or providing any substitute product identification. In the Sales Data Report the PIA segment can be used when a product specified in LIN has to be associated with a group or family of products whose identity could be specified in PIA. 0240 IMD, Item description
A segment for describing the product in the line item. 0250 PAC, Package
A segment specifying the number and type of packages. 0260 RFF, Reference
A segment for referencing documents or other numbers pertinent to the line item. 0270 DOC, Document/message details
A segment identifying and providing information relating to documents. 0280 ALI, Additional information
A segment indicating that the line item is subject to special conditions owing to origin, customs preference, embargo regulations or commercial factors. In the Sales Data Report the ALI segment can be used to specify promotional flags, e.g. to indicate what type of promotion if any was in effect when the product specified in LIN was sold. 0290 MOA, Monetary amount
A segment specifying any monetary amounts relating to the product. For the sales data report the MOA segment can be used to express the total monetary amount of the product sold in one location for one period. 0300 PRI, Price details
A segment to specify the price type and amount. The price used in the calculation of the total sales monetary amount will normally be the selling price. 0310 GIN, Goods identity number
A segment to specify identity numbers related to units of the product identified in the LIN segment, e.g. serial number. A group of segmens to identify the activity, e.g. sales, the quantity of the activity, and other data related to the specific activity such as buying party, selling price, date sold, etc. 0330 | QTY, Quantity
A segment identifying the quantity and activity, e.g. quantity sold. 0340 MKS, Market/sales channel information
To identify market and sales channel details for products and services information. 0350 | NAD, Name and address
To specify the name and address of a party related to the specific activity quantity identified in the previous QTY segment, e.g. the party the product(s) were sold to. 0360 + PRI, Price details
A segment specifying the price type and amount associated with the activity quantity. 0370 + DTM, Date/time/period
A segment identifying the date/time or period during which the activity quantity occurred if different than the date/time or period specified in either the header section or segment group 5. 0380 + RFF, Reference
A segment to specify reference numbers associated with the activity quantity. 0390 Segment Group 9: GIS-SG10A group of segments providing activity data, e.g. sales, by location within a specific line item. This segment group is mutually exclusive with segment group 5. If segment group 5 is not used, there shall be at least one occurence of segment group 9. 0400 + GIS, General indicator
This segment is used to initiate reporting by line item. A group of segments providing activity data, e.g. sales, by location within specific line item. 0420 + LIN, Line item
A segment identifying the line item by the line number and configuration level, and additionally identifying the product or service for which activity data is being reported. 0430 + PIA, Additional product id
A segment providing additional or alternate product identification, e.g. product group, identified in the LIN segment. 0440 + IMD, Item description
A segment used to provide the item description for the item identified in the LIN or PIA segments. 0450 + PAC, Package
A segment specifying the number and type of packages. 0460 + MOA, Monetary amount
A segment used to specify monetary amounts applicable to the line item, e.g. total sales. A group of segments to identify the location of the activity, e.g. sales, the quantity of the activity, and other data related to the specific activity such as buying party, selling price, date sold, etc. 0480 + LOC, Place/location identification
A segment indicating in coded form the location to which the sales data being reported apply, e.g. a retail outlet, a geographic area. 0490 + RFF, Reference
A segment to specify reference numbers associated with the location. 0500 + DTM, Date/time/period
A segment identifying the date, time or period during which all the activity quantities occured for the location if different than the date, time or period specified in the header section. 0510 + MOA, Monetary amount
A segment used to specify monetary amounts applicable to the location, e.g. total sales. 0520 Segment Group 12: QTY-PRI-DTM-RFFA group of segments to identify the activity, e.g. sales, the quantity of the activity, and other data related to the specific activity such as, selling price, date sold, etc. 0530 + QTY, Quantity
A segment identifying the quantity and activity, e.g. quantity sold. 0540 + PRI, Price details
A segment specifying the price type and amount associated with the quantity. 0550 + DTM, Date/time/period
A segment identifying the date, time or period during which the activity quantity occured if different than the date, time or period specified in either the header section or segment group 5. 0560 + RFF, Reference
A segment to specify reference numbers associated with the activity quantity. 0570 UNT, Message trailer
A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
4.2. Data segment index (Alphabetical sequence by tag)
|
ALI |
Additional information |
|
BGM |
Beginning of message |
|
COM |
Communication contact |
|
CTA |
Contact information |
|
CUX |
Currencies |
|
DOC |
Document/message details |
|
DTM |
Date/time/period |
|
GIN |
Goods identity number |
![](../images/plus.gif) |
GIS |
General indicator |
|
IMD |
Item description |
|
LIN |
Line item |
|
LOC |
Place/location identification |
|
MKS |
Market/sales channel information |
|
MOA |
Monetary amount |
|
NAD |
Name and address |
|
PAC |
Package |
|
PIA |
Additional product id |
|
PRI |
Price details |
|
QTY |
Quantity |
|
RFF |
Reference |
|
UNH |
Message header |
|
UNT |
Message trailer |
4.3. Message structure
4.3.1. Segment table
├─UNH Message header | ×1 | (M) |
├─BGM Beginning of message | ×1 | (M) |
├─DTM Date/time/period | ×5 | (M) |
├─Segment Group 1 | ×5 | (M) |
│─├─NAD Name and address | ×1 | (M) |
│─└─Segment Group 2 | ×5 | (C) |
│───├─CTA Contact information | ×1 | (M) |
│───└─COM Communication contact | ×5 | (C) |
├─Segment Group 3 | ×5 | (C) |
│─├─RFF Reference | ×1 | (M) |
│─└─DTM Date/time/period | ×5 | (C) |
├─Segment Group 4 | ×5 | (C) |
│─├─CUX Currencies | ×1 | (M) |
│─└─DTM Date/time/period | ×5 | (C) |
├─Segment Group 5 | ×20000 | (C) |
│─├─LOC Place/location identification | ×1 | (M) |
│─├─DTM Date/time/period | ×5 | (C) |
│─├─Segment Group 6 | ×99 | (C) |
│─│─├─RFF Reference | ×1 | (M) |
│─│─└─DTM Date/time/period | ×5 | (C) |
│─└─Segment Group 7 | ×20000 | (C) |
│───├─LIN Line item | ×1 | (M) |
│───├─PIA Additional product id | ×5 | (C) |
│───├─IMD Item description | ×5 | (C) |
│───├─PAC Package | ×5 | (C) |
│───├─RFF Reference | ×5 | (C) |
│───├─DOC Document/message details | ×5 | (C) |
│───├─ALI Additional information | ×5 | (C) |
│───├─MOA Monetary amount | ×5 | (C) |
│───├─PRI Price details | ×5 | (C) |
│───├─GIN Goods identity number | ×9999 | (C) |
│───└─Segment Group 8 | ×999 | (C) |
│─────├─QTY Quantity | ×1 | (M) |
│─────├─MKS Market/sales channel information | ×1 | (C) |
│─────├─NAD Name and address | ×1 | (C) |
│─────├─PRI Price details | ×9 | (C) |
│─────├─DTM Date/time/period | ×9 | (C) |
│─────└─RFF Reference | ×9 | (C) |
├─Segment Group 9 | ×1 | (C) |
│─├─GIS General indicator | ×1 | (M) |
│─└─Segment Group 10 | ×99999 | (C) |
│───├─LIN Line item | ×1 | (M) |
│───├─PIA Additional product id | ×99 | (C) |
│───├─IMD Item description | ×9 | (C) |
│───├─PAC Package | ×9 | (C) |
│───├─MOA Monetary amount | ×9 | (C) |
│───└─Segment Group 11 | ×9999 | (C) |
│─────├─LOC Place/location identification | ×1 | (M) |
│─────├─RFF Reference | ×9 | (C) |
│─────├─DTM Date/time/period | ×9 | (C) |
│─────├─MOA Monetary amount | ×9 | (C) |
│─────└─Segment Group 12 | ×99 | (C) |
│───────├─QTY Quantity | ×1 | (M) |
│───────├─PRI Price details | ×9 | (C) |
│───────├─DTM Date/time/period | ×9 | (C) |
│───────└─RFF Reference | ×9 | (C) |
└─UNT Message trailer | ×1 | (M) |
Change indicators |
plus sign |
|
An addition. |
asterisk |
|
Addition/substraction/change to a code entry for a particular data element. |
hash or pound sign |
|
Changes to names. |
vertical bar |
|
Changes to text for descriptions, notes and functions. |
minus sign |
|
A deletion. |
letter X |
|
Marked for deletion. |
Return to Stylus Studio EDIFACT D97A Messages page.
|
|