Type = API Reference,; Topic = Multienterprise Information Network Tower (MINT),;Persona = TraceLink Administrator, User,; Orchestration = Manufacturing, Logistics, Commerce,; Function = Supply Chain, IT, Procurement,

Price authorization acknowledgment transactions

The price authorization acknowledgment transaction, is used by manufacturers or suppliers to electronically communicate pricing decisions to distributors, resellers, or buying groups. Price authorization acknowledgment transaction is sent after a pricing agreement or contract has been established. It provides a standardized format to confirm whether a price request has been accepted, rejected, or modified, along with details such as pricing terms, reason codes, and any additional instructions. Upon receiving the Price Authorization Acknowledgment, the distributor acknowledges receipt with an functional acknowledgment, confirming successful processing within their EDI system. By automating this exchange, the Price Authorization Acknowledgment improves communication speed, accuracy, and transparency between trading partners. It helps reduce manual errors, supports faster decision-making, and integrates seamlessly with other EDI documents like purchase orders, acknowledgments, and invoices. As part of a broader digital supply chain strategy, the Price Authorization Acknowledgment plays a vital role in ensuring timely and accurate pricing updates across the procurement and distribution process.

Price authorization acknowledgment (X12)

The Price authorization acknowledgment X12 message maintains a record of the transaction details and metadata from the message payload that can be used for searching and troubleshooting.

Contact your TraceLink Services representative for more information about integrating with this message.

  • Message Type: MPC_PRICE_AUTHORIZATION_ACKNOWLEDGMENT
  • X12 Format: X12 845
  • Transform Names:

    • B2B_EDI_X12_845_PriceAuthorizationAcknowledgment_IB_V1

    • B2B_EDI_X12_845_PriceAuthorizationAcknowledgment_OB_V1

Input Element             Occurs Length Description Example Output Element Testing Notes
845             1…1 - X12 845 Price authorization Acknowledgment. - - -
  ISA           1…1 - ISA interchange envelope. - - -
    ISA01         1…1 2/2 Qualifier for authorization control number in ISA02. 00 authorizationInformationType -
    ISA02         1…1 10/10 Information used for additional identification or authorization of the interchange sender or the data in the interchange/ 10 spaces a valid entry. - authorizationInformationValue -
    ISA03         1…1 2/2 Qualifier for security information in ISA04. 00 securityInformationType -
    ISA04         1…1 10/10 Identifies security information about the interchange sender or data. - securityInformationValue -
    ISA05         1…1 2/2

Interchange sender partner ID qualifier.

07 ediEnvelopePartyType -
    ISA06         1…1 15/15

Interchange sender identification mapping to:

  • fileSenderNumber with party type defined in ISA05.

  • linkIdentifier

  • x12InterchangeControlEnvelope for sender in X12 control file header

 7777776067344 fileSenderNumber -
    ISA07         1…1 2/2

Interchange receiver partner ID qualifier.

01 ediEnvelopePartyType -
    ISA08         1…1 15/15 EDI receiver ID mapping to file control header and to ServiceLinkId. 888888404358877 fileReceiverNumber -
    ISA09         1…1 6/6 Interchange date in 6 char YYMMDD format 231020 fileDateTime -
    ISA10         1…1 4/4 Interchange time in 4 char HHMM format 1420 - -
    ISA11         1…1 1/1

This value is dependent on X12 version. Version 4012 and earlier, this is the interchange control standards identifier. Valid value is U.

Version 4020 and later, this is the repetition separator, a delimiter that separates repeated occurrences of a data element or composite data structure, which must be different than the data element separator, component separator, and segment terminator."

 ^ repetitionSeparator -
    ISA12         1…1 5/5 Interchange control version number. This could be any X12 version. 00501 interchangeControlVersion -
    ISA13         1…1 9/9

Interchange Control Number mapping to:

  • file control header

  • X12 control file header interchangeControlIdentifier.

 0000000000619827 fileControlNumber -
    ISA14         1…1 1/1

Interchange level acknowledgment requested.

Valid values:

  • 0 - No acknowledgment requested

  • 1 - Interchange level acknowledgment requested

 0 isAcknowledgmentRequired -
    ISA15         1…1 1/1

Indicates whether the interchange is for production, test, or information purposes.

Valid values:

  • I - Information

  • P - Production data

  • T - Test data

 P usageIndicator -
    ISA16         1…1 1/1 Component element separator. Delimiter that separates data elements within a composite data structure. Must be different than the data element separator and segment terminator > componentSeparator -
  GS           1…* - GS group functional envelope. Child of ISA. Only one GS group expected per interchange. - - -
    GS01         1…1 2/2

GS group function code.

Valid value is PA - Price Authorization Acknowledgment X12 845

 PA - -
    GS02         1…1 2/15 Application Sender's Code. 2222224043588 groupSenderNumber -
    GS03         1…1 2/15 Application Receiver's Code. TRACELINK groupReceiverNumber -
    GS04         1…1 8/8 Current date stamp in 8 char X12 date format YYYYMMDD. 20241020 groupDate -
    GS05         1…1 4/8 Current time stamp in 6 char X12 time format HHMMSS. 142000 groupTime -
    GS06         1…1 1/9 Group Control ID Number. 619827 groupControlNumber -
    GS07         1…1 1/2

Responsible Agency Code.

Valid values:

  • T - Transportation Data Coordinating Committee (TDCC)

  • X - Accredited Standards Committee X12

 X x12AgencyCode -
    GS08         1…1 1/12 X12 message version code. This could be any X12 version. 005010 ediMessageVersionCode -
  ST           1…* - ST transaction set envelope. Child of GS group. Only one ST transaction expected. - - -
    ST01         1…1 3/3 Transaction set identifier code. 845 - -
    ST02         1…1 4/9 Transaction set ID number. Counter for each ST segment beginning with 1. 0001 transactionSetControlNumber -
    BPA         1…1 -

Price authorization acknowledgment/status beginning segment.

Note: There is no transaction identifier in BPA.

 - - -
      BPA01       1…1 2/2

Transaction set purpose code.

Valid values:

  • 00 - ORIGINAL

  • 02 - CREATE (Add)

  • 03 - DELETE

  • 04 - CHANGE

  • 05 - REPLACE

  • 45 - FOLLOWUP

 00 processingFunctionTypeCode -
      BPA02       1…1 8/8 Report date in date format CCYYMMDD. 20240919 dateReported -
      BPA03       0…1 2/3 Reference identification qualifier for contract number. Valid value is CT - CONTRACT CT b2bTransactionIdentifierType -
      BPA04       0…1 '1/80 Reference identification number for contract number. 1234C b2bTransactionIdentifierValue -
    REF         0…12 - REF reference segment for mapping to the check number. - - -
      REF01       1…1 2/3 Reference identification qualifier for the contract class. Valid value: CE- Contract class CE transactionReferenceType -
      REF02       0…1 1/80 Reference identifier value: Contract class identifier. S340B transactionReferenceIdentifier -
      REF03       0…1 1/80 Description defined by qualifier code in REF02 sub-340B desription -
    DTM         0…10 -

DTM date segment for mapping to:

  • contract effective date

  • contract expiration date

  • group contract effective date

  • group contract expiration date

  • wholesale contract effective date

  • wholesale contract expiration date

 - - -
      DTM01       1…1 3/3

Date type qualifier for the effective date.

Valid values:

  • 092 - contract effective date

  • 093 - Contract expiration date

  • 124 - Group contract effective date

  • 125 - Group contract expiration date

  • 126 - Wholesale contract effective date

  • 127 - wholesale contract expiration date

  • 999 - Document date

 092 dateType -
      DTM02       0…1 8/8 Processing date in date format YYYYMMDD. 20240628 dateValue -
      DTM03       0…1 4/8 Processing time in time format HHMMSS. 123422 - -
    CUR         0…1 - Currency code info for payment record in price authorization acknowledgment/status. - - -
      CUR01       1…1 2/3

Entity identifier code for an organization, physical location, property or individual for use of the currency.

Valid value:

  • SE - Selling party currency

  • BY - Buying party (Purchaser) currency

 SE currencyEntityCode -
      CUR02       1…1 3/3 Standard ISO currency code for the country in which the payments are specified. USD currencyCode -
      CUR03       0…1 4/10 Exchange rate value to be used as a multiplier conversion factor to convert monetary value from one currency to another. - - -
    N1         0…1 -

N1 name segment loop for:

  • Purchasing group(customer or buyer) party information extended with dates and reference identifiers

  • Supplier party

  • manufacturer party

  • distributor party

  • distributor branch location

  • customer party information extended with dates and reference identifiers

  • contract party information extended with dates and reference identifiers

 - - -
      N101       1…1 2/3

Entity qualifier for the Customer or Buyer party identifier and address information.

Valid values:

  • BG - Buyer party

  • SU - Supplier party

  • MF - manufacturer party

  • DS - Distributor party

  • DB - Distributor branch

  • BY - Customer Party

  • 90 - Contract Party

 BG - -
      N102       0…1 1/60 Name. Pharma customer businessName -
      N103       0…1 1/2

Identifier code qualifier.

Valid values:

  • 01 – DUNS
  • 09 – DUNS+4
  • 11 – Drug Enforcement Agency registration number
  • 21 – Health Industry Number
  • 91 – Company identifier
  • 92 – Company location identifier
  • UL – Global Location Number
 UL companyIdentifierType -
      N104       0…1 2/80 Buyer party identifier as qualified by N103 mapping to companyIdentifierValue. 3333331013655 companyIdentifierValue -
      N3       0…1 - N3: Address: Child of purchasing group (buyer party) N1 name segment. - - -
        N301     1…1 1/55 Street address 1. 555 Neelan Road address1 -
        N302     0…1 1/55 Street address 2. Suite 123 address2 -
      N4       0…1 - N4: Geographic Location. Child of purchasing party N1 name segment. - - -
        N401     0…1 2/30 City name. Sacramento city -
        N402     0…1 2/2 State or province code. Code (Standard state/province) as defined by appropriate government agency. CA state -
        N403     0…1 3/15 Postal code. Code defining international postal zone code excluding punctuation and blanks. 95833 postalCode -
        N404     0…1 2/3 Country code. US country -
      PER       0…3 - Contact Information. - - -
        PER01     1…1 2/2

Contact function code identifying major duty or responsibility of person or group named as contact.

Valid value:

AJ - Primary contact

 AJ - -
        PER02     0…1 1/80 Name of the contact person responsible for authenticating the pedigree information. John Smith contactName -
        PER03     0…1 2/2

Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values:

  • TE - Telephone number

  • EM - email address

 TE - -
        PER04     0…1 1/2048

Communication number:

  • Telephone number of the contact person expected in this field.

  • Email address of the contact person.

 +1.516.747.6849 contactPhone -
        PER05     0…1 2/2 Communication Number Qualifier identifying the contact person's telephone number or email address.

Valid values:

  • TE - Telephone number

  • EM - email address

 EM - -
        PER06     0…1 1/2048

Communication number:

  • Telephone number of the contact person expected in this field.

  • Email address of the contact person.

 jsmith@manufac.com contactEmail -
      REF (N1-N3-N4-REF)       0…* - REF reference segment for mapping to the electronic payment identifier. - - -
        REF01     1…1 2/3

Transaction reference type for X12 segments REF and N9 and EDIFACT RFF for general reference data that is not a transaction document identifier.

HDA mapping for price authorization in N1 party loop for buying group only.

Valid value is CT

 CT transactionReferenceType -
        REF02     0…1 1/80

Transaction reference identifier value as defined by enum in transactionReferenceType.

HDA: Contract header type code defining identifier/description in description attribute (REF03).

 00987175534 transactionReferenceIdentifier -
    CON Loop         1…* - Contract Number details loop for specifying contract reference number and status. - - -
      CON01       1…1 2/3

Reference identification qualifier.

Transaction reference type for X12 segments REF and N9 and EDIFACT RFF for general reference data that is not a transaction document identifier. HDA mapping.

Valid values:

  • VC - Vendor/Supplier contract number

  • CT - Contract Number

 VC b2bTransactionIdentifierType -
      CON2       1…1 1/80

Reference identification id, Reference information as defined for a particular transaction set or as specified by the Reference Identification Qualifier

vendor or supplier contract id.

 12312LS b2bTransactionIdentifierValue -
      CON3       1…1 2/2

Contract current status code.

Valid values:

  • OC - Original contract

  • VA - Valid open contract

 OC contractStatusCode -
      REF       0…12 - REF reference segment loop for contract number reference in CON loop group - - -
        REF01     1…1 2/3

Reference identification qualifier for the previous contract number.

Valid values:

  • P1 - Previous contract number

  • BC - CUSTOMERCONTRACT

 P1 - -
        REF02     0…1 1/80 Reference identifier value: check number 4500018486 previousTransactionIdentifier -
      DTM       0…10 - DTM date segment for contract reference dates in CON loop. - - -
        DTM01     1…1 3/3

Date type qualifier for the contract reference dates in CON loop.

Valid values:

  • 092 - Contract effective date

  • 093 - Contract expiration date

  • 124 - Group contract effective date

  • 125 - Group contract expiration date

  • 999 - Document date

 092 dateType -
        DTM02     0…1 8/8 Processing date in date format YYYYMMDD. 20240628 dateValue -
        DTM03     0…1 4/8 Processing time in time format HHMMSS. 123422 - -
      N1       0…1 -

CON-N1 name segment loop for:

  • customer party information extended with dates and reference identifiers.

  • bill to party information extended with dates and reference identifiers.

  • contracted pharmacy party information extended with dates and reference identifiers.

  • eligible contract party Information extended with dates and reference identifiers.

  • eligible party for rate Information extended with dates and reference identifiers.

  • ship to party information extended with dates and reference identifiers.

  • purchasing group party information extended with dates and reference identifiers.

  • distributor party information extended with dates and reference identifiers .

HDA usage note: This N1 loop at the Detail Level in the CON loop is required to identify eligible customers belonging to the buying group or individual parties eligible for the contract.

 - - -
        N101     1…1 2/3

Entity qualifier for the Customer or Buyer party identifier and address information.

Valid value:

  • BY - Buyer party

  • BT - Bill to party

  • C9 - Contracted pharmacy party

  • EB - Eligible contracted pharmacy party

  • EP - Eligible party for rate Information

  • ST - ship to party

  • BG - Purchasing group party

  • DS - Distributor party

 BY - -
        N102     0…1 1/60 Name. Pharma customer businessName -
        N103     0…1 1/2

Identifier code qualifier.

Valid values:

  • 01 – DUNS
  • 09 – DUNS+4
  • 11 – Drug Enforcement Agency registration number
  • 21 – Health Industry Number
  • 91 – Company identifier
  • 92 – Company location identifier
  • UL – Global Location Number
 UL companyIdentifierType -
        N104     0…1 2/80 Buyer party identifier as qualified by N103 mapping to companyIdentifierValue. 3333331013655 companyIdentifierValue -
        N3     0…1 - N3: Address: Child of customer party N1 name segment. - - -
          N301   1…1 1/55 Street address 1. 555 Neelan Road address1 -
          N302   0…1 1/55 Street address 2. Suite 123 address2 -
        N4     0…1 - N4: Geographic Location. Child of customer party N1 name segment. - - -
          N401   0…1 2/30 City name. Sacramento city -
          N402   0…1 2/2 State or province code. Code (Standard state/province) as defined by appropriate government agency. CA state -
          N403   0…1 3/15 Postal code. Code defining international postal zone code excluding punctuation and blanks. 95833 postalCode -
          N404   0…1 2/3 Country code. US country -
        REF (CON-N1-N3-N4-REF)     0…12 -

REF reference segment for mapping for reference identifiers.

HDA Description: This REF segment at the Detail Level in the CON/N1 loop is used in the bid award/change to provide other information regarding the customers eligible for the contract including: previous identifiers, trade classification(s), GPO membership IDs, and account class codes. REF01 and REF02 must be present and in some instances, REF03 may be appropriate for description clarification.

 - - -
          REF01   1…1 2/3

Reference information for identifiers that are not related to transaction documents. This group would map to X12 segments REF and N9 and EDIFACT RFF for information other than transaction documents.

HDA mapping.

Valid values:

  • 1W

  • 9X

  • DH

  • HI

  • P2

  • P3

  • X8

  • ACD

1W transactionReferenceType -
          REF02   0…1 1/80

Transaction reference identifier value as defined by enum in transactionReferenceType.

HDA: Contract header type code defining identifier/description in description attribute (REF03).

 AC transactionReferenceIdentifier -
          REF03   0…1 1/80

A free-form description to clarify the related data elements and their content.

HDA: Identifier or description defined by qualifier code in transactionReferenceIdentifier (REF02).

 Acute Care desription -
        DTM     0…2 -

DTM date segment in CON-N1 loop group 110.

HDA usage description: This DTM segment at the Detail Level in the CON/N1 loop is used to provide the effective and expiration dates of the individual customers. This segment is required only if these dates are different from the dates of the buying group contract indicated at the Header level. DTM01 and DTM02 must be present. This segment can also be used to provide the effective date of an identifier being implemented. DTM01 and DTM02 must be present.

 - - -
          DTM01   1…1 3/3

Date type qualifier for contract dates in CIN-N1-DTM loop.

Valid values:

  • 092 - Contract effective date

  • 093- Contract expiration date

  • 124 - Group contract effective date

  • 125 - Group contract expiration date

  • 129 - Customer contract effective date

  • 130 - Customer contract expiration date

 129 dateType -
          DTM02   0…1 8/8 Contract date in date format YYYYMMDD. 20240628 dateValue -
          DTM03   0…1 4/8 Contract time in time format HHMMSS. 123422 - -
          PAD   0…* - Product adjustment detailed group. Adjustments with reason codes but without reference to an invoice. - - -
            PAD01 0…1 1/20 The line item number restarts and resets to 1 for each new loop of the canonicalPriceAuthorizationItemDetails array. 1 lineItemNumber -
            PAD02 0…1 2/2 Product transfer type code. Pass thru mapping to canonical. 02 productTransferTypeCode -
            PAD03 0…1 2/2

Change or response type code specifying the type of change recorded in the product adjustment details loop.

Valid values:

  • AI - Add additional items

  • CA - Changes to line items

  • CT - Change dates

  • DI - Delete items

  • OA - Original confirmation of revised announcement

  • OC - Original confirmation of original announcement

  • PC - Price change

  • RB - Replace all dates

  • RE - Replacement item

 AI adjustmentTypeCode -
        CTB     0…10 - Restrictions or conditions information such as shipping, ordersing. CON-PAD-CTB - - -
          CTB01   1…1 2/2 Restrictions or conditions type code. Valid value is OR - Ordering OR restrictionsType -
          CTB02   0…1 1/80 Description of the restriction condition. - desription -
          CTB03   0…1 2/2 Quantity type code valid value is 57 - Minimum order quantity 57 - -
          CTB04   0…1 1/15 Quantity value in numeric. 12 minimumQuantity -
          CTB05   0…1 1/3 Qualifying amount code valid value is MO - Minimum order value MO - -
          CTB06   0…1 1/15 Qualifying amount. 12000 minimumAmount -
        PID     0…200 - Product/Item Information. - - -
          PID01   1…1 1/1 Item Description Type Code. Valid value isF - Free form text F - -
          PID02   0…1 2/3 Product/Process Characteristic Code. - - -
          PID03   0…1 2/2 Agency Qualifier Code. - - -
          PID04   0…1 1/12 Product Description Code. - - -
          PID05   0…1 1/80 Description. Description of Product productDescription -
          PID09   0…1 2/3 Language code. EN productLanguageCode -
        UIT     0…20 -

Item unit data information such as shipping, ordersing. CON-PAD-UIT

Two occurrences of this segment at the detail level in the productAdjustmentDetails loop are required to add an item in a bid award: one to specify the wholesale price and the other to specify the contract price.

This is not necessarily the case in a bid award/change, when specifying a price change, for example. If the contract price changed then only one occurrence of the UIT segment would be required for the manufacturer to notify the distributor of this change.

 - - -
          UIT01   1…1 - - - - -
          UIT01.1   1…1 2/2

Unit of measure for recorded product in adjustment.

Valid values :

  • UN (HDA)

  • EA

  • CA

UN unitOfMeasure -
          UIT02   0…1 1/17 Item unit price. 12.10 itemUnitPrice -
          UIT03   0…1 2/2

Code identifying the type of unit price.

Valid values:

  • CT

  • LE

  • RE

  • WH

CT unitPriceTypeCode -
        DTM     0…2 -

DTM date segment in CON-PAD loop group 120.

HDA usage description: This date segment at the detail level in the canonical productAdjustmentDetails array (X12CON/PAD loop) is only used to provide the item contract effective and expiration dates that are different from the buying group dates at the header level.

When adding an item in a bid award/change, two occurrences of this date segment are required — one to specify the item contract effective date and the other to specify the item contract expiration date. DTM01 and DTM02 must be present.

 - - -
          DTM01   1…1 3/3

Date type qualifier for contract dates in CON-PAD-DTM loop.

Valid values:

  • 131 - Item contract effective date

  • 132 - Item contract expiration date

 131 dateType -
          DTM02   0…1 8/8 Contract date in date format YYYYMMDD. 20240628 dateValue -
          DTM03   0…1 4/8 Contract time in time format HHMMSS. 123422 - -
        LIN     0…1 - Item identification segment in CON-PAD, one segment per PAD. - - -
          LIN01   0…1 1/20 Line item identification. - - -
          LIN02   1…1 2/2 product service ID qualifier mapping from global standards enum list. VN productCodeType -
          LIN03   1…1 1/80 Product or service identifier. 08202000230 productCodeValue -
          LIN04   0…1 2/2 product service ID qualifier mapping from global standards enum list. VN productCodeType -
          LIN05   0…1 1/80 Product or service identifier. 08202000230 productCodeValue -
          LIN06   0…1 2/2 product service ID qualifier mapping from global standards enum list. VN productCodeType -
          LIN07   0…1 1/80 Product or service identifier. 08202000230 productCodeValue -
          LIN08   - - product service ID qualifier mapping from global standards enum list. VN productCodeType -
          LIN09   - - Product or service identifier. 08202000230 productCodeValue -
          LIN10   0…1 2/2 product service ID qualifier mapping from global standards enum list. VN productCodeType -
          LIN11   0…1 1/80 Product or service identifier. 08202000230 productCodeValue -
          LIN12   0…1 2/2 product service ID qualifier mapping from global standards enum list. VN productCodeType -
          LIN13   0…1 1/80 Product or service identifier. 08202000230 productCodeValue -
          LIN14   0…1 2/2 product service ID qualifier mapping from global standards enum list. VN productCodeType -
          LIN15   0…1 1/80 Product or service identifier. 08202000230 productCodeValue -
          LIN16   0…1 2/2 product service ID qualifier mapping from global standards enum list. VN productCodeType -
          LIN17   0…1 1/80 Product or service identifier. 08202000230 productCodeValue -
        CTP     0…* -

Pricing information segment in CON-PAD, optional

Pricing information for product.

HDA usage note: Used to communicate pricing scenarios where multiple price points exist for a given product on the same contract ID. This array does not represent tier contracts with unique contract IDs, which are typically sent in separate X12 845s messages.

Use of this segment must be agreed on by the manufacturer and wholesaler to ensure interpretation/implementation is as the manufacturer intended.

The price point for example, could be based on quantity purchased per order, per calendar quarter or some other parameter. Impacts on membership should also be considered. Feasibility may dictate all attached members are be able to access all price points sent in this segment.

 - - -
          CTP01   0…1 2/2 Class of Trade Code. DI - -
          CTP02   0…1 3/3

Pricing type for Price Authorization catalog.

Valid values:

  • C01 - Contract tier 1 price

  • C02 - Contract tier 2 price

  • C03 - Contract tier 3 price

  • C04 - Contract tier 4 price

  • C05 - Contract tier 5 price

  • C06 - Contract tier 6 price

  • PBQ - Begin quantity

  • CON - Contract

  • DIS - Distributor

 CON pricingType -
          CTP03   0…1 1/17 Price per unit of product or service etc. 21.20 pricingAmount -
          CTP04   0…1 1/15 Pricing type quantity in numeric. 12 pricingTypeQuantity -
          CTP05   0…1 - - - - -
          CTP05.1   1…1 2/2

Unit of measure used for pricing at the price conditions line item details level.

 

 UN unitOfMeasure -
    CTT         0…1 - CTT-Transaction Totals. - - -
      CTT01       1…1 1/6 Total number of line items in the transaction set. 15 summaryValue -
  SE           1…1 - ST … SE transaction set trailer envelope. Child of GS group. Only one ST transaction expected. - - -
    SE01         1…1 1/10 Total count of segments in ST … SE transaction set including ST and SE segments. 10 trailerSegmentCount -
    SE02         1…1 4/9 Transaction set control number. 0001 trailerSegmentIdentifier -
  GE           1…1 - GS … GE functional group trailer envelope. Child of ISA interchange. Only one GS group expected. - - -
    GE01         1…1 1/6 Number of transaction sets in functional group. 5 trailerSegmentCount -
    GE02         1…1 1/9 Functional group control number. 619827 trailerSegmentIdentifier -
  IEA           1…1 - ISA … IEA interchange control trailer envelope. Only one interchange expected per transmission. - - -
    IEA01         1…1 1/5 Number of functional groups in interchange. 1 trailerSegmentCount -
    IEA02         1…1 9/9 Interchange control number. 0000000000619827 trailerSegmentIdentifier -
Copy 
ISA*00*01        *00*11        *01*7777776067344  *07*888888404358877*241014*1348*^*00501*000619827*0*P*:~
GS*PA*2222224043588*TRACELINK*20241020*142000*619827*X*00501~
ST*845*0001*s23~
BPA*00*20240919*CT*1234C*1014~
REF*CE*S340B*sub-340B*STB:s39:STS:s41:SUB:s43~
DTM*092*20241014*134846*15*RTM*s179~
CUR*SE*USD*1821*F5*s18*NYC*424*20241014*134846*666*20241014*134846*425*20241014*134846*667*20241014*134846*426*20241014*134846~
N1*BG*BG_name*1*BG_123*38*FB~
N3*Address_1_BG*Address_2_BG~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*CT*REF_CT_BG*s218*2H:s220:2J:s222:2L:s224~
PER*AJ*John Smith*TE*1122334455*EM*jsmith@manufac.com*AB*s232*s233~
N1*SU*SU_name*9*SU_123*38*FB~
N3*Address_1_SU*Address_2_SU~
N4*Sacramento*CA*95833*US*IS*s209*s21~
PER*AJ*John Smith*TE*1122334466*EM*jsmith@manufac.com*AB*s232*s233~
N1*MF*MF_name*11*MF_123*38*FB~
N3*Address_1_MF*Address_2_MF~
N4*Sacramento*CA*95833*US*IS*s209*s21~
PER*AJ*John Smith*TE*1122334477*EM*jsmith@manufac.com*AB*s232*s233~
N1*DS*DS_name*21*DS_123*38*FB~
N3*Address_1_DS*Address_2_DS~
N4*Sacramento*CA*95833*US*IS*s209*s21~
PER*AJ*John Smith*TE*1122334488*EM*jsmith@manufac.com*AB*s232*s233~
N1*DB*DB_name*91*DB_123*38*FB~
N3*Address_1_DB*Address_2_DB~
N4*Sacramento*CA*95833*US*IS*s209*s21~
PER*AJ*John Smith*TE*1122334488*EM*jsmith@manufac.com*AB*s232*s233~
N1*BY*BY_name*92*BY_123*38*FB~
N3*Address_1_BY*Address_2_BY~
N4*Sacramento*CA*95833*US*IS*s209*s21~
PER*AJ*John Smith*TE*1122334499*EM*jsmith@manufac.com*AB*s232*s233~
N1*9O*9O_name*UL*9O_123*38*FB~
N3*Address_1_9O*Address_2_9O~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*CT*REF_CT_9O*s218*2H:s220:2J:s222:2L:s224~
PER*AJ*John Smith*TE*1122334400*EM*jsmith@manufac.com*AB*s232*s233~
CON*VC*12312LS*OC~
REF*P1*REF_P1*s218*2H:s220:2J:s222:2L:s224~
DTM*092*20241014*134846*09*TC*s575~
N1*BY*BY_nameLine*UL*BY_1239*38*FB~
N3*Address_1_BY*Address_2_BY~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*1W*REF_1W_BY*s218*2H:s220:2J:s222:2L:s224~
DTM*124*20241017*134846*09*TC*s575~
N1*BT*BT_nameLine*UL*BT_1239*38*FB~
N3*Address_1_BT*Address_2_BT~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*9X*REF_9X_C9*s218*2H:s220:2J:s222:2L:s224~
DTM*129*20241019*134846*09*TC*s575~
N1*C9*C9_nameLine*UL*C9_1239*38*FB~
N3*Address_1_C9*Address_2_C9~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*DH*REF_DH_C9*s218*2H:s220:2J:s222:2L:s224~
DTM*125*20241018*134846*09*TC*s575~
N1*EB*EB_nameLine*UL*EB_1239*38*FB~
N3*Address_1_EB*Address_2_EB~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*HI*REF_HI_EB*s218*2H:s220:2J:s222:2L:s224~
DTM*129*20241019*134846*09*TC*s575~
N1*EP*EP_nameLine*UL*EP_1239*38*FB~
N3*Address_1_EP*Address_2_EP~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*P2*REF_P2_EP*s218*2H:s220:2J:s222:2L:s224~
DTM*130*20241020*134846*09*TC*s575~
N1*ST*ST_nameLine*UL*ST_1239*38*FB~
N3*Address_1_ST*Address_2_ST~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*P3*REF_P3_ST*s218*2H:s220:2J:s222:2L:s224~
DTM*093*20241016*134846*09*TC*s575~
N1*BG*BG_nameLine*UL*BG_1239*38*FB~
N3*Address_1_BG*Address_2_BG~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*X8*REF_X8_BG*s218*2H:s220:2J:s222:2L:s224~
DTM*130*20241020*134846*09*TC*s575~
N1*DS*DS_nameLine*UL*DS_1239*38*FB~
N3*Address_1_DS*Address_2_DS~
N4*Sacramento*CA*95833*US*IS*s209*s21~
REF*ACD*REF_ACD_DS*s218*2H:s220:2J:s222:2L:s224~
DTM*124*20241017*134846*09*TC*s575~
PAD*1*PP*AI~
PID*F****Test stuff2****GA~
CTB*AA*CTB02_1*57*12*MO*12000~
UIT*UN*12.32*CT~
DTM*131*20241019*134846*09*TC*s575~
LIN**UA*CASEUPC~
CTP*CX*C01*21.20*12*UN~
CTT*1000~
SE*2147*s2148~
GE*2149*2150~
IEA*2151*215211111~

Tag end