1 of 18

Attachment, ADC 441

ATTACHMENT TO ADC 441

Exception Rules to Accommodate Communication of Ammunition/Ammunition Related

Quantities in Excess of Five Digits

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: PEO EIS LMP, (856) 988-4878

b. Functional POC: HQ JMC (JM&L LCMC), 309 782 6469

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/Logistics

b. Primary/Secondary Functional Process: Order Fulfillment/Requisition Processing

3. REFERENCES:

a. DoD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP) Manual

b. DoD 4000.25-2-M, Military Standard Transaction Reporting and Accounting 

Procedures (MILSTRAP) Manual

c. Joint Ordnance Commanders Group (JOCG) Joint Conventional Ammunition Policies 

and Procedures (JCAPPs)

 d. DLA Logistics Management Standards memorandum dated June 29, 2011 subject: 

PDC 466, Revise Asset Status Report Transactions (DLMS 846I and MILSTRAP DZA) to 

Document Ammunition Systems Use by Agreement of Nine Digit Quantity On-Hand 

MILSTRAP DZA/DLMS 846I) (Supply)

4. BACKGROUND: Substantive revisions subsequent to staffing are highlighted in green.

a. The Single Manager for Conventional Ammunition (SMCA) is the Joint Munitions and 

Lethality Command, which migrated from the Legacy Command Commodity Standard System 

(CCSS) to the Logistics Modernization Program (LMP) in October 2010. All Army-managed 

munitions and Army-stored munitions are handled within LMP. LMP completed its migration 

from MILS to DLMS in 2007 for all applicable transactions. The other systems involved in the 

process are at both the Wholesale level (LMP – Army, Combat Ammunition System (CAS) – Air 

Force, Ordnance Information System – Wholesale (OIS-W) – Navy, and Ordnance Information 

System – Marine Corps (OIS-M) – Marine Corps) and the Retail level (Standard Ammunition 

Accountability System – Modernized (SAAS –MOD) – Army, Combat Ammunition System 

(CAS) – Air Force, Ordnance Information System – Retail (OIS-R) - Marine Corps, Navy and 

Coast Guard). Of these systems, LMP is DLMS compliant, and the remainder transact in DLSS 

80-position legacy formats. SAAS-MOD currently transacts in DLSS format in order to 
2 of 18

Attachment, ADC 441

communicate with National Level Army systems, all of which have been subsumed by LMP, and 

is considering migrating to DLMS format, which would eliminate any impacts to their system. 

Legacy formats for ammunition items only [Federal Supply Group (FSG) 13], authorize the user 

to enter an “M” in the last position of the quantity field to express in thousands any quantity 

exceeding 99,999. Example: A quantity of 1,950,000 would be expressed as 1950M (e.g. 1950 

in record position (rp) 25-28 and an “M” in rp 29). Translation is required to support the 

communication of quantities between DLMS and legacy Defense Logistics Standard System 

(DLSS). 

b. OIS-M, OIS-R, and OIS-W systems are already configured to accept multiple 

documents with different quantities for ammunition as additive, as opposed to updates to the 

statuses, which is the format which these transactions were received from CCSS, which 

transacted in DLSS format, prior to the migration to LMP. Note: This practice is not 

consistent with MILSTRIP, but has been adopted by the identified systems for ammunition. 

SAAS-MOD currently interprets received multiple inbound status documents as duplicates, 

which would be eliminated with the migration to DLMS format as identified above. For 

wholesale processing, CAS does not currently update their inventory balances based on 

MILSTRAP transactions, but instead receives its balances from Worldwide Ammunition

Reporting System – New Technology (WARS-NT). For retail processing, CAS limits customer 

requisitions to fewer than 99,999, eliminating the requirement for residual quantity transactions. 

In all cases, the same business rules have been applied in LMP and no changes to the Legacy 

systems are required to support this change.

c. There are no MILSBILLS transactions associated with this proposal for handling of 

large quantities for ammunition. Ammunition requisitions between the Military Services are free 

issue, so no billing occurs. FMS Ammunition requisitions, while not free issue, generally have 

the funding for the procurement received in advance and no specific billing referencing the 

quantities is passed among systems.

d. Intent of the transaction: Current DLA Transaction Services mapping for quantities 

of ammunition and ammunition related (referred to as ammunition throughout this ADC, 

unless clarification is required for the updating of manuals and ICs) material in excess of 

99,999 is limited to even multiples of 1,000. This greatly limits the ability for systems 

transacting in DLMS format to legacy systems transacting in DLSS formats.

e. Scenario for which the transaction is used: There are three scenarios that comprise 

the scope of this request: (1) requisition of SMCA items, (2) issue of non-SMCA items from 

Army storage depots, and (3) reporting of Adjustment transactions. The procedures are 

documented in reference (c), JCAAP-5 Supply.

(1) Requisition of SMCA Items, as depicted in Figure 2, under section 5.c. below:

(a) Customers submit requisitions (MILSTRIP DLSS A0_/DLMS 511R) to their 

Military Service ICP.
3 of 18

Attachment, ADC 441

(b) Military Service ICPs send requisitions that are to e filled from Military 

Service-owned stock by a referral order (MILSTRIP DLSS A4_/DLMS 511R) to LMP as the 

SMCA.

(c) LMP as the SMCA supply source submits supply status (MILSTRIP DLSS 

AE8/DLMS 870S) to transmit to DLA Transaction Services for distribution to the requisitioner

and others. Upon receipt DLA Transaction Services will convert to the appropriate AE_ and 

make distribution per reference (a). Note that the supply source for ammunition transactions is 

the storage depot being transacted against, not the Inventory Control Points, to identify which 

storage depot the asset balance is being decremented against. Note: This practice is not 

consistent with MILSTRIP, but has been adopted by the identified systems for ammunition. 

(d) LMP as the SMCA selects the source and directs the shipment by issuing a 

Material Release Order internally to the LMP storage activity.

(e) The storage activity within LMP notifies the requiring activity of positive 

supply action by means of an Issue (MILSTRAP DLSS D7_, Component unique BG1/ BG2/ 

DLMS 867I).

(f) LMP as the SMCA supply source prepares a Shipment Status (MILSTRIP 

DLSS AS8/DLMS 856S) to transmit to DLA Transaction Services. Upon receipt DLA 

Transaction Services will convert to the appropriate AS_ and make distribution per reference (a).

Note that the supply source for ammunition transactions is the storage depot being transacted 

against, not the Inventory Control Points, to identify which storage depot the asset balance is 

being decremented against. Note: This practice is not consistent with MILSTRIP, but has been 

adopted by the identified systems for ammunition. Under MILSTRIP/DLMS, the preparation 

of the shipment status may be delegated to the storage activity; however, the ICP is the 

intended “from” activity. To resolve the gap in information in the MILSTRIP format for 

which the LMP practice compensates, the DLMS Shipment Status implemented an additional 

data field to identify the storage activity. For consistency in the DLMS, DLA Logistics 

Management Standards requests LMP review current mapping to ensure both parties are 

identified appropriately and transition to the correct format as soon as feasible.

(2) Issue of non-SMCA Items from Army Storage Depot, as depicted in Figure 3, under 

section 5.c. below:

(a) The owning Military Service ICP prepares the Material Release Order and 

sends it directly to the storage activity (MILSTRIP DLSS A5_/DLMS 940R) within LMP.

(b) The storage activity within LMP notifies the requiring activity of positive 

supply action by means of a Material Release Confirmation (MILSTRIP DLSS AR_, Component 

Unique BG1, BG2/ DLMS 945A).

(c) LMP as the supply source prepares a Shipment Status (MILSTRIP DLSS 

AS8/DLMS 856S) and Supply Status (MILSTRIP DLSS AE8/DLMS 870S) to transmit to DLA 

Transaction Services. Upon receipt DLA Transaction Services will convert to the appropriate 

AS_ or AE_ and make distribution per reference (a). Note that the supply source for ammunition 
4 of 18

Attachment, ADC 441

transactions is the storage depot being transacted against, not the Inventory Control Points, to 

identify which storage depot the asset balance is being decremented against.

(3) Reporting of Adjustment Transactions, as depicted in Figure 4, under section 5.c. 

below: LMP as either the SMCA or storage activity will advise the Military Service ICP as to 

Inventory Adjustments (gains and losses or changes in condition) (MILSTRAP DLSS D8_, D9_, 

DAC, DAD, DAS, Component Unique BG1, BG2/ DLMS 947I).

f. Procedures, transactions, data elements, processing details in use today Note: The 

terminology “separate supply action” used below is interpreted by the submitter to mean 

requiring a separate release order.

(1) MILSTRIP DLSS A4_/DLMS 511R and DLSS AM_/DLMS 511M - Other 

Services utilize legacy systems and business processes that state that all requisitions passed to 

LMP that are in excess of 99,999 will be in quantities evenly divisible by 1,000. This adheres to 

Appendix AP2.6, Unit of Issue and Quantity, paragraph AP2.6.2 which states that if the quantity 

required for ammunition transactions exceeds 99,999, it may be expressed in thousands by 

placing an M in record position 29, and that additional requisition(s) with new document 

number(s) will be prepared and submitted for the remaining balance. No new DLA Transaction 

Services mapping changes are requested for this requirement.

(2) MILSTRIP DLSS AE_/DLMS 870S – Based on availability of stock, despite the 

receipt of an evenly divisible initial requisition, residual quantities would need to be transmitted 

to all applicable activities. Per JCAPP-5, J5.3.1 of reference c, the SMCA Field Operating 

Activity (FOA) will provide accurate and timely information to the Military Services on 

ammunition stored at SMCA sites and for non-SMCA items similar data is provided by the 

storing activity. Reference (a), Appendix AP3.10., Supply Status (Issues from Stock), 

instructions for suffix state to enter suffix applicable to quantity in rp 25-29 when the 

requisitioned quantity is divided into separate supply actions or, when the requisition quantity is 

not divided, leave this field blank. The residual quantities are not the result of a separate supply 

action. Revised DLA Transaction Services mapping changes are requested.

 (3) MILSTRIP DLSS A5_, DZK/DLMS 940R – Material Release Orders submitted for 

Service managed materials follow the same business processes as for DLSS A4_ above, and are 

in evenly divisible quantities. Material Release Orders processed based on receipt of a Passing 

Order for Army managed materials are handled entirely in LMP. Appendix AP3.12, Materiel 

Release Order/Follow-Up for Materiel Release Order / Lateral Redistribution Order instructions 

for suffix state to enter suffix applicable to quantity in rp 25-29 when the requisitioned quantity 

is divided into separate supply actions or, when the requisition quantity is not divided, leave this 

field blank. No new DLA Transaction Services mapping changes are requested.

 (4) MILSTRIP DLSS AR_, AE6, AG_, DZK/DLMS 945A – Both based on the 

availability of stock (DLSS AE_, above) at the storage depot, and to release materials in unit 

pack quantities whenever practical (as supported by Chapter 3, paragraphs C3.16.2.2 and 

C3.16.2.3 (referring to DLSS ARA and ARB, respectively)) residual quantities would need to be 

transmitted to the applicable activities. Appendix AP3.14, Materiel Release Confirmation 

instructions for the Suffix field state to enter suffix contained in rp 44 of the MRO or leave blank 
5 of 18

Attachment, ADC 441

if no code is in rp 44 of the MRO/cancellation request. Additionally, Appendix AP2.8, Demand 

and Suffix Codes, paragraph AP2.8.2.7 states that “Storage and other activities responsible for 

processing transactions containing suffixes will always perpetuate the suffix onto related 

transactions which they generate.” Revised DLA Transaction Services mapping changes are 

requested.

(5) MILSTRIP DLSS AS_/DLMS 856S – Based both on the availability of stock 

(DLSS AE_, above) and requirement to release materials in unit pack quantities (DLSS AR_, 

above), residual quantities would need to be transmitted to all applicable activities. Appendix 

AP3.19, Shipment Status instructions for the Suffix field state to enter suffix contained in rp 44 

of the MRO or leave blank if no code is in rp 44 of the MRO / cancellation request. Revised 

DLA Transaction Services mapping changes are requested.

(6) MILSTRAP DLSS DD_ (Due-In - Procurement Instrument Source), DW_ (PrePositioned Materiel Receipt (PMR) (Other Than Procurement Instrument Source))/DLMS 

527D - These transactions would follow the quantities identified in the DLSS AE_ and AS_ 

above. Additionally, Appendix AP3, Formats Introduction, paragraph AP3.3.1 states that 

Quantities not evenly divisible by thousands will require two transactions. The first transaction 

will reflect the rounded thousands using the M modifier and the second transaction will reflect 

the residual quantity. Further, paragraph AP3.3.3 states that, “When all data elements, other than 

quantity, are identical and the quantity due-in or being adjusted exceeds 99,999 or 9999M (MModifier thousands - and residual quantities are for ammunition; or when all data elements are 

the same, except the condition of materiel, for materiel being received or being adjusted; assign 

consecutive suffix codes in record position 44 beginning with alpha code A in the initial 

transaction; otherwise, leave blank.” In these cases, the quantity would be the only value that 

would be different, hence two transactions, without suffix codes (or with suffix codes of the AS_ 

transaction) would be required. Revised DLA Transaction Services mapping changes are 

requested. DLA Transaction Services mapping changes for DLMS 527D are not a requirement 

for Army and Joint Services ammunition at this time, but are being included in this change for 

consistency. 

(7) MILSTRAP DLSS D7_ (Issue), Component Unique BG1, BG2, DZK/DLMS 867I -

These transactions would follow the quantities identified in the DLSS AR_ above. Revised DLA 

Transaction Services mapping changes are requested, except for BG1, which by definition has a 

quantity of one (1).

(8) MILSTRAP DLSS D4_ (Receipt - Procurement Instrument Source), D6_ (Receipt –

Other Than Procurement Instrument Source), DXA (Receipt Follow-up - Procurement 

Instrument Source), DXB (Receipt Follow-up - Other Than Procurement Instrument Source), 

DXC (Reply To Receipt Follow-up - Procurement Instrument Source), DXD (Reply To Receipt 

Follow-up - Other Than Procurement Instrument Source). Component Unique BG1, BG2, 

DZK/DLMS 527R - These transactions would follow the quantities identified in the DLSS DD_, 

DF_, DU_, or DW_ above. DLA Transaction Services mapping changes are requested, except 

for BG1, which by definition has a quantity of one (1). DLA Transaction Services mapping 

changes for DLSS DX_ are not a requirement for Army and Joint Services ammunition at this 

time, but are being included in this change for consistency.
6 of 18

Attachment, ADC 441

(9) MILSTRAP DLSS Inventory Adjustment Transactions: D8_, D9_, DAC, DAD, 

DAS, Component Unique BG1, BG2, DZK/DLMS 947I – In accordance with paragraph 

AP3.1.3, the quantity would be only value that would be different, hence two transactions, 

without suffix codes would be required. Revised DLA Transaction Services mapping changes 

are requested, except for BG1, which by definition has a quantity of one (1).

(10) MILSTRAP DLSS DZH (Location Reconciliation Request)/DLMS 846R – Due to 

10 digit quantities contained in the DLSS DZH transaction no DLA Transaction Services

mapping changes are requested. NOTE: MILSTRAP Administrator notes that an 

administrative correction is being to DLMS 846R Location Reconciliation Request transaction to 

note the 10 digit quantity field size. The corresponding MILSTRAP DI Code DZH provides fro 

a 10 position quantity field size.

(11) Note that changes for MILSTRAP DLSS DZA (Asset Status)/DLMS 846I will be 

addressed in separate PDC 466 (reference 3d).

5. REQUESTED CHANGE(S):

a. Requested change in detail: This change proposes that DLA Transaction Services 

split large quantities for ammunition communicated via DLMS Transaction into two legacy 80-

record position transactions without creating or changing the suffix code. The split into separate 

transactions is necessary because the legacy format restricts the allowable field length for 

quantities and does not accommodate residual quantities when using the “M” quantity multiplier 

described above. The Defense Automatic Addressing System (DAAS) conversion split from a 

single DLMS transaction into two separate 80-record position legacy transactions will result in 

the maximum allowable quantity on the first transaction and the residual quantity on the 

subsequent transaction produced with like document number/suffix. The legacy systems 

receiving the resulting two transactions will accumulate the identified quantities under existing 

unique ammunition processing rules, rather than interpreting them as duplicate or replacement 

transactions. 

 (1) Revise DLMS to DLSS mappings for DLMS 870S/DLSS AE_; DLMS 945A/ DLSS 

AR_, AE6, AG_, DZK; DLMS 856S/ DLSS AS_; DLMS 527D/ DLSS DD_, DF_, DU_, DW_ ; 

DLMS 867I/ DLSS D7_, BG2, DZK; DLMS 527R/ DLSS D4_, D6_, DX_, BG2, DZK; and 

DLMS 947I/ DLSS D8_, D9_, DAC, DAD, DAS, BG2, DZK. DLSS to DLMS mapping

changes are not required. These changes are only applicable for the following conditions:

(a) Federal Supply Group (FSG) = 13 or Federal Supply Classes (FSC) = 1410, 

1420, 1427, 1440, 5330, 5865, 6818 or 8140.

(b) Identified senders and recipients by DLMS IC follow. Note, per Chapter 

JCAPP-5, J5.3.1 of reference (c), the SMCA FOA will provide accurate and timely information 

to the Military Services on ammunition stored at the SMCA sites and for non-SMCA items 

similar data is provided by the storing activity (i.e. Storage RIC as identified above). To provide 

proper ammunition traceability the storage activity will be the submitter of the transaction where 

ever applicable. DLA Logistics Management Standards notes this deviation from authorized 
7 of 18

Attachment, ADC 441

procedures and this approved change has been updated to ensure DLMS transactions reflect 

appropriate identification of the storage activity and ICP.

(1) 856S - RIC From (N1/2200 Loop: N101=Z4, N103=M4, N106=FR, 

N104=B14; Storage RIC (N1/2200 Loop: N101=SB, N103=M4, N104=A0W, A5R, BAD, BA7, 

BA9, BB1, BB2, BC2, BD2, BKD, BRD, BTD, B13, N38, B47, B51

(2) 870S - RIC From (N1/50 Loop N101=Z4, N103=M4, N106=FR, 

N104=B14; Storage RIC (N1/50 Loop: N101=SB, N103=M4, N104=A0W, A5R, BAD, BA7, 

BA9, BB1, BB2, BC2, BD2, BKD, BRD, BTD, B13, N38, B47, B51

Staffing Note to All Components: In response to the MILSTRIP Administrator’s request to 

determine how to restrict applicability of the conversion process requiring accumulation of 

ammunition quantities reported supply and shipment status, the PDC submitter responded as 

follows:

“We (LMP, JM&LC, Navy and Marine Corps) have discussed this, and we do not believe that it 

is reasonable to restrict these transactions by recipient. The requisitioner or supplementary 

address are the two main addressees in the 856S and 870S, and there could be hundreds or 

thousands of possible activities. What they do have in common (to the best of our knowledge) is 

that the intended recipients of the transactions would be using ammunition specific systems 

(CAS, OIS-R, and SAAS-MOD) that would handle the transactions as depicted by the PDC. We 

further believe that the scope that has already been included in the PDC should be sufficient to 

adequately restrict the translation.”

The MILSTRIP Administrator notes that the restriction for the supply and shipment status apply 

to the originator only, and, therefore, all supply and shipment status applicable to FSG=13 or 

FSC = 1410, 1420, 1427, 1440, 5330, 5865, 6818 or 8140 prepared by LMP using ICP RIC B14 

and Storage RIC A0W, A5R, BAD, BA7, BA9, BB1, BB2, BC2, BD2, BKD, BRD, BTD, B13, N38, 

B47, or B51will be subject to DAAS conversion resulting in both the allowable MILSTRIP 

quantity and the separate residual quantity balance being reported on the same document 

number/suffix. The DLA Logistics Management Standards cannot verify that all ammunition 

requisitioners are supported by the systems identified above; therefore, specific concurrence 

with this portion of the proposal must be noted in the Components consolidated PDC response

(indicate concur/non-concur with availability of systems support for accumulation of supply and 

shipment status quantities). Refer to Enclosure for staffing response and comment resolution.

(3) 527D - RIC From (N1/70 Loop: N101=KA, N103=M4, N106=FR, 

N104=B14)

(4) 527R - RIC From: (N1/070 Loop: N101=RC, N103=M4, N106=FR, 

N104=B14); RIC To: (N1/210 Loop: N101=Z4, N103=M4, N106=TO, N104=MHQ, NCB, FG5, 

FL5, FGZ, FLZ)

(5) 867I - RIC From (N1/80 Loop: N101=SB, N103=M4, N106=FR, 

N194= A0W, A5R, BAD, BA7, BA9, BB1, BB2, BC2, BD2, BKD, BRD, BTD, B13, N38, B47, 

B51) ); RIC To (N1/50 Loop: N101=Z4, N103=M4, N106=TO, N104=MHQ, NCB, FG5, FL5, 

FGZ, FLZ)
8 of 18

Attachment, ADC 441

(6) 947I – RIC From (N1/0400 Loop: N101=SB, N103=M4, N106=FR, 

N104= A0W, A5R, BAD, BA7, BA9, BB1, BB2, BC2, BD2, BKD, BRD, BTD, B13, N38, B47, 

B51); RIC To (N1/1100 Loop: N101=Z4, N103=M4, N106=TO, N104=MHQ, NCB, FG5, FL5, 

FGZ, FLZ)

(7) 945A: RIC From (N1/40 Loop: N101=SB, N103=M4, N106=FR, 

N104=A0W, A5R, BAD, BA7, BA9, BB1, BB2, BC2, BD2, BKD, BRD, BTD, B13, N38, B47, 

B51); RIC To (N1/80 Loop: N101=Z4, N103=M4, N106=TO, N104=MHQ, NCB, FG5, FL5, 

FGZ, FLZ)

 (c) The description of the Routing Identifier Codes by purpose and system is 

below:

(1) Inventory Control Points:

a) B14 - Joint Munitions and Lethality Command (JM&LC) 

(LMP). Note that this RIC is shared with the Tank-Automotive and Armaments Command 

(TACOM), but for the purposes of this change, it refers to JM&LC

b) FG5, CBSG GACP Hill AFB; FGZ, Depot Storage Hill AFB; 

FL5, Letterkenny Munitions; FLZ, Warner Robbins Air Logistics Center (CAS)

c) MHQ - Program Manager for Ammunition, Marine Corps 

Systems Command (OIS-M)

d) NCB - Naval Operational Logistics Support Center Ammo 

(OIS-W)

(2) Storage Activities (all LMP):

a) A0W Tobyhanna Army Depot

b) A5R Blue Grass Ammunition Depot

c) BAD Anniston Munitions Center

d) BA7 Radford Army Ammunition Plant

e) BA9 Pine Bluff Munitions Center

f) BB1 Holston Army Ammunition Plant

g) BB2 Crane Ammunition Depot

h) BC2 McAlester Ammunition Plant

i) BD2 Hawthore Ammunition Depot
9 of 18

Attachment, ADC 441

j) BKD Letterkenny Munitions Center

k) BRD Red River Munitions Center

l) BTD Tooele Army Depot

 m) B13 Iowa Army Ammunition Plant

n) B38 Lake City Army Ammunition Plant

o) B47 Blue Grass Ammunition Depot

p) B51 Milan Army Ammunition Plant

 (2) For transactions containing ammunition items in Federal Supply Group 13, or 

Federal Supply Classes 1410, 1420, 1427, 1440, 5330, 5865, 6818 or 8140, where quantities 

exceed 99,999, perpetuate the Document Number and Suffix (if present) from the DLMS format 

into two DLSS transactions when the quantity is not evenly divisible by thousands. The first 

transaction would reflect the rounded thousands using the M modifier and the second transaction 

would reflect the residual quantity. All values would be identical between the two transactions 

with the exception of the quantity. This would also apply if a suffix code was already in use, and 

the suffix code would be perpetuated onto the second transaction.

 (3) This is depicted in Figure 1, below.

Figure 1: Proposed DLMS to MILS Mapping

 (4) The rationale for this change is that DLA Transaction Services currently has the 

capability to identify transactions with ammunition items that contain residual quantities, as 

evidenced by the logic to insert a decimal point to indicate that a residual quantity exists. 

Additionally, DLMS to DLSS mappings exist where a single DLMS message is mapped to 

multiple DLSS transactions. Examples include the 511R mapping to A0E and YRZ (as 

approved in ADC 69 and ADC 69A), and the 527R, 846R, 867I, 947I mappings to the 

corresponding DLSS transactions and BG1 and BG2 (as approved in ADC261 and ADC 283).

 (5) Procedures for DLA Transaction Services handling of large quantities where 

the legacy trading partner is not identified as a participating trading partner. The proposed 

new process will allow the larger quantities to process between the designated trading partners. 
10 of 18

Attachment, ADC 441

However, if other non-DLMS trading partners are identified as the intended recipient, the DLMS 

transaction will be rejected and the originator will be notified using the DLMS 824 transaction. 

There will no longer be any transactions passing to customers that contain a decimal point in the 

quantity field. The DLMS trading partner receiving the DLMS 824 rejection notice will need to 

research the processing capabilities of the intended recipient to determine if that activity can 

process MILSTRIP transactions as cumulative and should be added to the participating trading 

partners. If not, manual intervention may be needed to reduce the quantity transmitted to even 

multiples of 1,000, and/or to contact the designated recipient to ensure that the appropriate 

quantity is recorded.

b. Proposed procedures: 

 (1) Revise DoD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Chapter C4, Status, Appendix AP3.10, and Appendix 3.19 to incorporate the 

following clarification of procedures which deviate from standard MILSTRIP practice:

(a) Add new subparagraph C4.8.9 to read: “Intra-Service ammunition and 

ammunition related orders utilize the storage depot being transacted against instead of the 

Inventory Control Point when providing supply and shipment status in order to maintain 

traceability of ammunition and ammunition related items shipped.

1

_________________

1 Refer to ADC 441, Exception Rules to Accommodate Communication of

Ammunition/Ammunition Related Quantities in Excess of Five Digits.

(b) Insert new footnote in AP3.10 and 3.19 associated with “Routing Identifier”:

FIELD LEGEND RECORD POSTION(S) ENTRY AND INSTRUCTIONS

Routing Identifier 1 1-3 Enter the RI of the supply 

source.... __________________

1 “Intra-Service ammunition and ammunition related orders utilize the storage depot being 

transacted against instead of the Inventory Control Point when providing supply and shipment 

status in order to maintain traceability of ammunition and ammunition related items shipped. 

Refer to ADC 441, Exception Rules to Accommodate Communication of 

Ammunition/Ammunition Related Quantities in Excess of Five Digits.

 (2) Revise DoD 4000.25-1-M Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Appendix AP2.6, Unit of Issue and Quantity to incorporate the following:

“AP2.6.3. Exception rule for ammunition and ammunition related FSG 13 and FSC 

1410, 1420, 1427, 1440, 5330, 5865, 6818 or 8140: By trading partner agreement and by 

coordination with DLA Transaction Services, an exception rule is available for 

communicating larger quantities. This rule is only applicable when the initiating system is 

DLMS compliant (and supports larger quantities) and the receiving system is using legacy 

MILSTRIP. Under this rule, when the quantity exceeds 99,999, the DLA Transaction 

Services transaction conversion from DLMS to legacy format will transmit the initial 
11 of 18

Attachment, ADC 441

quantity using the standard configuration of using the qualifier “M” in rp 29 to represent 

thousands. The residual quantity from the DLMS transaction will be transmitted 

separately using the original document number and original/blank suffix code. The legacy 

trading partner system will be responsible for accumulating the quantities transmitted 

separately (rather than superseding or rejecting as duplicate transactions).1

”

------------------------

1 Refer to ADC 441, Exception Rules to Accommodate Communication of 

Ammunition/Ammunition Related Quantities in Excess of Five Digits

 (3) Revise DoD 4000.25-1-M, Appendix AP3.1 to add the following paragraph. This 

will align the MILSTRIP and MILSTRAP business rules:

“AP3.1.3. Special Explanation/Instruction. 

AP3.1.3.1 For ammunition and ammunition related items in Federal Supply Group 

Federal Supply Classes 1410, 1420, 1427, 1440, 5330, 5865, 6818 or 8140, quantities 

exceeding 99,999 may be expressed in thousands by placing an M in record position 29. 

Example: A quantity of 1,950,000 would be expressed as 1950M (1950 in record positions 

25-28 and an M in record position 29). Quantities not evenly divisible by thousands will 

require two transactions. The first transaction will reflect the rounded thousands using 

the M modifier and the second transaction will reflect the residual quantity: e.g., for a 

quantity of 100,001, the first document will reflect a quantity of 0100M and the second 

document will reflect a quantity of 00001.

AP3.1.3.2. Exception rule for ammunition and ammunition related FSG 13 and FSC 

1410, 1420, 1427, 1440, 5330, 5865, 6818 or 8140: By trading partner agreement and by 

coordination with DLA Transaction Services, an exception rule is available for 

communicating larger quantities in identified transactions. This rule is only applicable 

when the initiating system is DLMS compliant (and supports larger quantities) and the 

receiving system is using legacy MILSTRIP. Under this rule, when the quantity exceeds 

99,999, the DLA Transaction Services transaction conversion from DLMS to legacy 

format will transmit the initial quantity using the standard configuration using the 

qualifier “M” in rp 29 to represent thousands. The residual quantity from the DLMS 

transaction will be transmitted separately using the original document number and 

original/blank suffix code. The legacy trading partner system will be responsible for 

accumulating the quantities transmitted separately (rather than superseding or rejecting as 

duplicate transactions). 1

------------------------

1 Refer to ADC 441, Exception Rules to Accommodate Communication of 

Ammunition/Ammunition Related Quantities in Excess of Five Digits”

 (4) Revise DoD 4000.25-1-M, Appendices AP3.10 Supply Status (Issues From Stock),

AP3.12., Materiel Release Order/Follow-Up For Materiel Release Order/Lateral Redistribution 

Order , AP3.14, Materiel Release Confirmation, and AP3.19, Shipment Status to add the 

following footnote to the entry and instructions for Quantity:

“See Appendix AP3.1 - Formats Introduction, Paragraph AP3.1.3.”
12 of 18

Attachment, ADC 441

(5) Revise DoD 4000.25-1-M, MILSTIP, Appendix 3 “Entry and Instructions” to 

include additional FSCs applicable to ammunition quantity use of the M modifier as follows:

(a) AP3.2: Revise to read selected text to read: “Enter the quantity requisitioned. 

For ammunition and ammunition related requisitions only (items in FSG 13) and for FSC 1410, 

1420, 1427, 1440, 5330, 5865, 6818 or 8140) 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 rep 25-28 and an “M” in rp 29).

(b) Revise the following appendices to make comparable change to insert “and 

FSC 1410, 1420, 1427, 1440, 5330, 5865, 6818 or 8140” : AP3.3, AP3.7, AP3.8, AP3.9, 

AP3.10, AP3.11, AP3.12, AP3.14, AP3.16, AP3.17, AP3.18, AP3.19, AP3.22, AP3.24, AP3.25, 

AP3.26, AP3.29, AP3.31, AP3.33, AP3.34, AP3.35, AP3.36, AP3.38, AP3.39, AP3.40, AP3.42, 

AP3.47, AP3.55.

(6) Revise DLMS Supplements and DLA Transaction Services Mappings 856S and 

870S as follows:

Item 

#

Location Revision to 

856S, Shipment Status

Reason

1. DLMS 

Introductory 

Note

Added ADC 441 to DLMS Introductory note 3.

- ADC 441, Exception Rules to Accommodate Communication 

of Ammunition/Ammunition Related Quantities in Excess of 

Five Digits (Supply/MILSTRIP/MILSTRAP)

To identify DLMS 

changes included 

in the DS.

2. 2/N101/2200 Add DLMS Note 6 to existing qualifier ‘SB – Storage Area’:

6. When implemented as a DLMS enhancement to allow 

specific separate identification of Owning Inventory 

Control Point and Storage Activity RIC for ammunition

and ammunition related transactions, the storage activity 

may be the actual initiator of the status on behalf of the 

ICP identified at 1/N101/50 Code Z4 (N106=FR). A second 

instance of the SB must be used to identify the storage 

activity by DoDAAC. Refer to ADC 441.

To extend the 

existing logic to 

include all 

ammunition 

transactions

Field Legend DLSS

Position

Conditions Revision to

AS_ Mapping

856S

Position/Loop

Storage Activity 4 – 6 If Position 1-2 of LIN05=13 

or Positions 1-4 of 

LIN05=1410, 1420, 1427, 

1440, 5330, 5865, 6818 or

8140, when LIN04=FS 

AND

N104 = RP 4-6 2/N1/2200
13 of 18

Attachment, ADC 441

Field Legend DLSS

Position

Conditions Revision to

AS_ Mapping

856S

Position/Loop

N101=SB 

N103=M4 

N106=FR

Item 

#

Location Revision to 

870S, Supply Status

Reason

1. DLMS 

Introductory 

Note

Added ADC 441 to DLMS Introductory note 4.

- ADC 441, Exception Rules to Accommodate Communication 

of Ammunition/Ammunition Related Quantities in Excess of 

Five Digits (Supply/MILSTRIP/MILSTRAP)

To identify DLMS 

changes included 

in the DS.

2. 2/N101/90 Add qualifier ‘SB – Storage Area’:

DLMS Note:

1. Use to identify the storage activity applicable to the 

status provided.

2. When implemented as a DLMS enhancement to allow 

specific separate identification of Owning Inventory 

Control Point and Storage Activity RIC for and 

ammunition related transactions, the storage activity may 

be the actual initiator of the status on behalf of the ICP 

identified at 1/N101/50 Code Z4 (N106=FR). Refer to ADC 

441.

To extend the 

existing logic to 

include all 

ammunition 

transactions

Field Legend DLSS

Position

Conditions Revision to

AS_ Mapping

870S

Position/Loop

Storage Activity 4 – 6 If Position 1-2 of LIN05=13

or Positions 1-4 of 

LIN05=1410, 1420, 1427, 

1440, 5330, 5865, 6818 or

8140, when LIN04=FS

AND

N101=SB

N103=M4

N106=FR

N104 = RP 4-6 2/N101/90

(7) Revise DLMS Supplements 846R to make an administrative correction as follows:

Item 

#

Location DS 846R Revision Reason

1. DLMS 

Introductory 

Add ADC 441 to DLMS Introductory Note 6:

- ADC 441, Exception Rules to Accommodate 

Identifies DLMS 

Changes included in 
14 of 18

Attachment, ADC 441

Notes Communication of Ammunition/Ammunition Related

Quantities in Excess of Five Digits 

(Supply/MILSTRIP/ MILSTRAP) (Supply)

the DS.

2. 2/QTY02/320 Delete current DLMS note and replace with new 

note:

Quantity 

DLMS Note: A field size exceeding 5 positions (seven 

for FSG 13, ammunition) may not be received or 

understood by recipient's automated processing 

system. See introductory DLMS note 4d.

DLMS Note: Quantity field size in the Location 

Reconciliation Request Transaction is 10 positions. 

Corresponding MILSTRAP DZH transaction 

provides for a 10 position quantity field.

Administrative 

update to correct 

quantity field size to 

reflect existing 

MILSTRAP 

Document Identifier 

Code DZH field size. 

Quantity field in DI 

Code DZH is record 

position 25-34 (10 

positions).
15 of 18

Attachment, ADC 441

c. Proposed transaction flow: 

Figure 2: Requisition of SMCA Items

Figure 3: Requisition of Non-SMCA Items
16 of 18

Attachment, ADC 441

Figure 4: Reporting of Adjustment Transactions

 d. Alternatives: Systems migrating to DLMS would be required to continue to follow the 

limitations and processes of the legacy DLSS processes.

6. REASON FOR CHANGE: Documents and incorporates DLSS and DLMS requirements 

to support the Ammunition processing between the Army and Air Force, Marine Corps and 

Navy; and to facilitate ammunition accountability.

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages (tangible/intangible) Supports DLMS migration efforts across DoD to be 

able to accurately communicate with non-DLMS systems while allowing the DLMS systems to 

reduce the number of transactions and more fully align with DLMS capabilities. If this change 

were not implemented, the other alternative would be for major revisions to several common 

interfaces in LMP, and revisions to Legacy systems, which would require an as yet unknown 

time and cost. Lack of resolution would result in inaccurate inventory accountability balances 

for munitions.

b. Disadvantages: Extremely large scale changes to DLA Transaction Services maps. 

Increased processing logic required for DLA Transaction Services to perform quantity 

conversions. This process deviates from standards documented procedures, but the DLMS 

changes included in this document, if adopted, would align the process with the regulations.
17 of 18

Attachment, ADC 441

8. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT: 

a. Trading partner systems are either DLMS compliant for the affected transactions, or are 

already configured to accept multiple DLSS documents with different quantities for ammunition 

as additive, as opposed to updates to the statuses. 

b. DLMS compliant systems shall be required to support larger quantities in accordance 

with DLMS Supplements. 

c. PDC 467 identification of ammunition by FSG 13 was not all inclusive and was revised 

to include FSG 1410, 1420, 1427, 1440, 5330, 5865, 6818 or 8140. As requirements evolve, it 

may be necessary to expand the criteria to allow additional ammunition items to fall under the 

processing procedures defined in this change. 

d. Additional trading partners may be identified subsequent to implementation of this 

process. The Army lead will be responsible for ensuring that DLA Transaction Services and 

DLA Logistics Management Standards are notified so that updates may be made to the 

conversion processing criteria. Re-coordination using the proposed DLMS change process will 

not be required to apply these rules to additional ammunition trading partners. 

9. NOTE ANY REGULATIONS OR GUIDANCE: Modify DoD 4000.25-1-M and DoD 

4000.25-2-M as identified in this document. 

10. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Implementation is 

requested as soon a possible to ensure ammunition inventory accountability is maintained 

through the Joint Services. 

11. IMPACT:

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: The DLMS field length for quantity is currently 

defaulted to the X12 standard, which is 15 positions, where no specific alternative length has 

been defined (e.g., the Supply Discrepancy Report using DLMS 842A defines the quantity as 7 

positions). Although the original proposal indicated a desire to establish a maximum field length 

based upon requirements rather than X12, Components were primarily concerned that the length 

accommodate current use and no revision to the DLMS is necessary at this time. 

c. Integrated Data Environment (IDE)/Global Transportation Network (GTN) 

Convergence (IGC). Requires review to assess impact due to larger quantity fields in DLMS, 

and possibly for understanding that one DLMS transaction may equate to two legacy 

transactions. 

d. DLA Transaction Services: 

(1) Requires revisions to DLMS to DLSS legacy format conversion for larger 

quantities as specified above. 
18 of 18

Attachment, ADC 441

(2) Requires DAAS mapping update to populate the storage activity as the Routing 

Identifier-From on the MILSTRIP Supply and Shipment Status.

(3) DLMS to DLMS exchange of larger quantities must be supported (may impact 

internal transaction handling within DLA Transaction Services Micro Automated Routing 

System (DMARS)).

(4) WebVLIPS must support larger quantities transmitted under DLMS on summary 

screens.

e. Army LMP

(1) Implement expanded field length as described above. Coordinated testing with 

DLA Transaction Services is required.

(2) Requires update to populate the Inventory Control Point as the transaction initiator 

on the DLMS Supply and Shipment Status and separately identify the applicable storage activity.
Page 1, Enclosure, ADC 467

Enclosure, Staffing Response and Comment Resolution

Originator Response/Comment Disposition

1. Navy Concur Noted.

2. Navy, 

Ammunition 

Sentencing 

Program Manager

The Navy Ordnance Information System is

applying the M multiplier for FSC 5865. In 

addition the following FSC also reflected 

occurrences of the M multiplier being used: 

5330(packaging), 6818(chemical),

8140(Ammo Container/box).

Noted. ADC has been updated 

to include, 5330, 5865, 6818 and

8140. As FSC 5330, 6818 and 

8140 are not Ammunition, but 

are related to Ammunition 

functionality and is required by 

the Services, the title of this 

ADC will be amended to read 

“Ammunition/Ammunitionrelated Quantities”.

Additionally, comments received 

from the USMC under PDC 466 

requested the addition of FSCs 

1410, 1420, 1427, 1440, and 

8140, which are included here 

for consistency. USN and USAF 

were polled for the acceptability 

of inclusion of these FSCs and 

raised no objections.

3. Marine Corps Concur with comments:

1. Staffing Notes on p 5/6:

a. Preference is to apply across all users of 

FSG=13

1.a. The only additional 

qualifier identified is FSC = 

5865, which has been added 

where applicable with FSC = 13. 

Comments received from the 

USMC under PDC 466 

requested the addition of FSCs 

1410, 1420, 1427, 1440, and 8140, 

which are included here for 

consistency. USN and USAF were 

polled for the acceptability of 

inclusion of these FSCs and raised 

no objections.

USN later requested inclusion of 

FSCs 5330, 5865 and 6818, which 

were also agreed upon by all 

services.

1.b. Comments have been 
Page 2, Enclosure, ADC 467

Originator Response/Comment Disposition

b. Additional RICs be added to include all 

LMP storage activities as listed in para 

5.a.c.2 for shipment and supply status.

c. Distribution of shipment and supply 

status be made per ref (a).

2. Staffing Note on p 6:

a. Concur with availability of systems 

support for accumulation of supply and 

shipment status for all USMC stakeholders.

3. Staffing Note on p 14:

a. HQMC has no preference for maximum 

length of quantity fields. Minimum should 

not be less than 9 positions for FSG=13 

items.

4. General Comment

a. The DLSS DZH does not require 

quantity conversion to include the ‘M’ 

quantifier and the current DLMS 846R is 

being translated correctly because the DLSS 

DZH supports 10 positions for the quantity 

field. Thus no translation is required or 

desired by HQMC.

i. Recommendation to remove all 

references to the DLSS DZH / DLMS 846R 

in this PDC because it is not applicable.

5. Para 4.f.2 & 4.f.5

a. Both DLSS AE_/DLMS 870S and 

DLSS AS_/DLMS 856S (para 4.f.2 and 

4.f.5) state that “residual quantities would 

need to be transmitted to the requisitioner”.

i. If this PDC is enacted as written, then 

we would receive status on only MMHQ50 

document numbers.

ii. Recommendation to change text to 

read “residual quantities would need to be 

transmitted to all applicable activities”.

6. Para 4.e

a. Ref (c) will require revision to reflect 

the changes made based on SMCA’s 

included where identified in 

specific paragraphs, and is 

reflected in new para 5.b.1

1.c. See response to 1.b.

2.a. Noted

3.a. Noted.

4.a. Concur. References to 

changes to DZH have been 

removed, but DZH has been 

included in the business process 

flow for consistency.

5.a. Concur. Changes made. 

Similar changes have been made 

in paragraphs 4.e.1.c and 4.e.1.f 

for SMCA items and paragraphs 

4.e.2.c. for non-SMCA items.

6.a. Noted. This qualifying 

statement has been added to 

paragraph 4.e. for clarity.
Page 3, Enclosure, ADC 467

Originator Response/Comment Disposition

transition from CDSS/SDS to LMP. Para 4.e 

of the PDC references the procedures 

documented in Chapter 7 of ref (c). 

However, this reference is based on internal 

SMCA processes when CDSS and SDS were 

in service and not what LMP is doing today.

7. Para 4.e.1.f

a. Recommend change to read “LMP as 

the SMCA supply source prepares a 

shipment status (DLSS AS8/DLMS 856S) to 

transmit to DLA Transaction Services. Upon 

receipt, DLA Transaction Services will 

convert to the appropriate AS_ and make

distribution per ref (a).

i. Justification – the original text states 

“to be sent to the requisitioner”. This is in 

conflict with ref (a) and if enacted as written, 

the only status received would be those that 

were for MMHQ50 document numbers.

8. Para 4.e.2

a. Recommend adding a para 4.e.2.c 

which states that “LMP as the supply source 

prepares shipment and supply status 

transactions to transmit to DLA TS.

i. Justification – supply and shipment 

status are requirements but were omitted 

from this section.

9. Para 4.f.2

a. Recommend change “transmitted to the 

requisitioner” to read “transmitted to the 

applicable activities”.

10. Para 4.f.4

a. Recommend change “at the storage 

dept, and the requirement to release materials 

in the unit pack quantities” to read “at the 

storage depot, and to release materials in the 

unit pack quantities whenever practical”

i. Justification – there is no 

‘requirement’ to release to the nearest unit 

pack; but it is allowable under certain 

circumstances (ch 7 of ref (c)).

7.a. Concur. Changes made.

8.a. Concur. Changes made.

9.a. Concur. Changes made.

10.a. Concur. Changes made.

10.b. Concur. Changes made.
Page 4, Enclosure, ADC 467

Originator Response/Comment Disposition

b. Recommend change “transmitted to 

requisitioner” to read transmitted to the 

applicable activities”.

11. Para 4.f.10

a. Recommend delete this entirely.

i. Justification – do not need to revise 

DLA TS mapping for DLSS DZH/DLMS 

846R (DZH currently allows quantities in 

excess of 5 digits).

12. Para 5.a.1

a. Recommend change “DLSS 

876I/DLSS D7_” to read “DLMS 

876I/DLSS D7_”

13. Para 5.a.1.b.1

a. Recommend add ‘RIC from’ for all of 

the LMP associated storage activity RICS (as 

documented in para 5.a.1.c.2).

14. Para 5.a.1.b.2

a. Recommend add ‘RIC from’ for all of 

the LMP associated storage activity RICS (as 

documented in para 5.a.1.c.2).

15. Para 5.b.4

a. Recommend delete in its entirety. DZH 

quantity currently has 10 record position for 

the quantity field. Thus no translation is 

required or desired.

11.a. Non-concur. The 

paragraph is being included for 

consistency of depicting the 

business processes, but has been 

revised to indicate that no 

mapping changes are required.

12.a. Concur. Changes made.

13.a. Concur. Changes made. 

With the guidance of DLA 

Logistics Management 

Standards, changes to the DLMS 

IC for 856S and 870S have been 

added to specify the use of two 

iterations of the N1 segment for 

Owning ICP and Storage 

Activity in new paragraph 5.b.5.

14.a. Concur. See response for 

13.a.

15.a. Concur. Changes made.

4. Army CASCOM Concur with comments:

1. There is no projected impact to GCSSArmy since it will not be required to process 

Class V transactions of the types indicated 

and since it can be considered DLMS 

compliant when transacting with information 

trading partners that are also using DLMS.

1. Noted
Page 5, Enclosure, ADC 467

Originator Response/Comment Disposition

2. In regards to paragraph 4.a. 

(Background), and the statement, "the 

remainder (to include SAAS-MOD) transact 

in DLSS 80-position legacy formats." 

SAAS-MOD actually communicates 

internally (SAAS to SAAS) using a 500-

position transaction record (468 are in use 

and 32 remain unused) referred to as 

Logistics Modernization Program (LMP) 

format developed several years ago in 

anticipation of the fielding of a national level 

enterprise system but is currently only used 

for reporting to WARS-NT.

SAAS-MOD transacts today to/from the 

national level systems in DLSS only because 

of the compatibility limitations that existed 

within the CCSS/SDS environment that 

existed at the time SAAS was incorporating 

the LMP format.

It is possible and desirable that

SAAS-MOD could communicate 

transactional data using DLMS and will seek 

implementation guidance. Implementing 

would negate the need for DAAS to convert 

transactions moving to/from SAAS systems, 

eliminate the exception data problem, and 

would eliminate the residual risk of 

processing errors (misinterpretation of an 

actual status change, etc.) associated with 

this PDC.

Note that the SAAS-MOD LMP format is 

not DLMS or DLMS compliant and would 

require a level of effort to complete a 

conversion.

3. Reference PDC 467, paragraphs 4.b., 5.a., 

5.b.: SAAS-MOD will indeed be impacted 

when receiving multiple inbound documents 

(status or Advance Shipping Notice) without 

a suffix that it must treat as additive as this 

PDC would dictate. SAAS-Mod treats the 

second and sequent transactions as 

duplicates. This would require a change to 

SAAS-Mod to accommodate this situation. 

However the actual receipt will process 

2. Army LMP is interpreting this 

comment to mean that SAASMOD currently transacts with 

external systems. A comment 

has been added to paragraph 4.a. 

to accurately reflect the SAASMOD operating environment, 

and the intention to migrate to 

DLMS format.

3. A comment has been added to 

paragraph 4.b. to accurately 

reflect the SAAS-MOD 

operating environment, and the 

intention to migrate to DLMS 

format. It is believed that this 

comments covers the content 

referenced in paragraphs 5.a. and 

5.b.
Page 6, Enclosure, ADC 467

Originator Response/Comment Disposition

without difficulty and the MMC will process 

the remaining quantities as Receipts Not Due 

In.

4. Reference PDC 467, paragraph 8.a.: 

SAAS-Mod does not process any additive or 

cumulative transactions. Only the original 

transaction is posted, all others are treated as 

duplicate records.

5. The PDC 467 originator should consider 

including the D6_, DR_ and other Document 

Identifier Codes (DIC) that are used to report 

receipt acknowledgment by all users of the 

listed DLSS transacting systems. It is 

possible for any receiving activity to process 

a receipt in excess of 99,999. The D6_ and 

DR_ transactions will carry the same "M" 

qualifier for multiples of 1000. The 

additional amount is rolled up or down just 

as the A0_. The same loss of fidelity of the 

so-called residual quantity will exist. This 

PDC's recommended processing logic, 

applied in reverse (the DLSS system creates 

two transactions with blank/same suffix and 

DAAS adds them) would eliminate this 

potential.

6. Reference PDC 467, paragraph 11.a.: 

CASCOM's preference for a maximum 

DLMS Data element field length for quantity 

is 8 positions. 8 positions facilitates 

quantities up to but not including 100 million 

which far exceeds any expected transactional 

quantity even when dealing with class V 

small arms. 7 positions (as mentioned in the 

PDC regarding the DLMS 842A) would 

most likely be adequate but 8 positions all 

but provides a guarantee.

4. It is believed that the 

comments added in response to 

items 2 and 3 above cover this 

requirement.

5. D6_ is included in the PDC is 

several locations. As this 

situation is specific to a DLMS 

to MILS conversion of the 

quantities, Army LMP is the 

only Ammunition National 

Level system that is currently 

transacting in DLMS, and the 

business process does not require 

the receipt of a DRA/DRF, nor 

the transmission of a DRB.

6. Noted.

5. Air Force Concur with PDC 467. Noted.

6. DLA DLA concurs without comment. Noted.

7. DSCA 

(Navy FMS)

On page 2 of the subject PDC, it says, "There 

are no MILSBILLS transactions associated 

with this proposal for handling of large 

quantities for ammunition. All ammunition is 

Concur. Changes made to 

paragraph 4.c. to reflect this.
Page 7, Enclosure, ADC 467

Originator Response/Comment Disposition

provided "free issue" to the Military 

Services." Obviously, this is not true for 

FMS, as the customers must be billed for all 

ammunition quantities. In most instances the 

applicable FMS orders are billed via a 

funding document that we receive on the 

monthly DCAS file. Since the DCAS file 

does not have quantities on it, this is not an 

issue. However, there are some instances in 

which we receive interfund bills for 

ammunition orders with quantities on them. 

We are curious to know if interfund bills 

with quantities over 99,999 will contain a 

"M" in the last position of the quantity field.

Regardless, MISIL has logic on both the 

logistic and financial sides to recognize the 

"M" coding in the quantity field. As a result, 

we do not believe this PDC will impact 

MISIL.

This PDC makes no changes to 

the interfund billing processes 

and procedures as depicted in the 

MILSBILLS Manual, DoD 

4000.25-7-M

8. DSCA 

(Army FMS)

Concur with comments:

Para 5.a. Concur with the process described 

to have "The Defense Automatic Addressing 

System (DAAS) conversion split from a 

single DLMS transaction into two separate 

80-record position legacy transactions will 

result in the maximum allowable quantity on 

the first transaction and the residual quantity 

on the subsequent transaction produced with 

like document number/suffix."

Para 5.a.(1)(b) Need USASAC's RIC of 

BY7 added to the list of senders and 

receivers.

Noted.

The sending RICs listed in this 

PDC are either LMP ICPs or 

Storage Activities, and the 

receiving RICs are Other Service 

Ammunition ICP’s. USASAC 

RIC is neither of these types of 

activities. The only way that this 

could be provided is use the 

USASAC RIC as the Party to 

Receive Copy (856S: N1/2200 –

N101 = Z1; 870S: N1/90: N101 

= Z1). This functionality is not 

currently developed in LMP and 
Page 8, Enclosure, ADC 467

Originator Response/Comment Disposition

Para 5.a.(1), Page 6, Staffing note, USASAC 

does not use the systems listed however our 

management process will allow us to 

accumulate the quantities based on the 

MISTRIP requisition number and suffix 

code. CONCUR with staffing note.

Para 5.b.(1), The change to Appendix AP2.6 

needs reworded as follows in order to correct 

the quantity of 99,999 to the "M" modified 

quantity of 99M:

"AP2.6.3. Exception rule for ammunition 

FSG 13: By trading partner agreement and 

by coordination with DLA Transaction 

Services, an exception rule is available for 

communicating larger quantities. This rule is 

only applicable when the initiating system is 

DLMS compliant (and supports larger

quantities) and the receiving system is using 

legacy MILSTRIP. Under this rule, when 

the quantity exceeds 99,999, the DLA 

Transaction Services transaction conversion 

from DLMS to legacy format will transmit 

the initial quantity using the standard 

configuration 99M (M-Modifier thousands). 

The residual quantity from the DLMS 

transaction will be transmitted separately 

using the original document number and 

original/blank suffix code. The legacy 

trading partner system will be responsible for 

accumulating the quantities transmitted 

separately (rather than superseding or 

rejecting as duplicate transactions).1" 

Para 5.b.(2), The same correction needs to be 

done in AP3.1.3.2.

USASAC would be required to 

provide the appropriate logic.

Noted.

Concur. Changes have been 

made, but rather to represent the 

use of the M qualifier in general. 

The additional paragraphs were 

not intended for the M qualifier 

to represent an actual conversion 

of 99,999

Concur. Changes made. See 

comment above regarding 

disposition.

9. USTRANSCOM USTRANSCOM approves with the 

following comments:

Noted.
Page 9, Enclosure, ADC 467

Originator Response/Comment Disposition

1. This PDC allows for DLMS transactions 

containing ammunition quantities

greater than 99,999 to (a) contain quantities 

that will be divisible by a number other than 

1,000 and (b) convert that single DLMS 

transaction into two MILS transactions with 

the same Requisition Document Number and 

suffix; the sum of the quantities of those two 

MILS transactions would equal the quantity 

in the original DLMS transaction.

2. This would not affect IGC as they 

consume DLMS transactions (EDI) -

either native EDI or MILS that has been 

converted to EDI by DLA Transaction

Services. No change would be required on 

our system based on this PDC.

3. The PDC asked for feedback on what 

'quantity values' consumer systems can store. 

Please be advised that IGC can store 

quantities up to 7 characters -

(or a quantity equal to 9999999); if the ADC

that is produces from this PDC allows for 

quantities greater than 9,999,999 IGC will 

have to modify their database by increasing 

column sizes.