PARTIN Party information

TBG1 Supply Chain

A message to enable the transmission of basic information regarding locations and the related operational, administrative, financial, manufacturing, confirmation of registration and trading data.

Send feedback Share via email

Header

Position
Segment
Name
Max use

  1. 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 17A 0051 UN

    1. Data element S009/0057 is retained for upward compatibility. The use of
    S016 and/or S017 is encouraged in preference.
    2. The combination of the values carried in data elements 0062 and S009 shall
    be used to identify uniquely the message within its group (if used) or if
    not used, within its interchange, for the purpose of acknowledgement.

  2. 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.

  3. A segment specifying general dates, and when relevant, times related to the whole message.

  4. 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.

  5. 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.

  6. Segment group 1
    Repeat 5

    1. A segment for referencing documents relating to the whole message, e.g. previously sent PARTIN message number, Interchange Agreement contract.

    2. A segment specifying the date of the reference number indicated in the RFF segment.

  7. Segment group 2
    Repeat 2

    1. A segment for identifying the Sender and Receiver name and address.

    2. Segment group 3
      Repeat 5

      1. 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.

      2. A segment to identify communication numbers of departments or persons related to the contact information provided in CTA.

Detail

Position
Segment
Name
Max use

  1. A service segment placed at the start of the detail section to avoid segment collision.

  2. Segment group 4
    Repeat 200000

    1. 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.

    2. A segment specifying the date and the time details relevant to the party information identified in the NAD segment.

    3. A segment identifying the financial institution, (e.g. bank) and relevant account numbers for the party identified in the NAD segment.

    4. This segment is used to indicate an alternative identification of a party.

    5. 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.

    6. This segment is used to specify duty/tax/fee information related to the current party, e.g. party is exempt from tax.

    7. This segment is used to identify hierarchical connections from a given party to a higher or lower level party.

    8. Segment group 5
      Repeat 99

      1. A segment specifying the locations relevant to the party identified in the NAD segment, e.g. internal building number on a site.

      2. A segment specifying dates and times relevant to the LOC segment.

    9. Segment group 6
      Repeat 15

      1. A segment for referencing numbers related to the party such as Party Tax Identification Number.

      2. A segment specifying the date of the reference number indicated in the RFF segment.

    10. Segment group 7
      Repeat 5

      1. 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.

      2. A segment to identify communication numbers of departments or persons related to the contact information provided in CTA.

    11. Segment group 8
      Repeat 10

      1. 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.

      2. 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.

    12. Segment group 9
      Repeat 1

      1. A segment indicating terms of delivery related to the referenced NAD segment.

      2. A segment specifying location for the referenced terms of delivery.

    13. Segment group 10
      Repeat 999

      1. A segment giving information on payment instructions.

      2. A segment giving information on the payment terms basis.

      3. A segment giving information on the currencies.

      4. This segment is used to specify dates, and/or times, or periods related to general payment conditions.

      5. This segment is used to specify percentage information related to payment conditions.

      6. This segment is used to specify a monetary amount related to payment conditions.

    14. Segment group 11
      Repeat 999

      1. A segment to specify a requirement or a condition.

      2. A segment specifying monetary amounts such as annual revenue.

      3. A segment specifying quantities, such as the number of employees.

    15. Segment group 12
      Repeat 999

      1. A segment to specify a characteristic or a class.

      2. A segment specifying monetary amounts.

      3. A segment specifying quantities.

      4. A segment to further specify party characteristics which apply to the party in the messages.

      5. A segment providing dates/times related to the characteristic identification.

      6. A segment providing measurements related to the characteristic identification.

    16. Segment group 13
      Repeat 999

      1. A segment for identifying a process.

      2. A segment to specify dates/time/periods related to the process or sub-process.

      3. Segment group 14
        Repeat 999

        1. A segment for specifying a line number.

        2. A segment for citing an entity and a related address.

        3. Segment group 15
          Repeat 99

          1. A segment to cite a document.

          2. A segment to relate a date, such as an effective date or a version date to a document.

  3. 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.

    1. 0062, the value shall be identical to the value in 0062 in the
    corresponding UNH segment.
Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.