|
This message is available for formal trial in the present version for a period of at least twelve months from the date of approval by the UN/ECE/TRADE/WP.4. Organisations are invited to trial this message and are requested to notify their Rapporteur Team Secretariat of their intention. Comments on the results from the trial should also be forwarded to the Secretariat as soon as they are available. Based on the results of the trials, a UNSM will be issued. It should be noted that this material is contained in a Trial Directory; however, it may differ from that in the UN Directories (UNTDID) having the same identfying tags. Any differences will be reconciled prior to the message becoming a UNSM. |
| Message Type: | PARTIN |
|---|---|
| Version: | D |
| Release: | 93A |
| Contr. Agency: | UN |
| Status: | 2 |
| Date: | 93-07 |
| SOURCE: | Submitted by WEEB-MD1 on behalf of PAEB |
|
For general information on UN standard message types see UN Trade Data Interchange Directory, UNTDID, Part 4, Section 2.5, 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 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.
The UN Standard Party Information 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.
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 Section 2.5 UN/ECE UNSM - General Introduction, Section 1.
See UNTDID, Part 4, Section 2.5 UN/ECE UNSM - General Introduction, Section 2.
This section should be read in conjunction with the Branching Diagram and the Segment Table which indicate mandatory, conditional and repeating requirements.
A service segment starting and uniquely identifying a message. The message type code for the UN Party Information Message is 'PARTIN'. Note: Party Information Message conforming to this document must contain the following data in UNH, composite S009: Data element 0065 PARTIN 0052 D 0054 93A 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.
UNS, Section control A service segment placed at the start of the detail section to avoid segment collision.
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.
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 service segment ending the message giving the total number of segments in the message and the control reference number of the message.
| ├─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 | ×200000 | (C) |
| │─├─NAD Name and address | ×1 | (M) |
| │─├─DTM Date/time/period | ×5 | (C) |
| │─├─FII Financial institution information | ×10 | (C) |
| │─├─Segment Group 5 | ×20 | (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) |
| └─UNT Message trailer | ×1 | (M) |
| BGM | Beginning of message | |
| COM | Communication contact | |
| CTA | Contact information | |
| DTM | Date/time/period | |
| FII | Financial institution information | |
| FTX | Free text | |
| LOC | Place/location identification | |
| NAD | Name and address | |
| RFF | Reference | |
| SCC | Scheduling conditions | |
| UNH | Message header | |
| UNS | Section control | |
| UNT | Message trailer |