| Version: | D |
|---|---|
| Release: | 01A |
| Contr. Agency: | UN |
| Revision: | 6 |
| Date: | 2000-10-26 |
| SOURCE: | D2 Purchasing (SWG) |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.3, UN/ECE UNSM General Introduction |
|
This message also occurs in the following versions of this standard: D93A, D94A, D94B, D95A, D95B, D96A, D96B, D97A, D97B, D98A, D98B, D99A, D99B, D00A, D00B, D01A, D01B, D01C, D02A, D02B, D03A, D03B, D04A, D04B |
This specification 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, confirmation of registration and trading data.
The Party information 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.
The accurate and unambiguous identification of the trading partners and their operational parameters is an essential issue for EDI.
The Party Information Message serves to maintain the partners master data files.
Note: Once the data available in master data files is established:
The Party Information Message is used to specify information related to physical locations and to functional locations. A functional location is usually a specific department within a company.
The change, delete, add indicator being given in the BGM segment, one separate message has to be provided per type of function required.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Chapter 2.3 UN/ECE UNSM - General Introduction, Section 2.
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 'ccyymmdd'/'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.
Information to be provided in the Header section:
A service segment starting and uniquely identifying a message. The message type code for the Party information message is PARTIN.
Note: Party information messages conforming to this document must contain the following data in segment UNH, composite S009:
| Data element | 0065 | PARTIN |
| 0052 | D | |
| 0054 | 01A | |
| 0051 | UN |
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 partner's 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.
A segment specifying general dates, and when relevant, times related to the whole message.
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.
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.
A group of segments indicating reference numbers and optionally date of the reference relating to the whole message.
A segment for referencing documents relating to the whole message, e.g. previously sent PARTIN message number, Interchange Agreement contract.
A segment specifying the date of the reference number indicated in the RFF segment.
A group of segments identifying Names, Addresses, Contacts and Communication numbers relevant to the sender and the receiver of the message.
A segment for identifying the Sender and Receiver name and address.
A group of segments giving details of the specific person or department within the party.
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.
A segment to identify communication numbers of departments or persons related to the contact information provided in CTA.
Information to be provided in the Detail section:
A service segment placed at the start of the detail section to avoid segment collision.
SG9-SG10-SG11-SG12-SG13 A group of segments for giving the details of a party.
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.
A segment specifying the date and the time details relevant to the party information identified in the NAD segment.
A segment identifying the financial institution, (e.g. bank) and relevant account numbers for the party identified in the NAD segment.
This segment is used to indicate an alternative identification of a party.
This segment is used to provide free form or coded text information related to the current party, e.g. a description of the primary activities of a party.
This segment is used to specify duty/tax/fee information related to the current party, e.g. party is exempt from tax.
This segment is used to identify hierarchical connections from a given party to a higher or lower level party.
A group of segments for giving locations and dates relevant to party.
A segment specifying the locations relevant to the party identified in the NAD segment, e.g. internal building number on a site.
A segment specifying dates and times relevant to the LOC segment.
A group of segments for giving references relevant to the party.
A segment for referencing numbers related to the party such as Party Tax Identification Number.
A segment specifying the date of the reference number indicated in the RFF segment.
A group of segments giving contact details of the specific person or department within the party.
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.
A segment to identify communication numbers of departments or persons related to the contact information provided in CTA.
A group of segment specifying schedules related to the party identified in the NAD segment.
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.
A segment indicating the date/time details relevant to the schedule details in the SCC segment. This segment may be used to indicate date/time ranges.
A group of segments specifying the standard terms of delivery.
A segment indicating terms of delivery related to the referenced NAD segment.
A segment specifying location for the referenced terms of delivery.
A group of segments relating to the standard payment instructions, payment terms, the reference and the payment currencies.
A segment giving information on payment instructions.
A segment giving information on the payment terms basis.
A segment giving information on the currencies.
This segment is used to specify dates, and/or times, or periods related to general payment conditions.
This segment is used to specify percentage information related to payment conditions.
This segment is used to specify a monetary amount related to payment conditions.
A group of segments for relating monetary amounts and quantities to requirements and conditions.
A segment to specify a requirement or a condition.
A segment specifying monetary amounts such as annual revenue.
A segment specifying quantities, such as the number of employees.
A group of segments for relating monetary amounts and quantities to characteristics and classes.
A segment to specify a characteristic or a class.
A segment specifying monetary amounts.
A segment specifying quantities.
A segment to further specify party characteristics which apply to the party in the messages.
A segment providing dates/times related to the characteristic identification.
A segment providing measurements related to the characteristic identification.
A group of segments for relating processes, entities and documents.
A segment for identifying a process.
A segment to specify dates/time/periods related to the process or sub-process.
A group of segments for relating a line number and entity to a document.
A segment for specifying a line number.
A segment for citing an entity and a related address.
A group of segments to relate a document and a date.
A segment to cite a document.
A segment to relate a date, such as an effective date or a version date to a document.
A service segment ending a message, giving the total number of segments in the message (including the UNH & UNT) and the control reference number of the message.
| BGM | Beginning of message | |
| CAV | Characteristic value | |
| CCI | Characteristic/class id | |
| COM | Communication contact | |
| CTA | Contact information | |
| CUX | Currencies | |
| DOC | Document/message details | |
| DTM | Date/time/period | |
| FII | Financial institution information | |
| FTX | Free text | |
| HYN | Hierarchy information | |
| IDE | Identity | |
| LIN | Line item | |
| LOC | Place/location identification | |
| MEA | Measurements | |
| MOA | Monetary amount | |
| NAD | Name and address | |
| PAI | Payment instructions | |
|
PAT | Payment terms basis |
| PCD | Percentage details | |
| PRC | Process identification | |
| QTY | Quantity | |
| RCS | Requirements and conditions | |
| RFF | Reference | |
| SCC | Scheduling conditions | |
| TAX | Duty/tax/fee details | |
| TOD | Terms of delivery or transport | |
| UNH | Message header | |
| UNS | Section control | |
| UNT | Message trailer |
| ├─UNH Message header | ×1 | (M) |
| ├─BGM Beginning of message | ×1 | (M) |
| ├─DTM Date/time/period | ×5 | (M) |
| ├─FII Financial institution information | ×10 | (C) |
| ├─FTX Free text | ×5 | (C) |
| ├─Segment Group 1 | ×5 | (C) |
| │─├─RFF Reference | ×1 | (M) |
| │─└─DTM Date/time/period | ×1 | (C) |
| ├─Segment Group 2 | ×2 | (C) |
| │─├─NAD Name and address | ×1 | (M) |
| │─└─Segment Group 3 | ×5 | (C) |
| │───├─CTA Contact information | ×1 | (M) |
| │───└─COM Communication contact | ×5 | (C) |
| ├─UNS Section control | ×1 | (M) |
| ├─Segment Group 4 | ×20000 | (C) |
| │─├─NAD Name and address | ×1 | (M) |
| │─├─DTM Date/time/period | ×5 | (C) |
| │─├─FII Financial institution information | ×10 | (C) |
| │─├─IDE Identity | ×9 | (C) |
| │─├─FTX Free text | ×9 | (C) |
| │─├─TAX Duty/tax/fee details | ×9 | (C) |
| │─├─HYN Hierarchy information | ×9 | (C) |
| │─├─Segment Group 5 | ×99 | (C) |
| │─│─├─LOC Place/location identification | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×2 | (C) |
| │─├─Segment Group 6 | ×15 | (C) |
| │─│─├─RFF Reference | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×1 | (C) |
| │─├─Segment Group 7 | ×5 | (C) |
| │─│─├─CTA Contact information | ×1 | (M) |
| │─│─└─COM Communication contact | ×5 | (C) |
| │─├─Segment Group 8 | ×10 | (C) |
| │─│─├─SCC Scheduling conditions | ×1 | (M) |
| │─│─└─DTM Date/time/period | ×2 | (C) |
| │─├─Segment Group 9 | ×1 | (C) |
| │─│─├─TOD Terms of delivery or transport | ×1 | (M) |
| │─│─└─LOC Place/location identification | ×1 | (C) |
| │─├─Segment Group 10 | ×999 | (C) |
| │─│─├─PAI Payment instructions | ×1 | (M) |
| │─│─├─PAT Payment terms basis | ×1 | (C) |
| │─│─├─CUX Currencies | ×2 | (C) |
| │─│─├─DTM Date/time/period | ×9 | (C) |
| │─│─├─PCD Percentage details | ×9 | (C) |
| │─│─└─MOA Monetary amount | ×9 | (C) |
| │─├─Segment Group 11 | ×999 | (C) |
| │─│─├─RCS Requirements and conditions | ×1 | (M) |
| │─│─├─MOA Monetary amount | ×9 | (C) |
| │─│─└─QTY Quantity | ×9 | (C) |
| │─├─Segment Group 12 | ×999 | (C) |
| │─│─├─CCI Characteristic/class id | ×1 | (M) |
| │─│─├─MOA Monetary amount | ×9 | (C) |
| │─│─├─QTY Quantity | ×9 | (C) |
| │─│─├─CAV Characteristic value | ×9 | (C) |
| │─│─├─DTM Date/time/period | ×9 | (C) |
| │─│─└─MEA Measurements | ×9 | (C) |
| │─└─Segment Group 13 | ×999 | (C) |
| │───├─PRC Process identification | ×1 | (M) |
| │───├─DTM Date/time/period | ×9 | (C) |
| │───└─Segment Group 14 | ×999 | (C) |
| │─────├─LIN Line item | ×1 | (M) |
| │─────├─NAD Name and address | ×1 | (M) |
| │─────└─Segment Group 15 | ×99 | (M) |
| │───────├─DOC Document/message details | ×1 | (M) |
| │───────└─DTM Date/time/period | ×9 | (C) |
| └─UNT Message trailer | ×1 | (M) |
