Economic and Social Council

Transcription

1 UNITED NATIONS E Economic and Social Council ECONOMIC COMMISSION FOR EUROPE Distr. RESTRICTED TRADE/WP.4/R June 1995 Working Party on Facilitation of International Trade Procedures (Item 4 of the provisional agenda of the Meeting of Experts on Data Elements and Automatic Data Interchange (GE.1) Fifty-second session, September 1995) ENGLISH ONLY TRADE DATA INTERCHANGE PROTOCOLS Development of United Nations Standard Messages (UNSMs) (Item of the Programme of work) MESSAGE TYPE SUBMITTED AS STATUS 0 FOR INFORMATION PRODUCT INQUIRY MESSAGE (PROINQ) Transmitted by the UN/EDIFACT Rapporteurs* * * *

2 page 2 * The present document is reproduced in the form in which it was received by the secretariat. GE.95- UN/EDIFACT DRAFT DOCUMENT Product Inquiry 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 : PROINQ Version : 0 Release : 1 Contr. Agency: RT

3 page 3 Status : 0 Date : SOURCE: Submitted by WEEB -MD1

4 page 4 CONTENTS Product Inquiry 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 Heading Section Detail Section 4.2 Data Segment Index (Alphabetical Sequence) 4.3 Message Structure 5. DIRECTORIES Segment Table Branching Diagram 5.1 Directory References 5.2 Explanation of Directory Variations Segment Variation Composite Variation Data Element Variation

5 page 5 0. INTRODUCTION This specification provides a proposal for the definition of the United Nations Standard Product Inquiry Message (PROINQ) to be used in Electronic Data Interchange (EDI) between partners involved in administration, commerce and transport. 1. SCOPE 1.1 Functional Definition A message to enabling the sender to inquire or request information on product or group of products from master product catalogue or file according to criteria defined in the message. 1.2 Field of Application The Product Inquiry Message may be applied 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 message usually relates to a manufacturer and/or a supplier of goods and a buyer, or their respective agents. The buyer may specify in the message the specific attributes of a product or group of products for which it is interested in receiving additional information. This will allow a manufacturer and/or supplier to send the buyer only information for those products the customer is specifically interested in rather than the entire product catalogue. The product Inquiry message may request information in order to: - select a specific group or family or products from a supplier entire product catalogue, e.g. a buyer requesting a supplier of medical equipment all product information related to sterilized products. - select a product group of products according to attributes or product characteristics as defined by the sender in the message, e.g. a retailer requesting a clothing manufacturer to send product information for all blue, white or stripped men's shirts, sizes medium to extra-large. determine the availability, lead -time and/or general commercial/sales conditions for a specific product. The response to a Product Inquiry message will be either a Price/sales Catalogue (PRICAT) or Product Data message (PRODAT).

6 page 6 2. REFERENCES See UNTDID, Part 4, Section 2.6, UN/ECE UNSM - General Introduction, Section TERMS AND DEFINITIONS See UNTDID, Part 4, Section 2.6, UN/ECE UNSM - General Introduction, Section MESSAGE DEFINITION 4.1 Data Segment Clarification This section should be read in conjunction with the Branching Diagram and Segment Table which indicate 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. It is only used when additional information that cannot be accommodated within the other segments is required Heading Section Information to be provided in the Heading Section UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the UN Product Inquiry Message is

7 page 7 PROINQ. Note : A Product Inquiry Message conforming to this document must contain the following data in UNH, composite S009: Data element 0065 PROINQ RT 0020 BGM, Beginning of message A segment by which the sender must uniquely identify the Product Inquiry message by means of its number DTM, Date/time/period This segment specifying general dates and, when relevant, times related to the whole message. The Product Inquiry message preparation date must be specified using this segment Segment Group 1: NAD -SG2 A group of segments identifying the parties with associated information relevant to the whole Product Inquiry message NAD, Name and address A segment identifying names and addresses of parties, in coded or clear form, and their functions relevant to the Product inquiry message. Identification of the sender of the report and the recipient is mandatory for the Product Inquiry 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 Segment Group 2: CTA -COM A group of segments giving contact details of the specific person or department within the party identified in NAD segment CTA, Contact information A segment to identify a person or department, and their function, to whom communications should be directed 0080 COM, Communication contact A segment to identify a communications type and number for the contact specified in the CTA segment Segment Group 3: RFF -DTM A group of segments for giving references and where necessary, their dates, relating to the whole message e.g. contract number.

8 page RFF, Reference A segment identifying the reference by its number and where appropriate a line number within the document DTM, Date/time/period A segment specifying the date/time related to the reference Segment Group 4: CUX -DTM A group of segments specifying the currencies and related dates/periods valid for the whole Product Inquiry message. The segment group 4 may be omitted in national applications but will be required for international exchanges CUX, Currencies A segment identifying the currencies specified in the Product Inquiry message e.g. the currency in which the product prices are expressed in. A rate of exchange may be given to convert a reference currency into a target currency DTM, Date/time/period A segment specifying the date/time/period related to the rate of exchange Detail Section Information to be provided in the Detail Section Segment Group 5: IRQ -SG6 A group of segments specifying the type of requested information and product information relevant to the whole Product Inquiry message IRQ, Information required A segment specifying the type of information requested by the Product Inquiry message, e.g. a price/sales catalogue, allowances and charges information, delivery lead times, etc Segment Group 6: LIN -PIA-MEA-NAD-SG7-SG8-SG9 A group of segments identifying the request line in a specific inquiry and optionally product identification(s), measurements, attributes, suppliers, quantity ranges, dates and prices ranges LIN, Line item A segment specifying the inquiry request line and if available, the identification of the product/service for

9 page 9 which the inquiry is being made PIA, Additional product id A segment providing either additional identification to the product specified in the LIN segment or providing a substitute product identification MEA, Measurements A segment specifying the physical measurements for a product NAD, Name and address A segment identifying the name and address of a party related to the product for which an inquiry is being made, e.g. supplier, ultimate customer, etc Segment Group 7: ATT -REL A group of segments identifying the attributes of a product or group of products and relationship between the various attributes ATT, Attribute A segment specifying the attributes type and details for a product or group of products on basis of which a selection of specific items from a product master catalogue or file will be made REL, Relationship A segment specifying the relationship between different attributes within an inquiry request line on the basis of which specific products will be selected from a product data base, e.g. attribute 1 AND attribute 2 OR attribute Segment Group 8: QTY -RNG-DTM A group of segments identifying discrete or range quantities and related dates for the product for which an inquiry is being made QTY, Quantity A segment providing quantity information related to the product identified in the LIN segment or through the attributes specified in the ATT and REL segments, e.g. provisional order quantity, maximum order quantity, etc RNG, Range details A segment providing range information related to the QTY segment, e.g. quantity range between units.

10 page DTM, Date/time/period A segment identifying relevant dates or periods for a product, e.g. availability date, lead time, delivery date, etc Segment Group 9: PRI -RNG A group of segments providing pricing information and price ranges for the product identified in the LIN segment or through the ATT and REL segments PRI, Price details A segment to specify the price type and amount, e.g. proposed purchase price, suggested retail price, etc RNG, Range details A segment to specify range information related to prices, e.g. price range between BEF UNT, Message trailer A service segment ending a message giving the total number of the segments in the message and the control reference number of the message. 4.2 Data Segment Index (Alphabetical Sequence) ATT Attribute BGM Beginning of message COM Communication contact CTA Contact information CUX Currencies DTM Date/time/period IRQ Information required LIN Line item MEA Measurements NAD Name and address PIA Additional product id PRI Price details QTY Quantity REL Relationship RFF Reference RNG Range details UNH Message header UNT Message trailer 4.3 Message Structure

11 page Segment Table POS TAG NAME S R HEADING SECTION 0010 UNH Message header M BGM Beginning of message M DTM Date/time/period C ))))) Segment Group 1 )))))))))))))))))) C 5))))))))))), 0050 NAD Name and address M 1 * * 0060 ))))) Segment Group 2 )))))))))))))))))) C 5)))))))))),* 0070 CTA Contact information M 1 ** 0080 COM Communication contact C 5 )))))))))) ))))) Segment Group 3 )))))))))))))))))) C 5))))))))))), 0100 RFF Reference M 1 * 0110 DTM Date/time/period C 5 ))))))))))) ))))) Segment Group 4 )))))))))))))))))) C 5))))))))))), 0130 CUX Currencies M 1 * 0140 DTM Date/time/period C 5 )))))))))))- POS TAG NAME S R DETAIL SECTION 0150 ))))) Segment Group 5 )))))))))))))))))) M 9999)))))))), 0160 IRQ Information required M 1 * * 0170 ))))) Segment Group 6 )))))))))))))))))) C 9999))))))),* 0180 LIN Line item M 1 ** 0190 PIA Additional product id C 10 ** 0200 MEA Measurements C 10 ** 0210 NAD Name and address C 10 ** ** 0220 ))))) Segment Group 7 )))))))))))))))))) C 99)))))))),** 0230 ATT Attribute M 1 *** 0240 REL Relationship C 1 )))))))))-** ** 0250 ))))) Segment Group 8 )))))))))))))))))) C 10)))))))),** 0260 QTY Quantity M 1 *** 0270 RNG Range details C 1 *** 0280 DTM Date/time/period C 5 )))))))))-** ** 0290 ))))) Segment Group 9 )))))))))))))))))) C 10)))))))),** 0300 PRI Price details M 1 *** 0310 RNG Range details C 1 ))))))))) UNT Message trailer M Branching Diagram

12 page DIRECTORIES 5.1 Directory References Explanation of Directory Variations Segment Variation + IRQ INFORMATION REQUIRED AD Function: To indicate which information is requested in a responding message C887 INFORMATION REQUEST M 7735 Requested information, coded C an Code list qualifier C an Code list responsible agency, coded C an Requested information C an Segment Variation + IRQ INFORMATION REQUIRED AD Function: To indicate which information is requested in a responding message C887 INFORMATION REQUEST M 7735 Requested information, coded C an Code list qualifier C an Code list responsible agency, coded C an Requested information C an Composite Variation + C887 INFORMATION REQUEST AD Desc: To specify the information requested in a responding message 7735 Requested information, coded C an Code list qualifier C an Code list responsible agency, coded C an Requested information C an..35

13 page Data Element Variation Requested information AD Desc: To specify the information requested in a responding message in a clear text form Repr: an Requested information, coded AD Desc: To specify the information requested in a responding message in a coded form. Repr: an..3