© 2018 ProgM

Nachricht PARTIN: D

NamePARTIN
VersionD
Release18B
BeschreibungParty information message

Elemente

SegmentEbeneBeschreibungOpt/Mand.
UNH0A 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 D B UNMandatory
BGM0A 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.Mandatory
DTM0A segment specifying general dates, and when relevant, times related to the whole message.Mandatory
FII0A 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.Optional
FTX0A 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.Optional
SG10SG1Optional
RFF1A segment for referencing documents relating to the whole message, e.g. previously sent PARTIN message number, Interchange Agreement contract.Mandatory
DTM1A segment specifying the date of the reference number indicated in the RFF segment.Optional
SG20SG2Optional
NAD1A segment for identifying the Sender and Receiver name and address.Mandatory
SG31SG3Mandatory
CTA2A segment giving additional contact information relating to the party specified in the NAD segment, e.g. contact person or department in a particular function.Mandatory
COM2A segment to identify communication numbers of departments or persons related to the contact information provided in CTA.Optional
UNS0A service segment placed at the start of the detail section to avoid segment collision.Mandatory
SG40SG4Mandatory
NAD1A 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.Mandatory
DTM1A segment specifying the date and the time details relevant to the party information identified in the NAD segment.Optional
FII1A segment identifying the financial institution, (e.g. bank) and relevant account numbers for the party identified in the NAD segment.Optional
IDE1This segment is used to indicate an alternative identification of a party.Optional
FTX1This 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.Optional
TAX1This segment is used to specify duty/tax/fee information related to the current party, e.g. party is exempt from tax.Optional
HYN1This segment is used to identify hierarchical connections from a given party to a higher or lower level party.Optional
SG51SG5Optional
LOC2A segment specifying the locations relevant to the party identified in the NAD segment, e.g. internal building number on a site.Mandatory
DTM2A segment specifying dates and times relevant to the LOC segment.Optional
SG61SG6Optional
RFF2A segment for referencing numbers related to the party such as Party Tax Identification Number.Mandatory
DTM2A segment specifying the date of the reference number indicated in the RFF segment.Optional
SG71SG7Optional
CTA2A segment giving additional contact information relating to the party specified in the NAD segment, e.g. contact person of department in a particular function.Mandatory
COM2A segment to identify communication numbers of departments or persons related to the contact information provided in CTA.Optional
SG81SG8Optional
SCC2A 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.Mandatory
DTM2A 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.Optional
SG91SG9Optional
TOD2A segment indicating terms of delivery related to the referenced NAD segment.Mandatory
LOC2A segment specifying location for the referenced terms of delivery.Optional
SG101SG10Optional
PAI2A segment giving information on payment instructions.Mandatory
PYT2A segment giving information on the payment terms basis.Optional
CUX2A segment giving information on the currencies.Optional
DTM2This segment is used to specify dates, and/or times, or periods related to general payment conditions.Optional
PCD2This segment is used to specify percentage information related to payment conditions.Optional
MOA2This segment is used to specify a monetary amount related to payment conditions.Optional
SG111SG11Optional
RCS2A segment to specify a requirement or a condition.Mandatory
MOA2A segment specifying monetary amounts such as annual revenue.Optional
QTY2A segment specifying quantities, such as the number of employees.Optional
SG121SG12Optional
CCI2A segment to specify a characteristic or a class.Mandatory
MOA2A segment specifying monetary amounts.Optional
QTY2A segment specifying quantities.Optional
CAV2A segment to further specify party characteristics which apply to the party in the messages.Optional
DTM2A segment providing dates/times related to the characteristic identification.Optional
MEA2A segment providing measurements related to the characteristic identification.Optional
SG131SG13Optional
PRC2A segment for identifying a process.Mandatory
DTM2A segment to specify dates/time/periods related to the process or sub-process.Optional
SG142SG14Optional
LIN3A segment for specifying a line number.Mandatory
NAD3A segment for citing an entity and a related address.Mandatory
SG153SG15Mandatory
DOC4A segment to cite a document.Mandatory
DTM4A segment to relate a date, such as an effective date or a version date to a document.Optional
UNT0A 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.Mandatory