ADC 263 Inclusion of Unit Price in Requisition Modification and Cancellation

ADC 263 Inclusion of Unit Price in Requisition Modification and Cancellation 1. ORIGINATING SERVICE/AGENCY: USAF, 754 ELSG/LRS; DSN 596-2012; COMM 334-416-2012 2. FUNCTIONAL AREA: a. Primary/Secondary Functional Area: AF Retail Supply b. Primary/Secondary Functional Process: Requisition Modifier AM(X) Output Transaction and Requisition Cancellation Request - AC(X) and Follow-up on Requisition Cancellation - AK(X) Transactions. 3. BACKGROUND: a. Intent of the transaction: This proposed DLMS change is in support of an AF Jump Start program. The Standard Base Supply System (SBSS) transmits the unit price on all requisition modifiers, requisition cancellation requests, and follow-ups on cancellation requests. The intent of this change is to open the DLMS unit price field to carry this unit price, and establish business rules for DAASC conversion between DLMS and MILS for intra-af transactions. This change permits optimal identification of the unit price for intra-af use; it does not make inclusion of the unit price a required entry under DLMS. Additionally, although the AF currently may provide the unit price regardless of supply source, there is no known requirement to perpetuate this practice to the DLMS for inter-service submission. b. Scenario for which the transaction is used: The Standard Base Supply System transmits the unit price on all requisition modifiers, MILSTRIP Document Identifiers AM(x): AM1, AM2, AM4, AM5, AMA, AMB, AMD, AME; requisition cancellation requests, MILSTRIP AC(x): AC1,AC2,AC3,AC4,AC5; and, follow-ups on cancellation requests, MILSTRIP AK(x): AK1,AK2,AK3,AK4, AK5. These transactions have the unit price on the transaction, regardless of the SOS. Whenever an applicable field (Priority, RDD, etc) on an SBSS Requisition is modified by an inline (user caused) or programmatic input, the SBSS produces an AM(x) outbound transaction. The cancellation requests are produced when the requisition becomes excess to base needs/requirements. Although the AM(x), AC(x) and AK(x) are normally programmatically produced and sent to DAASC, they may be input manually and transmitted to DAASC from the SBSS. 4. Procedures, transactions, data elements, processing details in use today: Under the Jump Start program, these AM(x) and AC(x)/AK(x) transactions will be produced in DLMS XML using the DLMS 511R/869C formats, respectively. AF is required to perpetuate the unit price as currently done the MILS transactions. The unit cost is taken from the SBSS Requisition (Due-in-Detail) record; specifically, from the field name, [202-UNIT-PRICE]. For the SBSS, the unit price is not the unit price on the SBSS item record, but includes surcharges or other added costs, i.e., for GSA items, the unit cost is the item record unit price plus the GSA surcharge. 5. PROPOSED CHANGE(S): a. Requested change in detail: Update the DLMS 511M, Requisition Modification, and 869C, Requisition Cancellation, as indicated in Enclosure 1. Update MILSTRIP Appendix 3.2 and Appendix 3.7, as indicated in Enclosure 2. Revisions from the original staffing are highlighted. 1 Attachment 1

b. Proposed procedures: The USAF will generate the DLMS transactions containing the unit price as described. For intra-af, where the receiver is operating in a MILS environment, DAAS will convert to allow the unit price to populate the MILS format. The unit price in the MILS format will be a structured as: (1) 8-digit dollar and 2-digit cents, and will populate rp 71-80 in the modification; (2) 5-digit dollar and 2-digit cents, and will populate rp 74-80 in the cancellation. 6. REASON FOR CHANGE: The Air Force SBSS MILS transactions identified carry a unit price. The AF needs to perpetuate the MILS unit price in the DLMS transactions to be used in the Jump Start program. 7. ADVANTAGES AND DISADVANTAGES: a. Advantages (tangible/intangible): The DLMS transaction needs to carry the data that the Air Force (SBSS) MILS contains, i.e., specifically for the unit price. b. Disadvantages: Refer to paragraph 10, below. c. Alternatives: Refer to paragraph 10, below. 8. ADDITIONAL COMMENTS TO CONSIDER: The AF field length for unit price is smaller than the DLMS enhancement field length. This does not present a problem since it is the AF originating system that will populate this field with current field length, which will then fit within the DLMS field length. AF should convert to standard DLMS field length during full modernization. 9. NOTE ANY REGULATIONS OR GUIDANCE: AFMAN 23-110, Volume II, Part 2, Chapter 9, Attachment 9E-3 (Requisition Modifier (AM*) Output Transaction. DoD 4000.25-1-M, MISTRIP (April 28, 2004). Attachment 9C-12 (Request for Cancellation of Requisition). 10. NOTE ADDITIONAL REQUIREMENTS: The USAF has been unable to identify the source requirement for the unit price in the requisition modification and cancellation/follow-up for cancellation, so there is no known functional requirement. DLMSO is, therefore, restricting the communication of the unit price for intra-air Force use. Rather than impose a program change on a legacy system, DLMSO proposes that the restriction be applied during DAASC Micro Automated Routing System (DMARS) processing. DAASC is requested not to perpetuate the unit price to either MILS or DLMS transactions forwarded to non-air Force supply sources. Under full modernization, the Air Force is requested to terminate the practice of sending the unit price back to the DoD supply source unless justification can be provided, or alternatively restrict to Air Force supply sources if an internal Air Force requirement is identified. 11. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: As soon as possible. 12. IMPACT: Requires DAASC conversion functionality for this data element (unit price of requisitioned item) to support the implementation of Air Force DLMS. As indicated above, DLMSO is proposing that the conversion be limited to perpetuating the unit price on intra-af communication only. 2 Attachment 1

Enclosure 1: DLMS Supplements a. Modify DLMS Supplement 511M : # Location Revision Reason for Change 1 2/PO104/30 Add new DLMS note for data element: Unit Price DLMS Note: 1. For nonreimbursable material (free issue), indicate 0 dollars. 2. Use for nonstandard material to indicate an estimated price. 3. Estimated unit price for nonstandard material is a DLMS enhancement, see introductory note 3a. 4. For intra-air Force, the unit price will be perpetuated to the requisition modifier. 5. Under DLMS, the unit price will be expressed as R9.2. Establishes a new business rule for USAF. Maps to positions 71-80 of the AF requisition modifier/ cancellation/ follow-up for cancellation. (The MILS transaction will only carry 8-digit dollar and 2-digit cents.) 2/PO105/30 Basis of Unit Price Code DLMS Note: Use for nonstandard and nonreimbursable (free issue) material. For nonstandard material, use to identify an estimated unit price. ES Estimated DLMS Note: Use to indicate an estimated unit price for the nonstandard material. NC No Charge DLMS Note: Use to indicate nonreimbursable (free issue) material. UM Price per Unit of Measure DLMS Note: Use for intra-air Force. 1 Enclosure 1

b. Modify DLMS Supplement 869C: # Location Revision Reason for Change 1 2/REF01/105 Add additional qualifier and corresponding DLMS note: PR Price Quote Number. DLMS Note: 1. For intra-air Force, the unit price will be perpetuated to the cancellation and follow-up for cancellation. 2. Under DLMS, the unit price will be expressed as R9.2. Establishes a new business rule for USAF. Maps to positions 74-80 of the AF requisition modifier/ cancellation/ follow-up for cancellation. (The MILS transaction will carry 5-digit dollar and 2-digit cents.) Mapping of the UP to the REF is proposed as best available location. The price data element is not available in this transaction. 2 Enclosure 1

Enclosure 2: DoD 4000.25-1-M, MILSTRIP Insert new footnote 13 and renumber remaining footnotes. AP3.2. APPENDIX 3.2 REQUISITION TYPE REQUISITION BLOCK NUMBER(S) (MANUAL) RECORD POSITION(S) FIELD LEGEND (MECHANICAL) Send to Block A 1 Not Applicable Requisition Is From Block B Not Applicable ENTRY AND INSTRUCTIONS Enter the appropriate in-the-clear name and address corresponding to the RI, if applicable. Enter the appropriate in-the-clear name and address of the requisitioner, if applicable. Document Identifier Block 1 1-3 Enter DI A0_ or AM_. Routing Identifier Block 2 4-6 Enter RI indicating the supply source to which the document is being submitted. Media and Status Block 3 7 Enter the M&S code. Stock Number 2 Blocks 4, 5, 6 8-22 Enter the stock or part number of the item being requisitioned. For subsistence items, enter the type of pack in rp 21. Unit of Issue Block 7 23-24 Enter the unit of issue. Quantity Block 8 25-29 Enter the quantity requisitioned. For ammunition requisitions only (items in FSG 13), enter an M in rp 29 to express in thousands any quantity exceeding 99,999. Example: A quantity of 1,950,000 will be expressed as 1950M (1950 in rp 25-28 and an M in rp 29). Document Number Blocks 9-12 30-43 Enter document number as assigned by the preparing activity. 1 See the AP2 series of appendices for an explanation of the data fields. 2 Requisitions to DRMS (RI S9D) cannot reflect an entry in rp 21-22 other than a DTID number suffix in rp 21, when applicable. 1 Enclosure 2

FIELD LEGEND TYPE REQUISITION BLOCK NUMBER(S) (MANUAL) RECORD POSITION(S) (MECHANICAL) ENTRY AND INSTRUCTIONS Demand 3 Block 13 44 Enter the demand; otherwise, leave blank. Supplementary Address Blocks 14-15 45-50 When applicable, enter the coded SUPADD of the ship-to or bill-to activity; otherwise, leave blank. When coded data is not significant to the supply source (other than an AAC), enter an alphabetic Y in rp 45. Signal Block 16 51 Enter the signal code. Fund Block 17 52-53 Enter the fund code as directed by the Component. Distribution Block 18 54 When applicable, enter the distribution code of the activity to receive status information in addition to the requisitioner or the SUPADD. 55-56 Enter the code as directed by the Components. Project Block 19 57-59 When applicable, enter the appropriate code under Component instructions. Priority Block 20 60-61 Enter priority designator. Required Delivery Date/Required Delivery Period 4 Block 21 62-64 Enter data requirements from AP2.14, as applicable; otherwise, leave blank. Advice Block 22 65-66 Enter advice code to convey instructions to the supply source; otherwise, leave blank. Date of Receipt of Requisition 5, 6, 7 Block 23 67-69 Leave blank. 3 On an Intra-Army basis a suffix code entry is authorized for identification of post-post partial issues of materiel by Army Single Stock Fund Activities. These requisitions will contain Army Edit Action Code IV in rps 74-75. 4 Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL 148. 5 Processing points passing DI AM_ transactions to another supply source for continued processing will enter their RI code in rp 67-69. 6 The Map Support Office Distribution System (MSODS) will enter the MSODS RI Code SD& in A0_ transactions returned to Mapping Agency Automated Distribution Management System (DADMS) (HM8) for processing. This will indicate to DADMS that this is not the initial processing of the requisition (requisition was previously reviewed and forwarded to MSODS, which was unable to fulfill). 2 Enclosure 2

FIELD LEGEND TYPE REQUISITION BLOCK NUMBER(S) (MANUAL) RECORD POSITION(S) (MECHANICAL) ENTRY AND INSTRUCTIONS Blank Block 23 70-80 Leave blank on inter-component requisitions forwarded to the DLA and GSA supply sources. a. This field is optional for intra- 8, 9, 10, 11, 12, 13 Component use. b. This field may be used for internal purposes on retained copies of requisitions. Remarks Blocks L-W This field will be used to convey any additional required information not provided for in the requisition format. GOVERNMENT-FURNISHED MATERIEL REQUISITION ENTRIES. 14 Manufacturer s Directive Number Contract Call Order Number 54-56 If required by the Component contracts, enter the MDN. 69-72 If required by the Component contracts, enter the appropriate contract call order number. Contract Identification 73-80 At the option of the Component, enter the last eight positions of the PIIN in rp 73-80 in lieu of the MDN in rp 54-56. This entry is mandatory if the MDN is not entered in rp 54-56. 7 On an Intra-Army basis a RI code entry is authorized for identification of the storage site related to post-post issues of materiel by Army Single Stock Fund Activities. These post-post requisitions will contain Army Edit Action Code IV in rps 74-75. 8 On Intra-Army requisitions rp 70 will contain the ownership/purpose code and rp 71 will contain the supply condition code of the material post-post issued by Army Single Stock Fund Activities. These post-post requisitions will contain Army Edit Action Code IV in rp 74-75. 9 On Intra-Army basis both post-post and image Single Stock Fund Activity requisitions may contain a management code in rp 72 to facilitate processing. 10 On Intra-Army basis requisitions may contain an Army Edit Action Code in rp 74-75 to indicate the actions required by the receiving system in order to process transactions and direct authorized follow-on actions. This code is meaningful to the Army only and is used on both post-post and image requisitions. 11 On Intra-Army basis requisitions may contain the date generated in rp 77-80. This date is required to accurately process transactions relative to image, post-post and working requisitions submitted by Army Single Stock Fund activities. 12 For Intra-Air Force lateral requisitions, the supply source identified in rp 4-6 is another Air Force base, the Routing Identifier of the requisitioner is identified in rp 73-75, and the Routing Identifier of the DoD Source of Supply is identified in rp 78-80. Refer to PDC 283. 13 For intra-air Force requisition modification, the unit price may be identified in rp71-80. Refer to ADC 263. 14 Procedures to control access to DOD material inventories by defense contractors last reported as not implemented by USA (Retail). Refer to AMCL 1A. 3 Enclosure 2

FIELD LEGEND TYPE REQUISITION BLOCK NUMBER(S) (MANUAL) RECORD POSITION(S) (MECHANICAL) ENTRY AND INSTRUCTIONS MANAGEMENT CONTROL ACTIVITY ENTRIES: Entries Required for Requisitions for Government-Furnished Materiel. 15 Routing Identifier 4-6 Enter the RI code of the supply source. Distribution 54-56 Enter the distribution code of the MCA validating the transaction or the MDN consisting of the MCA s distribution code in rp 54 and two other alpha/numeric characters in rp 55-56. Routing Identifier 74-76 If required by the Component, enter the RI code of the validating MCA in rp 74-76. DEFENSE REUTILIZATION AND MARKETING ENTRIES: Entries Required When Requisitioning a Specific Item From Disposal. 16 Disposal Turn-in Document Number or Excess Report Number 67-80 This entry is optional on DI A01/A0A/A05/A0E requisitions and is mandatory on DI A04/A0D requisitions. If applicable, the DTID suffix will be entered in rp 21. DEFENSE REUTILIZATION AND MARKETING ENTRIES: Entries Required on Requisitions to Disposal When a Specific Item is Not Required. 17 Blank 70 Leave blank. Condition Code 71 Enter lowest acceptable supply condition code under Component criteria furnished to DRMS. See Chapter C2, paragraph C2.21., for requirement. Blank 72-80 Leave blank. 15 See Footnote 6. 16 Procedures, formats, and codes for requisitioning material from disposal last reported as not implemented by DLA. Refer to AMCL 139A. 17 See Footnote 8. 4 Enclosure 2

AP3.7. APPENDIX 3.7 REQUISITION CANCELLATION FIELD LEGEND RECORD POSITION(S) ENTRY AND INSTRUCTIONS Document Identifier 1-3 Enter DI AC_ or AK_. Routing Identifier 4-6 Enter RI for the last known supply source. Media and Status 7 Enter M&S as shown in the original requisition. Stock or Part Number 8-22 Enter the NSN or part number as shown in the requisition or in supply status, when such status has been received. Unit of Issue 23-24 Enter the U/I as shown in the requisition or status. Quantity 25-29 Enter the quantity for which cancellation is requested. For ammunition cancellations only (items in FSG 13), enter an M in rp 29 to express in thousands any quantity exceeding 99,999. Example: A quantity of 1,950,000 will be expressed as 1950M (1950 in rp 25-28 and an M in rp 29). Document Number 30-43 Enter document number of the requisition for which cancellation is requested. Suffix 44 Enter suffix as shown on the supply status, when applicable. Otherwise, enter demand code from the requisition. All Other Fields 1 45-61 Enter data from the requisition or supply status. Date of Preparation 62-64 Enter the ordinal day of preparation. All Other Fields 65-80 Enter data from the requisition or supply status. 2 1 On Intra-Army basis cancellations may contain an Army Edit Action Code in rp 74-75 to indicate the actions required by the receiving system in order to process transactions and direct authorized followon actions. This code is meaningful to the Army only. 2 For intra-air Force requisition cancellation/follow-up for cancellation, the unit price may be identified in rp74-80. Refer to ADC 263. 5 Enclosure 2