BS-EN-1685-1996.pdf
BRITISH STANDARD BS EN 1685:1996 EDI Message Party information message (PARTIN) The European Standard EN 1685:1995 has the status of a British Standard ICS 35.240.60 Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS EN 1685:1996 This British Standard, having been prepared under the direction of the Information Systems Technology Assembly, was published under the authority of the Standards Board and comes into effect on 15 July 1996 © BSI 01-2000 The following BSI references relate to the work on this standard: Committee reference IST/14 Draft for comment 94/647661 DC ISBN 0 580 25742 8 Committees responsible for this British Standard The preparation of this British Standard was entrusted to Technical Committee IST/14, Electronic Data Interchange, upon which the following bodies were represented: Association for Payment Clearing Services (APACS) British Telecommunications plc CCTA (the Government Centre for Information Systems) Computing Services and Software Association EDI Association NHS (Information Management Centre) NHS (Management Executive) PC Security Ltd. Simpler Trade Procedures Board Co-opted members Amendments issued since publication Amd. No.DateComments Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS EN 1685:1996 © BSI 01-2000i Contents Page Committees responsibleInside front cover National forewordii Foreword2 Text of EN 16853 Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS EN 1685:1996 ii © BSI 01-2000 National foreword This British Standard has been prepared by Technical Committee IST/14 and is the English language version of EN 1685:1995, EDI Message Party information message (PARTIN), published by the European Committee for Standardization (CEN). This British Standard is published under the direction of the Information Systems Technology Assembly whose Technical Committee IST/14 has the responsibility to: aid enquirers to understand the text; present to the responsible international/European committee any enquiries on interpretation, or proposals for change, and keep UK interests informed; monitor related international and European developments and promulgate them in the UK. NOTEInternational and European Standards, as well as overseas standards, are available from Customer Services, BSI, 389 Chiswick High Road, London, W4 4AL. A British Standard does not purport to include all the necessary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii, the EN title page, pages 2 to 8 and a back cover. This standard has been updated (see copyright date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover. Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM EN 1685 August 1995 ICS 35.240.60 Descriptors: Information interchange, data transfer, data transmission, messages, information, files, common transaction language English version EDI Message Party information message (PARTIN) EDI Message Information sur des intervenants (PARTIN) EDI Nachricht Partnerstammdaten (PARTIN) This European Standard was approved by CEN on 1995-05-27. CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CEN member. This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN member into its own language and notified to the Central Secretariat has the same status as the official versions. CEN members are the national standards bodies of Austria, Belgium, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and United Kingdom. CEN European Committee for Standardization Comité Européen de Normalisation Europäisches Komitee für Normung Central Secretariat: rue de Stassart 36, B-1050 Brussels © 1995 All rights of reproduction and communication in any form and by any means reserved in all countries to CEN and its members Ref. No. EN 1685:1995 E Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI EN 1685:1995 © BSI 01-2000 2 Foreword This European Standard has been taken over by CEN from the Western European EDIFACT Board in the UN/EDIFACT context. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by February 1996, and conflicting national standards shall be withdrawn at the latest by February 1996. According to CEN/CENELEC Internal Regulations, the following countries are bound to implement this European Standard: Austria, Belgium, Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and the United Kingdom. This message standard shall be used in conjunction with EN 1475:1995 Supporting Directory based on UN/EDIFACT D.93A Directory. For reference to codes (which are not part of this or any other standard) refer to WE/EB Secretariat ECE DG III B/5, rue de la Loi 200, 1049 Brussels. This standard is technically identical to the corresponding UN/EDIFACT recommendation. Contents Page Foreword2 1Scope3 2Normative references3 3Definitions3 4Requirements3 4.1Data segment clarification3 4.1.1 Header section3 4.1.2 Detail section4 4.2Message structure5 4.2.1 Branching diagram5 4.2.2 Segment table6 4.3Data segment index7 Annex A (informative) Additional information8 A.1Field of application8 A.2Principles8 Table 1 Segment table6 Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI EN 1685:1995 © BSI 01-20003 1 Scope This message provides the definition of the Party Information Message (PARTIN) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. A message to enable the transmission of basic information regarding locations and the related operational, administrative, financial, manufacturing and trading data. 2 Normative references This standard incorporates by dated or undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this standard only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies. UNTDID UN Trade Data Interchange Directory, Issue UN/ECE/TRADE/WP.4/R.1016, Part 4, UN/ECE UNSM General Introduction1). 3 Definitions For the purposes of this standard, the following definitions apply: UNTDID (see normative reference). 4 Requirements 4.1 Data segment clarification This section should be read in conjunction with the branching diagram and 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. 4.1.1 Header section Information to be provided in the header section. UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the UN Party Information Message is “PARTIN”. NOTEParty Information Message conforming to this document must contain the following data in UNH, composite S009: BGM, Beginning of message A segment for unique identification of the document name and number. The message function code (DE 1225) applies to all transactions indicated in the message. Consequently, one separate message has to be provided per type of function required. The following rules apply. Addition (DE 1225 = 2). This code is used for providing information about parties for the first time to the trading partner. Deletion (DE 1225 = 3). This code is used to delete parties from the partners master file; in case of deletion, only the NAD segments need to be sent in the detail section. Change (DE 1225 = 4). This code is used to modify any information relevant to parties already known by the trading partner. All the segments relating to the party including the address to be modified need to be sent. Confirmation (DE 1225 = 6). This code is used when party information is sent again for confirmation. DTM, Date/time/period A segment specifying general dates, and when relevant, times related to the whole message. FII, Financial institution information 1) Information about sources of supply can be obtained from WE/EB Secretariat CEC DG III B/5, rue de la Loi 200, 1049 Brussels. Data element0065PARTIN 0052D 005493A 0051UN Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI EN 1685:1995 4 © BSI 01-2000 A segment identifying the financial institution (e.g. bank) and relevant account numbers valid for all the parties described in the detail section of the message. 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. Segment Group 1: RFF-DTM A group of segments indicating reference numbers and optionally date of the reference relating to the whole message. RFF, Reference A segment for referencing documents relating to the whole message, e.g. previously sent PARTIN message number, Interchange Agreement contract. DTM, Date/time/period A segment specifying the date of the reference number indicated in the RFF segment. Segment Group 2: NAD-SG3 A group of segments identifying names, addresses, contacts and communication numbers relevant to the sender and the receiver of the message. NAD, Name and address A segment for identifying the sender and receiver name and address. Segment Group 3: CTA-COM A group of segments giving details of the specific person or department within the party. CTA, Contact information A segment giving additional contact information relating to the party specified in the NAD segment, e.g. contact person or department in a particular function. COM, Communication contact A segment to identify communication numbers of departments or persons related to the contact information provided in CTA. 4.1.2 Detail section Information to be provided in the detail section. UNS, Section control A service segment placed at the start of the detail section to avoid segment collision. Segment Group 4: NAD-DTM-FII-SG5-SG6-SG7-SG8 A group of segments for giving the details of a party. NAD, Name and address A segment for identifying the party identification code and the corresponding function, name and address. The party identification code is mandatory, and the structured address form is preferred. DTM, Date/time/period A segment specifying the date and the time details relevant to the party information identified in the NAD segment. FII, Financial institution information A segment identifying the financial institution (e.g. bank), and relevant account numbers for the party identified in the NAD segment. Segment Group 5: LOC-DTM A group of segments for giving locations and dates relevant to party. LOC, Place/location identification A segment specifying the locations relevant to the party identified in the NAD segment, e.g. internal building number on a site. DTM, Date/time/period A segment specifying dates and times relevant to the LOC segment. Segment Group 6: RFF-DTM A group of segments for giving references relevant to the party. RFF, Reference A segment for referencing numbers related to the party such as Party Tax Identification Number. DTM, Date/time/period A segment specifying the date of the reference number indicated in the RFF segment. Segment Group 7: CTA-COM A group of segments giving contact details of the specific person or department within the party. CTA, Contact information A segment giving additional contact information relating to the party specified in the NAD segment, e.g. contact person of department in a particular function. COM, Communication contact A segment to identify communication numbers of departments or persons related to the contact information provided in CTA. Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI EN 1685:1995 © BSI 01-20005 Segment Group 8: SCC-DTM A group of segments specifying schedules related to the party identified in the NAD segment. SCC, Scheduling conditions A segment specifying the type and status of the schedule being given, and optionally defining a pattern to be established, e.g. firm or proposed schedule for a weekly pattern of delivery hours. DTM, Date/time/period A segment indicating the date/time details relevant to the schedule details in the SCC segment. This segment may be used to indicated date/time ranges. 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 Message structure 4.2.1 Branching diagram (informative) NOTENot part of this European Standard. Licensed Copy: sheffieldun sheffieldun, na, Fri Nov 17 07:59:43 GMT+00:00 2006, Uncontrolled Copy, (c) BSI EN 1685:1995 6 © BSI 01-2000 4.2.2 Segment table Table 1 Segment table Licensed Copy: sheffieldun sheff
