Tracelink University ## Breadcrumb 1. [Home](/) 2. [Resources](/resources/resource-center) 3. [TraceLink University](/resources/tracelink-university) # Receiving advice acceptances transactions - [Download PDF](/node/626196/pdf) - [Share](#) - [ LinkedIn ](https://www.linkedin.com/shareArticle?mini=true&url=https://www.tracelink.com/resources/tracelink-university/receiving-advice-acceptances-transactions&title=Receiving advice acceptances transactions&summary=Receiving advice acceptances streamline goods transportation between entities to verify and manage delivery details efficiently. &source=TraceLink "LinkedIn") - [ Facebook ](https://www.facebook.com/share.php?u=https://www.tracelink.com/resources/tracelink-university/receiving-advice-acceptances-transactions&t=Receiving advice acceptances transactions "Facebook") - [ Mail ](mailto:?subject=Receiving advice acceptances transactions+|+TraceLink&body=https://www.tracelink.com/resources/tracelink-university/receiving-advice-acceptances-transactions "Mail") - [ Twitter ](https://twitter.com/intent/tweet?text=Receiving advice acceptances transactions https://www.tracelink.com/resources/tracelink-university/receiving-advice-acceptances-transactions&via=TraceLink "Twitter") #### Table of contents 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. ![](/sites/default/files/tech_comms/mpl/Content/Resources/Images/global_images/note_tip_24x24.png) 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 [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Guidelines](#) Input Element Occurs Length Description Example ISA \[1…1\] – **Required.**ISA interchange envelope. – ISA01 \[1…1\] 2/2 **Required.**Authorization information qualifier identifying the type of identifier in ISA02. Valid values: - `00` – No authorization information in ISA02 - `01` – UCS communications - `02`– EDX - `03` – Additional identifier - `04` – Rail communication identifier - `05` – Dept of Defense (DOD) identifier - `06` – US Federal Government identifier - `07` – Truck communications identifier - `08` – Ocean communications identifier Typically this value – 00 00 ISA02 \[1…1\] 10/10 **Required.**Authorization identifier value used for additional identification or authorization of the interchange sender or the data in the interchange. - If ISA01 = `00`, this will be populated by a ten spaces. - If ISA01 ≠ `00`, ISA02 must be populated with an identifier padded to 10 characters, if less than 10 characters. – ISA03 \[1…1\] 2/2 **Required.**Qualifier for security information in ISA04. Valid values: - `00` - No security information present. - `01` - Password. 00 ISA04 \[1…1\] 10/10 **Required.**Security information identifying for the interchange sender or data. - If ISA01 = `00`, this will be populated by ten spaces. - If ISA01 ≠ `00`, ISA04 must be populated with a password that is padded to 10 characters, if less than 10 characters. – ISA05 \[1…1\] 2/2 **Required.**Interchange sender partner ID qualifier. 07 ISA06 \[1…1\] 15/15 **Required.**ISA interchange sender identifier. 7777776067344 ISA07 \[1…1\] 2/2 **Required.**Interchange receiver partner ID qualifier. 01 ISA08 \[1…1\] 15/15 **Required.**ISA interchange receiver ID. 888888404358877 ISA09 \[1…1\] 6/6 **Required.**Interchange date in 6 char date format YYMMDD. 241215 ISA10 \[1…1\] 4/4 **Required.**Interchange time in 4 char time format HHMM. 1420 ISA11 \[1…1\] 1/1 **Required.**The value of this element is dependent on X12 version. - `Version 4012 and earlier` – Interchange control standards identifier. The valid value is `U`. - `Version 004020 and later` – Repetition separator, a delimiter that separates repeated occurrences of a data element or composite data structure, which must be different from the data element separator, component separator, and segment terminator. ^ ISA12 \[1…1\] 5/5 **Required.**Interchange control version number. This could be any X12 version. 00501 ISA13 \[1…1\] 9/9 **Required.**ISA interchange control number. 0000000000619827 ISA14 \[1…1\] 1/1 **Required.**Interchange level acknowledgment requested. Valid values: - `0` - No acknowledgment requested. - `1` - Interchange level acknowledgment requested. 0 ISA15 \[1…1\] 1/1 **Required.**Indicates whether the interchange is for production, test, or information purposes. Valid values: - `I` - Information. - `P` - Production data. - `T` - Test data. P ISA16 \[1…1\] 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 \[1…\*\] – **Required.**GS group functional envelope. Child of ISA. Only one GS group expected per interchange. – GS01 \[1…1\] 2/2 **Required.**GS group function code. The valid value is `RC` – Receiving Advice X12 861. RC GS02 \[1…1\] 2/15 **Required.**Application sender's code in the group envelope. 2222224043588 GS03 \[1…1\] 2/15 **Required.**Application receiver's code in the group envelope. TRACELINK GS04 \[1…1\] 8/8 **Required.**Group envelope date value in date format YYYYMMDD. 20241215 GS05 \[1…1\] 4/8 **Required.**Group envelope time value in time format HHMM or HHMMSS. 142000 GS06 \[1…1\] 1/9 **Required.**Group control identifier. 619827 GS07 \[1…1\] 1/2 **Required.**Responsible agency code. Valid values: - `T` – Transportation data coordinating committee (TDCC). - `X` – X12 accredited standards committee. X GS08 \[1…1\] 1/12 **Required.**X12 message version code. This could be any X12 version. 005010 ST \[1…\*\] – ST transaction set envelope. Child of GS group. Only one ST transaction expected. – ST01 \[1…1\] 3/3 **Required.**Transaction set identifier code. 861 ST02 \[1…1\] 4/9 **Required.**Transaction set ID number. Counter for each ST segment beginning with 1. 0001 BRA \[1…1\] – **Required.**Beginning segment for receiving advice. – BRA01 \[1…1\] 1/80 **Required.**Transaction reference identifier is the receiving or delivery document identifier for the receiving advice. 8524700258 BRA02 \[1…1\] 8/8 **Required.**Date of receiving advice in date format YYYYMMDD. 20241215 BRA03 \[1…1\] 2/2 Code identifying purpose of transaction set. Valid values: - `00` – Original - `02` – Create **Required.** - `03` – Delete - `04` – Change - `05` – Replace - `45` – Follow up 00 BRA04 \[1…1\] 1/1 **Required.**Code specifying type of receiving advice. Valid values: - `1` – Receiving Advice - `2` – Post Receipt - `3` – Disposition - `8` – Acceptance 1 BRA05 \[0…1\] 4/8 The time when receiving advice transaction set document is created. – BRA06 \[0…1\] 2/2 Code designating physical condition or status of units received in a specific shipment. – BRA07 \[0…1\] 1/2 Code indicating type of action. – CUR \[0…1\] – CUR segment is used to specify the currency (dollars, pounds, francs, etc.) used in a transaction. – CUR01 \[1…1\] 2/3 **Required.**Currency entity code. SE CUR02 \[1…1\] 3/3 **Required.**Code (Standard ISO) for country in whose currency the charges are specified. USD REF \[0…\*\] – REF segment is used to specify receiving advice information. – REF01 \[1…1\] 2/3 **Required.**Code qualifying the reference identification. - `SI` – Shipment - `BM` – Bill of lading - `2I` - Tracking number - `CN` – Carrier reference - `DO` – Delivery - `PK` – Packing List - `TB` – Trucker bill Of lading - `IA` – Internal vendor Number - `KK` – Proof of delivery DO REF02 \[0…1\] 1/80 Reference or transaction identifier. If REF01 is populated, REF02 is required. 8456732 REF03 \[0…1\] 1/80 A free-form description to clarify the related data elements and their content. – DTM \[1…10\] – DTM segment is used to specify pertinent dates and times. – DTM01 \[1…1\] 3/3 **Required.**Code specifying type of date or time, or both date and time. Valid values: - `050` – Goods receipt - `201` – Acceptance - `011` – Shipped 050 DTM02 \[0…1\] 8/8 Date as defined by one of the valid enumerators in DTM01 in date format YYYYMMDD. 20241215 DTM03 \[0…1\] 4/8 Time recorded for date in time format HHMM or HHMMSS or HHMMSSnn. 122655 DTM04 \[0…1\] 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 \[0…25\] – PRF segment is used to provide reference to a specific purchase order – PRF01 \[1…1\] 1/22 **Required.**Identifying number for Purchase Order assigned by the orderer or purchaser. 0045687901 PRF02 \[0…1\] 1/30 Number identifying a release against a purchase order previously placed by the parties involved in the transaction. – PRF03 \[0…1\] 1/8 Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set. – PRF04 \[0…1\] 8/8 Purchase order date in date format YYYYMMDD. 20241215 TD1 \[0…2\] – TD1 segment is used to specify the transportation details relative to commodity, weight, and quantity – TD101 \[0…1\] 3/5 Packaging container unit of measure. Valid values: - `PLT` - Pallet - `CAS` - Case - `BDL`- Bundle/Inner case If segment TD1 is present, TD101 and TD102 are required. PLT TD102 \[0…1\] 1/7 Number of units (pieces) of the lading commodity. If segment TD1 is present, TD101 and TD102 are required. 45 TD103 \[0…1\] 1/1 Commodity code qualifier. – TD104 \[0…1\] 1/30 Commodity code. – TD105 \[0…1\] 1/50 Lading description. – TD106 \[0…1\] 1/2 Code defining the weight type: Valid values: - `G` - Gross weight - `L` - Allowed - `N` - Net Weight - `T` - Tare G TD107 \[0…1\] 1/10 Numeric value of weight. If TD106 is present, TD107 is required. – TD108 \[0…1\] 2/2 Unit of measure for the weight. If TD106 and TD107 are present, TD108 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values](#)- `02` – Statute Mile - `4G` – Microliter - `AM` – Ampoule - `AV` – Capsule - `BD` – Bundle - `BG` – Bag - `BO` – Bottle - `BX` – Box - `C3` – Centiliter - `CA` – Case - `CC` – Cubic Centimeter - `CF` – Cubic Feet - `CG` – Card Blister - `CH` – Container - `CI` – Cubic Inches - `CL` – Cylinder - `CM` – Centimeter - `CN` – Can - `CP` – Crate - `CQ` – Cartridge - `CR` – Cubic Meters - `CT` – Carton - `DA` – Day - `DI` – Dispenser - `DK` – Kilometers - `DL` – Deciliter - `DM` – Decimeter - `DQ` – Cubic decimeters - `DR` – Drum - `DS` – Display - `DZ` – Dozen - `EA` – Each - `FO` – US Fluid Ounce - `FT` – Foot - `GA` – US Gallon - `GL` – Gram/Liter - `GR` – Gram - `GS` – Gross - `H4` – Hectoliter - `HF` – Hundred Feet - `HR` – Hours - `IN` – Inch - `K6` – Kiloliters - `KG` – Kilogram - `KT` – Kit - `LB` – US Pound - `LF` – Linear Foot - `LO` – Lot (unit of procurement) - `LT` – Liter - `LY` – Linear Yard - `MC` – Microgram - `ME` – Milligram - `ML` – Milliliter - `MM` – Millimeter - `MO` – Months - `01` – Cubic millimeter - `MR` – Meter - `OZ` – Ounce - `P1` – Percent - `PC` – Piece - `PF` – Pallet - `PH` – Pack - `PK` – Package - `PR` – Pair - `PT` – Pint - `QT` – Quart - `RL` – Roll - `SC` – Square Centimeter - `SF` – Square Foot - `SH` – Sheet - `SI` – Square Inch - `SM` – Square Meter - `SP` – Self Package - `ST` – Set - `SY` – Square Yard - `SZ` – Syringe - `T3` – Thousand Pieces - `TB` – Tube - `TH` – Thousands - `TN` – Tonne - `TS` – Thousands - `TY` – Tray - `U2` – Tablet - `UM` – Million - `UN` – Unit - `US` – Dosage Form - `V2` – Pouch - `VI` – Vial - `WK` – Week - `YD` – Yard - `YR` – Years TD5 \[0…12\] – TD5 segment is used to specify the carrier and sequence of routing and provide transit time information. – TD501 \[0…1\] 1/2 Routing sequence code defining the relationship of a carrier to a specific shipment movement. – TD502 \[0…1\] 1/2 Qualifier identifying the standard carrier alpha code (SCAC) identifying a carrier. Valid value is `2` - SCAC. TD502 is required if TD503 is present. 2 TD503 \[0…1\] 2/80 Standard alpha carrier code (SCAC) as defined by the qualifier in TD502. – TD504 \[0…1\] 1/2 Code specifying the method or type of transportation for the shipment. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `A` - Air - `AE` - Air express - `AF` - Air frieght - `H` - To be picked up customer - `J` - Truck - `L` - Contract carrier - `LT` - Less than truckload - `M` - Motor (Common Carrier) - `O` - Container by ship - `R` - Shipped by train - `S` - Sea - `SR` - Supplier truck - `X` - Piggy back transport, ie trailer on train - `ZZ` - Custom agreed transport TD503 is required if TD502 is present. J TD505 \[0…1\] 1/35 Business name of the carrier party identified by SCAC code in TD503. – TD506 \[0…1\] 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 \[0…12\] – TD3 segment is used to specify transportation details relating to the equipment used by the carrier. – TD301 \[0…1\] 2/2 Code identifying the type of equipment used for shipment. Valid values: - `AP` - Aircraft - `CN` - Container - `RR` - Railcar - `TA` - Trailer - `VT` - Ship CN TD302 \[0…1\] 1/4 Equipment identifier prefix or alphabetic part of the equipment item's identifier. If TD302 is present, TD303 is required. – TD303 \[0…1\] 1/15 Equipment identifier. The equipment unit's unique identifier. If TD303 is present, TD302 is required. – N1 \[0…200\] – Name and address segment loop. The following party types are currently supported: - `BY` - Customer - `CA` - Carrier (for Carrier and SCAC) - `SU` - Supplier or vendor - `SF` - Ship from party - `ST` - Ship to party - `SE` - Sales organization - `RL` - Reporting location - `FW` - Freight forwarder – N101 \[1…1\] 2/3 **Required.**Entity qualifier for the carrier party identifier and address information. - `BY` - Customer - `CA` - Carrier (for Carrier and SCAC) - `SU` - Supplier or vendor - `SF` - Ship from party - `ST` - Ship to party - `SE` - Sales organization - `RL` - Reporting location - `FW` - Freight forwarder BY N102 \[0…1\] 1/60 Business party or location name. At least one of N102 or N103 is required. Both may be present. Pharma supplier 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 At least one of N102 or N103 is required. Both may be present. If N103 is present, N104 is required. UL N104 \[0…1\] 2/80 Carrier party identifier as qualified by N103 mapping to companyIdentifierValue. If N103 is present, N104 is required. 8568745 N2 \[0…1\] – N2: Additional names: Child of carrier party N1 name segment. – N201 \[1…1\] 1/55 **Required.**Free-form name for business name 2. – N202 \[0…1\] 1/55 Free-form name for business name 3. – N3 \[0…1\] – N3: Address: Child of carrier party N1 name segment. – N301 \[1…1\] 1/55 **Required.**Street address 1 Required if segment N3 is present. 555 Neelan Road N302 \[0…1\] 1/55 Street address 2. Suite 123 N4 \[0…1\] – N4: Geographic Location. Child of carrier party N1 name segment. – N401 \[0…1\] 2/30 City name. Sacramento N402 \[0…1\] 2/2 State or province code. Code (Standard state/province) as defined by appropriate government agency. CA N403 \[0…1\] 3/15 Postal code. Code defining international postal zone code excluding punctuation and blanks. 95833 N404 \[0…1\] 2/3 Country code. US PER \[0…3\] – PER segment under N1 loop is used to identify a person or office to whom administrative communications should be directed. – PER01 \[1…1\] 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 \[0…1\] 1/60 Name of the contact person responsible for authenticating the pedigree information. John Smith 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 If PER03 is present, PER04 is required. TE PER04 \[0…1\] 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 \[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 If PER05 is present, PER06 is required EM PER06 \[0…1\] 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 \[0…\*\] – 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 \[0…1\] 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 \[0…1\] 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 \[0…1\] 2/2 Unit of measure for number of units received or accepted. If RCD02 is present, RCD03-01 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values](#)- `02` – Statute Mile - `4G` – Microliter - `AM` – Ampoule - `AV` – Capsule - `BD` – Bundle - `BG` – Bag - `BO` – Bottle - `BX` – Box - `C3` – Centiliter - `CA` – Case - `CC` – Cubic Centimeter - `CF` – Cubic Feet - `CG` – Card Blister - `CH` – Container - `CI` – Cubic Inches - `CL` – Cylinder - `CM` – Centimeter - `CN` – Can - `CP` – Crate - `CQ` – Cartridge - `CR` – Cubic Meters - `CT` – Carton - `DA` – Day - `DI` – Dispenser - `DK` – Kilometers - `DL` – Deciliter - `DM` – Decimeter - `DQ` – Cubic decimeters - `DR` – Drum - `DS` – Display - `DZ` – Dozen - `EA` – Each - `FO` – US Fluid Ounce - `FT` – Foot - `GA` – US Gallon - `GL` – Gram/Liter - `GR` – Gram - `GS` – Gross - `H4` – Hectoliter - `HF` – Hundred Feet - `HR` – Hours - `IN` – Inch - `K6` – Kiloliters - `KG` – Kilogram - `KT` – Kit - `LB` – US Pound - `LF` – Linear Foot - `LO` – Lot (unit of procurement) - `LT` – Liter - `LY` – Linear Yard - `MC` – Microgram - `ME` – Milligram - `ML` – Milliliter - `MM` – Millimeter - `MO` – Months - `01` – Cubic millimeter - `MR` – Meter - `OZ` – Ounce - `P1` – Percent - `PC` – Piece - `PF` – Pallet - `PH` – Pack - `PK` – Package - `PR` – Pair - `PT` – Pint - `QT` – Quart - `RL` – Roll - `SC` – Square Centimeter - `SF` – Square Foot - `SH` – Sheet - `SI` – Square Inch - `SM` – Square Meter - `SP` – Self Package - `ST` – Set - `SY` – Square Yard - `SZ` – Syringe - `T3` – Thousand Pieces - `TB` – Tube - `TH` – Thousands - `TN` – Tonne - `TS` – Thousands - `TY` – Tray - `U2` – Tablet - `UM` – Million - `UN` – Unit - `US` – Dosage Form - `V2` – Pouch - `VI` – Vial - `WK` – Week - `YD` – Yard - `YR` – Years EA RCD04 \[0…1\] 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 \[0…1\] 2/2 Unit of measure for number of units returned. If RCD05-01 is present, RCD04 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values](#)- `02` – Statute Mile - `4G` – Microliter - `AM` – Ampoule - `AV` – Capsule - `BD` – Bundle - `BG` – Bag - `BO` – Bottle - `BX` – Box - `C3` – Centiliter - `CA` – Case - `CC` – Cubic Centimeter - `CF` – Cubic Feet - `CG` – Card Blister - `CH` – Container - `CI` – Cubic Inches - `CL` – Cylinder - `CM` – Centimeter - `CN` – Can - `CP` – Crate - `CQ` – Cartridge - `CR` – Cubic Meters - `CT` – Carton - `DA` – Day - `DI` – Dispenser - `DK` – Kilometers - `DL` – Deciliter - `DM` – Decimeter - `DQ` – Cubic decimeters - `DR` – Drum - `DS` – Display - `DZ` – Dozen - `EA` – Each - `FO` – US Fluid Ounce - `FT` – Foot - `GA` – US Gallon - `GL` – Gram/Liter - `GR` – Gram - `GS` – Gross - `H4` – Hectoliter - `HF` – Hundred Feet - `HR` – Hours - `IN` – Inch - `K6` – Kiloliters - `KG` – Kilogram - `KT` – Kit - `LB` – US Pound - `LF` – Linear Foot - `LO` – Lot (unit of procurement) - `LT` – Liter - `LY` – Linear Yard - `MC` – Microgram - `ME` – Milligram - `ML` – Milliliter - `MM` – Millimeter - `MO` – Months - `01` – Cubic millimeter - `MR` – Meter - `OZ` – Ounce - `P1` – Percent - `PC` – Piece - `PF` – Pallet - `PH` – Pack - `PK` – Package - `PR` – Pair - `PT` – Pint - `QT` – Quart - `RL` – Roll - `SC` – Square Centimeter - `SF` – Square Foot - `SH` – Sheet - `SI` – Square Inch - `SM` – Square Meter - `SP` – Self Package - `ST` – Set - `SY` – Square Yard - `SZ` – Syringe - `T3` – Thousand Pieces - `TB` – Tube - `TH` – Thousands - `TN` – Tonne - `TS` – Thousands - `TY` – Tray - `U2` – Tablet - `UM` – Million - `UN` – Unit - `US` – Dosage Form - `V2` – Pouch - `VI` – Vial - `WK` – Week - `YD` – Yard - `YR` – Years EA RCD06 \[0…1\] 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 \[0…1\] 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. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values](#)- `02` – Statute Mile - `4G` – Microliter - `AM` – Ampoule - `AV` – Capsule - `BD` – Bundle - `BG` – Bag - `BO` – Bottle - `BX` – Box - `C3` – Centiliter - `CA` – Case - `CC` – Cubic Centimeter - `CF` – Cubic Feet - `CG` – Card Blister - `CH` – Container - `CI` – Cubic Inches - `CL` – Cylinder - `CM` – Centimeter - `CN` – Can - `CP` – Crate - `CQ` – Cartridge - `CR` – Cubic Meters - `CT` – Carton - `DA` – Day - `DI` – Dispenser - `DK` – Kilometers - `DL` – Deciliter - `DM` – Decimeter - `DQ` – Cubic decimeters - `DR` – Drum - `DS` – Display - `DZ` – Dozen - `EA` – Each - `FO` – US Fluid Ounce - `FT` – Foot - `GA` – US Gallon - `GL` – Gram/Liter - `GR` – Gram - `GS` – Gross - `H4` – Hectoliter - `HF` – Hundred Feet - `HR` – Hours - `IN` – Inch - `K6` – Kiloliters - `KG` – Kilogram - `KT` – Kit - `LB` – US Pound - `LF` – Linear Foot - `LO` – Lot (unit of procurement) - `LT` – Liter - `LY` – Linear Yard - `MC` – Microgram - `ME` – Milligram - `ML` – Milliliter - `MM` – Millimeter - `MO` – Months - `01` – Cubic millimeter - `MR` – Meter - `OZ` – Ounce - `P1` – Percent - `PC` – Piece - `PF` – Pallet - `PH` – Pack - `PK` – Package - `PR` – Pair - `PT` – Pint - `QT` – Quart - `RL` – Roll - `SC` – Square Centimeter - `SF` – Square Foot - `SH` – Sheet - `SI` – Square Inch - `SM` – Square Meter - `SP` – Self Package - `ST` – Set - `SY` – Square Yard - `SZ` – Syringe - `T3` – Thousand Pieces - `TB` – Tube - `TH` – Thousands - `TN` – Tonne - `TS` – Thousands - `TY` – Tray - `U2` – Tablet - `UM` – Million - `UN` – Unit - `US` – Dosage Form - `V2` – Pouch - `VI` – Vial - `WK` – Week - `YD` – Yard - `YR` – Years EA RCD08 \[0…1\] 2/2 Questioned quantity reason code describing the physical condition or status of units received in a specific shipment. Valid values: - `01` - Product or container was damaged - `02` - Quantity is short - `03` - Quantity is more than ordered - `09` - Item on hold - `10` - Material has been scrapped - `11` - Supplier's YTD cumulative quantity to be adjusted - `16` - Receipt without corresponding ASN If RCD06 is present, RCD07-01 and RCD08 are required. 01 RCD09 \[0…1\] 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 \[0…1\] 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. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values](#)- `02` – Statute Mile - `4G` – Microliter - `AM` – Ampoule - `AV` – Capsule - `BD` – Bundle - `BG` – Bag - `BO` – Bottle - `BX` – Box - `C3` – Centiliter - `CA` – Case - `CC` – Cubic Centimeter - `CF` – Cubic Feet - `CG` – Card Blister - `CH` – Container - `CI` – Cubic Inches - `CL` – Cylinder - `CM` – Centimeter - `CN` – Can - `CP` – Crate - `CQ` – Cartridge - `CR` – Cubic Meters - `CT` – Carton - `DA` – Day - `DI` – Dispenser - `DK` – Kilometers - `DL` – Deciliter - `DM` – Decimeter - `DQ` – Cubic decimeters - `DR` – Drum - `DS` – Display - `DZ` – Dozen - `EA` – Each - `FO` – US Fluid Ounce - `FT` – Foot - `GA` – US Gallon - `GL` – Gram/Liter - `GR` – Gram - `GS` – Gross - `H4` – Hectoliter - `HF` – Hundred Feet - `HR` – Hours - `IN` – Inch - `K6` – Kiloliters - `KG` – Kilogram - `KT` – Kit - `LB` – US Pound - `LF` – Linear Foot - `LO` – Lot (unit of procurement) - `LT` – Liter - `LY` – Linear Yard - `MC` – Microgram - `ME` – Milligram - `ML` – Milliliter - `MM` – Millimeter - `MO` – Months - `01` – Cubic millimeter - `MR` – Meter - `OZ` – Ounce - `P1` – Percent - `PC` – Piece - `PF` – Pallet - `PH` – Pack - `PK` – Package - `PR` – Pair - `PT` – Pint - `QT` – Quart - `RL` – Roll - `SC` – Square Centimeter - `SF` – Square Foot - `SH` – Sheet - `SI` – Square Inch - `SM` – Square Meter - `SP` – Self Package - `ST` – Set - `SY` – Square Yard - `SZ` – Syringe - `T3` – Thousand Pieces - `TB` – Tube - `TH` – Thousands - `TN` – Tonne - `TS` – Thousands - `TY` – Tray - `U2` – Tablet - `UM` – Million - `UN` – Unit - `US` – Dosage Form - `V2` – Pouch - `VI` – Vial - `WK` – Week - `YD` – Yard - `YR` – Years EA RCD11 \[0…1\] 2/2 Questioned quantity reason code describing the physical condition or status of units received in a specific shipment. Valid values: - `01` - Product or container was damaged - `02` - Quantity is short - `03` - Quantity is more than ordered - `09` - Item on hold - `10` - Material has been scrapped - `11` - Supplier's YTD cumulative quantity to be adjusted - `16` - Receipt without corresponding ASN If RCD09 is present, RCD10-01 and RCD11 are required. 02 RCD12 \[0…1\] 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 \[0…1\] 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. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values](#)- `02` – Statute Mile - `4G` – Microliter - `AM` – Ampoule - `AV` – Capsule - `BD` – Bundle - `BG` – Bag - `BO` – Bottle - `BX` – Box - `C3` – Centiliter - `CA` – Case - `CC` – Cubic Centimeter - `CF` – Cubic Feet - `CG` – Card Blister - `CH` – Container - `CI` – Cubic Inches - `CL` – Cylinder - `CM` – Centimeter - `CN` – Can - `CP` – Crate - `CQ` – Cartridge - `CR` – Cubic Meters - `CT` – Carton - `DA` – Day - `DI` – Dispenser - `DK` – Kilometers - `DL` – Deciliter - `DM` – Decimeter - `DQ` – Cubic decimeters - `DR` – Drum - `DS` – Display - `DZ` – Dozen - `EA` – Each - `FO` – US Fluid Ounce - `FT` – Foot - `GA` – US Gallon - `GL` – Gram/Liter - `GR` – Gram - `GS` – Gross - `H4` – Hectoliter - `HF` – Hundred Feet - `HR` – Hours - `IN` – Inch - `K6` – Kiloliters - `KG` – Kilogram - `KT` – Kit - `LB` – US Pound - `LF` – Linear Foot - `LO` – Lot (unit of procurement) - `LT` – Liter - `LY` – Linear Yard - `MC` – Microgram - `ME` – Milligram - `ML` – Milliliter - `MM` – Millimeter - `MO` – Months - `01` – Cubic millimeter - `MR` – Meter - `OZ` – Ounce - `P1` – Percent - `PC` – Piece - `PF` – Pallet - `PH` – Pack - `PK` – Package - `PR` – Pair - `PT` – Pint - `QT` – Quart - `RL` – Roll - `SC` – Square Centimeter - `SF` – Square Foot - `SH` – Sheet - `SI` – Square Inch - `SM` – Square Meter - `SP` – Self Package - `ST` – Set - `SY` – Square Yard - `SZ` – Syringe - `T3` – Thousand Pieces - `TB` – Tube - `TH` – Thousands - `TN` – Tonne - `TS` – Thousands - `TY` – Tray - `U2` – Tablet - `UM` – Million - `UN` – Unit - `US` – Dosage Form - `V2` – Pouch - `VI` – Vial - `WK` – Week - `YD` – Yard - `YR` – Years EA RCD14 \[0…1\] 2/2 Questioned quantity reason code describing the physical condition or status of units received in a specific shipment Valid values: - `01` - Product or container was damaged - `02` - Quantity is short - `03` - Quantity is more than ordered - `09` - Item on hold - `10` - Material has been scrapped - `11` - Supplier's YTD cumulative quantity to be adjusted - `16` - Receipt without corresponding ASN If RCD12 is present, RCD13-01 and RCD14 are required. 03 RCD15 \[0…1\] 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 \[0…1\] 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. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values](#)- `02` – Statute Mile - `4G` – Microliter - `AM` – Ampoule - `AV` – Capsule - `BD` – Bundle - `BG` – Bag - `BO` – Bottle - `BX` – Box - `C3` – Centiliter - `CA` – Case - `CC` – Cubic Centimeter - `CF` – Cubic Feet - `CG` – Card Blister - `CH` – Container - `CI` – Cubic Inches - `CL` – Cylinder - `CM` – Centimeter - `CN` – Can - `CP` – Crate - `CQ` – Cartridge - `CR` – Cubic Meters - `CT` – Carton - `DA` – Day - `DI` – Dispenser - `DK` – Kilometers - `DL` – Deciliter - `DM` – Decimeter - `DQ` – Cubic decimeters - `DR` – Drum - `DS` – Display - `DZ` – Dozen - `EA` – Each - `FO` – US Fluid Ounce - `FT` – Foot - `GA` – US Gallon - `GL` – Gram/Liter - `GR` – Gram - `GS` – Gross - `H4` – Hectoliter - `HF` – Hundred Feet - `HR` – Hours - `IN` – Inch - `K6` – Kiloliters - `KG` – Kilogram - `KT` – Kit - `LB` – US Pound - `LF` – Linear Foot - `LO` – Lot (unit of procurement) - `LT` – Liter - `LY` – Linear Yard - `MC` – Microgram - `ME` – Milligram - `ML` – Milliliter - `MM` – Millimeter - `MO` – Months - `01` – Cubic millimeter - `MR` – Meter - `OZ` – Ounce - `P1` – Percent - `PC` – Piece - `PF` – Pallet - `PH` – Pack - `PK` – Package - `PR` – Pair - `PT` – Pint - `QT` – Quart - `RL` – Roll - `SC` – Square Centimeter - `SF` – Square Foot - `SH` – Sheet - `SI` – Square Inch - `SM` – Square Meter - `SP` – Self Package - `ST` – Set - `SY` – Square Yard - `SZ` – Syringe - `T3` – Thousand Pieces - `TB` – Tube - `TH` – Thousands - `TN` – Tonne - `TS` – Thousands - `TY` – Tray - `U2` – Tablet - `UM` – Million - `UN` – Unit - `US` – Dosage Form - `V2` – Pouch - `VI` – Vial - `WK` – Week - `YD` – Yard - `YR` – Years EA RCD17 \[0…1\] 2/2 Questioned quantity reason code describing the physical condition or status of units received in a specific shipment Valid values: - `01` - Product or container was damaged - `02` - Quantity is short - `03` - Quantity is more than ordered - `09` - Item on hold - `10` - Material has been scrapped - `11` - Supplier's YTD cumulative quantity to be adjusted - `16` - Receipt without corresponding ASN If RCD15 is present, RCD16-01 and RCD17 are required. 09 RCD18 \[0…1\] 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 \[0…1\] 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. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values](#)- `02` – Statute Mile - `4G` – Microliter - `AM` – Ampoule - `AV` – Capsule - `BD` – Bundle - `BG` – Bag - `BO` – Bottle - `BX` – Box - `C3` – Centiliter - `CA` – Case - `CC` – Cubic Centimeter - `CF` – Cubic Feet - `CG` – Card Blister - `CH` – Container - `CI` – Cubic Inches - `CL` – Cylinder - `CM` – Centimeter - `CN` – Can - `CP` – Crate - `CQ` – Cartridge - `CR` – Cubic Meters - `CT` – Carton - `DA` – Day - `DI` – Dispenser - `DK` – Kilometers - `DL` – Deciliter - `DM` – Decimeter - `DQ` – Cubic decimeters - `DR` – Drum - `DS` – Display - `DZ` – Dozen - `EA` – Each - `FO` – US Fluid Ounce - `FT` – Foot - `GA` – US Gallon - `GL` – Gram/Liter - `GR` – Gram - `GS` – Gross - `H4` – Hectoliter - `HF` – Hundred Feet - `HR` – Hours - `IN` – Inch - `K6` – Kiloliters - `KG` – Kilogram - `KT` – Kit - `LB` – US Pound - `LF` – Linear Foot - `LO` – Lot (unit of procurement) - `LT` – Liter - `LY` – Linear Yard - `MC` – Microgram - `ME` – Milligram - `ML` – Milliliter - `MM` – Millimeter - `MO` – Months - `01` – Cubic millimeter - `MR` – Meter - `OZ` – Ounce - `P1` – Percent - `PC` – Piece - `PF` – Pallet - `PH` – Pack - `PK` – Package - `PR` – Pair - `PT` – Pint - `QT` – Quart - `RL` – Roll - `SC` – Square Centimeter - `SF` – Square Foot - `SH` – Sheet - `SI` – Square Inch - `SM` – Square Meter - `SP` – Self Package - `ST` – Set - `SY` – Square Yard - `SZ` – Syringe - `T3` – Thousand Pieces - `TB` – Tube - `TH` – Thousands - `TN` – Tonne - `TS` – Thousands - `TY` – Tray - `U2` – Tablet - `UM` – Million - `UN` – Unit - `US` – Dosage Form - `V2` – Pouch - `VI` – Vial - `WK` – Week - `YD` – Yard - `YR` – Years EA RCD20 \[0…1\] 2/2 Questioned quantity reason code describing the physical condition or status of units received in a specific shipment. Valid values: - `01` - Product or container was damaged - `02` - Quantity is short - `03` - Quantity is more than ordered - `09` - Item on hold - `10` - Material has been scrapped - `11` - Supplier's YTD cumulative quantity to be adjusted - `16` - Receipt without corresponding ASN If RCD18 is present, RCD19-01 and RCD20 are required. 10 LIN \[1…100\] – LIN segment within RCD loop specifies product identifiers and identifier types. – LIN01 \[0…1\] 1/20 Line item number or other assigned identifier value. – LIN02 \[1…1\] 2/2 **Required.**Product code qualifier specifying the product identifier type. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `BP` – Customer's material number - `CB` – Buyer Catalog - `EN` – EAN 2-5-5-1 - `FV` – Canada product number - `IN` – Customer's(Buyer's) product item number - `MF` – Manufacturer's product number - `MG` – Manufacturer's part number - `N1` – US National-Drug-Code-NDC442-with-hyphen-separators - `N2` – US National-Drug-Code-NDC532-with-hyphen-separators - `N3` – US National-Drug-Code-NDC541-with-hyphen-separators - `N4` – US-National-Drug-Code-NDC542-with-hyphen-separators - `N5` – US National Health Related Item Code with hypen separator with 5 and characters - `N6` – US National Health Related Item Code with hypen separators with 6 and 4 characters - `ND` – US-National-Drug-Code - `NH` – US National Health Related Item Code - `PI` – Customer's material number - `SK` – Stock keeping unit - `UA` – UPC Case Code (2-5-5) - `UJ` - PackageUPC - `UI` – UPC Consumer Package Code (1-5-5) - `UK` – GTIN14 identifier - `UP` – EAN/UPC Universal Item Number/GTIN12 - `UX` – Universal product number - `VC` – Vendor (Supplier) material number - `VN` – Supplier material number. – LIN03 \[1…1\] 1/80 **Required.**Product or service identifier as defined by the qualifier in LIN02 – LIN04 \[0…1\] 2/2 Product code qualifier specifying the product identifier type. If LIN04 is present, LIN05 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `BP` – Customer's material number - `CB` – Buyer Catalog - `EN` – EAN 2-5-5-1 - `FV` – Canada product number - `IN` – Customer's(Buyer's) product item number - `MF` – Manufacturer's product number - `MG` – Manufacturer's part number - `N1` – US National-Drug-Code-NDC442-with-hyphen-separators - `N2` – US National-Drug-Code-NDC532-with-hyphen-separators - `N3` – US National-Drug-Code-NDC541-with-hyphen-separators - `N4` – US-National-Drug-Code-NDC542-with-hyphen-separators - `N5` – US National Health Related Item Code with hypen separator with 5 and characters - `N6` – US National Health Related Item Code with hypen separators with 6 and 4 characters - `ND` – US-National-Drug-Code - `NH` – US National Health Related Item Code - `PI` – Customer's material number - `SK` – Stock keeping unit - `UA` – UPC Case Code (2-5-5) - `UJ` - PackageUPC - `UI` – UPC Consumer Package Code (1-5-5) - `UK` – GTIN14 identifier - `UP` – EAN/UPC Universal Item Number/GTIN12 - `UX` – Universal product number - `VC` – Vendor (Supplier) material number - `VN` – Supplier material number. – LIN05 \[0…1\] 1/80 Product or service identifier as defined by the qualifier in LIN02. If LIN06 is present, LIN04 is required. – LIN06 \[0…1\] 2/2 Product code qualifier specifying the product identifier type. If LIN06 is present, LIN07 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `BP` – Customer's material number - `CB` – Buyer Catalog - `EN` – EAN 2-5-5-1 - `FV` – Canada product number - `IN` – Customer's(Buyer's) product item number - `MF` – Manufacturer's product number - `MG` – Manufacturer's part number - `N1` – US National-Drug-Code-NDC442-with-hyphen-separators - `N2` – US National-Drug-Code-NDC532-with-hyphen-separators - `N3` – US National-Drug-Code-NDC541-with-hyphen-separators - `N4` – US-National-Drug-Code-NDC542-with-hyphen-separators - `N5` – US National Health Related Item Code with hypen separator with 5 and characters - `N6` – US National Health Related Item Code with hypen separators with 6 and 4 characters - `ND` – US-National-Drug-Code - `NH` – US National Health Related Item Code - `PI` – Customer's material number - `SK` – Stock keeping unit - `UA` – UPC Case Code (2-5-5) - `UJ` - PackageUPC - `UI` – UPC Consumer Package Code (1-5-5) - `UK` – GTIN14 identifier - `UP` – EAN/UPC Universal Item Number/GTIN12 - `UX` – Universal product number - `VC` – Vendor (Supplier) material number - `VN` – Supplier material number. – LIN07 \[0…1\] 1/80 Product or service identifier as defined by the qualifier in LIN02. If LIN07 is present, LIN06 is required. – LIN08 \[0…1\] 2/2 Product code qualifier specifying the product identifier type. If LIN08 is present, LIN09 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `BP` – Customer's material number - `CB` – Buyer Catalog - `EN` – EAN 2-5-5-1 - `FV` – Canada product number - `IN` – Customer's(Buyer's) product item number - `MF` – Manufacturer's product number - `MG` – Manufacturer's part number - `N1` – US National-Drug-Code-NDC442-with-hyphen-separators - `N2` – US National-Drug-Code-NDC532-with-hyphen-separators - `N3` – US National-Drug-Code-NDC541-with-hyphen-separators - `N4` – US-National-Drug-Code-NDC542-with-hyphen-separators - `N5` – US National Health Related Item Code with hypen separator with 5 and characters - `N6` – US National Health Related Item Code with hypen separators with 6 and 4 characters - `ND` – US-National-Drug-Code - `NH` – US National Health Related Item Code - `PI` – Customer's material number - `SK` – Stock keeping unit - `UA` – UPC Case Code (2-5-5) - `UJ` - PackageUPC - `UI` – UPC Consumer Package Code (1-5-5) - `UK` – GTIN14 identifier - `UP` – EAN/UPC Universal Item Number/GTIN12 - `UX` – Universal product number - `VC` – Vendor (Supplier) material number - `VN` – Supplier material number. – LIN09 \[0…1\] 1/80 Product or service identifier as defined by the qualifier in LIN02. If LIN09 is present, LIN08 is required. – LIN10 \[0…1\] 2/2 Product code qualifier specifying the product identifier type. If LIN10 is present, LIN11 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `BP` – Customer's material number - `CB` – Buyer Catalog - `EN` – EAN 2-5-5-1 - `FV` – Canada product number - `IN` – Customer's(Buyer's) product item number - `MF` – Manufacturer's product number - `MG` – Manufacturer's part number - `N1` – US National-Drug-Code-NDC442-with-hyphen-separators - `N2` – US National-Drug-Code-NDC532-with-hyphen-separators - `N3` – US National-Drug-Code-NDC541-with-hyphen-separators - `N4` – US-National-Drug-Code-NDC542-with-hyphen-separators - `N5` – US National Health Related Item Code with hypen separator with 5 and characters - `N6` – US National Health Related Item Code with hypen separators with 6 and 4 characters - `ND` – US-National-Drug-Code - `NH` – US National Health Related Item Code - `PI` – Customer's material number - `SK` – Stock keeping unit - `UA` – UPC Case Code (2-5-5) - `UJ` - PackageUPC - `UI` – UPC Consumer Package Code (1-5-5) - `UK` – GTIN14 identifier - `UP` – EAN/UPC Universal Item Number/GTIN12 - `UX` – Universal product number - `VC` – Vendor (Supplier) material number - `VN` – Supplier material number. – LIN11 \[0…1\] 1/80 Product or service identifier as defined by the qualifier in LIN02. If LIN11 is present, LIN12 is required. – LIN12 \[0…1\] 2/2 Product code qualifier specifying the product identifier type. If LIN13 is present, LIN14 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `BP` – Customer's material number - `CB` – Buyer Catalog - `EN` – EAN 2-5-5-1 - `FV` – Canada product number - `IN` – Customer's(Buyer's) product item number - `MF` – Manufacturer's product number - `MG` – Manufacturer's part number - `N1` – US National-Drug-Code-NDC442-with-hyphen-separators - `N2` – US National-Drug-Code-NDC532-with-hyphen-separators - `N3` – US National-Drug-Code-NDC541-with-hyphen-separators - `N4` – US-National-Drug-Code-NDC542-with-hyphen-separators - `N5` – US National Health Related Item Code with hypen separator with 5 and characters - `N6` – US National Health Related Item Code with hypen separators with 6 and 4 characters - `ND` – US-National-Drug-Code - `NH` – US National Health Related Item Code - `PI` – Customer's material number - `SK` – Stock keeping unit - `UA` – UPC Case Code (2-5-5) - `UJ` - PackageUPC - `UI` – UPC Consumer Package Code (1-5-5) - `UK` – GTIN14 identifier - `UP` – EAN/UPC Universal Item Number/GTIN12 - `UX` – Universal product number - `VC` – Vendor (Supplier) material number - `VN` – Supplier material number. – LIN13 \[0…1\] 1/80 Product or service identifier as defined by the qualifier in LIN02. If LIN14 is present, LIN13 is required. – LIN14 \[0…1\] 2/2 Product code qualifier specifying the product identifier type. If LIN14 is present, LIN15 is required. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `BP` – Customer's material number - `CB` – Buyer Catalog - `EN` – EAN 2-5-5-1 - `FV` – Canada product number - `IN` – Customer's(Buyer's) product item number - `MF` – Manufacturer's product number - `MG` – Manufacturer's part number - `N1` – US National-Drug-Code-NDC442-with-hyphen-separators - `N2` – US National-Drug-Code-NDC532-with-hyphen-separators - `N3` – US National-Drug-Code-NDC541-with-hyphen-separators - `N4` – US-National-Drug-Code-NDC542-with-hyphen-separators - `N5` – US National Health Related Item Code with hypen separator with 5 and characters - `N6` – US National Health Related Item Code with hypen separators with 6 and 4 characters - `ND` – US-National-Drug-Code - `NH` – US National Health Related Item Code - `PI` – Customer's material number - `SK` – Stock keeping unit - `UA` – UPC Case Code (2-5-5) - `UJ` - PackageUPC - `UI` – UPC Consumer Package Code (1-5-5) - `UK` – GTIN14 identifier - `UP` – EAN/UPC Universal Item Number/GTIN12 - `UX` – Universal product number - `VC` – Vendor (Supplier) material number - `VN` – Supplier material number. – LIN15 \[0…1\] 1/80 Product or service identifier as defined by the qualifier in LIN02. If LIN15 is present, LIN14 is required. – PID \[1…1000\] – PID segment under RCD loop is used to describe a product or process in coded or free-form format. – PID01 \[1…1\] 1/1 **Required.**Item description type code. Hard code "F" for free text. F PID05 \[0…1\] 1/80 Product descriptions or names. – REF 0…12 – REF segment under RCD loop is used to specify identifying information – REF01 \[1…1\] 2/3 **Required.**Code qualifying the Reference Identification. Valid values: - `PO` - Purchase order - `DO`- Delivery order - `PK` - Packing list - `VN` - Supplier order - `LT` - Lot number - `IA` - Internal vendor number DO REF02 \[0…1\] 1/80 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier. 8456732 REF03 \[0…1\] 1/80 A free-form description to clarify the related data elements and their content. – DTM \[1…10\] – DTM segment is used to specify pertinent dates and times. – DTM01 \[1…1\] 3/3 **Required.**Code specifying type of date or time, or both date and time. Valid values: - `004` – Purchase Order - `050` – Goods receipt - `310` – Received 310 DTM02 \[0…1\] 8/8 Date defined by DTM01 qualifier in date format YYYYMMDD. 20241215 DTM03 \[0…1\] 4/8 Time for date defined by DTM01 qualifier in time format HHMM or HHMMSS or HHMMSSnn. 124523 MAN \[0…\*\] – MAN segment under RCD loop is used to indicate identifying marks and numbers for shipping containers. – MAN01 \[1…1\] 1/2 **Required.**Code specifying the application or source of Marks and Numbers. – MAN02 \[1…1\] 1/48 **Required.**Marks and numbers used to identify a shipment or parts of a shipment. – N1 \[0…1\] – N1 name segment loop for the ship to location party information. – N101 \[1…1\] 2/3 **Required.**Entity qualifier for the ship to party identifier and address information. Valid values: - `ST` – Ship to - `RL` – Reporting location ST N102 \[0…1\] 1/60 Name. Pharma supplier 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 N104 \[0…1\] 2/80 Ship to party identifier as qualified by N103 mapping to companyIdentifierValue. 8568745 N2 \[0…1\] – N2: Additional names: Child of ship to party N1 name segment. – N201 \[1…1\] 1/55 **Required.**Free-form name. – N202 \[0…1\] 1/55 Free-form name. – N3 \[0…1\] – N3: Address: Child of ship to party N1 name segment. – N301 \[1…1\] 1/55 **Required.**Street address 1. 555 Neelan Road N302 \[0…1\] 1/55 Street address 2. Suite 123 N4 \[0…1\] – N4: Geographic Location. Child of ship to party N1 name segment. – N401 \[0…1\] 2/30 City name. Sacramento N402 \[0…1\] 2/2 State or province code. Code (Standard state/province) as defined by appropriate government agency. CA N403 \[0…1\] 3/15 Postal code. Code defining international postal zone code excluding punctuation and blanks. 95833 N404 \[0…1\] 2/3 Country code. US PER \[0…3\] – PER segment under RCD-N1 loop is used to identify a person or office to whom administrative communications should be directed – PER01 \[1…1\] 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 \[0…1\] 1/60 Name of the contact person responsible for authenticating the pedigree information. John Smith 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 If PER03 is present, PER04 is required TE PER04 \[0…1\] 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 \[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 If PER05 is present, PER06 is required EM PER06 \[0…1\] 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 \[0…1\] – CTT segment is used to transmit a hash total for a specific element in the transaction set. – CTT01 \[1…1\] 1/6 **Required.**Total number of line items in the transaction set 10 SE \[1…1\] – **Required.**ST … SE transaction set trailer envelope. Child of GS group. Only one ST transaction expected. – SE01 \[1…1\] 1/10 **Required.**Total count of segments in ST … SE transaction set including ST and SE segments. 10 SE02 \[1…1\] 4/9 **Required.**Transaction set control number. 0001 GE \[1…1\] – **Required.**GS … GE functional group trailer envelope. Child of ISA interchange. Only one GS group expected. – GE01 \[1…1\] 1/6 **Required.**Number of transaction sets in functional group. 5 GE02 \[1…1\] 1/9 **Required.**Functional group control number. 619827 IEA \[1…1\] – **Required.**ISA … IEA interchange control trailer envelope. Only one interchange expected per transmission. – IEA01 \[1…1\] 1/5 **Required.**Number of functional groups in interchange. 1 IEA02 \[1…1\] 9/9 **Required.**Interchange control number. 0000000000619827 [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Example](#)```xml 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 ``` ![](/sites/default/files/tech_comms/mpl/Content/Resources/Images/global_images/note_tip_24x24.png) Review TraceLink's [API: Terms of Use](https://www.tracelink.com/legal-and-trust/api-terms-of-use) #### Table of contents ##### Related Content [ ![Related content](https://www.tracelink.com/sites/default/files/2024-09/cloud.svg) ](/resources/tracelink-university/forecast-plan-idoc) ##### Forecast plan (IDoc) Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with upstream supply chain Partners without giving these Partners access to their serialization system of record. [View More](/resources/tracelink-university/forecast-plan-idoc) [ ![Related content](https://www.tracelink.com/sites/default/files/2024-09/cloud.svg) ](/resources/tracelink-university/forecast-plan-x12) ##### Forecast plan (X12) Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with upstream supply chain Partners without giving these Partners access to their serialization system of record. [View More](/resources/tracelink-university/forecast-plan-x12) [ ![Related content](https://www.tracelink.com/sites/default/files/2024-09/cloud.svg) ](/resources/tracelink-university/forecast-plan-response-idoc) ##### Forecast plan response (IDoc) Forecasting APIs allow companies to exchange data about anticipated product demand and supply availability with downstream supply chain Partners without giving these Partners access to their serialization system of record. [View More](/resources/tracelink-university/forecast-plan-response-idoc)