D96A
Message D96A/PARTIN
Party information message
A message to enable the transmission of basic information regarding locations and the related operational, administrative, financial, manufacturing and trading data.
Message description
UNH
M(1) : Message headerA 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 96A 0051 UN
BGM
M(1) : Beginning of messageA 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.
DTM
M(5) : Date/time/periodA segment specifying general dates, and when relevant, times related to the whole message.
FII
C(10) : Financial institution informationA 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
C(5) : Free textA 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.
SG1 C(5) : RFF-DTM
A group of segments indicating reference numbers and optionally date of the reference relating to the whole message.
RFF
M(1) : ReferenceA segment for referencing documents relating to the whole message, e.g. previously sent PARTIN message number, Interchange Agreement contract.
DTM
C(1) : Date/time/periodA segment specifying the date of the reference number indicated in the RFF segment.
SG2 C(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
M(1) : Name and addressA segment for identifying the Sender and Receiver name and address.
SG3 C(5) : CTA-COM
A group of segments giving details of the specific person or department within the party.
CTA
M(1) : Contact informationA 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
C(5) : Communication contactA segment to identify communication numbers of departments or persons related to the contact information provided in CTA.
UNS
M(1) : Section controlA service segment placed at the start of the detail section to avoid segment collision.
SG4 C(200000) : NAD-DTM-FII-SG5-SG6-SG7-SG8-SG9-SG10
A group of segments for giving the details of a party.
NAD
M(1) : Name and addressA 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
C(5) : Date/time/periodA segment specifying the date and the time details relevant to the party information identified in the NAD segment.
FII
C(10) : Financial institution informationA segment identifying the financial institution, (e.g. bank) and relevant account numbers for the party identified in the NAD segment.
SG5 C(99) : LOC-DTM
A group of segments for giving locations and dates relevant to party.
LOC
M(1) : Place/location identificationA segment specifying the locations relevant to the party identified in the NAD segment, e.g. internal building number on a site.
DTM
C(2) : Date/time/periodA segment specifying dates and times relevant to the LOC segment.
SG6 C(15) : RFF-DTM
SG7 C(5) : CTA-COM
A group of segments giving contact details of the specific person or department within the party.
CTA
M(1) : Contact informationA 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
C(5) : Communication contactA segment to identify communication numbers of departments or persons related to the contact information provided in CTA.
SG8 C(10) : SCC-DTM
A group of segment specifying schedules related to the party identified in the NAD segment.
SCC
M(1) : Scheduling conditionsA 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
C(2) : Date/time/periodA 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.
SG9 C(1) : TOD-LOC
SG10 C(1) : PAI-PAT-CUX
A group of segments relating to the standard payment instructions, payment terms, the reference and the payment currencies.
PAI
M(1) : Payment instructionsA segment giving information on payment instructions.
PAT
C(1) : Payment terms basisA segment giving information on the payment terms basis.
CUX
C(2) : CurrenciesA segment giving information on the currencies.
UNT
M(1) : Message trailerA service segment ending a message, giving the total number of segments in the message and the control reference number of the message.
Message structure
UNH, Message header M 1
BGM, Beginning of message M 1
DTM, Date/time/period M 5
FII, Financial institution information C 10
FTX, Free text C 5
--- Segment Group 1 ------------------------- C 5 -------+
RFF, Reference M 1 |
DTM, Date/time/period C 1 |
---- -----------------------------------------------------------+
--- Segment Group 2 ------------------------- C 2 -------+
NAD, Name and address M 1 |
|
--- Segment Group 3 ------------------------- C 5 ------+|
CTA, Contact information M 1 ||
COM, Communication contact C 5 ||
---- ----------------------------------------------------------++
UNS, Section control M 1
--- Segment Group 4 ------------------------- C 200000 -------+
NAD, Name and address M 1 |
DTM, Date/time/period C 5 |
FII, Financial institution information C 10 |
|
--- Segment Group 5 ------------------------- C 99 ------+|
LOC, Place/location identification M 1 ||
DTM, Date/time/period C 2 ||
---- ----------------------------------------------------------+|
|
--- Segment Group 6 ------------------------- C 15 ------+|
RFF, Reference M 1 ||
DTM, Date/time/period C 1 ||
---- ----------------------------------------------------------+|
|
--- Segment Group 7 ------------------------- C 5 ------+|
CTA, Contact information M 1 ||
COM, Communication contact C 5 ||
---- ----------------------------------------------------------+|
|
--- Segment Group 8 ------------------------- C 10 ------+|
SCC, Scheduling conditions M 1 ||
DTM, Date/time/period C 2 ||
---- ----------------------------------------------------------+|
|
--- Segment Group 9 ------------------------- C 1 ------+|
TOD, Terms of delivery or transport M 1 ||
LOC, Place/location identification C 1 ||
---- ----------------------------------------------------------+|
|
--- Segment Group 10 ------------------------ C 1 ------+|
PAI, Payment instructions M 1 ||
PAT, Payment terms basis C 1 ||
CUX, Currencies C 2 ||
---- ----------------------------------------------------------++
UNT, Message trailer M 1