*DLM 4000.25, Volume 2, November 26, 2019*

*Change 13*

**AP6.1. APPENDIX 6.1**

**FORMS/MESSAGE FORMATS(INTRODUCTION)**

AP 1.1.1.  Requisitions may be transmitted using the CJCSI 5721.01E, The Defense Message System[footnoteRef:1] and Associated Legacy Message Processing Systems, requirements.  DLM 4000.25, Volume 1, describes methods used to transmit and receive requisition and requisition-related transactions.  In addition, the specific forms and message formats[footnoteRef:2] prescribed for use under MILSTRIP are described below.   [1: CJCS Directives Home Page – https://www.jcs.mil/library]  [2: Narrative messages shall only be used on an exception basis.  When used, each transmission shall be limited to a maximum of seven transactions or the contents of a single page, whichever is greater.  ] 

AP6.1.2.  MILSTRIP Message Requisition (AP6.8.) and Abbreviated MILSTRIP Message Supply Status (AP6.11)

	AP6.1.2.1.  The first line in the body of the message will contain the words “MILSTRIP REQUISITION.”  Thereafter, each requisition will be numbered, commencing with number 1, and the first 66 positions of data (except for dividing slashes (/)) will be inserted.  The basic requisition will consist of 18 separated field-lengths of data.

	AP6.1.2.2.  Below is a sample message requisition segmented and explained. 

		AP6.1.2.2.1.  First Line:  A0E/(DIC); XYS/(RIC); S/(M&S); 1224005123456/(stock or part number); EA/(unit of issue); 00015(quantity); ZY1234/(requisitioner); 1150/(ordinal date); 0112/(serial number); R/(demand); BLNK/(SUPADD); A/(signal).[footnoteRef:3] [3: When an element of data is not available, the field shall be recognized and entered as “BLNK.”] 

		AP6.1.2.2.2.  Second Line:  19/(fund); 089/(distribution); BLNK/(project); 03/(PD); 154 (RDD); 2B/(advice).[footnoteRef:4] [4: Ibid.] 

		AP6.1.2.3.  Part number requisitions converted to message format are illustrated in AP6.13.

AP6.1.3.  MILSTRIP Message Follow-Up (AP6.9.).

	AP6.1.3.1.  Follow-up on requisitions may be transmitted electronically in the form of a formatted message or a narrative message when requesting status and improved estimated shipping date (ESD), under Volume 2, Chapter 4.

	AP6.1.3.2.  The first line in the body of the message will contain the words “MILSTRIP FOLLOW-UPS.”  When requesting normal status, DICs AF1, AF2, and AF3 apply.  When requesting an improved ESD, DIC AFC applies.  Exception data, and additional wording will be omitted unless DIC AT_ is used.  The DIC dictates action to be taken by the supply source, under Volume 2, Chapter C4, and added comments or requests are not applicable since the narrative message is no more than one of the media of communications for submitting follow-ups.

	AP6.1.3.3.  Below is a sample narrative follow-up message segmented and explained:

		AP6.1.3.3.1.  First Line:  AT5/(DIC); S/(M&S); 8305001234567/(stock or part number); EA/(unit of issue); 00040/(quantity); XTZ456/(requisitioner); 1250/(ordinal date); 0111/(serial number); R/(demand); BLNK/(SUPADD).[footnoteRef:5] [5: Ibid.] 

		AP6.1.3.3.2.  Second Line:  12/(fund code); 089/(distribution code); BLNK/(project code); 02/(PD); 154/(RDD); 2B/(advice).[footnoteRef:6] [6: Ibid.] 

AP6.1.4.  Request for Supply Assistance.  Requests for Supply Assistance are described under Volume 2, Chapter 4 and illustrated in AP6.10.  Paragraphs AP6.3.2 and AP6.3.3., above, also apply, except DIC AFC will always be used.  This will ensure manual review and reply using Volume 2, Chapters 4 and 5.

AP6.1.5.  Message Cancellation

	AP6.1.5.1.  Cancellation of a requisition may be transmitted electronically in the form of a narrative message[footnoteRef:7] under Volume 2, Chapters 1 and 4. [7:  Narrative messages shall only be used on an exception basis.  When used, each transmission shall be limited to a maximum of seven transactions or the contents of a single page, whichever is greater.  ] 

	AP6.1.5.2.  The first line is the body of the message will contain the words “MILSTRIP CANCELLATION.”  Exception data, remarks, and additional verbiage will be omitted.

		AP6.1.5.2.1.  First Line:  AC1/(DIC); FMI/(R); 2/(M&S); 8305001234567/(stock or part number); EA/(unit of issue); 00040/(quantity); FB2300/(requisitioner); 6265/(ordinal date); 0111/(serial number); R/)demand code); BLNK/(SUPADD); A/(signal).[footnoteRef:8]  [8:  When an element of data is not available, the field shall be recognized and entered as “BLNK.”.] 

		AP6.1.5.2.2.  Second Line: 12/(fund); 089/(distribution); BLNK/(project); 02/(PD); 354/(RDD); BLNK/(advice).[footnoteRef:9] [9:  Ibid.] 

AP6.1.6.  Abbreviated Message Documents (AP6.11 and AP6.12)

	AP6.1.6.1.  Abbreviated message formats are provided for MILSTRIP follow-ups (DIC AF_ series only), cancellations, supply status, and shipment status, respectively.  Use of these documents will be at the option of the individual Service/Sgency (S/A).  Use between S/As will be based upon agreement between the S/As.

	AP6.1.6.2.  Abbreviated message follow-up (DIC AF_ only) and cancellation documents will be initiated only by those activities with capability to prepare machine-readable documents for transmission by the Defense Message System (DMS).[footnoteRef:10] [10:  CJCS Directives Home Page – https://www.jcs.mil/library.] 

	AP6.1.6.3.  When abbreviated messages are used, each message will be limited to a maximum of seven items or the contents of a single page, whichever is greater.

	AP6.1.6.4.  The first line in the body of the message will contain the words ABBREVIATED MILSTRIP FOLLOW-UP, CANCELLATIONS, SUPPLY STATUS, OR SHIPMENT STATUS, as applicable.  Thereafter, number each line item, commencing with number 1.  Insert slashes (/) or other appropriate marks between each code and/or data element as depicted in AP6.11 and AP6.12.  The authorized data elements[footnoteRef:11] and code entries for abbreviated messages are as follows: [11:  When an element of data is not available, the field shall be recognized and entered as “BLNK.”.] 

		AP6.1.6.4.1.  Follow-Ups and Cancellation Requests (No Supply Status Received)

			AP6.1.6.4.1.1.  Document Identifier Code (DIC)

			AP6.1.6.4.1.2.  Routing Identifier Code (RIC) (To) 

			AP6.1.6.4.1.3.  Stock or Part Number

			AP6.1.6.4.1.4.  Unit of Issue

			AP6.1.6.4.1.5.  Quantity

			AP6.1.6.4.1.6.  Requisition Document Number

			AP6.1.6.4.1.7.  Distribution, when applicable; otherwise, leave blank.

			AP6.1.6.4.1.8.  Priority Designator

		AP6.1.6.4.2.  Follow-Ups and Cancellation Requests (Supply Status Received)

			AP6.1.6.4.2.1.  Document Identifier Code

			AP6.1.6.4.2.2.  Routing Identifier Code (To) 

			AP6.1.6.4.2.3.  Stock or Part Number

			AP6.1.6.4.2.4.  Unit of Issue

			AP6.1.6.4.2.5.  Quantity

			AP6.1.6.4.2.6.  Requisition Document Number

			AP6.1.6.4.2.7.  Suffix, when applicable; otherwise, leave blank.

			AP6.1.6.4.2.8.  Status

			AP6.1.6.4.2.9.  Distribution, when applicable; otherwise, leave blank.

			AP6.1.6.4.2.10.  Priority Designator

		AP6.1.6.4.3.  Supply Status

			AP6.1.6.4.3.1.  Document Identifier Code

			AP6.1.6.4.3.2.  Stock or Part Number

			AP6.1.6.4.3.3.  Unit of Issue

			AP6.1.6.4.3.4.  Quantity

			AP6.1.6.4.3.5.  Requisition Document Number

			AP6.1.6.4.3.6.  Suffix, when applicable; otherwise, leave blank.

			AP6.1.6.4.3.7.  Priority Designator

			AP6.1.6.4.3.8.  Status

			AP6.1.6.4.3.9.  Estimated Shipping Date

		AP6.1.6.4.4.  Shipment Status

			AP6.1.6.4.4.1.  Document Number Code

			AP6.1.6.4.4.2.  Quantity

			AP6.1.6.4.4.3.  Requisition Document Number

			AP6.1.6.4.4.4.  Suffix, when applicable; otherwise, leave blank.

			AP6.1.6.4.4.5.  Date Shipped or Estimated Shipping Date

			AP6.1.6.4.4.6.  Priority Designator

			AP6.1.6.4.4.7.  Transportation Control Number (TCN).

			AP6.1.6.4.4.8.  Mode-of-Shipment

			AP6.1.6.4.4.9.  If available, any of the following may also be provided:  GBL Number, Registered Parcel Post Number, or other shipment number.

	AP6.1.6.5.  Materiel Obligation Validation Form Letters and Messages.  Form letter requests, followup requests, message requests, and replies are provided in AP6.15 through AP6.20 and AP6.32 for use in connection with Materiel Obligation Validation (MOV) procedures under Chapter C8.

	AP6.1.6.6.  DD Form 1348-1A, Issue Release/Receipt Document (AP6.25, AP6.27, AP6.29, AP6.31, and AP6.35).

		AP6.1.6.6.1.  Non-Preprinted Issue Release/Receipt Document.  A single line item, single part form produced on plain stock paper (see example, AP6.25).  The size may vary within a range of 7-3/4 to 9 inches long (side to side) and 4 to 5 inches high (top to bottom) (see Chapter 29).  Data to be entered in the data blocks are shown in Appendices 8.48 and 8.49.  Blocks 24, 25, and 26 must contain bar coded data except for DLA Disposition Services Field Office documents.  DLA Disposition Services Field Office documents will not contain bar coding in Block 26.  Block 27 must contain a two-dimensional (2D) bar code (Portable Data File (PDF) 417) encompassing the linear bar code data elements plus additional elements to improve automated information technology (AIT) efficiencies and to facilitate item unique identification (IUID) when applicable.

		AP6.1.6.6.2.  The Issue Release/Receipt Document data elements, configuration and locations are as follows:

			AP6.1.6.6.3.  The Issue Release/Receipt Document is used as:

			AP6.1.6.3.1.  An issue document from distribution point to consignee resulting from a requisition.

			AP6.1.6.3.2.  A release document for retrograde materiel or inter base (post, camp, station, etc.) movements.

			AP6.1.6.3.3.  A materiel return document from base to depot.

			AP6.1.6.3.4.  A receipt document by the consignee

			AP6.1.6.3.5.  Disposal turn-in document.

			AP6.1.6.3.6.  Local requisition on DLA Disposition Services Field Office.

		AP6.1.6.6.4.  The Issue Release/Receipt Document is designed to accommodate the various elements of data used by any of the Services as source information for preparing other documentation.  The document enables supply sources to use a single method of documentation for all requisitions and provide a standard receiving document that will accommodate both manual and automated requisitioners and consignees.

AP6.1.7.  DD Form 1348-2, Issue Release/Receipt Document with Address Label (AP6.31)

	AP6.1.7.1.  The Service/Agencies have the option to stock or print the DD Form 1348-2.  The DD Form 1348-2 configuration is a DD Form 1348-1A with a perforated address label attached to the outer right edge.  The length of the DD Form 1348-2 is 13 inches.  The DD Form 1348-2 may be configured for printing as continuous forms.  For continuous forms configuration, pin-fed strips of one-half inch on each side may be added.  The length of the DD Form 1348-2 with pin-fed strip will not exceed 14 inches.  The address label dimensions of the DD Form 1348-2 are 4-1/4 inches long and 5-1/2 inches high.  Use of the address label with preprinted postage data is only authorized for shipments by the U.S. Postal Service.  The address label will contain the following elements.

		AP6.1.7.1.1.  Postage Data

		AP6.1.7.1.2.  TCN Data

		AP6.1.7.1.3.  Weight Data

		AP6.1.7.1.4.  Type Service Data

		AP6.1.7.1.5.  From Data

		AP6.1.7.1.6.  Ship-to Data

	AP 1.1.7.2.  Data will be entered on the address label as follows:

		AP6.1.7.2.1.  Postage Data.  A shipment through the U.S.P.S. must contain the following phrase, “OFFICIAL BUSINESS.”  This phrase will be printed on the bottom line of the postage block.

		AP6.1.7.2.2.  Transportation Control Number.  Enter the TCN applicable to the shipment.

		AP6.1.7.2.3.  Weight.  Enter the weight of the item being shipped.

		AP6.1.7.2.4.  Type Service.  Enter the appropriate type of delivery service; for example, first-class-priority, express mail, and Military Official Mail (MOM).

		AP6.1.7.2.5.  Ship-to.  Enter the applicable in-the-clear address of the activity that is to receive the shipment.  If mark-for data is required, enter the mark-for data above the city/state/zip code data.  If the Port of Embarkation (POE) is required, enter the POE in this block.

AP6.1.8.  IRRD (DD Form 1348-1A or DD Form 1348-2) Continuation Page.  This is a mandatory document for serialized Item shipments containing machine readable bar codes for the encoded content information to include the serial numbers, unique item identifiers (UIIs), and batch/lot numbers as required for tracking under a UIT program or in support of DoD policy for the application of IUID in supply processes.  The continuation page is intended to expedite supply and distribution processes by providing a means to automate the capture of data using automatic identification technology (AIT) devices.  The continuation page is free form.  The data elements and preferred format are shown in AP6.36.

AP6.1-1

APPENDIX 6.1