Tracelink University ## Breadcrumb 1. [Home](/) 2. [Resources](/resources/resource-center) 3. [TraceLink University](/resources/tracelink-university) # Inventory update confirmation (EDIFACT) - [Download PDF](/node/627576/pdf) - [Share](#) - [ LinkedIn ](https://www.linkedin.com/shareArticle?mini=true&url=https://www.tracelink.com/resources/tracelink-university/inventory-update-confirmation-edifact&title=Inventory update confirmation (EDIFACT) &summary=An Inventory Update Confirmation is an electronic message sent in response to an Inventory Update Request to verify that the requested changes to stock status, usability, or location have been completed. &source=TraceLink "LinkedIn") - [ Facebook ](https://www.facebook.com/share.php?u=https://www.tracelink.com/resources/tracelink-university/inventory-update-confirmation-edifact&t=Inventory update confirmation (EDIFACT) "Facebook") - [ Mail ](mailto:?subject=Inventory update confirmation (EDIFACT) +|+TraceLink&body=https://www.tracelink.com/resources/tracelink-university/inventory-update-confirmation-edifact "Mail") - [ Twitter ](https://twitter.com/intent/tweet?text=Inventory update confirmation (EDIFACT) https://www.tracelink.com/resources/tracelink-university/inventory-update-confirmation-edifact&via=TraceLink "Twitter") #### Table of contents An Inventory Update Confirmation is an electronic message sent in response to an Inventory Update Request to verify that the requested changes to stock status, usability, or location have been completed. It includes a reference to the original request, updated property details and product identifiers (NDC, GTIN, lot, or serial number), the new stock status or disposition (e.g., available, quarantined, destroyed), any location changes, the date and time the update was applied. An Inventory Update Confirmation verifies that important actions, such as quarantined products, security checks, and adjusting cold chain handling, have been executed. The Inventory Update Request EDIFACT message communicates instruction for status change to cargo goods, handling units or inventory. ![](/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\_INVENTORY\_UPDATE\_CONFIRMATION - **EDIFACT Format**: INVENTORYUPDATECONFIRMATION - **Transform Names**: - B2B\_EDIFACT\_INVRPT\_InventoryUpdateConfirmation\_IB\_V1 - B2B\_EDIFACT\_INVRPT\_InventoryUpdateConfirmation\_OB\_V1 [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Guidelines](#) Input Element Occurs Length Description Example INVRPT 1…1 – **Required.**EDIFACT Inventory Report: Inventory Update Confirmation. – UNA 0…1 – Optional UNA service envelope segment. Used to inform the interchange receiver that a set of service string characters used are different from the default characters. UNA:+.? ' UNA010 1…1 1/1 **Required.**Component data element separator between component elements within a composite data element (default value: ":") – UNA020 1…1 1/1 **Required.**Data element separator that separates two simple or composite data elements (default value: "+" ) – UNA030 1…1 1/1 **Required.**Decimal Mark. Indicate the character used for decimal notation (default value:".") – UNA040 1…1 1/1 **Required.**Release character. Restores any service character to its original specification (default value: "?"). – UNA050 1…1 1/1 **Required.**Repetition separator. Indicates the character used for repetition separation (default value: " \* " ). – UNA060 1…1 1/1 **Required.**Segment terminator. Indicates the end of segment data (default value: " ' ") – UNB 1…1 – **Required.**UNB Interchange Envelope. UNB+UNOA+5400102000086: 14+055762322:1+251228:1420+2597 ++INVRPT++1++1' UNB010 1…1 – **Required.**Syntax identifier compound element. Identifies the agency controlling the syntax, the syntax level and version number. – UNB010-010 1…1 4/4 **Required.**Syntax identifier. Code identifies agency controlling the syntax and character repertoire used in an interchange. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `UNOA` - UN/ECE Level A - `UNOB` - UN/ECE Level B - `UNOC` - UN/ECE Level C - `UNOD` - UN/ECE Level D - `UNOE` - UN/ECE Level E - `UNOF` - UN/ECE Level F - `UNOG` - UN/ECE Level G - `UNOH` - UN/ECE Level H - `UNOI` - UN/ECE Level I - `UNOJ` - UN/ECE Level J - `UNOK` - UN/ECE Level K - `UNOL` - UN/ECE Level L - `UNOW` - UN/ECE Level W - `UNOX` - UN/ECE Level X - `UNOY` - UN/ECE Level Y UN0A UNB010-020 1…1 1/1 **Required.**Syntax version number 3 UNB020 1…1 – **Required.**Interchange sender identification and type compound element – UNB020-010 1…1 1/35 **Required.**Sender party identifier 5400102000086 UNB020-020 1…1 1/4 **Required.**Sender partner identifier type. Complete EDIFACT code list is supported. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `1` – D-U-N-S number, Dun and Bradstreet - `2` – D-U-N-S + 4r, Dun and Bradstreet number plus suffix - `9` – D-U-N-S + 4r, Dun and Bradstreet number plus suffix - `11` – Drug Enforcement Agency registration number - `21` – Health Industry Number - `91` – Assigned by seller … company identifier - `92` – Assigned by buyer … company site identifier - `UL` – Global Location Number - `12` – Telephone number - `20` – Standard Point Location Code (SPLC) - `ZZ` – Mutually defined 14 UNB030 1…1 – **Required.**Interchange receiver identification and type compound element – UNB030-010 1…1 1/35 **Required.**Receiver party identifier 055762322 UNB030-020 1…1 1/4 **Required.**Receiver partner identifier type. Complete EDIFACT code list is supported. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `1` – D-U-N-S number, Dun and Bradstreet - `2` – D-U-N-S + 4r, Dun and Bradstreet number plus suffix - `9` – D-U-N-S + 4r, Dun and Bradstreet number plus suffix - `11` – Drug Enforcement Agency registration number - `21` – Health Industry Number - `91` – Assigned by seller … company identifier - `92` – Assigned by buyer … company site identifier - `UL` – Global Location Number - `12` – Telephone number - `20` – Standard Point Location Code (SPLC) - `ZZ` – Mutually defined 1 UNB040 1…1 – **Required.** Date and time of preparation. – UNB040-010 1…1 6/8 **Required.** Local date when an interchange or a group was prepared in date formats YYMMDD or YYYMMDD. 20251228 UNB040-020 1…1 4/4 **Required.** Local time of day when an interchange or a group was prepared in time format HHMM. 1420 UNB050 1…1 1/14 **Required.** Interchange control reference identifier. 2597 UNB060 0…1 – Recipient's reference password. – UNB060-010 0…1 1/14 Recipient's reference or password. XYZ UNB060-020 0…1 2/2 Recipient's reference or password. qualifier. Valid values: - `BB` – Password. - `AA` – Reference. REFERENCE UNB070 0…1 1/14 Identifies the application area assigned by the sender to all messages in the interchange file when all messages in the interchange are the same type. Could be a message type or something else. INVRPT UNB080 0…1 1/1 Processing priority code determined by sender requesting processing priority for the interchange. The valid value is `A` - Highest priority. A UNB090 0…1 1/1 Acknowledgment request. Valid values: - `1` - Acknowledgment requested. - `2` - Indicates receipt - `Unpopulated` - No acknowledgment requested 1 UNB100 0…1 1/35 Interchange agreement identifier. Name or code identifying the type of agreement under which the interchange takes place. – UNB110 0…1 1/1 Test indicator. Valid values: - `1` - Test interchange - `2` - Syntax only test - `3` - Echo request - `4` - Echo response - `5` - Service provider test 3 UNG 0…1 – UNG functional group header for message identifying functionality of a group of UNH messages of the same message type. UNG is optional: supported if used, but not required. If present inbound to TraceLink, it will be mapped. Its presence can be configured for outbound processing from TraceLink. UNG+INVRPT+5400102000086:14+ 055762322: 1+20251228:1420+2597+UN+UN+ D:96A' UNG010 0…1 1/6 Message group identifying the single message type for the group of messages within the group. INVRPT UNG020 0…1 – Message sender identifier and type at group level. – UNG020-010 1…1 1/35 **Required.** Sender partner identifier at group level. 5400102000086 UNG020-020 1…1 1/4 **Required.** Sender partner identifier type mapping to EDI envelope party type. Complete EDIFACT code list is supported. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `1` – D-U-N-S number, Dun and Bradstreet - `2` – D-U-N-S + 4r, Dun and Bradstreet number plus suffix - `9` – D-U-N-S + 4r, Dun and Bradstreet number plus suffix - `11` – Drug Enforcement Agency registration number - `21` – Health Industry Number - `91` – Assigned by seller … company identifier - `92` – Assigned by buyer … company site identifier - `UL` – Global Location Number - `12` – Telephone number - `20` – Standard Point Location Code (SPLC) - `ZZ` – Mutually defined 14 UNG030 0…1 – Message receiver identifier and type at group level. – UNG020-010 1…1 1/35 **Required.** Receiver partner identifier at group level. 055762322 UNG020-020 1…1 1/4 **Required.** Receiver partner identifier type mappiing to EDI envelope party type. Complete EDIFACT code list is supported. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values ](#)- `1` – D-U-N-S number, Dun and Bradstreet - `2` – D-U-N-S + 4r, Dun and Bradstreet number plus suffix - `9` – D-U-N-S + 4r, Dun and Bradstreet number plus suffix - `11` – Drug Enforcement Agency registration number - `21` – Health Industry Number - `91` – Assigned by seller … company identifier - `92` – Assigned by buyer … company site identifier - `UL` – Global Location Number - `12` – Telephone number - `20` – Standard Point Location Code (SPLC) - `ZZ` – Mutually defined 1 UNG040 1…1 – **Required.** Date and time group generated 1 UNG040-010 1…1 6/8 **Required.** Local date when the functional group was prepared in date formats YYMMDD or YYYMMDD. 20251228 UNG040-020 1…1 4/4 **Required.** Local time of day when an interchange or a group was prepared in time format HHMM. 1420 UNG050 1…1 1/14 **Required.** Group level control reference identifier mapping into fileControlNumber. 2597 UNG60 1…1 1/3 **Required.** Controlling agency code. UN UNG070 0…1 – Message version at group level compound element. – UNG070-010 0…1 1/3 Message version number. D UNG070-020 0…1 1/3 Message release number. 97A UNG070-030 0…1 1/6 Association assigned code. EAN004 UNH 1…\* – UNH Message header segment identifying message reference, message type, version and controlling agency for message standard. UNH+000000101+ INVRPT:D:97A:UN' UNH010 1…1 1/14 **Required.** Unique message reference number assigned by the sender. H12133143 UNH020 1…1 – **Required.** Message identifier, type and version compound element. – UNH020-010 1…1 1/6 **Required.** Message type identifying the transaction. The valid value is `INVRPT`. INVRPT UNH020-020 1…1 1/3 **Required.** Message type version number. The valid value is `D` - Draft version/UN/EDIFACT Directory. D UNH020-030 1…1 '1/3 **Required.** Message type release number within the current message version number. 97A UNH020-040 1…1 '1/3 **Required.** Controlling agency code. UN UNH020-050 0…1 1/6 Association assigned code. – BGM 1…1 – **Required.** Beginning of message. Uniquely identifies the INVRPT report message or message function by name or code. BGM+79+INV00684+4' BGM010 1…1 – **Required.** Document or message name. – BGM010-010 1…1 1/3 **Required.** Document name code identifying the message and its purpose. The valid value for inventory update request is `263` - Inventory adjustment status report. 78 BGM010-020 0…1 1/17 Code list qualifier. – BGM010-030 0…1 1/3 Code list responsible agency, coded. – BGM010-040 0…1 1/35 Document or message name. INVRPT BGM020 0…1 – Document or message identification. – BGM020-010 0…1 1/70 Document identifier. INV00684 BGM030 0…1 1/3 Processing function code for message. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `1` – Cancel order, if LIN020 - Item added - `2` – Create document or item from message, if LIN020 - `39` - `3` – Delete document or item, if LIN020 - `2 - Item changed`. - `4` – Changes to document header, if LIN020 - `No particular action is required`. - `5` – Replace entire document, if LIN020 - `38` - `6` – Document is a confirmation. - `7` – Duplicate transaction. - `8` – Document or item status. - `9` – Original document, create in target. - `11` – Response message, if LIN020 - Item has not been changed. - `13` – Request message. - `14` – Advanced notification. - `16` – Proposed document or item, if LIN020 - `41` - `37` – Item canceled. - `55` – Information only. 4 FTX 0…99 – Free text segment for coded or free text information relevant to the message. – FTX010 1…1 1/3 **Required.** Text subject code qualifier identifying the subject of the text. Pass thrru mapping. – FTX020 1…1 1/3 **Required.** Free text function code. – FTX040 0…1 – Text literal complex element. Free text is mapped here. – FTX040-010 0…1 1/512 Free text field instance 1. – FTX040-020 0…1 1/512 Free text field instance 2. – FTX040-030 0…1 1/512 Free text field instance 3. – FTX040-040 0…1 1/512 Free text field instance 4. – DTM 0…10 – Dates related to inventory update request. DTM+137:20230304:102' DTM010 1…1 – **Required.** Date or time or period. – DTM010-010 1…1 1/3 **Required.** Date or time or period qualifier. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `2` - Delivery requested by date - `4` - Purchase order date - `7` - Effective date - `9` - Processing date - `10` - Shipment requested by date - `11` - Date shipped - `17` - Estimated delivery date - `35` - Date of delivery document, ASN - `36` - Expiration date - `37` - Not before shipment date - `38` - Not later shipment date - `44` - Product availability date - `46` - Cancel by date - `50` - Date goods receipt posted (received into available inventory) - `67` - Current scheduled delivery date - `74` - Requested delivery date - `90` - Report start date - `91` - Report end date - `97` - Manufacturing date - `132` - Estimated date of arrival - `133` - Estimated date of departure - `137` - Document date - `147` - Export permit effective end date - `149` - Invoice date - `182` - Export permit effective issue date - `186` - Actual date of departure - `194` - Date Start - `206` - End date - `261` - Release date - `310` - Purchase order received date 50 DTM010-020 0…1 1/35 Date in date format defined by DTM010-30. 20251228 DTM010-030 0…1 1/3 Date or time or period format qualifier. Valid values: - ` 102` - YYYYMMDD format - `203` - CCYYMMDDHHMM format 102 Segment Group 1 0…10 – Segment loop group 1 with RFF and DTM segments. – RFF 0…1 – RFF reference information for inventory update request. RFF+DM:12358741' RFF010 1…1 – **Required.** Reference information complex element. – RFF010-010 1…1 **Required.** Reference code identifier qualifier. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `BC` - Customer contract number - `BM` - Bill of lading - `BT` - Batch - `CD` - Credit advice - `CG` - Consignee order number - `CK` - Check number - `CM` – Credit memo - `CN` – Carrier reference - `CR` – Customer reference identifier - `CT` – Contract number - `DI` – Distributor invoice number - `DM` – Document number - `IV` – Seller's invoice - `MB` – Master bill of lading - `ON` – Purchase order number - `OR` - Order number - `PK` – Packing list number - `PR` – Price quote identifier - `RE` – Release document number - `SI` – Shipment number - `SN` – Seal number - `TB` – Trucker's Bill of Lading - `TN` – Transaction reference number - `VC` – Supplier contract number - `VN` – Supplier order number - `AAJ` - Delivery - `AAM` – Tracking number - `AAN` – Delivery schedule - `AFH` – Replenishment purchase order number - `ALN` – Physical inventory recount reference identifier - `ALQ` – Return authorization transaction identifier type - `ANK` – Third party reference identifier - `AOV` – Work order (production order) number - `API` – Inventory report - `ASS` – Master account ON RFF010-020 1…1 – **Required.** Document or transaction identifier referenced by qualifier in RFF010-010. 004587452 RFF010-030 0…1 – Document line item number. – DTM 0…1 – Dates related to inventory update request. DTM+137:20230304:102' DTM010 1…1 – **Required.** Date or time or period. – DTM010-010 1…1 1/3 **Required.** Date or time or period qualifier for the document or transaction identified in the RFF reference information segment. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `2` - Delivery requested by date - `4` - Purchase order date - `7` - Effective date - `9` - Processing date - `10` - Shipment requested by date - `11` - Date shipped - `17` - Estimated delivery date - `35` - Date of delivery document, ASN - `36` - Expiration date - `37` - Not before shipment date - `38` - Not later shipment date - `44` - Product availability date - `46` - Cancel by date - `50` - Date goods receipt posted (received into available inventory) - `67` - Current scheduled delivery date - `74` - Requested delivery date - `90` - Report start date - `91` - Report end date - `97` - Manufacturing date - `132` - Estimated date of arrival - `133` - Estimated date of departure - `137` - Document date - `147` - Export permit effective end date - `149` - Invoice date - `182` - Export permit effective issue date - `186` - Actual date of departure - `194` - Date Start - `206` - End date - `261` - Release date - `310` - Purchase order received date 37 DTM010-020 0…1 1/35 Date. 20251228 DTM010-030 0…1 1/3 Date or time or period format qualifier. Valid values: - ` 102` - YYYYMMDD format - `203` - CCYYMMDDHHMM format 102 NAD 0…20 – NAD: Business partner identifier and name segment group loop. Supported party types: - NAD01 - BY (Buyer/Customer party) - NAD01 = GY (Inventory reporting party) - NAD01 - SU (Supplier party) - NAD01 - ST (Ship to party) Note: If present, some elements are required. NAD+BY+8712199999999::9++Acme Pharma Harma+23 Jay Bird St East::Suite 669+Tuscaloosa+AL+35401+US' NAD010 1…1 1/3 **Required.** Company identifier type for business partner for bill to, supplier or ship to parties. Supported party types: - NAD01 - BY (Buyer/Customer party) - NAD01 = GY (Inventory reporting party) - NAD01 - SU (Supplier party) - NAD01 - ST (Ship to party) BY NAD020 0…1 – Party Identifier details. – NAD020-010 1…1 1/35 **Required.** Party Identifier. 8712199999999 NAD020-020 0…1 1/3 Identification code for party identifier type code list. – NAD020-030 0…1 1/3 Party identifier type. Valid values: - `9` – Global Location Number - `16` – D-U-N-S number, Dun and Bradstreet - `91` – Assigned by seller company identifier - `92` – Assigned by buyer company site identifier - `164` – Drug Enforcement Agency registration number - `182` – Standard Carrier Alpha Code - `237` – Health Industry Number 16 NAD030 0…1 – Name and Address. – NAD030-010 1…1 1/35 **Required.** Name and address description. – NAD030-020 0…1 1/35 Name and address description. – NAD040 0…1 – Party Name. – NAD040-010 1…1 1/35 **Required.** Party name. Supplier Name NAD040-020 0…1 1/35 Party name. – NAD040-030 0…1 1/35 Party name. – NAD050 0…1 – Street. – NAD050-010 1…1 1/35 **Required.** Street and number/p.o. box. Supplier Street NAD050-020 0…1 1/35 Street and number/p.o. box. NAD060 0…1 1/35 City name. SuppliCity NAD070 0…1 – Country subdivision details. – NAD070-010 0…1 1/9 Country sub-entity identification. – NAD080 0…1 1/17 Postcode identification code. PostalCode NAD090 0…1 1/3 Country identifier. – CTA 0…10 – CTA: Contact Information. CTA+PD+:Contact Person CTA010 1…1 1/3 **Required.** Contact function, coded. Valid contact types: - `BS` - Main contact at customer location - `DL` - Delivery contact - `OC` - Contact for questions regarding the order - `PM` - Product management contact for order - `RP` - Authorized responsible person - `SU` - Main contact at supplier location RP CTA020 0…1 – Department or employee details. – CTA020-010 0…1 1/17 Department or employee identification. – CTA020-020 0…1 1/256 Department or employee. John Smith COM 0…5 – COM: Communication Contact. Telephone and email contact info supported. COM+stx.team@partner.de:EM COM010 1…3 – Communication Information. – COM010-010 1…1 1/512 **Required.** Communication phone number or email address as defined by COM010-020. 50812345678 COM010-020 1…1 1/3 **Required.** Communication channel qualifier. Valid values: - `TE` – Telephone number - `EM` – Email address TE LIN 1…9999999 – Line Item. LIN+15++8712100000010:VN' LIN010 0…1 1/6 Line item number. 15 LIN020 0…1 1/3 Processing function type code at the line item level. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `1` – Cancel order, if LIN020 - Item added - `2` – Create document or item from message, if LIN020 - `39` - `3` – Delete document or item, if LIN020 - `2 - Item changed`. - `4` – Changes to document header, if LIN020 - `No particular action is required`. - `5` – Replace entire document, if LIN020 - `38` - `6` – Document is a confirmation. - `7` – Duplicate transaction. - `8` – Document or item status. - `9` – Original document, create in target. - `11` – Response message, if LIN020 - Item has not been changed. - `13` – Request message. - `14` – Advanced notification. - `16` – Proposed document or item, if LIN020 - `41` - `37` – Item canceled. - `55` – Information only. 1 LIN030 0…1 – Item Number Identification – LIN030-010 0…1 1/35 Product item identifier 8712100000010 LIN030-020 0…1 1/3 Product identifier type identifying the customer lot number. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `BC` – Buyer's product identifier - `BD` – Manufacturer's product identifier. - `BE` – Supplier's catalog number. - `BF` – Universal product number (UPC) - `BP` – Buyer/Customer's product item number - `IN` – Customer's item number - `MF` – Manufacturer's product identifier - `SK` – SKU, Stock Keeping Unit - `SRV` – GS1 Global Trade Item Number - `UP` – Universal product number (UPC) - `VN` – Supplier's catalog number. VN LIN030-030 0…1 1/17 Code list qualifier – PIA 0…1 – PIA instance 1 customer lot number mapping. PIA+1+98465AW23:BB' PIA010 1…1 1/3 **Required.** Product id. function qualifier. Hard code to 1 additional information. 1 PIA020 1…1 – **Required.** Item Number Identification. – PIA020-010 0…1 1/35 Customer lot number. 98465AW23 PIA020-020 0…1 1/3 Product identifier type identifying the customer lot number. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `BB` – Lot number - `BC` – US National-Drug-Code-NDC442-with-hyphen-separators - `BD` – US National-Drug-Code-NDC532-with-hyphen-separators - `BE` – US National-Drug-Code-NDC541-with-hyphen-separators - `BF` – US-National-Drug-Code-NDC542-with-hyphen-separators - `BP` – Buyer's product identifier - `IN` – Customer's(Buyer's) product item number - `MF` – Manufacturer's product identifier. - `SK` – Stock keeping unit - `SRV` – GS1 Global Trade Item Number - `UP` – Universal product number (UPC) - `VN` – Supplier's catalog number. BB PIA020-030 0…1 1/17 Code list qualifier. Pass thru value. – PIA020-040 0…1 1/3 Code list responsible agency. Pass thru value. 9 PIA(2) 0…10 – PIA instance 2 for additional product type identifiers. PIA+1+AB80:SA PIA010 1…1 1/3 **Required.** Product id. function qualifier. Hard code to 1 additional information. 1 PIA020 1…1 – **Required.** Item Number Identification – PIA020-010 0…1 1/35 Product item identifier AB80 PIA020-020 0…1 1/3 Product identifier type identifying the customer lot number. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `BC` – Buyer's product identifier - `BD` – Manufacturer's product identifier. - `BE` – Supplier's catalog number. - `BF` – Universal product number (UPC) - `BP` – Buyer/Customer's product item number - `IN` – Customer's item number - `MF` – Manufacturer's product identifier - `SK` – SKU, Stock Keeping Unit - `SRV` – GS1 Global Trade Item Number - `UP` – Universal product number (UPC) - `VN` – Supplier's catalog number. BC PIA020-030 0…1 1/17 Code list qualifier – IMD 0…10 – Item Description. IMD+F++:::Product description 1 IMD010 0…1 1/3 Product item description type. The valid value is `F` - Free-form (default value, if not populated by IB map) F IMD020 0…1 1/3 Item characteristic, coded. – IMD020-010 0…1 1/3 Item description identification. – IMD020-020 0…1 1/17 Code list identification code. – IMD020-030 0…1 1/3 Code list responsible agency code. – IMD030 0…1 – Item description. – IMD030-010 0…1 1/17 Item description identification code from an industry code list, if available. – IMD030-020 0…1 1/17 Code list identification code identifying a user or association maintained code list, if available. – IMD030-030 0…1 1/3 Code list specifying the agency responsible for a code list, if available. – IMD030-040 0…1 1/256 Product name as a free-form description. Headache tabs IMD030-050 0…1 1/256 Free-form description of a product. Long description IMD030-060 0…1 1/3 Language code. EN LOC 0…5 – Place or location identification with details regarding specific place or location of the specified line item. – LOC010 1…1 1/3 **Required.** Location function code qualifier. Supported values include: - `14` - Storage location - `19` - Plant identifier 14 LOC020 1…1 – **Required.** Location identification by code or name. – LOC020-010 0…1 1/35 Location identifier. 0058745214 DTM 0…5 – Product item details dates. Expiration and manufacturing dates recorded, Java call-out supports all TL date types that map to EDIFACT. DTM+36:20200311:102 DTM010 1…1 – **Required.** Date or time or period details. – DTM010-010 1…1 1/3 **Required.** Date or time or period qualifier. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `2` - Delivery requested by date - `4` - Purchase order date - `7` - Effective date - `9` - Processing date - `10` - Shipment requested by date - `11` - Date shipped - `17` - Estimated delivery date - `35` - Date of delivery document, ASN - `36` - Expiration date - `37` - Not before shipment date - `38` - Not later shipment date - `44` - Product availability date - `46` - Cancel by date - `50` - Date goods receipt posted (received into available inventory) - `67` - Current scheduled delivery date - `74` - Requested delivery date - `90` - Report start date - `91` - Report end date - `97` - Manufacturing date - `132` - Estimated date of arrival - `133` - Estimated date of departure - `137` - Document date - `147` - Export permit effective end date - `149` - Invoice date - `182` - Export permit effective issue date - `186` - Actual date of departure - `194` - Date Start - `206` - End date - `261` - Release date - `310` - Purchase order received date 36 DTM010-020 0…1 1/35 Date. 20230304 DTM010-030 0…1 1/3 Date or time or period format qualifier. The valid value is `102` - YYYYMMDD format. 102 FTX 0…99 – Free text segment for coded or free text information relevant to the message. – FTX010 1…1 1/3 **Required.** Text subject code qualifier identifying the subject of the text. Pass thru mapping. – FTX020 1…1 1/3 **Required.** Free text function code. – FTX040 0…1 – Text literal complex element. Free text is mapped here. – FTX040-010 0…1 1/512 Free text field instance 1. – FTX040-020 0…1 1/512 Free text field instance 2. – FTX040-030 0…1 1/512 Free text field instance 3. – FTX040-040 0…1 1/512 Free text field instance 4. – FTX050 0…1 1/3 ISO language name code. – Segment Group 10 0…10 – Segment loop group 10 with line item level RFF and DTM segments. – RFF 0…1 – RFF reference information for inventory update request. RFF+DM:12358741 RFF010 1…1 – **Required.** Reference information complex element – RFF010-010 1…1 – **Required.** Reference code identifier qualifier. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `BC` - Customer contract number - `BM` - Bill of lading - `BT` - Batch - `CD` - Credit advice - `CG` - Consignee order number - `CK` - Check number - `CM` – Credit memo - `CN` – Carrier reference - `CR` – Customer reference identifier - `CT` – Contract number - `DI` – Distributor invoice number - `DM` – Document number - `IV` – Seller's invoice - `MB` – Master bill of lading - `ON` – Purchase order number - `OR` - Order number - `PK` – Packing list number - `PR` – Price quote identifier - `RE` – Release document number - `SI` – Shipment number - `SN` – Seal number - `TB` – Trucker's Bill of Lading - `TN` – Transaction reference number - `VC` – Supplier contract number - `VN` – Supplier order number - `AAJ` - Delivery - `AAM` – Tracking number - `AAN` – Delivery schedule - `AFH` – Replenishment purchase order number - `ALN` – Physical inventory recount reference identifier - `ALQ` – Return authorization transaction identifier type - `ANK` – Third party reference identifier - `AOV` – Work order (production order) number - `API` – Inventory report - `ASS` – Master account OP RFF010-020 1…1 – **Required.** Document or transaction identifier referenced by qualifier in RFF010-010 004528459 RFF010-030 0…1 – Document line item number 010 DTM 0…1 – Dates related to inventory update request at line item level. DTM+137:20230304:102' DTM010 1…1 – **Required.** Date or time or period – DTM010-010 1…1 1/3 **Required.** Date or time or period qualifier for the document or transaction identified in the RFF reference information segment. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `2` - Delivery requested by date - `4` - Purchase order date - `7` - Effective date - `9` - Processing date - `10` - Shipment requested by date - `11` - Date shipped - `17` - Estimated delivery date - `35` - Date of delivery document, ASN - `36` - Expiration date - `37` - Not before shipment date - `38` - Not later shipment date - `44` - Product availability date - `46` - Cancel by date - `50` - Date goods receipt posted (received into available inventory) - `67` - Current scheduled delivery date - `74` - Requested delivery date - `90` - Report start date - `91` - Report end date - `97` - Manufacturing date - `132` - Estimated date of arrival - `133` - Estimated date of departure - `137` - Document date - `147` - Export permit effective end date - `149` - Invoice date - `182` - Export permit effective issue date - `186` - Actual date of departure - `194` - Date Start - `206` - End date - `261` - Release date - `310` - Purchase order received date 310 DTM010-020 0…1 1/35 Date 20251228 DTM010-030 0…1 1/3 Date or time or period format qualifier. Valid values: - `102` - YYYYMMDD format - `203` - CCYYMMDDHHMM format 102 Segment Group 12 0…10 – Segment loop group 12 for inventory management related details.. Segment group provides a quantity with inventory management related information and references. – INV 0…9999 – Inventory managed details. Provides parameters for an inventory activity, including direction (addition or subtraction) and reason for an inventory movement. INV+2+1+1+1 INV010 0…1 1/3 Inventory movement direction code specifying whether an inventory movement is an addition to or a subtraction from inventory. Valid values: - `1` - Movement out of inventory - `2` - Movement into inventory Use to determine if inventory movement is a posting or a reverse posting. 2 INV020 0…1 1/3 Code specifying a type of inventory. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `1` – Unrestricted/accepted product inventory - `2` – Damaged product inventory - `3` – Inventory of product bonded for customs reasons - `4` – Reserved product in inventory - `5` – Inventory in quality inspection or waiting for inspection - `6` – Inventory of products that are complete and ready for sale - `7` – Maintenance, repair, and operations (MRO). Inventory of items used for manufacture of products that are NOT part of producing a finished product. - `8` – Packing materials. Inventory of any goods used for packing or protecting goods in storage, or during shipping. - `9` – Inventory of raw materials used to manufactuire finished goods. - `10` – Inventory of products that are incomplete and not ready for sale. - `11` – Work in process. Inventory of items or components currently in production. 1 INV030 0…1 1/3 Inventory movement reason code specifying the reason for an inventory movement. INV010 is taken into account when determining whether the movement status is driven by an addition to or subtraction from inventory. Valid values: - 1 - GOODSRECEIPT if INV010 - 2 - 1 - GOODSRECEIPTREVERSE if INV010 - 1 - 2 - GOODSISSUEDELIVERY if INVO10 - 2 - 2 - GOODSISSUEDELIVERYREVERSE if INVO10 - 1 - 3 - SCRAPFROMUNRESTRICTED if INVO10 - 2 - 3 - SCRAPFROMUNRESTRICTEDREVERSE if INVO10 - 1 - 4 - The difference between the inventory, as physically counted, and inventory recorded by the system, if INVO10 - 2 - 5 - Transfer posting plant to plant, if INVO10 - 2 - 5 - Reverse transfer posting plant to plant, if INVO10 - 1 - 6 - Inventory recycling. Inventory movement due to recycling of goods, ie, defective goods have been repaired and put back into available inventory, if INVO10 - 2 - 7 - Reversal of previous inventory movement. Issued to cancel a previously processed inventory movement, if INVO10 - 1 - 8 - Goods received damaged, if INVO10 - 1 - 9 - Inventory movement has been issued for commercial reasons, if INVO10 - 2 - 10 - The inventory movement is due to the conversion of goods, if INVO10 - 2 - 11 - The inventory movement records goods taken out of consigned inventory for consumption, if INVO10 - 2 1 INV040 0…1 1/3 Inventory balance method code. – QTY01 1…9 – Quantity. QTY+21:6:EA' QTY010 1…1 – **Required.** Quantity details. 5 QTY010-010 1…1 1/3 **Required.** Quantity qualifier. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `1` – Discrete quantity - `3` – Cumulative quantity - `17` – Quantity on hand for sale - `21` - Quantity on order - `21` – Order quantity - `27` – Quantity on hold for quality - `47` – Invoice quantity - `48` - Received quantity - `51` – Transfer quantity/Inventory category transfer - `52` – Packaged quantity - `53` – Minimum quantity per order - `57` – Quantity in transit - `58` – Quantity withdrawn - `60` – Current inventory quantity available for shipment - `61` – Returned quantity - `64` – Quantity of scrap - `66` – Quantity committed - `73` – Outstanding/remaining quantity - `83` – Backordered quantity - `89` – Quantity in inspection - `113` – Quantity delivered - `119` – Total quantity shipped short - `124` – Quantity of damaged goods - `131` – Delivery ASN quantity - `155` – Replenishment quantity - `156` – Inventory movement quantity - `160` – Minimum make to order quantity - `169` – Shipped quantity - `170` – Quantity allocated - `182` – Quantity cancelled - `185` – Total or cumulative rejected quantity - `191` – Inventory movement quantity - `199` – Quantity withdrawn from inventory since the last inventory report - `212` – Total quantity sold - `215` – Total quantity that can't be sold because of its present condition/Unusable quantity. - `216` – Quantity reserved for consumer delivery or pickup that has not yet been withdrawn from inventory. - `217` – Quantity of inventory that was request but is unavailable - `250` – The difference recorded between system and physical inventory. - `257` – Total quantity of goods held in physical inventory - `490` – Component quantity - `501` – Quantity represents an increase or addition - `502` – Quantity represents a decrease or subtraction - `OV` – Surplus quantity above order or agreement 17 QTY010-020 1…1 1/35 **Required.** Quantity. 6 QTY010-030 0…1 1/8 Measure unit qualifier. [![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 - `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 LOC 0…5 – Place or location identification with details regarding specific place or location of the specified line item. – LOC010 1…1 1/3 **Required.** Location function code qualifier. Supported values include: - 14 = Storage location - 19 = Plant identifier 14 LOC020 1…1 – **Required.** Location identification by code or name. – LOC020-010 0…1 1/35 Location identifier. 0058745214 Segment Group 15 0…10 – Segment loop group 1 with RFF and DTM segments. – RFF 0…1 – RFF reference information for inventory update request. RFF+DM:12358741' RFF010 1…1 – **Required.** Reference information complex element. – RFF010-010 1…1 – **Required.** Reference code identifier qualifier. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `BC` - Customer contract number - `BM` - Bill of lading - `BT` - Batch - `CD` - Credit advice - `CG` - Consignee order number - `CK` - Check number - `CM` – Credit memo - `CN` – Carrier reference - `CR` – Customer reference identifier - `CT` – Contract number - `DI` – Distributor invoice number - `DM` – Document number - `IV` – Seller's invoice - `MB` – Master bill of lading - `ON` – Purchase order number - `OR` - Order number - `PK` – Packing list number - `PR` – Price quote identifier - `RE` – Release document number - `SI` – Shipment number - `SN` – Seal number - `TB` – Trucker's Bill of Lading - `TN` – Transaction reference number - `VC` – Supplier contract number - `VN` – Supplier order number - `AAJ` - Delivery - `AAM` – Tracking number - `AAN` – Delivery schedule - `AFH` – Replenishment purchase order number - `ALN` – Physical inventory recount reference identifier - `ALQ` – Return authorization transaction identifier type - `ANK` – Third party reference identifier - `AOV` – Work order (production order) number - `API` – Inventory report - `ASS` – Master account OP RFF010-020 1…1 – **Required.** Document or transaction identifier referenced by qualifier in RFF010-010. 004528459 RFF010-030 0…1 – Document line item number. 010 DTM 0…1 – Dates related to inventory update request. DTM+137:20230304:102 DTM010 1…1 – **Required.** Date or time or period. – DTM010-010 1…1 1/3 **Required.** Date or time or period qualifier for the document or transaction identified in the RFF reference information segment. [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Valid values:](#)- `2` - Delivery requested by date - `4` - Purchase order date - `7` - Effective date - `9` - Processing date - `10` - Shipment requested by date - `11` - Date shipped - `17` - Estimated delivery date - `35` - Date of delivery document, ASN - `36` - Expiration date - `37` - Not before shipment date - `38` - Not later shipment date - `44` - Product availability date - `46` - Cancel by date - `50` - Date goods receipt posted (received into available inventory) - `67` - Current scheduled delivery date - `74` - Requested delivery date - `90` - Report start date - `91` - Report end date - `97` - Manufacturing date - `132` - Estimated date of arrival - `133` - Estimated date of departure - `137` - Document date - `147` - Export permit effective end date - `149` - Invoice date - `182` - Export permit effective issue date - `186` - Actual date of departure - `194` - Date Start - `206` - End date - `261` - Release date - `310` - Purchase order received date 37 DTM010-020 0…1 1/35 Date. 20251228 DTM010-030 0…1 1/3 Date or time or period format qualifier. Valid value: - `102` - YYYYMMDD format - `203` - CCYYMMDDHHMM format 102 UNT 1…1 – **Required.** UNT Message Trailer (UNH…UNT transaction) . UNT+45+1 UNT010 1…1 1/10 **Required.** Number of segments in a message, starting with UNH and ending with UNT. 45 UNT020 1…1 1/14 **Required.** Message reference number. H12133143 UNE 0…1 – UNE Function group trailer (UNG…UNE transaction) UNG+1+2597' UNE010 1…1 1/10 Number of functional group in an interchange. 45 UNE020 1…1 1/14 Functional group reference number. 2597 UNZ 1…1 – **Required.** UNB… UNZ interchange control trailer envelope. Only one interchange expected per transmission. UNZ+1+3 UNZ010 1…1 1/6 **Required.** Interchange control count. 1 UNZ020 1…1 1/14 **Required.** Interchange control reference. 2597 [![Closed](/sites/default/files/tech_comms/mpl/Skins/Default/Stylesheets/Images/transparent.gif)Example](#)```xml UNA:+.? ' UNB+UNOB:3+4012345000009:14+4000004000002:14+250812:1213+INVRPT12345678+Data:AA+INVRPT+A+1+AGREE+T' UNG+INVRPT+5400102000086:14+055762322:14+251228:1420+2597+UN+UN:96A+D' UNH+H12133143+INVRPT:D:97A:UN' BGM+263+2738662+9' FTX+ABC+1++File:Type:Is:Verified+ISO' DTM+137:20251222:102' DTM+366:202512250502:203' RFF+DM:12358741' DTM+50:20251212:102' NAD+BY+8712199999999::9++Acme Pharma™ Harma+23 Jay Bird St East::Suite 669+Tuscaloosa+AL+35401+US' CTA+BS+:Johnny Doe' COM+(659) 123-4568:TE' COM+team@mate.de:EM' NAD+SU+8712199999999::9++Haldiram Pharma™ co.+72 Blicker street+Barcelona+AU+123444+CA' CTA+DL+:Tony Stark' COM+(326) 723-5433:TE' COM+game@partner.de:EM' NAD+GY+8712199999999::9++Alexis Medicos™ Pvt. Ltd.+223 Blackbird Way+Lonavla+AL+883322+PY' CTA+OC+:Steve Rogers' COM+(326) 678-6745:TE' COM+lame@Cardon.de:EM' NAD+ST+8712199999999::9++Acme Pharma Harma™+23 Jay Bird St East::Suite 669+Tuscaloosa+AL+35401+US' CTA+OC+:Jim Carry' COM+(326) 432-45343:TE' COM+tata@motors.de:EM' LIN+1+2+11112222:SRV' PIA+1+98465AW23:BB' PIA+1+AB80:UP' IMD+F++:::Product description 1' LOC+14+0058745214' DTM+36:20200311:102' FTX+AAA+1++GAME:Disc:Is:Purchased+ITI' RFF+DM:6677446' DTM+50:20250808:102' INV+2+1+1+1' QTY+17:6:EA' LOC+14+0058745214' RFF+AAK:00453432:542333' DTM+50:20251201:102' UNT+45+H12133143' UNE+1+2597' UNZ+1+2597' ``` ![](/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)