WPC3' 2PBVTZL#|Q )?xxx,nXx6X@DQX@HP LaserJet IIIPSi MXHPLAIIIP.WRSx  @,4{X@ M' 3'3'Standard6&6&StandardrJet IIIP + USUK#&Q2PQ&P#2:@X+Courier New (TT)Arial (TT)"5@^33Affz#==Gk3=33ffffffffff33kkkfzzzp3\zfzzpzzzp333Vf=ff\ff3ff))\)ffff=\3f\\\\>0>k3====IL=epzfzfzfzfzf\zfzfzfzf33333333fffffffffz\zffpfz\fzfzfzfzf\\\zfzfzfffffffIp=p==3p\z\f)fLfff=Lz\z\N@3cf=pfffffDCf=f=))==f==ff)===t=ddddkoo.Iik2[ffydCpi`vZdfdloPpPi`d}}tro33Affz#==Gk3=33ffffffffff33kkkfzzzp3\zfzzpzzzp333Vf=ff\ff3ff))\)ffff=\3f\\\\>0>k)f=ff=z=))==@f=\=z3=ffff0f=Dfk=eId===ic3==Cfpzzzzzzzzzz3333kzzpffffff\ffff3333fffffffdpffff\f?xxx,nXx6X@DQX@,Q=3,&Q2PQ&P6&StandardrJet IIIP + USUK#&Q22 l Z| @#|Q HP LaserJet IIIPSi MXHPLAIIIP.WRSx  @,4{X@+"5@^33Affz#==Gk3=33ffffffffff33kkkfzzzp3\zfzzpzzzp333Vf=ff\ff3ff))\)ffff=\3f\\\\>0>k3====IL=epzfzfzfzfzf\zfzfzfzf33333333fffffffffz\zffpfz\fzfzfzfzf\\\zfzfzfffffffIp=p==3p\z\f)fLfff=Lz\z\N@3cf=pfffffDCf=f=))==f==ff)===t=ddddkoo.Iik2[ffydCpi`vZdfdloPpPi`d}}tro33Affz#==Gk3=33ffffffffff33kkkfzzzp3\zfzzpzzzp333Vf=ff\ff3ff))\)ffff=\3f\\\\>0>k)f=ff=z=))==@f=\=z3=ffff0f=Dfk=eId===ic3==Cfpzzzzzzzzzz3333kzzpffffff\ffff3333fffffffdpffff\f2u_J L @ @5Courier New (TT)Arial (TT)Courier 10pt (12cpi)Arial (Bold) (TT)Courier New (Bold) (TT) M' 3'3'Standard6&6&StandardHPLAIIIP.WRSx  + USUK#&Q2PQ&P#"5@^8B_oo0BBNu8B88ooooooooooBBuuuzÐz8ozzzB8BuoBozozoBzz88o8zzzzNoBzooodN8Nu8BB!BBPRBnzoooooȲooooo88888888zzzzzzzzzoozzzozzooooooooozzzzzzPzBzBB8zooz8zRzzzȽNRooNF8ooBzoooooJIoBoB88ddoBBoo8dBBtBnnnnuyy2Psu6coonCzshbnonvyXzXshn~|y8B_oo0BBNu8B88ooooooooooBBuuuzÐz8ozzzB8BuoBozozoBzz88o8zzzzNoBzooodN8Nu8odooBȆBȖ88ddFoBoB8Boooo8oBJouBnPnBBBso8BBIozȐ8888uzooooooooooo8888zzzzzzznzzzzzoz"5@^ANoШ8NN[ANAANN䨨AèܜNANNNAAAЏ[Nu[A[ANN'NN]`NШAAAAAAAA]NNNAA`ܨ[`NQANVUÁNNAAuuNNAuNNtN捍:]@tCzsffzANoШ8NN[ANAANN䨨AèܜNANNNAAAЏ[Nu[A[Au遁NN鯯AAuuQNNܯANANVN]NNNANNUÏ騜AAAAЁAAAA2&^^@c \#"H^^hx$$$$2hhhhN2hh2hNhN2hNNN2$222222222$S2hhhhhhNNNNh22222h2h2h2h2Nhh222Nh2N2hhhhhhNNN2222h2h2222h22h2h22hhNNN2qqt$.. }$e IC2hhBh(.2Z~hVV<e7.wwwwwwwwwwwwwwwwwwwwwwwwwwwwww whx$$$$2hhhhN2hh2hNhN2hNNN2$222222222$wwwNwwwwwwNq$q2hhhhhhhNNNNhh$hhhhNN22222222222222"H^^Td HdduTdTTdd%TdTdddTTT uduTuTdd2ddx|d, TTTTTTTTxdddTT|,u|NiTdonddTT,dd,,T,ddtd(9KxR(9CTd HdduTdTTdd%TdTdddTTT uduTuT,d,d,TTi,d,dTdTdodxdddTddn,TTTT TTTT"5@^//;\\o 77Aa/7//\\\\\\\\\\//aaa\ooxxofx/To\xoxofxooof///N\7\\T\\/\\%%T%\\\\7T/\TxTTT8+8a/7777BE7\fo\o\o\o\o\xTo\o\o\o\////////x\\\\\x\x\x\x\oTo\x\f\oTx\o\o\o\o\xTxTxTo\o\o\\\\\x\x\Bf7f77/fToT\%\Ex\x\\x7xEoToTN:/Z\7f\\\\\==\7{{\7%%77\77\\%777t7[[[[aee*B`a-wS\\n[Cfx`xWkRx[\[ceIfIs`Wx[rriwhe}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}//;\\o 77Aa/7//\\\\\\\\\\//aaa\ooxxofx/To\xoxofxooof///N\7\\T\\/\\%%T%\\\\7T/\TxTTT8+8a}}}%\7\\7o7}}}}%%77:\7T7}}o/7\\\\+\7{=\a7{\B[777`Z/77=\fooooooxoooo////xxaxxxxoof\\\\\\T\\\\////\\\\\\\[f\\\\T\?xxx,nXx6X@DQX@,Q=3,&Q2PQ&P s5ddd,`d6X@?BQ@&/`C8,3(&X`2p NQX&6pNA,3p2p NQ&u,32p NQ&GdT,3X.2p NQ~)J8/,vJ2PQPs5eee,Fe `NQs4ddd,fd6X@DQ@21' W4  R qV s54 + X` hp x (#%'0*,.8135@8:44  yL /?dddjy#J2PQvP# i  ++fECONOMIC COMMISSION FOR EUROPE  s5 4 ?7+  ++3 Kb #d6X@?BQ`@# Distr. RESTRICTED TRADE/WP.4/R.1183/Rev.1 17 January 1996  ENGLISH ONLY  s5X 4. ++    ++b ++ Rb  COMMITTEE ON THE DEVELOPMENT OF TRADE  s54Working Party on the Facilitation of International Trade Procedures  s54(Item 6 of the provisional agenda of the Meeting of Experts on Data Elements and Automatic Data Interchange (GE.1)  s54fiftythird session, 1819 March 1996)  s54  s5[4D3 TRADE DATA INTERCHANGE PROTOCOLS  s54   s54  Development of United Nations Standard Messages (UNSMs)  s5S4 ( (Item 3.2.15 of the Programme of work)   s5K4  MESSAGE TYPE SUBMITTED AS STATUS 0 FOR INFORMATION   s54  PRODUCT SOURCE INFORMATION MESSAGE (PRDSRC)  . Transmitted by the UN/EDIFACT Rapporteurs *  * * *     f+ __________________________________________________________________________ * The present document is reproduced in the form in which it was received by the secretariat. + -,,RR0@e?`$h?`==t=dddd?$?j[  s44 1 H  bb  1 H =PtTRADE/WP.4/R.1183/Rev.1 page = 6&6&StandardHPLAIIIP.WRSx  6&6&StandardHPLAIIIP.WRSx  ++b #d6X@DQ f@#    s44m UN/EDIFACT   s4/4  s44]DRAFT DOCUMENT  s4u4   s44  Product source information message  s4^4f+  s44  s4 4 ---------------------------------------------------------------------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  s4H4Section 5 (or, in some cases, which should have been shown in Section 5 -  s44directory 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  s4(4 "c),)*4"ԌSource: Submitted by X12E GN=+b +b ++bb TRADE/WP.4/R.1183/Rev.1 bb page G  s44q CONTENTS    Product source information message b  s44f+  s44  s4^40. INTRODUCTION  s4G4 1. SCOPE 1.1 Functional definition 1.2 Field of application 1.3 Principles  s4 4 2. REFERENCES  s4_ 4  s44 3. TERMS AND DEFINITIONS 4. MESSAGE DEFINITION  s44 4.1 Data segment clarification  s44  s44 4.2 Data segment index (alphabetical sequence) 4.3 Message structure 4.3.1 Segment table  s424 5. DIRECTORIES 5.1 Directory references 5.2 Explanation of directory variations  s44 5.2.1 Segment variations "J,)*`%"  s44 0. INTRODUCTION  s44  s4F4This 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.  s4/4 1. SCOPE  s4u4 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). ",**("  s44 2. REFERENCES  s44 See UNTDID, Part 4, Section 2.6, UN/ECE UNSM - General Introduction, Section 1.  s44 3. TERMS AND DEFINITIONS See UNTDID, Part 4, Section 2.6, UN/ECE UNSM - General Introduction, Section 2.  s44 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. 7bbThe message type code for the Product source information Message is !!'PRDSRC'.#b 7bbNote: Product source information messages conforming to this document must contain the following data in segment UNH, composite S009:#b Data element 0065 PRDSRC 0052 0 0054 1 0051 51    0020 BGM, Beginning of message 7bbA segment for the unique identification of the document name and number.#b 0030 Segment group 1: FII-DTM-SG2 7bbA group of segments indicating the date and source of the information.#b 0040 FII, Financial institution information 7bbA segment identifying the organization responsible for the creation of the information.#b 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. 7bbFor the purposes of this message, this segment should not be used to communicate address information.#b 0090 Segment group 3: BUS-SG4 7bbA group of segments identifying the functions performed at a facility.#b 0100 BUS, Business function 7bbA segment identifying the function performed at a facility, e.g., warehousing, retail, manufacturing, service, support.#b 0110 Segment group 4: LOC-SG4 A group of segments identifying the facilities."),**4"Ԍ0120 LOC, Place/location identification 7bbA segment identifying the physical location from which an organization performs a function.#b 0130 Segment group 5: NAD-COM-SG6 7bbA group of segments identifying the point of contact where information, goods or services can be exchanged, e.g. postal address, telephone, electronic mail.#b 0140 NAD, Name and address 7bbA 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.#b 0150 COM, Communication contact 7bbA segment identifying a communication number of a point of contact.#b 0160 Segment group 6: IMD-CCI 7bbA group of segments identifying a product and its characteristics.#b 0170 IMD, Item description A segment for identifying a product by its UNCCS code. 7bbIn composite C273, data element 7009 is required to contain a valid United Nations Common Code.#b 0180 CCI, Characteristic/class id A segment used to describe distinctive properties of a product. 0190 UNT, Message trailer 7bbA service segment ending the message giving the total number of segments in the message and the control reference number of the message.#b ",**" 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 ",**`%"  s44 6&6&StandardHPLAIIIP.WRSx  6&6&StandardHPLAIIIP.WRSx  ++b 5. DIRECTORIES  s44 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) ---------------------------------------------------------------------