**DoD 4000.25-M, Vol 3**

**DRAFT**

*DLM 4000.25, Volume 3, December 14, 2016*

*Change 6*

# C2. ChAPTER 2

**RETAIL SUPPLY AND TRANSPORTATION INTERCHANGE – STOCK SHIPMENTS**

C2.1.  GENERAL.  This chapter provides procedures for use in retail transportation and supply processes related to the transportation in-check of cargo from a supply warehouse and subsequent outbound shipment by the servicing transportation activity.  These procedures create a virtual warehouse between supply and transportation by standardizing a supply-transportation interchange, and provide in-transit visibility and accountability of government assets shipped in the Defense Transportation System (DTS).  The transactions provide users with an electronic method of obtaining shipment data and status on specific line items upon inquiry.

C2.2.  BACKGROUND.  This section documents a standardized interchange of information between retail transportation and supply through the use of Electronic Data Interchange (EDI) transactions.  For materiel requirements processed using Military Standard Requisitioning and Issue Procedures (MILSTRIP) legacy 80 record position transactions and Defense Logistics Management Standards (DLMS) procedures, the standardized interchange employs DLMS 940R, Materiel Release and DLMS 945A, Materiel Release Advice.  This standard provides retail supply systems the ability to pre-position release order data in transportation, to submit follow-up status messages to transportation requesting updated shipment status, and to submit cancellation requests to transportation for release orders already turned over to transportation for shipment planning and execution.  The standard also provides retail transportation systems the capability to provide supply status messages to supply, to provide cancellation response messages to supply, and to submit materiel release confirmation messages to supply when the materiel has shipped.

C2.3.  STOCK SHIPMENT PROCEDURES

	C2.3.1.  Supply and Transportation Systems.  ***T***here are ***six***Automated Information Systems (AISs) that use this standardized interchange between retail transportation and supply activities.  They are the Defense Medical Logistics Standard Support (DMLSS), Global Combat Support System – Marine Corps (GCSS-MC), USAF Expeditionary Combat Support System (ECSS), and the ***Integrated Logistics Solution—Supply (ILS—S; formerly***Standard Base Supply System (SBSS)***)***, which represent the supply systems for their respective business areas, and the Cargo Movement Operations System (CMOS), ***as well as the Distribution Standard System (DSS)***, which represents the transportation system.  Systems other than the ***six*** systems above, planning to use these standardized interchange transactions to implement a similar capability must coordinate with ***the******Defense Enterprise Data Standards Office (DEDSO)***prior to attempting to implement the interchange.

	C2.3.2.  Retail Supply Activity.  This paragraph provides general procedures for retail supply activities related to the delivery of items to the servicing transportation activity for further shipment.

		C2.3.2.1.  Pre-Positioned Release Order.  For designated supply trading partners, the Defense Automatic Addressing System (DAAS) will transmit copies of the DLMS 940R, Materiel Release Order/Disposal Release Order/Redistribution Order (Document Identifier Codes (DIC) A2_/A5_/A4_) transactions to the designated transportation system to be pre-positioned awaiting actual arrival of cargo from the supply warehouse.

			C2.3.2.1.1.  For designated supply trading partners (currently limited to the SBSS—CMOS interface) the DLMS 940R, Materiel Release will be used to pass Federal Logistics Information System (FLIS) National Stock Number (NSN) item data (as identified in the 940R) that is not otherwise available to CMOS.  This is an interim measure pending establishment of a FLIS interface.

			C2.3.2.1.2.  For designated supply trading partners (currently limited to the SBSS—CMOS interface), the DLMS 940R, Materiel Release will be used to support the unique item tracking (UIT) program for Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM).  A unique item identifier (UII) and the associated serial number will be passed in the DLMS 940R for each item meeting the PIC NWRM program criteria.  For legacy items where the UII has not been marked in accordance with Item Unique Identification (IUID) policy, the serial number alone will be passed.  This is an interim measure pending transition to tracking by UII and associated IUID business rules/transactions.  DLMS Volume ***2***, Chapter 19, UIT Procedures applies (with exceptions as noted).  Future CMOS releases will include the serial number/UII in the DLMS 945A, Materiel Release Advice transaction.

			C.2.3.2.1.3.  For designated supply trading partners (currently limited to the SBSS—CMOS interface), an information copy (image) of the Materiel Release 940R will be used in support of Air Force PIC Fusion program data requirements.  The routing of an additional information-only copy of the DLMS standard transactions (940R) is authorized for forwarding PIC Fusion data needed for the Air Force UIT registry. This is a specific authorized use with unique identifiers to flag the transaction as information only.[footnoteRef:1] [1:  Refer to ADC 316C.] 

******C2.3.2.1.4.  Item Unique Identification.  For designated trading partners, when NSNs containing an IUID indicator Yes (Y), indicating that DoD IUID Supply Policy is required, the DLMS 940R Materiel Release must contain the UII and/or serial number for each item when available.[footnoteRef:2] [2:  Refer to DLM 4000.25 Volume 2, Chapter 5, Status Reporting, and ADC 1030] 

			C2.3.2.1.5.  Updated Pre-Positioned Release Order.  In the event required UII and/or serial number information is not transmitted in the initial DLMS 940R to transportation, an updated DLMS 940R citing the value R at 1/W0502/0200 must be sent prior to sending the materiel to transportation.

			C2.3.2.1.6.  When authorized by the trading partners, the materiel release may include identification of a pre-designated carrier and the carrier account number for the applicable shipment.  When provided, this information will be perpetuated to the materiel release confirmation.[footnoteRef:3] [3:  Refer to ADC 1164] 

		C2.3.2.2.  Delivery and In-Check.  The supply activity will make local deliveries of the items to be shipped to the servicing transportation activity.  The line items will be in-checked by the transportation activity based on the cargo and the documentation received from the supply activity.

		C2.3.2.3.  Shipment Documentation.  The materiel for shipment will be delivered to the servicing transportation activity by the retail supply activity accompanied by a DD Form 1348-1A, Issue Release/Receipt Document, (IRRD).  DLM 4000.25, Volume 2, Chapter 29 documents procedures for the use and generation of the IRRD.

		C2.3.2.4.  Follow-up Requests.  The supply system will initiate DLMS 940R, Materiel Release Inquiry/Disposal Release Inquiry (DIC AF6/AFJ) message for follow-up requests.  Based upon elapsed time from either the initial release of the Materiel Release Order/Disposal Release Order/Redistribution Order or the estimated shipping date from the Materiel Release Advice/Disposal Shipment Advice, the supply system will initiate the inquiry using normal follow-up procedures as documented inDLM 4000.25, Volume 2, Chapter 4.  The only exceptions relate to multi-packs (see paragraph C2.3.6. below) and assemblages (e.g., medical (see paragraph C2.3.7. below)).

		C2.3.2.5.  Cancellation Requests.  The supply system will initiate DLMS 940R, Materiel Release Cancellation/Disposal Release Cancellation (DIC AC6/ACJ) message for cancellation requests.  DLM 4000.25, Volume 2, Chapter 4 prevails; the only exceptions relate to multi-packs (see paragraph C2.3.6. below) and assemblages (e.g., medical (see paragraph C2.3.7. below)).

		C2.3.2.6.  Shipment Status Messages

			C2.3.2.6.1.  Initial Shipment Status Message.  When the retail supply activity receives the Materiel Release Confirmation for a multi-pack, the activity must associate it with all the document numbers that were contained in the initial Materiel Release Order, generate the required DLMS 856S, Shipment Advice (DIC AS_) shipment status transactions for the multipack, and transmit to DAAS for distribution per existing procedures and trading partner profiles.  When the retail supply activity receives the Materiel Release Confirmation for an assemblage (e.g., medical), the activity will generate the required DLMS 856S Shipment Status transaction at the Assemblage Identification Number (AIN) level.  For all Materiel Release Confirmations, the retail supply activity will insert the original distribution code assigned to the Materiel Release Order/Disposal Release Order/Redistribution Order in lieu of the special distribution code used to denote the retail transportation and supply interchange when generating the shipment status transactions.

			C2.3.2.6.2.  Shipment Status Message Updates.  In the event a shipment does not get lifted as originally intended (e.g., shipment is left off the truck) and the retail supply activity receives an updated DLMS 945A, Materiel Release Confirmation message from the retail transportation activity, then the retail supply activity will generate an updated DLMS 856S, Shipment Status transaction to convey the changed transportation information.  See DLM 4000.25, Volume 2, Chapter 5 for detailed procedures.  Examples of changed transportation information would include transportation method code, standard carrier alpha code (SCAC), ship date, bill of lading information, and tracking information.

******C2.3.2.6.3.  Unique Item Identification.[footnoteRef:4]  Shipment Status for NSNs containing an IUID indicator Yes (Y), indicating that DoD IUID Supply Policy is required, must contain the UII and/or serial number for each item when available. Refer to DLM 4000.25 Volume 2, Chapter 5, Status Reporting; paragraph C5.1.3.5. contains specific shipment status requirements for IUID.  [4:  Refer to DLM 4000.25 Volume 2, Chapter 5, Status Reporting, and ADC 1030] 

C2.3.3.  Servicing Transportation Activity.  This paragraph provides general procedures for servicing transportation activities following***receipt of******the materiel release order (MRO) from the retail supply systems and subsequent*** local delivery of items for shipment (received from retail supply).

***C2.3.3.1.  Initial Transportation Account Code Validation.[footnoteRef:5]  Following receipt of the MRO from the retail supply system, transportation will validate the transmitted transportation account code (TAC).  In case of an invalid or missing TAC, the transportation system will generate a DLMS 945A (AE6), Materiel Release Advice transaction with Shipment Hold Code S, Invalid or Missing Transportation Account Code (TAC), and send it back to the retail supply system.  This provides visibility for possible delays in processing a shipment due to an invalid or missing TAC and gives the supply activity the option to resend the DLMS 940R with the correct TAC.  If the supply activity sends an updated MRO, the transportation activity will validate the TAC and append the MRO.  Figure C2.F1 depicts the transaction account code validation process.*** [5:  Refer to ADC 1206 for detailed procedures.] 

		C2.3.3.***2***.  In-Check.  Upon local delivery of the item (from retail supply) to the transportation activity customer service area, transportation personnel will in-check the items as follows:

			C2.3.3.***2***.1.  Either scan the DD Form 1348-1A, IRRD using a handheld scanner or manually in-check the document numbers into the transportation system. 

			C2.3.3.***2***.2.  Generate DLMS 945A, Materiel Release Advice/Disposal Shipment Advice (DIC AE6/AEJ) in-check status message and send it to the supply activity electronically.

******		C2.3.3.***2***.3. When CMOS is the servicing transportation activity, the in-check status message will include the transportation in-checker identification code (three position numeric value) and the associated in-checker full name in the format of First Name Middle Initial Last Name, with no special characters (e.g., periods, commas) to separate the components of the full name.  If there is no middle initial, then insert NMN (no middle name) in place of the middle initial.  Optional contact information may include phone numbers (e.g., commercial, DSN, international, and fax) and electronic mail.  If more than three types of contact information are required, repeat the X12 PER segment, not to exceed two repetitions.

***C2.3.3.3.  Transportation Account Code Validation on Shipping Documents.  Verify that the TAC on the DD Form 1348-1A matches the TAC on the MRO.  If the TAC on the DD Form 1348-1A is either missing or there is a mismatch, then coordinate with the supply activity.  Upon receipt of a valid TAC from the supply activity, update historical records and shipping documentation to reflect the correct TAC citation.  Figure C2.F1 depicts the transaction account code validation process.***

		C2.3.3.***4***.  Hold Status.  Subsequent to in-check and prior to materiel release confirmation, if the cargo is placed in transportation hold status, additional DLMS 945A, Materiel Release Advice/Disposal Shipment Advice (DIC AE6/AEJ) status messages will be sent by transportation to supply.

		C2.3.3.***5***.  Status/Follow-up Response.  The transportation system will respond to a follow-up request using DLMS 945A, Materiel Release Advice/Disposal Shipment Advice (DIC AE6/AEJ) supply status message.

		C2.3.3.***6***.  Cancellation Response.  The transportation system will generate a DLMS 945A, Materiel Release Advice/Disposal Shipment Advice (DIC AE6/AEJ) status message with applicable status code indicating acknowledgement of the cancellation requirements.

		C2.3.3.***7***.  Materiel Release Confirmation

			C2.3.3.***7***.1.  Initial Materiel Release Confirmation.  After the shipment is processed and shipped, the transportation activity generates a DLMS 945A, Materiel Release Confirmation/Disposal Release Confirmation, and sends it to the supply activity, where the shipment status message will be generated and transmitted.

****C2.3.3.***7***.2.  Materiel Release Confirmation Changes/Updates.  In the event a shipment does not get lifted as originally intended (e.g., shipment is left off the truck), the transportation activities that originate the DLMS 945A Materiel Release Confirmation will send an updated MRC transaction with all of the changed transportation information to the supply activity to enable the supply activity to prepare an updated DLMS 856A Shipping Status message.  See DLM 4000.25 Volume 2, Chapter 4 for detailed procedures for preparation of the MRC change/update message.  Examples of changed transportation information would include transportation method code, SCAC, ship date, bill of lading information, and tracking information. 

******C2.3.3.***7***.3.  Item Unique Identification. When the DLMS 940R contains IUID data content (e.g., UII and/or serial number), perpetuate the IUID content in the DLMS 945A Materiel Release Confirmation to clearly delineate which UIIs/serial numbers were shipped under a particular TCN.  When a shipment contains IUID content and is shipped in multiple freight pieces, shippers are NOT authorized to execute the movement of the shipment using multiple freight piece procedures (e.g., citing the same TCN for all boxes).  Those shipments must be “partialled” by using the 16th position of the TCN to uniquely identify each freight piece.  A separate DLMS 945A MRC will be transmitted for each document number – partial TCN pair, identifying the contents of each freight piece, to include pRFID tag(s) and UII(s) and/or serial numbers.

		C2.3.3.***8***.  Transaction Information Copy.  For designated supply trading partners (currently limited to the SBSS–CMOS interface), an information copy (image) of the DLMS 945A, Materiel Release Advice will be used in support of Air Force PIC Fusion program data requirements.  The routing of an additional information-only copy of the DLMS 945A, Materiel Release Advice transaction is authorized for forwarding PIC Fusion data needed for the Air Force UIT Registry.  This is a specific authorized use with unique identifiers to flag the transaction as information only.

***C2.3.3.9.  Transportation Account Code Validation Process Flow.******Figure C2.F1 depicts the transaction account code validation process.***

***Figure C2.F1 – Transportation Account Code (TAC) Validation Process Flow***

	C2.3.4.  DAAS Processing.  DAAS will route transactions between designated supply and transportation systems based on mutual agreements between the trading partners. This includes both DLMS compliant and MILSTRIP legacy transaction compliant systems.

		C2.3.4.1.  ***Transportation*** System***s***.  The Cargo Movement Operations System (CMOS) ***and Distribution Standard System (DSS) are*** capable of receiving DLMS compliant DLMS 940R, Materiel Release and transmitting DLMS 945A, Materiel Release Advice messages.

		C2.3.4.2.  Supply Systems.  Depending on whether the supply system is DLMS compliant, DAAS will process the transactions as follows:

			C2.3.4.2.1.  DLMS Compliant Systems. If the supply system is DLMS compliant, DAAS will not transform the transactions to/from MILSTRIP legacy transactions, based on established trading partner profiles held by DAAS.  If the supply system is DLMS compliant and is exchanging information about multi-packs, the W0507 data element in the DLMS 940R, Materiel Release and W0612 data element in the DLMS 945A, Materiel Release Advice will carry Action Code CN.  For assemblages (e.g., medical), the W0507 data element in the DLMS 940R, Materiel Release and W0612 data element in the DLMS 945A, Materiel Release Advice will carry Action Code ME.  For interchanges other than multi-packs and assemblages, the W0507 data element in the DLMS 940R, Materiel Release and the W06112 data element in the DLMS 945A, Materiel Release Advice will carry Action Code A6.  Additionally, DLMS 940R and DLMS 945A will have Distribution Code 111.  These action codes and Distribution Code 111 will denote the applicability of special procedures authorized under this Chapter and authorize the use of selected EDI segments and loops to denote contents of multi-packs and assemblages.

			C2.3.4.2.2.  MILSTRIP Legacy Transaction Compliant Systems.  If the supply system is MILSTRIP legacy transaction compliant, Distribution Code 111 will be identified to denote the applicability of special procedures authorized under this Chapter.  Normally DAAS will transform the transactions to/from MILSTRIP legacy formats based on existing maps, except when there is a Distribution Code 111 in DLMS 945A, Materiel Release Advice/Disposal Shipment Advice messages from the transportation system.  Distribution Code 111 authorizes the following actions:  use of DIC AE6/AEJ for unsolicited supply status responses by the transportation system; use of transportation hold and delay codes in DIC AE6/AEJ (rp51) by the transportation system in addition to its normal usage in the Materiel Release Confirmation; and use of DIC AE6/AEJ in lieu of DIC AG6/AGJ as a cancellation response by transportation system to facilitate usage of the supply status and transportation hold and delay codes.

	C2.3.5.  Retail Transportation and Supply Interchange.  Figure C2.F1 shows the standard transactions that will occur between retail supply and the transportation activity for the business processes covered in this chapter.

Figure C2.F***2*** – Retail Transportation and Supply Data Interchange

****

		C2.3.5.1.  DLMS and MILSTRIP Legacy Transaction Designations.  To denote a transaction is in support of the Retail Transportation and Supply Receipt and Acknowledgement Interchange, it will contain the designated action code and/or distribution code as delineated below:

			C2.3.5.1.1.  Action Code (Other than Multi-packs and Assemblages (e.g., Medical))

				C2.3.5.1.1.1.  DLMS 940R (W0507) = A6

				C2.3.5.1.1.2.  DLMS 945A (W0612) = A6 

			C2.3.5.1.2.  Action Code (Multi-Packs and Assemblages (e.g., Medical))

				C2.3.5.1.2.1.  Multi-Packs.  DLMS 940R (W0507) = CN and DLMS 945A (W0612) = CN

				C2.3.5.1.2.2.  Assemblages.  DLMS 940R (W0507) = ME and DLMS 945A (W0612) = ME

			C2.3.5.1.3.  Distribution Code

				C2.3.5.1.3.1.  DLMS 940R and DLMS 945A LQ01 = AK and LQ02 = 111

				C2.3.5.1.3.2.  MILSTRIP legacy transaction distribution code = 111.

		C2.3.5.2.  Pre-Positioned transactions from Supply.  For designated supply trading partners, DAAS will transmit copies of DLMS 940R, Materiel Release Order/Disposal Release Order/Redistribution Order (DICs A2_/A5_/A5J/A4_) transactions to the designated transportation system to be pre-positioned awaiting actual arrival of cargo from the supply warehouse.  The applicable transactions can be readily identified by use of Distribution Code = 111.  Additionally, the action code in DLMS 940R (W0507) and DLMS 945A (W0612) will be either A6, CN, or ME.

***C2.3.5.3.  Transportation Account Code Validation.[footnoteRef:6]  Following receipt of the DLMS 940R MRO transaction from the supply system, transportation will perform a validation of the transmitted TAC.  If the provided TAC proves to be invalid or is missing, the transportation system generates a DLMS 945A (AE6), Materiel Release Advice transaction with Shipment Hold Code S, Invalid or Missing TAC, and sends it back to the supply system.  The supply activity then has the option to resend the DLMS 940R MRO with the correct TAC to prevent delays in processing the shipment for release.*** [6:  Refer to ADC 1206 for detailed procedures.] 

***C2.3.5.3.1.  If the supply activity sends an updated MRO, the transportation activity will validate the TAC and append the MRO.***

***C2.3.5.3.2.  If the supply activity does not send an updated MRO, the transportation activity will validate the TAC following in-check of the materiel by comparing the DD 1348-1A to the MRO.  If there is a mismatch, the transportation activity will coordinate with the supply activity to identify a valid TAC, at which time the transportation activity will update its records and process the shipment for release.***

		C2.3.5.***4***.  Receipt/In-Check of Cargo by Transportation.  Upon physical receipt/in-check of cargo by transportation, the transportation system will self-initiate a DLMS 945A, Materiel Release Advice/Disposal Shipment Advice (DIC AE6/AEJ) supply status response message to notify the supply activity via DAAS that the property has been received.  Since there was no initial DLMS 940R, Materiel Release Inquiry/Disposal Release Inquiry (DIC AF6/AFJ) follow-up request prompting the status message, the American National Standards Institute, Accredited Standards Committee X12 (X12) Code NO will be inserted in the W0611 data element to denote that this is being used by transportation to report cargo processing status prior to materiel release confirmation, and X12 code A6 will be inserted in the W0612 data element to denote that the supply status response is part of the Retail Transportation and Supply Receipt and Acknowledgement Interchange.  To facilitate mapping of the DLMS 945A, Materiel Release Inquiry/Disposal Release Inquiry to a MILSTRIP legacy DIC AE6/AEJ transaction, the Distribution Code will carry a value of 111 to inform DAAS of the special routing and generation of an unsolicited supply status message and to authorize the use of the transportation hold and delay code in lieu of a signal code for a supply status response, in addition to the Materiel Release Confirmation where it normally is reported.  If the materiel is later placed into a transportation hold status, such as awaiting air clearance, a self-initiated DLMS 945A, Materiel Release Advice/Disposal Shipment Advice supply status message will be generated for every reportable status change prior to shipment.  The W06, LQ, and G62 segment values in the DLMS 945A, Materiel Release Advice/Disposal Shipment Advice for this step are as follows:

			C2.3.5.***4***.1.  In-Check Reporting.  To report in-check of cargo, W0611 = NO and W0612 = A6; LQ01 = AK and LQ02 = 111; LQ01 = 81 and LQ02 = BA; G6201 = 17 and G6202 = estimated shipping date in CCYYMMDD format.

			C2.3.5.***4***.2.  Transportation Hold and Delay Reporting.  To report a transportation hold and delay status, W0611 = NO and W0612 = A6; LQ01 = AK and LQ02 = 111; LQ01 = BC and LQ02 = authorized code values from ***DLM 4000.25, Volume 2, Appendix 7.17, Shipment Hold Codes;*** G6201 = 17 and G6202 = estimated shipping date in CCYYMMDD format.

		C2.3.5.***5***.  Status Inquiry and Response.  The supply system will initiate a DLMS 940R, Materiel Release Inquiry/Disposal Release Inquiry (DIC AF6/AFJ) message for follow-up requests to inquire on the status of a release order turned over to transportation for shipping; the W0507 data element will carry an A6 to denote that the follow-up request is part of the Retail Transportation and Supply Receipt and Acknowledgement Interchange.  Based upon elapsed time from either the initial release of the Materiel Release Order/Disposal Release Order/Redistribution Order or the estimated shipping date from the Materiel Release Advice/Disposal Shipment Advice, the supply system will initiate the inquiry using normal follow-up procedures, with communications via DAAS.  The transportation system will respond to a follow-up request with a DLMS 945A, Materiel Release Advice/Disposal Shipment Advice supply status response message with an A6 in the W0612 data element and Distribution Code 111 to denote that the supply status response is part of the Retail Transportation and Supply Receipt and Acknowledgement Interchange.  Distribution Code 111 also authorizes the use of the transportation hold and delay code in lieu of the signal code, as applicable for a supply status response, in addition to the Materiel Release Confirmation where it normally is reported.  The W06, LQ, and G62 segment values in the DLMS 945A, Materiel Release Advice/Disposal Shipment Advice for this step are as follows:

			C2.3.5.***5***.1.  Materiel Release Order

				C2.3.5.***5***.1.1.  W0611 = NL

				C2.3.5.***5***.1.2.  W0612 = A6

				C2.3.5.***5***.1.3.  LQ01 = AK and LQ02 = 111

			C2.3.5.***5***.2.  Disposal Release Order

				C2.3.5.***5***.2.1.  W0611 = NQ

				C2.3.5.***5***.2.2.  W0612 = A6

				C2.3.5.***5***.2.3.  LQ01 = AK and LQ02 = 111.

			C2.3.5.***5***.3.  To report the applicable supply status code, LQ01 = 81 and LQ02 = authorized code values from DLM 4000.25-1, Appendix 2.16.  Typical status codes that may be reported by transportation are BA to denote the item is being processed for release and shipment (in-checked) or BF to denote that transportation has no record of the document for the follow-up request, or BX to indicate that pre-positioned data on the item from shipment was received from supply but the item has not yet arrived at the transportation activity for in-check.  When providing a BA status, G6201 = 17 and G6202 = estimated shipping date in CCYYMMDD format.

			C2.3.5.***5***.4.  To report a transportation hold and delay status, LQ01 = AK and LQ02 = 111; LQ01 = BC and LQ02 = authorized code values ***from******DLM 4000.25, Volume 2, Appendix 7.17, Shipment Hold Codes;***G6201 = 17 and G6202 = estimated shipping date in CCYYMMDD format.

		C2.3.5.***6***.  Cancellation Requests and Responses.  The supply system will initiate a DLMS 940R, Materiel Release Cancellation/Disposal Release Cancellation (DIC AC6/ACJ) message when it wants to issue a cancellation request to the transportation system for release orders that have already been turned over to transportation for shipping; the W0507 data element will carry an A6 to denote that the cancellation request is part of the Retail Transportation and Supply Receipt and Acknowledgement Interchange.  Normal cancellation request procedures will apply.  The transportation system will respond to the cancellation request with a DLMS 945A, Materiel Release Advice/Disposal Shipment Advice message, with an A6 in the W0612 data element.  The distribution code will carry a value of 111 to inform DAAS of the use of the supply status response (MILSTRIP legacy DIC AE6/AEJ format) as part of the Retail Transportation and Supply Interchange.  In addition to Distribution Code 111 identifying the retail interface, it also authorizes the use of supply status codes, as a response to the cancellation request.  DLMS 945A, Materiel Release Advice/Disposal Shipment Advice (W0611), (W0612), and LQ01/02 data element values for this step are as follows:

			C2.3.5.***6***.1.  Materiel Release Order

				C2.3.5.***6***.1.1.  W0611 = NL

				C2.3.5.***6***.1.2.  W0612 = A6

				C2.3.5.***6***.1.3.  LQ01 = AK and LQ02 = 111

			C2.3.5.***6***.2.  Disposal Release Order

				C2.3.5.***6***.2.1.  W0611 = NQ

				C2.3.5.***6***.2.2.  W0612 = A6

				C2.3.5.***6***.2.3.  LQ01 = AK and LQ02 = 111.

			C2.3.5.***6***.3.  To report the applicable supply status code associated with the cancellation response, LQ01 = 81 and LQ02 = authorized code values from DLM 4000.25, Volume 2, Appendix 7.16.  Typical status codes that may be reported by transportation are BF to denote that transportation has no record of the document for the cancellation request, BQ to denote that the cancellation request is confirmed and the release order is no longer being processed for shipment, and B8 to denote that the quantity requested for cancellation cannot be processed because the item has already been shipped.

		C2.3.5.***7***.  Shipment Notification (Materiel Release Confirmation).  Once the materiel is shipped, the transportation system will initiate a DLMS 945A, Materiel Release Confirmation/Disposal Release Confirmation (DIC AR_) message to notify the supply system via DAAS that the materiel has been shipped.  The W0612 data element will contain an A6 and Distribution Code 111.  Upon receipt of a DLMS 945A, Materiel Release Confirmation/Disposal Release Confirmation (DIC AR_), the supply system will transmit, via DAAS, the required DLMS 856S, Shipment Advice (DIC AS_) messages to the designated recipients following normal supply business rules.  Note: the retail supply system will apply the original distribution code in lieu of the specially assigned code value of 111 in the shipment status messages.  The W06, LQ, and G62 segment values in the DLMS 945A, Materiel Release Confirmation/Disposal Release Confirmation for this step are as follows:

			C2.3.5.***7***.1.  Materiel Release Order

				C2.3.5.***7***.1.1.  W0611 = NJ

				C2.3.5.***7***.1.2.  W0612 = A6

				C2.3.5.***7***.1.3.  LQ01 = AK and LQ02 = 111

			C2.3.5.***7***.2.  Disposal Release Order

				C2.3.5.***7***.2.1.  W0611 = NM

				C2.3.5.***7***.2.2.  W0612 = A6

				C2.3.5.***7***.2.3.  LQ01 = AK and LQ02 = 111.

			C2.3.5.***7***.3.  Partial Transportation Control Numbers.  If the shipment is partialed into multiple TCNs (e.g., alpha character other than X in record position 16), the W12 sub-loop will be repeated for each related partial TCN (e.g., record positions 1-15 are identical) with the TCN and the document number for the shipment identified in the N9/0040 segment.

	C2.3.6.  Multi-Pack Processing Procedures.  This paragraph provides procedures for use when processing multi-packs.

		C2.3.6.1.  DLMS Compliant Supply Systems

			C2.3.6.1.1.  DLMS 940R, Materiel Release.  DLMS 940R will be used as a multi-line document transaction to identify the lead document number for a multi-pack and the document numbers contained within the multi-pack.  The authorization to do this will be carried in the W0507/0200 data element with a value CN.  For materiel and disposal release orders and redistribution orders, the N9/0900 segment will contain the lead document number assigned to the multi-pack, from which the transportation control number will be derived/assigned.  The W01 Loop (Loop ID 0310) will be repeated for each document number associated with the multi-pack including the lead document number identified in N9/0900.  Follow-up requests will only be at the lead document number level, with it identified in the N9/0400 segment in the W01 loop; no looping of the W01 is required; however, the following values will be used to satisfy X12 syntax compliance:  W0101 = 1, W0102 = MX, W0104 = ZZ, and W0105 = MIXED.  Cancellation requests will contain the single line Materiel Release Order document number, and the transportation system will recognize that the document number being used may not be the lead document number, but may still be part of a multi-pack.  Cancellation will be attempted for all items/quantities for which a DD Form 1348-1A has been released and there is no record of transportation release, unless the dollar value of a single line packed in a consolidated shipment unit is less than $200, per DLM 4000.25, Volume 2, Chapter 4.

			C2.3.6.1.2.  DLMS 945A, Materiel Release Advice.  DLMS 945A will be used as a multi-line document transaction to identify the transportation control number (and partial TCNs) and lead document number associated to it.  The authorization to do this will be carried in the W0507/0200 data element with a value CN.  Status responses will only be at the lead document number level, with it identified in the W12 loop in the N9/0040 segment and the W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data element to denote a multi-pack with mixed commodities.  For cancellation responses, the response will be at the single line document number level.  For materiel release confirmation when the multi-pack is not partialed into multiple TCNs, the transaction will be processed as a single line transaction with the TCN and the lead document number identified in the W12 sub-loop, and the W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data element.  If the multi-pack is partialed into multiple TCNs (e.g., alpha character other than X in record position 16), the W12 sub-loop will be repeated for each related partial TCN (e.g. record positions 1-15 are identical) with the TCN and the lead document number for the multi-pack identified in the N9/0040 segment and the W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data element.  When the retail supply activity receives the Materiel Release Confirmation, the activity will associate it with all the document numbers that were contained in the initial Materiel Release Order, generate the required DLMS 856S, Shipment Advice shipment status transactions for the multi-pack, and transmit to DAAS for distribution per existing procedures and trading partner profiles. 

		C2.3.6.2.  MILSTRIP Legacy Compliant Supply Systems

			C2.3.6.2.1.  DLMS 940R, Materiel Release.  DLMS 940R will be transformed by DAAS from the MILSTRIP legacy transaction release order into a single line item order, as it is normally done today.  The transportation system will in-check the multi-pack by either scanning or manually loading the lead document number; the transportation operator will then have to read the individual DD Form 1348-1A contained within the pack list to in-check the items individually and associate them to the lead document number.  The TCN will be derived from the lead document number.  Follow-up and cancellation requests will contain the single line Materiel Release Order document number.  For cancellations, the transportation system will recognize that the document number used may not be the lead document number, but may still be part of a multi-pack.  Cancellation will be attempted for all items/quantities for which a DD Form 1348-1A has been released and there is no record of transportation release, unless the dollar value of a single line packed in a consolidated shipment unit is less than $200, per DLM 4000.25, Volume 2, Chapter 4.

			C2.3.6.2.2.  DLMS 945A, Materiel Release Advice.  For status and cancellation responses, the message will be originated by the transportation system at the single line item transaction, comparable to the single line item DLMS 940R, Materiel Release received from the supply system; it will be transformed by DAAS into a single line MILSTRIP legacy DIC AE6/AEJ transaction at the Materiel Release Order document number level.  For materiel release confirmations, the transportation system will originate the transaction at the single line item level, comparable to the single line item DLMS 940R, Materiel Release received from the retail supply system; DAAS will transform the message into individual MILSTRIP legacy DIC AR_ transactions with the appropriate TCN (or partial TCN) mapped to the document numbers cited in the N9/0040 segment within the W12 sub-loop.

	C2.3.7.  Assemblage (e.g., Medical) Processing Procedures.  This paragraph provides procedures for assemblage processing and the associated transactions between supply and transportation for shipment requirements.  Refer to Volume 2, Chapter 20, Medical Unit Assembly Program, for related procedures used by the medical supply system to construct assemblages.

		C2.3.7.1.  DLMS Compliant Supply Systems

			C2.3.7.1.1.  DLMS 940R, Materiel Release.  The DLMS 940R will be used as a multi-line document transaction to identify the Assemblage Identification Number (AIN) for an assemblage and the internal document numbers contained within the assemblage.  The authorization to do this will be carried in the W0507/0200 data element with a value ME.  The N9/0900 segment will contain the AIN assigned to the assemblage, from which the transportation control number will be derived/assigned.  The W01 (Loop ID 0310) loop will be repeated for each internal document number associated with the assemblage, with the information associated with the AIN being the first loop.  Follow-up and cancellation requests will be only at the AIN level (no looping of the W01 is required); however, the following values will be used to satisfy X12 syntax compliance:  W0101 = 1, W0102 = MX, W0104 = ZZ, and W0105 = “MIXED”.  The lead document number will be in the W01 loop in the N9/0400 segment.

			C2.3.7.1.2.  DLMS 945A, Materiel Release Advice.  The DLMS 945A will be used as a multi-line document transaction to identify the transportation control number (and partial TCNs) and AIN associated to it.  The authorization to do this will be carried in the W0612/0200 data element with a value ME.  Status and cancellation responses will only be at the lead AIN level, with it identified in the W12 loop in the N9/0040 segment, and the W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data element to denote an assemblage with mixed commodities; no looping of the W12 is required.  For materiel release confirmation when the assemblage is not partialed into multiple TCNs, the transaction will be processed as a single line transaction with the TCN and the AIN identified in the W12 sub-loop, and the W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data element.  If the assemblage is partialed into multiple TCNs (e.g., alpha character other than X in record position 16), the W12 sub-loop will be repeated for each related partial TCN (e.g. record positions 1-15 are identical) with the TCN and the AIN for the assemblage identified in the N9/0040 segment, and the W1207 data element will carry a ZZ with the word “MIXED” in the W1208 data element.  When the retail supply activity receives the Materiel Release Confirmation, the supply activity will generate the required DLMS 856S, Shipment Advice shipment status transaction at the AIN level for the assemblage.

		C2.3.7.2.  MILSTRIP Legacy Compliant Supply Systems

			C2.3.7.2.1.  DLMS 940R, Materiel Release.  DLMS 940R will be transformed by DAAS from the MILSTRIP legacy release order into a single line item for the entire assemblage as a single unit.  The transportation system will in-check the assemblage by scanning or manually loading the AIN and process the assemblage as a single shipment unit.  The TCN will be derived from the AIN.  Follow-up and cancellation requests must only be at AIN level; no looping of the W01 is authorized.

			C2.3.7.2.2.  DLMS 945A, Materiel Release Advice.  For status and cancellation responses, the message will be originated by the transportation system at the single line item transaction, comparable to the single line item DLMS 940R Materiel Release received from the supply system; it will be transformed by DAAS into a single line MILSTRIP legacy DIC AE6/AEJ transaction at the AIN level.  For materiel release confirmations, the transportation system will originate the transaction at the single line item level, comparable to the single line item DLMS 940R received from the retail supply system; DAAS will transform the message into individual MILSTRIP legacy equivalent DIC AR_ transactions with the appropriate TCN (or partial TCN) mapped to the AIN cited in the N9/0040 segment within the W12 sub-loop.

**C**

C2-15	CHAPTER 2

# image1.emf

# Microsoft_Visio_2003-2010_Drawing.vsd

# image2.png