Distr.
RESTRICTED

TRADE/WP.4/R.1183/Rev.1
17 January 1996

ENGLISH ONLY
ECONOMIC COMMISSION FOR EUROPE
COMMITTEE ON THE DEVELOPMENT OF TRADE

Working Party on the Facilitation of
International Trade Procedures
(Item 6 of the provisional agenda
of the Meeting of Experts on Data
Elements and Automatic Data Interchange (GE.1)
fifty-third session, 18-19 March 1996)

* * *

TRADE DATA INTERCHANGE PROTOCOLS

Development of United Nations Standard Messages (UNSMs)

(Item 3.2.15 of the Programme of work)

MESSAGE TYPE SUBMITTED AS STATUS 0 FOR INFORMATION

PRODUCT SOURCE INFORMATION MESSAGE (PRDSRC)

Transmitted by the UN/EDIFACT Rapporteurs *

* * *

***
* The present document is reproduced in the form in which it was received by the secretariat.


                    UN/EDIFACT

                  DRAFT DOCUMENT

          Product source information message
                    









---------------------------------------------------------------
This message has undergone only an initial technical assessment
which may have found certain technical and presentation problems.
These will be solved before the message is submitted as a request
for Status 1. Anything shown under Section 5 (or, in some cases,
which should have been shown in Section 5 - directory variations)
is NOT approved at this stage. Further information on the
development of this message can be obtained from the Rapporteur's
EDIFACT Board Secretariat. This document is issued for
information and comments and is not intended for implementation.
-----------------------------------------------------------------











                                           Message Type  :PRDSRC
                                           Version       :0
                                           Release       :1 
                                           Contr. Agency :RT
                                           Status        :0
                                           Date          :94-06  







Source: Submitted by X12E



CONTENTS 

Product source information message
 
    

0.    INTRODUCTION


1.    SCOPE

      1.1   Functional definition
      1.2   Field of application
      1.3   Principles


2.    REFERENCES


3.    TERMS AND DEFINITIONS


4.    MESSAGE DEFINITION

      
      4.1   Data segment clarification

      4.2   Data segment index (alphabetical sequence)

      4.3   Message structure

            4.3.1 Segment table


5.    DIRECTORIES

      5.1   Directory references

      5.2   Explanation of directory variations

            5.2.1 Segment variations

0. INTRODUCTION

This specification provides the definition of the Product source
information message (PRDSRC) 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 the classification and
categorization of information regarding an organization’s
products, and facilities.

1.2 Field of Application

The Product source information message may be used for both
national and international trade. It is based on universal
commercial practice and is not dependent on the type of business
or industry.

1.3 Principles

The ever increasing diversity of products and services creates a
business need for automated product sourcing. Traditional
directories are expensive to create, maintain, and distribute,
even in electronic form. The creation of a standard product
source message facilitates automated product sourcing.

A product design or procurement application would use the product
source message to automatically create and maintain a local
database of product source information. Once a source has been
identified, the exchange of a trading profile would establish the
trading relationship.

The product source message supports the concept of open EDI as it
does not presume a pre-existing trading relationship. The product
source message will be used to create listing agency
servers,where product source messages can be stored and
retrieved.

The message design is based on a data model elaborated by the
technical and architecture task group of X12E.

The accurate and unambiguous classification of an organization's
products, and facilities is essential to automate the
identification of potential trading partners.

The Product Source Information Message is used to specify
information related to physical and functional locations. A
functional location is usually a specific department within a
company.

A Product Source Information message is used to populate a
database from which information is retrieved using the Request
For Product Source Message (REQSRC).


2. REFERENCES

See UNTDID, Part 4, Section 2.6, UN/ECE UNSM - General
Introduction, Section 1.


3. TERMS AND DEFINITIONS

See UNTDID, Part 4, Section 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 Branching
Diagram and the Segment Table which indicate mandatory,
conditional and repeating requirements.

0010  UNH, Message header
     A service segment starting and uniquely identifying a
     message.  The message type code for the Product source
     information Message is 'PRDSRC'.

     Note: Product source information messages conforming to this
     documentmust contain the following data in segment UNH,
     composite S009:

      Data element  0065 PRDSRC
                    0052 0
                    0054 1
                    0051 51

0020  BGM, Beginning of message
     A segment for the unique identification of the document name
     and number.

0030  Segment group 1: FII-DTM-SG2
     A group of segments indicating the date and source of the
     information.

0040  FII, Financial institution information
     A segment identifying the organization responsible for the
     creation of the information.

0050  DTM, Date/time/period
      A segment specifying the original date of the information.

0060  Segment group 2: FII-NAD-SG3
     A group of segments identifying an Organization and its
     trade names.

0070  FII, Financial institution information
     A segment for identifying the organization and its legal
     status.

0080  NAD, Name and address
     A segment for identifying the trade names of an
     organization. For the purposes of this message, this segment
     should not be used to communicate address information.

0090  Segment group 3: BUS-SG4
     A group of segments identifying the functions performed at a
     facility.

0100  BUS, Business function
     A segment identifying the function performed at a facility,
     e.g., warehousing, retail, manufacturing, service, support.

0110  Segment group 4: LOC-SG4
      A group of segments identifying the facilities.

0120  LOC, Place/location identification
     A segment identifying the physical location from which an
     organization performs a function.

0130  Segment group 5: NAD-COM-SG6
     A group of segments identifying the point of contact where
     information, goods or services can be exchanged, e.g. postal
     address, telephone, electronic mail.

0140  NAD, Name and address
     A segment identifying the address of a point of contact. For
     the purposes of this message this segment should not be used
     to communicate name information.

0150  COM, Communication contact
     A segment identifying a communication number of a point of
     contact.

0160  Segment group 6: IMD-CCI
     A group of segments identifying a product and its
     characteristics.

0170  IMD, Item description
      A segment for identifying a product by its UNCCS code.

     In composite C273, data element 7009 is required to contain
     a validUnited Nations Common Code.



0180  CCI, Characteristic/class id
     A segment used to describe distinctive properties of a
     product.

0190  UNT, Message trailer
     A service segment ending the message giving the total number
     of segments in the message and the control reference number
     of the message.

4.2 Data segment index (alphabetic sequence)

  BGM Beginning of message
  BUS Business function
  CCI Characteristic/class id
  COM Communication contact
  DTM Date/time/period
  FII Institution information
  IMD Item description
  LOC Placce/location identification
  NAD Name and address
  UNH Message header
  UNT Message trailer
4.3 Message Structure

4.3.1 Segment Table

  TAG   NAME                             S  REPT S   REPT

  UNH  Message header                    M    1                  
  BGM  Beginning of message              M    1                  

  --- Segment Group 1 -------------------M - 9999-----------+
  FII  Financial institution information M    1             |
  DTM  Date/time/period                  M    1             |
                                                            |
  --- Segment Group 2 -------------------M - 9999---------+ |
  FII  Financial institution information M    1           | |
  NAD Name and address                   C    10          | |
                                                          | |
  --- Segment Group 3 -------------------M - 9999-------+ | |
  BUS Business function                  M    1         | | |
                                                        | | |
  --- Segment Group 4 -------------------M - 9999 -----+| | |
  LOC Place/location identification      M    10       || | |
                                                       || | |
  --- Segment Group 5 -------------------M - 9999 ---+ || | |
  NAD Name and address                   C    10     | || | |
  COM Communication contact              C    10     | || | |
                                                     | || | |
  --- Segment Group 6 -------------------M - 99999 + | || | |
  IMD Item description                   M    1    | | || | |
  CCI Characteristic/class id            C    10---+-+-++-+-+
  UNT Message trailer                    M    1                  

5.    DIRECTORIES

5.1   Directory References

      Draft standard directory D.93A


5.2   Explanation of directory variations

5.2.1 Segment variations

Note: requests for the following new codes will not form part of
the final document:

-----------------------------------------------------------------

* 3035  Party qualifier

  Desc: Code giving specific meaning to a party.

  Repr: an  3

+          Point of exchange of information, goods, or services.

-----------------------------------------------------------------

* 3039  Party id identification

  Desc: Code identifying a party involved in a transaction.

  Repr: an..3

+         Company
+         Partnership
+         Limited partnership
+         Sole trader
+         Not for profit
+         Government agency

-----------------------------------------------------------------


* 1131  Code list qualifier

  Desc: Identification of a code list.

  Repr: an..3

+         UNCCS (United Nations Common Coding System)

-----------------------------------------------------------------