This Help Center is a preview of a future release. The final Help Center will be available on the Validation date.
Type = API Reference,; Topic = Multienterprise Information Network Tower (MINT),;Persona = TraceLink Administrator, User,; Orchestration = Manufacturing, Logistics, Commerce,; Function = Supply Chain, IT, Procurement,
Receiving advice acceptances APIs
Receiving advice acceptances streamline goods transportation between entities to verify and manage delivery details efficiently. Receiving advices acceptances is sent by the ship-to-party (receiver) to inform the shipper (sender) of the receipt of goods. Additionally, receiving advice acceptances highlights any discrepancies or issues related to the shipment.
Receiving advices acceptances plays a vital role in ensuring effective communication during the transfer of goods, fostering transparency, and accuracy in supply chain operations by allowing the receiving entity to confirm receipt, report discrepancies or damages, and reconcile delivery details with related documents like purchase orders or advance shipping notices. Receiving advices acceptances serves as a tool for reconciling the received shipment ensuring the accuracy of the goods received against the initial order and shipping notification.
Receiving advice acceptances (X12)
The Receiving advices acceptances (X12) provides the shipper with a receiving advice or acceptance notification upon receiving the shipment.
Contact your TraceLink Services representative for more information about integrating with this message.
- Message Type: MPC_RECEIVING_ADVICE_ACCEPTANCE
- X12 Format: 861
- Transform Names:
- B2B_EDI_X12_861_ReceivingAdvice_IB_V1
- B2B_EDI_X12_861_ReceivingAdvice_OB_V1

Input Element | Occurs | Length | Description | Example | ||||
---|---|---|---|---|---|---|---|---|
ISA | – | Required.ISA interchange envelope. | – | |||||
ISA01 | 2/2 |
Required.Authorization information qualifier identifying the type of identifier in ISA02. Valid values:
Typically this value – 00 |
00 | |||||
ISA02 | 10/10 |
Required.Authorization identifier value used for additional identification or authorization of the interchange sender or the data in the interchange.
|
– | |||||
ISA03 | 2/2 |
Required.Qualifier for security information in ISA04. Valid values:
|
00 | |||||
ISA04 | 10/10 |
Required.Security information identifying for the interchange sender or data.
|
– | |||||
ISA05 | 2/2 |
Required.Interchange sender partner ID qualifier. Valid values:
|
07 | |||||
ISA06 | 15/15 | Required.ISA interchange sender identifier. | 7777776067344 | |||||
ISA07 | 2/2 |
Required.Interchange receiver partner ID qualifier. Valid values:
|
01 | |||||
ISA08 | 15/15 | Required.ISA interchange receiver ID. | 888888404358877 | |||||
ISA09 | 6/6 | Required.Interchange date in 6 char date format YYMMDD. | 241215 | |||||
ISA10 | 4/4 | Required.Interchange time in 4 char time format HHMM. | 1420 | |||||
ISA11 | 1/1 |
Required.The value of this element is dependent on X12 version.
|
^ | |||||
ISA12 | 5/5 | Required.Interchange control version number. This could be any X12 version. | 00501 | |||||
ISA13 | 9/9 | Required.ISA interchange control number. | 0000000000619827 | |||||
ISA14 | 1/1 |
Required.Interchange level acknowledgment requested. Valid values:
|
0 | |||||
ISA15 | 1/1 |
Required.Indicates whether the interchange is for production, test, or information purposes. Valid values:
|
P | |||||
ISA16 | 1/1 | Required.Component element separator. Delimiter that separates data elements within a composite data structure. Must be different than the data element separator and segment terminator. | > | |||||
GS | – | Required.GS group functional envelope. Child of ISA. Only one GS group expected per interchange. | – | |||||
GS01 | 2/2 | Required.GS group function code. The valid
value is RC – Receiving Advice X12 861. |
RC | |||||
GS02 | 2/15 | Required.Application sender's code in the group envelope. | 2222224043588 | |||||
GS03 | 2/15 | Required.Application receiver's code in the group envelope. | TRACELINK | |||||
GS04 | 8/8 | Required.Group envelope date value in date format YYYYMMDD. | 20241215 | |||||
GS05 | 4/8 | Required.Group envelope time value in time format HHMM or HHMMSS. | 142000 | |||||
GS06 | 1/9 | Required.Group control identifier. | 619827 | |||||
GS07 | 1/2 |
Required.Responsible agency code. Valid values:
|
X | |||||
GS08 | 1/12 | Required.X12 message version code. This could be any X12 version. | 005010 | |||||
ST | – | ST transaction set envelope. Child of GS group. Only one ST transaction expected. | – | |||||
ST01 | 3/3 | Required.Transaction set identifier code. | 861 | |||||
ST02 | 4/9 | Required.Transaction set ID number. Counter for each ST segment beginning with 1. | 0001 | |||||
BRA | – | Required.Beginning segment for receiving advice. | – | |||||
BRA01 | 1/80 | Required.Transaction reference identifier is the receiving or delivery document identifier for the receiving advice. | 8524700258 | |||||
BRA02 | 8/8 | Required.Date of receiving advice in date format YYYYMMDD. | 20241215 | |||||
BRA03 | 2/2 |
Code identifying purpose of transaction set. Valid values:
|
00 | |||||
BRA04 | 1/1 |
Required.Code specifying type of receiving advice. Valid values:
|
1 | |||||
BRA05 | 4/8 | The time when receiving advice transaction set document is created. | – | |||||
BRA06 | 2/2 | Code designating physical condition or status of units received in a specific shipment. | – | |||||
BRA07 | 1/2 | Code indicating type of action. | – | |||||
CUR | – | CUR segment is used to specify the currency (dollars, pounds, francs, etc.) used in a transaction. | – | |||||
CUR01 | 2/3 | Required.Currency entity code. | SE | |||||
CUR02 | 3/3 | Required.Code (Standard ISO) for country in whose currency the charges are specified. | USD | |||||
REF | – | REF segment is used to specify receiving advice information. | – | |||||
REF01 | 2/3 |
Required.Code qualifying the reference identification.
|
DO | |||||
REF02 | 1/80 | Reference or transaction identifier. If REF01 is populated, REF02 is required. | 8456732 | |||||
REF03 | 1/80 | A free-form description to clarify the related data elements and their content. | – | |||||
DTM | – | DTM segment is used to specify pertinent dates and times. | – | |||||
DTM01 | 3/3 |
Required.Code specifying type of date or time, or both date and time. Valid values:
|
050 | |||||
DTM02 | 8/8 | Date as defined by one of the valid enumerators in DTM01 in date format YYYYMMDD. | 20241215 | |||||
DTM03 | 4/8 | Time recorded for date in time format HHMM or HHMMSS or HHMMSSnn. | 122655 | |||||
DTM04 | 2/2 | Code identifying either the time zone or the formatting standard for the date. This is an optional field. Only the time zone is expected here. | – | |||||
PRF | – | PRF segment is used to provide reference to a specific purchase order | – | |||||
PRF01 | 1/22 | Required.Identifying number for Purchase Order assigned by the orderer or purchaser. | 0045687901 | |||||
PRF02 | 1/30 | Number identifying a release against a purchase order previously placed by the parties involved in the transaction. | – | |||||
PRF03 | 1/8 | Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set. | – | |||||
PRF04 | 8/8 | Purchase order date in date format YYYYMMDD. | 20241215 | |||||
TD1 | – | TD1 segment is used to specify the transportation details relative to commodity, weight, and quantity | – | |||||
TD101 | 3/5 |
Packaging container unit of measure. Valid values:
If segment TD1 is present, TD101 and TD102 are required. |
PLT | |||||
TD102 | 1/7 | Number of units (pieces) of the lading commodity. If segment TD1 is present, TD101 and TD102 are required. | 45 | |||||
TD103 | 1/1 | Commodity code qualifier. | – | |||||
TD104 | 1/30 | Commodity code. | – | |||||
TD105 | 1/50 | Lading description. | – | |||||
TD106 | 1/2 |
Code defining the weight type: Valid values:
|
G | |||||
TD107 | 1/10 | Numeric value of weight. If TD106 is present, TD107 is required. | – | |||||
TD108 | 2/2 |
Unit of measure for the weight. If TD106 and TD107 are present, TD108 is required. ![]()
|
||||||
TD5 | – | TD5 segment is used to specify the carrier and sequence of routing and provide transit time information. | – | |||||
TD501 | 1/2 | Routing sequence code defining the relationship of a carrier to a specific shipment movement. | – | |||||
TD502 | 1/2 |
Qualifier identifying the
standard carrier alpha code (SCAC) identifying a carrier. Valid value is TD502 is required if TD503 is present. |
2 | |||||
TD503 | 2/80 | Standard alpha carrier code (SCAC) as defined by the qualifier in TD502. | – | |||||
TD504 | 1/2 |
Code specifying the method or type of transportation for the shipment. Valid values:
TD503 is required if TD502 is present. |
J | |||||
TD505 | 1/35 | Business name of the carrier party identified by SCAC code in TD503. | – | |||||
TD506 | 2/2 | Shipment or order status code. If TD506 - PR, this is a partial delivery. Otherwise whatever value is present will be mapped through as received. | PR | |||||
TD3 | – | TD3 segment is used to specify transportation details relating to the equipment used by the carrier. | – | |||||
TD301 | 2/2 |
Code identifying the type of equipment used for shipment. Valid values:
|
CN | |||||
TD302 | 1/4 | Equipment identifier prefix or alphabetic part of the equipment item's identifier. If TD302 is present, TD303 is required. | – | |||||
TD303 | 1/15 | Equipment identifier. The equipment unit's unique identifier. If TD303 is present, TD302 is required. | – | |||||
N1 | – |
Name and address segment loop. The following party types are currently supported:
|
– | |||||
N101 | 2/3 |
Required.Entity qualifier for the carrier party identifier and address information.
|
BY | |||||
N102 | 1/60 | Business party or location name. At least one of N102 or N103 is required. Both may be present. | Pharma supplier | |||||
N103 | 1/2 |
Identifier code qualifier. ![]()
At least one of N102 or N103 is required. Both may be present. If N103 is present, N104 is required. |
UL | |||||
N104 | 2/80 | Carrier party identifier as qualified by N103 mapping to companyIdentifierValue. If N103 is present, N104 is required. | 8568745 | |||||
N2 | – | N2: Additional names: Child of carrier party N1 name segment. | – | |||||
N201 | 1/55 | Required.Free-form name for business name 2. | – | |||||
N202 | 1/55 | Free-form name for business name 3. | – | |||||
N3 | – | N3: Address: Child of carrier party N1 name segment. | – | |||||
N301 | 1/55 | Required.Street address 1 Required if segment N3 is present. | 555 Neelan Road | |||||
N302 | 1/55 | Street address 2. | Suite 123 | |||||
N4 | – | N4: Geographic Location. Child of carrier party N1 name segment. | – | |||||
N401 | 2/30 | City name. | Sacramento | |||||
N402 | 2/2 | State or province code. Code (Standard state/province) as defined by appropriate government agency. | CA | |||||
N403 | 3/15 | Postal code. Code defining international postal zone code excluding punctuation and blanks. | 95833 | |||||
N404 | 2/3 | Country code. | US | |||||
PER | – | PER segment under N1 loop is used to identify a person or office to whom administrative communications should be directed. | – | |||||
PER01 | 2/2 | Required.Contact function code
identifying major duty or responsibility of person or group named as contact.
Valid value is AJ - Primary contact. |
AJ | |||||
PER02 | 1/60 | Name of the contact person responsible for authenticating the pedigree information. | John Smith | |||||
PER03 | 2/2 |
Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values:
If PER03 is present, PER04 is required. |
TE | |||||
PER04 | 1/2048 |
Communication number. Telephone number or email address of the contact person expected in this field. If PER04 is present, PER03 is required. |
+1.516.747.6849 | |||||
PER05 | 2/2 |
Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values:
If PER05 is present, PER06 is required |
EM | |||||
PER06 | 1/2048 |
Communication number. Email address or telephone number for the contact person expected in this field. If PER06 is present, PER05 is required. |
jsmith@manufac.com | |||||
RCD | – | Receiving conditions loop. Line item level details for receiving advice. Reports on the products and quantities received, returned, and with issues. RCD may appear only once or multiple times within any 861 transaction set. | – | |||||
RCD01 | 1/20 | Assigned identification number for the RCD segment. Can be any assigned identification value, such as a line item number, a transaction or document identifier, or a hard coded value. | 1 | |||||
RCD02 | 1/9 |
Total number of units received or accepted. At least one of RCD02, RCD04, or RCD06 is required. If RCD03-01 is present, RCD02 is required. |
10 | |||||
RCD03 | 2/2 |
Unit of measure for number of units received or accepted. If RCD02 is present, RCD03-01 is required. ![]()
|
EA | |||||
RCD04 | 1/9 |
Total number of units returned. At least one of RCD04, RCD02, or RCD06 is required. If RCD04 is present, RCD05-01 is required. |
20 | |||||
RCD05 | 2/2 |
Unit of measure for number of units returned. If RCD05-01 is present, RCD04 is required. ![]()
|
EA | |||||
RCD06 | 1/9 |
Number of units contested because of physical condition or status of units. At least one of RCD06, RCD02, or RCD04 is required. If RCD06 is present, RCD07-01 and RCD08 are required |
30 | |||||
RCD07 | 2/2 |
Unit of measure for number of units contested because of physical condition or status. If RCD06 is present, RCD07-01 and RCD08 are required. ![]()
|
EA | |||||
RCD08 | 2/2 |
Questioned quantity reason code describing the physical condition or status of units received in a specific shipment. Valid values:
If RCD06 is present, RCD07-01 and RCD08 are required. |
01 | |||||
RCD09 | 1/9 |
Number of units contested because of physical condition or status of units. If RCD09 is present, RCD10-01 and RCD11 are required. |
30 | |||||
RCD10 | 2/2 |
Unit of measure for number of units contested because of physical condition or status. If RCD09 is present, RCD10-01 and RCD11 are required. ![]()
|
EA | |||||
RCD11 | 2/2 |
Questioned quantity reason code describing the physical condition or status of units received in a specific shipment. Valid values:
If RCD09 is present, RCD10-01 and RCD11 are required. |
02 | |||||
RCD12 | 1/9 |
Number of units contested because of physical condition or status of units. If RCD12 is present, RCD13-01 and RCD14 are required. |
30 | |||||
RCD13 | 2/2 |
Unit of measure for number of units contested because of physical condition or status. If RCD12 is present, RCD13-01 and RCD14 are required. ![]()
|
EA | |||||
RCD14 | 2/2 |
Questioned quantity reason code describing the physical condition or status of units received in a specific shipment Valid values:
If RCD12 is present, RCD13-01 and RCD14 are required. |
03 | |||||
RCD15 | 1/9 |
Number of units contested because of physical condition or status of units. If RCD15 is present, RCD16-01 and RCD17 are required. |
30 | |||||
RCD16 | 2/2 |
Unit of measure for number of units contested because of physical condition or status. If RCD15 is present, RCD16-01 and RCD17 are required. ![]()
|
EA | |||||
RCD17 | 2/2 |
Questioned quantity reason code describing the physical condition or status of units received in a specific shipment Valid values:
If RCD15 is present, RCD16-01 and RCD17 are required. |
09 | |||||
RCD18 | 1/9 |
Number of units contested because of physical condition or status of units. If RCD18 is present, RCD19-01 and RCD20 are required. |
30 | |||||
RCD19 | 2/2 |
Unit of measure for number of units contested because of physical condition or status. If RCD18 is present, RCD19-01 and RCD20 are required. ![]()
|
EA | |||||
RCD20 | 2/2 |
Questioned quantity reason code describing the physical condition or status of units received in a specific shipment. Valid values:
If RCD18 is present, RCD19-01 and RCD20 are required. |
10 | |||||
LIN | – | LIN segment within RCD loop specifies product identifiers and identifier types. | – | |||||
LIN01 | 1/20 | Line item number or other assigned identifier value. | – | |||||
LIN02 | 2/2 |
Required.Product code qualifier specifying the product identifier type. ![]()
|
– | |||||
LIN03 | 1/80 | Required.Product or service identifier as defined by the qualifier in LIN02 | – | |||||
LIN04 | 2/2 |
Product code qualifier specifying the product identifier type. If LIN04 is present, LIN05 is required. ![]()
|
– | |||||
LIN05 | 1/80 |
Product or service identifier as defined by the qualifier in LIN02. If LIN06 is present, LIN04 is required. |
– | |||||
LIN06 | 2/2 |
Product code qualifier specifying the product identifier type. If LIN06 is present, LIN07 is required. ![]()
|
– | |||||
LIN07 | 1/80 |
Product or service identifier as defined by the qualifier in LIN02. If LIN07 is present, LIN06 is required. |
– | |||||
LIN08 | 2/2 |
Product code qualifier specifying the product identifier type. If LIN08 is present, LIN09 is required. ![]()
|
– | |||||
LIN09 | 1/80 |
Product or service identifier as defined by the qualifier in LIN02. If LIN09 is present, LIN08 is required. |
– | |||||
LIN10 | 2/2 |
Product code qualifier specifying the product identifier type. If LIN10 is present, LIN11 is required. ![]()
|
– | |||||
LIN11 | 1/80 |
Product or service identifier as defined by the qualifier in LIN02. If LIN11 is present, LIN12 is required. |
– | |||||
LIN12 | 2/2 |
Product code qualifier specifying the product identifier type. If LIN13 is present, LIN14 is required. ![]()
|
– | |||||
LIN13 | 1/80 |
Product or service identifier as defined by the qualifier in LIN02. If LIN14 is present, LIN13 is required. |
– | |||||
LIN14 | 2/2 |
Product code qualifier specifying the product identifier type. If LIN14 is present, LIN15 is required. ![]()
|
– | |||||
LIN15 | 1/80 |
Product or service identifier as defined by the qualifier in LIN02. If LIN15 is present, LIN14 is required. |
– | |||||
PID | – | PID segment under RCD loop is used to describe a product or process in coded or free-form format. | – | |||||
PID01 | 1/1 | Required.Item description type code. Hard code "F" for free text. | F | |||||
PID05 | 1/80 | Product descriptions or names. | – | |||||
REF | 0…12 | – | REF segment under RCD loop is used to specify identifying information | – | ||||
REF01 | 2/3 |
Required.Code qualifying the Reference Identification. Valid values:
|
DO | |||||
REF02 | 1/80 | Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier. | 8456732 | |||||
REF03 | 1/80 | A free-form description to clarify the related data elements and their content. | – | |||||
DTM | – | DTM segment is used to specify pertinent dates and times. | – | |||||
DTM01 | 3/3 |
Required.Code specifying type of date or time, or both date and time. Valid values:
|
310 | |||||
DTM02 | 8/8 | Date defined by DTM01 qualifier in date format YYYYMMDD. | 20241215 | |||||
DTM03 | 4/8 | Time for date defined by DTM01 qualifier in time format HHMM or HHMMSS or HHMMSSnn. | 124523 | |||||
MAN | – | MAN segment under RCD loop is used to indicate identifying marks and numbers for shipping containers. | – | |||||
MAN01 | 1/2 | Required.Code specifying the application or source of Marks and Numbers. | – | |||||
MAN02 | 1/48 | Required.Marks and numbers used to identify a shipment or parts of a shipment. | – | |||||
N1 | – | N1 name segment loop for the ship to location party information. | – | |||||
N101 | 2/3 |
Required.Entity qualifier for the ship to party identifier and address information. Valid values:
|
ST | |||||
N102 | 1/60 | Name. | Pharma supplier | |||||
N103 | 1/2 |
Identifier code qualifier. ![]()
|
UL | |||||
N104 | 2/80 | Ship to party identifier as qualified by N103 mapping to companyIdentifierValue. | 8568745 | |||||
N2 | – | N2: Additional names: Child of ship to party N1 name segment. | – | |||||
N201 | 1/55 | Required.Free-form name. | – | |||||
N202 | 1/55 | Free-form name. | – | |||||
N3 | – | N3: Address: Child of ship to party N1 name segment. | – | |||||
N301 | 1/55 | Required.Street address 1. | 555 Neelan Road | |||||
N302 | 1/55 | Street address 2. | Suite 123 | |||||
N4 | – | N4: Geographic Location. Child of ship to party N1 name segment. | – | |||||
N401 | 2/30 | City name. | Sacramento | |||||
N402 | 2/2 | State or province code. Code (Standard state/province) as defined by appropriate government agency. | CA | |||||
N403 | 3/15 | Postal code. Code defining international postal zone code excluding punctuation and blanks. | 95833 | |||||
N404 | 2/3 | Country code. | US | |||||
PER | – | PER segment under RCD-N1 loop is used to identify a person or office to whom administrative communications should be directed | – | |||||
PER01 | 2/2 | Required.Contact function code
identifying major duty or responsibility of person or group named as contact.
Valid value is AJ - Primary contact. |
AJ | |||||
PER02 | 1/60 | Name of the contact person responsible for authenticating the pedigree information. | John Smith | |||||
PER03 | 2/2 |
Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values:
If PER03 is present, PER04 is required |
TE | |||||
PER04 | 1/2048 |
Communication number: Telephone number or email address of the contact person expected in this field. If PER04 is present, PER03 is required |
+1.516.747.6849 | |||||
PER05 | 2/2 |
Communication Number Qualifier identifying the contact person's telephone number or email address. Valid values:
If PER05 is present, PER06 is required |
EM | |||||
PER06 | 1/2048 |
Communication number: Email address or telephone number for the contact person expected in this field. If PER06 is present, PER05 is required. |
jsmith@manufac.com | |||||
CTT | – | CTT segment is used to transmit a hash total for a specific element in the transaction set. | – | |||||
CTT01 | 1/6 | Required.Total number of line items in the transaction set | 10 | |||||
SE | – | Required.ST … SE transaction set trailer envelope. Child of GS group. Only one ST transaction expected. | – | |||||
SE01 | 1/10 | Required.Total count of segments in ST … SE transaction set including ST and SE segments. | 10 | |||||
SE02 | 4/9 | Required.Transaction set control number. | 0001 | |||||
GE | – | Required.GS … GE functional group trailer envelope. Child of ISA interchange. Only one GS group expected. | – | |||||
GE01 | 1/6 | Required.Number of transaction sets in functional group. | 5 | |||||
GE02 | 1/9 | Required.Functional group control number. | 619827 | |||||
IEA | – | Required.ISA … IEA interchange control trailer envelope. Only one interchange expected per transmission. | – | |||||
IEA01 | 1/5 | Required.Number of functional groups in interchange. | 1 | |||||
IEA02 | 9/9 | Required.Interchange control number. | 0000000000619827 |

ISA*00*authInfo *00*secInfo *16*SENDER1 *14*RECEIVER1
*071216*1406*U*00204*000000263*1*T*>
GS*IN*SENDER1*RECEIVER1*20071216*14062233*000000001*X*005010
ST*861*0006
BRA*123456*20241011*00*8*10153344*BR*49
CUR*SE*USD*1003*23*USD*ZUR*007*20241128*0102*001*20241128*0102
REF*SI*Ship111*desc*RE
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
DTM*011*20240502*11103142*10*TM*06
PRF*852147*8524700258*01*20241104*A*CNum*LN
TD1*PLT*2*T*A1*S1*G*4545.55*GR*109*TD
TD5*3*2*TSG355*SR*Acme*CC**EP***11****15
TD3*RR*LTL*447542*04*110*06***09215*D310
TD4***403*404*N
MEA***120*ME*115*110*44*****110
N1*CA*PharmaSUp*UL*8568745*05*106
N2*FFN*FFN2
N3*Addr1*Addr2
N4*City*MA*99999*US**06**
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
FOB***FOB03****FOB07**FOB09
N1*BY*Buyer*91*555*05*106
N2*FFN*FFN2
N3*Addr1*Addr2
N4*LINCOLN*RI*02865*US**06**
REF*IA*77000*desc*RE*
PER*AJ*nm1*TE*12348564*EM*name@corp.com*PH*1234*desc
FOB***FOB03****FOB07**FOB09
N1*SU*Supplier*92*777555*05*106
N2*FFN*FFN2
N3*5566 NEW VIENNA ROAD*Addr2
N4*City1*ME*1111*JP**06**
REF*IA*77000*desc*RE*
PER*AJ*nm2*TE*1111*EM*buyer@corp.com*PH*1234*desc
FOB***FOB03****FOB07**FOB09
N1*SF*PharmaSUp*92*IT-SITE-SF*05*106
N2*FFN*FFN2
N3*Addr1*Addr2
N4*DECORAH*IA*99999*US**06**
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
FOB***FOB03****FOB07**FOB09
N1*ST*PharmaSUp*9*IT-DUNS4-ST00073*05*106
N2*FFN*FFN2
N3*Addr1*Addr2
N4*SUMMIT*IL*99999*US**06**
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
FOB***FOB03****FOB07**FOB09
N1*SE*Nantucket Corp*11*SE-4554*05*106
N2*FFN*FFN2
N3*Endless Rd
N4*NY City*NY*4552211*US**06**
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
FOB***FOB03****FOB07**FOB09
N1*RL*RL-Reporting*1*RL*05*106
N2*FFN*FFN2
N3*0000 ROAD
N4*Gapan*XX*7777*CH**06**
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
FOB***FOB03****FOB07**FOB09
N1*FW*PharmaSUp*21*HIN-FW-45454*05*106
N2*FFN*FFN2
N3*5566 NEW VIENNA ROAD*Addr2
N4*SUMMIT*IL*99999*US**06**
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
FOB***FOB03****FOB07**FOB09
LM**LM02
LQ**LQ02
FA1*FA**
FA2**A202
RCD*2*12345*PC*2*EA*1*CT*01*2*EA*02*3*CT*03*4*PC*09*5*CA*10*21
SN1**1220*EA*1223*1221*EA**AC
CUR*SE*USD*1003*23*USD*ZUR*007*20241128*0102*001*20241128*0102
LIN*1*UK*025420080112*SK*00254200801-2
L1*IN*243599*MF*M7875*NH*NH7200*VN*V47878*N3*1234567890
PID*F****IT Name*****
PO4*4*1225*EA***********1222****
REF*DO*Del222A*desc*04
REF*IA*77000*desc*04
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
DTM*310*20240302*11103142***
PRF*852147*8524700258*01*20241104*A*CNum*LN
MEA***120*ME*115*110*44*****110
FOB***FOB03****FOB07**FOB09
TD1*PLT*2*T*A1*S1*G*4545.55*GR*109*TD
TD5*3*2*TSG355*SR*Acme*CC**EP***11****15
TD3*RR*LTL*447542*04*110*06***09215*D310
TD4***403*404*N
SAC*S***************~
MAN*GM*00000498840009089000****
LM**LM02
LQ**LQ02
SLN*S01*********
PID*F****IT Name*****
NM1*NM***********
LM**LM02
LQ**LQ02
N1*ST*PharmaSUp*9*IT-DUNS4-ST00073*05*106
N2*FFN*FFN2
N3*Addr1*Addr2
N4*SUMMIT*IL*99999*US**06**
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
FOB***FOB03****FOB07**FOB09
N1*RL*RL-Reporting*1*RL*05*106
N2*FFN*FFN2
N3*0000 ROAD
N4*Gapan*XX*7777*CH**06**
REF*IA*77000*desc*RE*
PER*AJ*name2*TE*99999*EM*email*PH*1234*desc
FOB***FOB03****FOB07**FOB09
FA1*FA**
FA2**A202
CTT*1******
SE*12*0006
GE*2*000000001
IEA*1*000000263
Tag end