ADC 178 

DS 511R Requisition to Support DEPMED Unit Assembly 

1. ORIGINATOR: Defense Logistics Agency (DLA), HQ DLA, Order Fulfillment 

Division, Planning Branch (J-335), DSN 427-2845, commercial telephone number 

703-767-2845. 

2. FUNCTIONAL AREA: Order Fulfillment/Supply. 

3. REFERENCES: SASS Assembly Standard System (SASS) User Handbook, DLAH 

4140.5, VOL I, Part 2, Appendix B-609-615 – C2L to C2S

(http://www.dla.mil/dlaps/dlah/h4140.5/h4140.5.e-guide.htm) 

4. REQUESTED CHANGE:

 a. Title: DS 511R Requisition to Support DEPMED Unit Assembly 

 b. Description of Change: The C2L transaction provides the requisition data to the 

source of supply for DEPMED units which require assembly. Its basic structure mirrors the 

MILSTRIP Requisition, DI Code A0_. It is not currently translated by DOD Automatic 

Addressing System Center (DAASC) into DLMS X12. This ADC requests the DLMS and 

DAASC maps be updated to incorporate the C2L transaction in the DLMS Supplement 511R, 

Requisition. 

 c. Procedures: 

(1) Revise DS 511R, Requisition as follows: 

Location DS 511R Revision Reason Federal 

IC 

Impact

2/ PO102/30 Revise DLMS Note: 

Quantity Ordered 

Federal Note: 1. Must use to identify the requisitioned quantity. 

2. Express as a whole number with no decimal. 

DLMS Note: 1. A field size exceeding 5 positions may not be 

received or understood by the recipient's automated processing 

system. See introductory DLMS note 3d. 

2. If quantity exceeds 20 for DEPMED major assemblies/kitting 

requisition, prepare separate additional requisitions as required. A 

future DLMS enhancement will eliminate the need for this 

restriction. 

Information No 

revision 

required 

(2) Provide infrastructure at DAASC to permit C2L transaction to be captured and 

mapped into the 511R. The format/mapping of the C2L should be the same as the basic A0_ 

requisition. Do not map the Document Sequence Number (77-80) as this data element is not 

required under DLMS. Do not edit at DAAS for quantity restriction above. Format for C2L 

is as follows: 
FIELD FIELD 

LEGEND POSITION(S) EXPLANATION/INSTRUCTIONS 

Document Identifier Code 1-3 Enter DIC C2L. 

Routing Identifier Code 4-6 Enter RIC of the DSC 

 directing the Assembly. 

Blank 7-8 Leave blank. 

Document Number 9-22 Enter the Service, Requisi- 

 tioner date and Serial 

 Number. 

Unit of Issue 23-24 Enter UI of item requisi- 

 tioned. 

Quantity* 25-29 Enter quantity received, 

 preceding significant 

 digits with zeros. If 

 quantity exceeds 20 for 

 Major Assemblies, prepare 

 additional requisitions as 

 required. 

End-Item Stock Number 30-42 Enter NSN of End-Item re- 

 quired. 

Blank 43-44 Leave blank. 

Supplementary Address Code 45-50 Enter the AAC of the SHIP- 

 TO or BILL-TO activity. 

Signal Code 51 Enter applicable code (must 

 be J, K, L, or M). 

Fund Code 52-53 Enter appropriate code as 

 directed by Service. 

Distribution Code 54-56 Enter the code as follows: 

 (54) Enter, when applicable, 

 the alpha/numeric one-posi- 

 tion code of the activity 

 to receive status informa- 

 tion in addition to the 

 requisitioner or the 

 supplementary address. 

 (55-56) Enter codes as directed by 

 the Service. 

Project Code 57-59 Enter, when applicable, the 

 appropriate code IAW Ser- 

 vice instructions. 

Priority 60-61 Enter applicable code. 

Required Delivery Date 62-64 Enter the RDD (DDD) if 

 available. 

Advice Code 65-66 Enter applicable code to 

 convey instructions to the 

 supply source. May be left 
 blank. 

Blank 67-76 Leave blank. 

Document Sequence Number 77-80 Enter 0001. 

 d. Alternatives: None. 

5. REASON FOR CHANGE: 

 a. This ADC is necessary to authorize the DAASC to modify the 511R translation map so 

that all requisitions are in the same format and to ensure the DEPMED C2L requisitions go 

through all the DAASC 511R edit checks. DLA requires this change for immediate 

implementation in BSM release R2.2, scheduled to go live December 2005. 

 b. Future enhancement of this functional process will address consolidation of additional 

trailer 80-column transaction data associated with the end item assembly requisition. This 

approach is feasible at this time due to mixed DLMS/legacy environment. Consolidation 

would require holding transactions at DAAS when transmitted as individual transactions. 

 c. The quantity restriction note is provided to mirror the legacy process and will be 

enforced by the supply source. There is a potential that each kit will be shipped separately 

and therefore a separate MRO with a different suffix for each end item. For example, the 

customer may order 20 kits on one requisition and want one a week for the next twenty 

weeks. The kitting location will then build one a week, and one MRO will be sent for each 

end item with a different suffix. A future DLMS enhancement could eliminate the need for 

the quantity restriction by permitting a two-position suffix. Such a change is not practical 

until all parties are DLMS compliant. 

6. ADVANTAGES/DISADVANTAGES:

 a. Advantages: This change will accomplish the following: 

(1) Facilitate DLA BSM release 2.2 implementation. 

(2) All DLA BSM requisitions will use the DLMS 511R. 

(3) All requisition edits and validations will remain in DAASC. 

 b. Disadvantages: None known. 

7. IMPACT: DLMS Supplement 511R and DAASC translation conversion mapping.