Frames | No Frames

Return to Stylus Studio EDIFACT home page.
Return to Stylus Studio EDIFACT D04B Messages page.
UN/EDIFACT
UNITED NATIONS STANDARD MESSAGE (UNSM)

Sales data report message

Version:D
Release:04B
Contr. Agency:UN
Revision:9
Date:2004-11-23
SOURCE:TBG1 Supply Chain

CONTENTS
Sales data report message
  1. INTRODUCTION
  2. SCOPE
    1. Functional definition
    2. Field of application
    3. Principles
  3. REFERENCES
  4. TERMS AND DEFINITIONS
    1. Standard terms and definitions
  5. MESSAGE DEFINITION
    1. Segment clarification
      1. Header section
      2. Detail section
    2. Segment index (alphabetical sequence by tag)
    3. Message structure
      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


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 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 element0065SLSRPT
0052D
005404B
0051UN

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.

0250 RFF, Reference

To specify a reference.

0260 DTM, Date/time/period

To specify date, and/or time, or period.

0270 Segment Group 8: LIN-PIA-IMD-DTM-PAC-RFF-DOC-ALI-MOA-GIN-

SG9-PAI-SG10 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

0280 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.

0290 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.

0300 IMD, Item description

A segment for describing the product in the line item.

0310 DTM, Date/time/period

A segment specifying the date/time related to the sale of the product specified in the LIN segment.

0320 PAC, Package

A segment specifying the number and type of packages.

0330 RFF, Reference

A segment for referencing documents or other numbers pertinent to the line item.

0340 DOC, Document/message details

A segment identifying and providing information relating to documents.

0350 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.

0360 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.

0370 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.

0380 Segment Group 9: PRI-CUX

A group of segments providing prices and currencies per location and period.

0390 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.

0400 CUX, Currencies

A segment identifying the currencies and rate of exchange for each line item.

0410 PAI, Payment instructions

A segment to report the means of payment for the current product (e.g. cash payment).

0420 Segment Group 10: QTY-MKS-NAD-PRI-DTM-RFF-STS

A 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 buying party, selling price, date sold, status for the quantity, etc.

0430 QTY, Quantity

A segment identifying the quantity and activity, e.g. quantity sold.

0440 MKS, Market/sales channel information

To identify market and sales channel details for products and services information.

0450 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.

0460 PRI, Price details

A segment specifying the price type and amount associated with the activity quantity.

0470 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.

0480 RFF, Reference

A segment to specify reference numbers associated with the activity quantity.

0490 STS, Status

A segment giving a status for the quantity, e.g. metered, estimated or corrected.

0500 Segment Group 11: GEI-SG12

A 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 occurrence of segment group 10.

0510 GEI, Processing information

This segment is used to initiate reporting by line item.

0520 Segment Group 12: LIN-PIA-IMD-PAC-MOA-SG13

A group of segments providing activity data, e.g. sales, by location within specific line item.

0530 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.

0540 PIA, Additional product id

A segment providing additional or alternate product identification, e.g. product group, identified in the LIN segment.

0550 IMD, Item description

A segment used to provide the item description for the item identified in the LIN or PIA segments.

0560 PAC, Package

A segment specifying the number and type of packages.

0570 MOA, Monetary amount

A segment used to specify monetary amounts applicable to the line item, e.g. total sales.

0580 Segment Group 13: LOC-RFF-DTM-MOA-SG14

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.

0590 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.

0600 RFF, Reference

A segment to specify reference numbers associated with the location.

0610 DTM, Date/time/period

A segment identifying the date, time or period during which all the activity quantities occurred for the location if different than the date, time or period specified in the header section.

0620 MOA, Monetary amount

A segment used to specify monetary amounts applicable to the location, e.g. total sales.

0630 Segment Group 14: QTY-PRI-DTM-RFF-STS

A 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, status for the quantity, etc.

0640 QTY, Quantity

A segment identifying the quantity and activity, e.g. quantity sold.

0650 PRI, Price details

A segment specifying the price type and amount associated with the quantity.

0660 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.

0670 RFF, Reference

A segment to specify reference numbers associated with the activity quantity.

0680 STS, Status

A segment giving a status for the quantity, e.g. metered, estimated or corrected.

0690 UNS, Section control

A service segment placed at the start of the summary section to avoid segment collision.

0700 MOA, Monetary amount

A segment to specify monetary amounts relevant to the whole message, such as the goods and services tax amounts.

0710 UNT, Message trailer

A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.


4.2. 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
FTX Free text
GEI Processing information
GIN Goods identity number
IMD Item description
LIN Line item
LOC Place/location identification
MKS Market/sales channel information
MOA Monetary amount
NAD Name and address
PAC Package
PAI Payment instructions
PIA Additional product id
PRI Price details
QTY Quantity
RFF Reference
STS Status
UNH Message header
UNS Section control
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)
├─MKS Market/sales channel information ×1 (C)
├─Segment Group 1 ×9 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×9 (C)
├─Segment Group 2 ×5 (M)
├─NAD Name and address ×1 (M)
├─Segment Group 3 ×5 (C)
├─CTA Contact information ×1 (M)
└─COM Communication contact ×5 (C)
└─Segment Group 4 ×9 (C)
──├─RFF Reference ×1 (M)
──└─DTM Date/time/period ×9 (C)
├─Segment Group 5 ×5 (C)
├─CUX Currencies ×1 (M)
├─DTM Date/time/period ×5 (C)
└─STS Status ×5 (C)
├─Segment Group 6 ×20000 (C)
├─LOC Place/location identification ×1 (M)
├─DTM Date/time/period ×5 (C)
├─FTX Free text ×5 (C)
├─Segment Group 7 ×99 (C)
├─RFF Reference ×1 (M)
└─DTM Date/time/period ×5 (C)
└─Segment Group 8 ×20000 (C)
──├─LIN Line item ×1 (M)
──├─PIA Additional product id ×5 (C)
──├─IMD Item description ×5 (C)
──├─DTM Date/time/period ×9 (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)
──├─GIN Goods identity number ×9999 (C)
──├─Segment Group 9 ×999 (C)
──├─PRI Price details ×1 (M)
──└─CUX Currencies ×1 (C)
──├─PAI Payment instructions ×9 (C)
──└─Segment Group 10 ×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)
────└─STS Status ×9 (C)
├─Segment Group 11 ×1 (C)
├─GEI Processing information ×1 (M)
└─Segment Group 12 ×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 13 ×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 14 ×99 (C)
──────├─QTY Quantity ×1 (M)
──────├─PRI Price details ×9 (C)
──────├─DTM Date/time/period ×9 (C)
──────├─RFF Reference ×9 (C)
──────└─STS Status ×9 (C)
├─UNS Section control ×1 (M)
├─MOA Monetary amount ×9 (C)
└─UNT Message trailer ×1 (M)

Return to Stylus Studio EDIFACT D04B Messages page.
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools EDIFACT to XML
Return to Stylus Studio EDIFACT home page.

Return to Stylus Studio home page.
Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.