Directory   Messages   Segments   Composites   Data elements   Codes Meaning of the change indicators
  UN/EDIFACT  D.03A (Batch) Syntax version 3 Issue date 2003-06-23  
  Message type specification SLSFCT
 
 
SLSFCT 2 Sales forecast message  
  Date:
2003-06-10

Source:
TBG1 Supply Chain

0. INTRODUCTION
This specification provides the definition of the Sales forecast message (SLSFCT) 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 transmission of forecast data related to products or services, such as corresponding location, period, product identification, pricing, monetary amount, quantity, market sector information, sales parties. It enables the recipient to process the information automatically and use it for production, planning, marketing, statistical purposes, etc.

1.2 Field of application
The Sales forecast 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
The message intent is to provide sales forecast information for one or more locations for a series of products within a specified time period.

The message is transmitted either from a seller to its supplier or from a headquarters, coordination or distribution centre to a manufacturer, supplier or a third party.

It allows the recipient to know sales forecast for a specific product by:

- Sales location

- Sales period

- Product identification

- Product selling price, quantity and value of the sales

- Additional Identification of the products such as promotional flags, product group or family identification and internal identification numbers

- Periodical Turnover of a specified location

- Global specified product sales, i.e. total sales of a product in all locations

- Sales channel, market segment end use, if known.

- Sales parties identification, if known.

- Outlet identification, if known.

Though the message is location driven, it is conceivable that the recipient process the data to derive information based on other variables such as a specific product and all its related sales locations and/or addresses or forecasted periodic turnover and the related locations.

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 Data 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 '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.

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.

Free text information within the message should be avoided as this inhibits automatic processing.
 
  Generated by GEFEG.FX  
  http://www.gefeg.com