United Nations Directories
for Electronic Data Interchange for
Administration, Commerce and Transport



 UN/EDIFACT

Message Type : SLSRPT Version : D Release : 11A Contr. Agency: UN Revision : 9 Date : 2011-06-29 SOURCE: TBG1 Supply Chain CONTENTS Sales data report message 0. INTRODUCTION 1. SCOPE 1.1 Functional definition 1.2 Field of application 1.3 Principles 2. REFERENCES 3. TERMS AND DEFINITIONS 3.1 Standard terms and definitions 4. MESSAGE DEFINITION 4.1 Segment clarification 4.1.1 Header section 4.1.2 Detail section 4.2 Segment index (alphabetical sequence by tag) 4.3 Message structure 4.3.1 Segment table --------------------------------------------------------------------------- For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction --------------------------------------------------------------------------- 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 10 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 10 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 10 and its subordinate groups. If segment group 10 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.3 UN/ECE UNSM - General Introduction, Section 1. 3. TERMS AND DEFINITIONS 3.1 Standard terms and definitions See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2. 4. MESSAGE DEFINITION 4.1 Segment clarification This section should be read in conjunction with the segment table which indicates 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 'ccyymmdd'/'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: Data element 0065 SLSRPT 0052 D 0054 11A 0051 UN 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 MKS, Market/sales channel information To identify market and sales channel details for products and services information. 0050 Segment group 1: RFF-DTM A group of segments for giving references and where necessary, their dates, relating to the whole message e.g. contract number. 0060 RFF, Reference A segment identifying the reference by its number and where appropriate a line number within the document. 0070 DTM, Date/time/period A segment specifying the date/time related to the reference. 0080 Segment group 2: NAD-SG3-SG4 A group of segments identifying the parties with associated information. 0090 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. 0100 Segment group 3: CTA-COM A group of segments giving contact details of the specific person or department within the party identified in the NAD segment. 0110 CTA, Contact information A segment to identify a person or department, and their function, to whom communications should be directed. 0120 COM, Communication contact A segment to identify a communications type and number for the contact specified in the CTA segment. 0130 Segment group 4: RFF-DTM A group of segments for giving references and where necessary, their dates, relating to the party specified in the preceding name and address segment, e.g. tax reference number. 0140 RFF, Reference A segment identifying the reference by its number and where appropriate a line number within the document. 0150 DTM, Date/time/period A segment specifying the date/time related to the reference. 0160 Segment group 5: CUX-DTM-STS A group of segments specifying the currencies, related dates/periods and status for the rate of exchange valid for the whole sales data report. The Segment Group 4 may be omitted in national applications but will be required for international exchanges. 0170 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. 0180 DTM, Date/time/period A segment specifying the date/time/period related to the rate of exchange. 0190 STS, Status A segment giving a status for the range of exchange, e.g. if the exchange rate is preliminary or accurate. 4.1.2 Detail section Information to be provided in the Detail section: 0200 Segment group 6: LOC-DTM-FTX-SG7-SG8 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 10. If segment group 10 is not used, there shall be at least on occurrence of segment group 5. 0210 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. 0220 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. 0230 FTX, Free text A segment with free text information, in coded or clear form, used when additional information is needed but cannot be accommodated within other segments. In computer to computer exchanges such text will normally require the receiver to process this segment manually. 0240 Segment group 7: RFF-DTM A group of segments giving references at an intermediate level relating to several lines items, e.g. an invoice, shipment, notification, etc. 0