SUSTAINMENT 

OFFICE OF THE ASSISTANT SECRETARY OF DEFENSE 

3500 DEFENSE PENTAGON 

WASHINGTON, DC 20301-3500 

 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE

 

SUBJECT: Approved Defense Logistics Management Standards Change 1387, Routing of Prepositioned Materiel Receipt by Department of Defense Activity Address Code and 

Mark-For Party Identification

The attached Approved Defense Logistics Management Standards Change (ADC), as 

outlined in the attachment, is approved for implementation.

Addressees may direct questions to Mr. Rafael Gonzalez, e-mail: Rafael.Gonzalez@dla.mil.

Others must contact their designated Supply Process Review Committee representative available at 

http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/.

METHOD.LEIGH Digitally signed by METHOD.LEIGH.E.1098529302

.E.1098529302 Date: 2021.09.17 12:27:02 -04'00'

Leigh E. Method, SES

Deputy Assistant Secretary of Defense 

for Logistics

Attachment: 

As stated

cc: 

OUSD(C) 

DLA J6DS
Attachment, ADC 1387

Page 1

ADC 1387

Materiel Receipt DoDAAC Routing and Mark-For Party Identification in 

Receipt-Related Transactions

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Mr. Randall Reed, Leidos DPAS Program; 717-261-2602; or 

e-mail: randall.l.reed.ctr@dla.mil

b. Functional POC: Mr. Joseph Stossel, DLA J62 LCDS Portfolio; 571-363-8744; or 

e-mail: joseph.stossel@dla.mil

2. REFERENCES: 

a. Approved DLMS Change (ADC) 1009A, DLMS Enhancements for Requisitioning to 

Improve Use of Mark-for Addressing, Expand Authorized Priority Designator Validation, 

Correct EMALL Purchase/Credit Card Format Rules, and Require Distribution of Status for 

Requisitions associated with Purchase/Credit Card Payment, August 06, 2014

b. Defense Logistics Manual (DLM) 4000.25, Volume 2, Appendix AP2.8: Reject 

Advice Codes

3. APPROVED CHANGE(S):

a. Brief Overview of Change: This change: 

(1) Modifies the current business rules and routing logic in the Defense 

Automatic Addressing System (DAAS) to enable routing of the DLMS 527D Pre-positioned 

Materiel Receipt transaction by Department of Defense Activity Address Code (DoDAAC) when 

the receiving activity does not have an assigned routing identifier code (RIC). Routing by 

DoDAAC will only be available to those customers enabled to transact by DoDAAC. 

(Reference 2.a. and 2.b.)

(2) Modifies the DLMS 527D Pre-positioned Materiel Receipt (PMR) to identify 

a mark-for party within the ship-to address and an optional point of contact.

(3) Authorizes existing reject advise codes for the purpose of rejecting a PMR 

due to invalid/missing data via the DLMS 824R Reject Advice transaction. 

(4) Updates Appendix 2.8 and add several new reject advice codes to facilitate 

the reject of transactions under selected scenarios described in the section 3.d. 

(5) Opens a new segment to allow DoD Components to identify the United States 

Special Operations Command (USSOCOM) or U.S. Army fielding representative responsible for 

the shipment or Point of Contact (POC) via the DLMS 527D PMR transaction. 
Attachment, ADC 1387

Page 2

b. Background:

(1) The Defense Property Accountability System (DPAS) supports new 

equipment fielding for the U.S. Army. DPAS uses the DLMS 527D to establish PMRs for 

Property Book, Armory, Tool Crib, Bench Stock, and other items shipped to activities below the 

wholesale Supply level (end-user) that do not have an assigned RIC. DPAS provides the DLMS 

527D when pushing materiel to these activities. For example, Global Combat Support System 

(GCSS)-Army requires a DLMS 527D PMR transaction to establish a due-in to process the 

receipt and produce the DLMS 527R Materiel Receipt. Without a due-in, the GCSS-Army user 

must receipt the materiel either as “Found on Installation” or “Administrative Adjustment”. 

Neither action will generate a materiel receipt acknowledgement (MRA) to enable the shipping 

organization to close the push order. 

(2) To support push orders, the DLMS 527D needs to allow routing by 

DoDAAC, as accountable records below supply typically do not have an assigned RIC. There is 

also a need to support the mark-for-party within the DLMS 527D when used as a PMR, 

especially for the notification of a weapons shipment. Providing support for the mark-for-party 

allows the recipient of the PMR to know exactly who will be receiving the materiel.

(3) DPAS requires the ability to reject PMRs with missing or invalid information. 

Often, PMRs can pass DAAS validation rules but may lack necessary information to properly 

receipt a shipment. To address this issue, DPAS requires use of the DLMS 824R Reject Advice 

transaction to communicate the reason for a reject back to the transaction originator.

(4) DPAS requires the ability to electronically provide an accountable property 

officer with the point of contact (POC). Today, this information must be provided through email 

or phone. Including the POC as part of the push Due-in record, it will enable this information to 

be a part of the record that was established by the Program Executive Office. This will allow the 

accountable property officer to easily contact the POC concerning the materiel being pushed to 

their unit.

c. Approved Change in Detail:

(1) Authorize use of the DoDAAC to identify the sender or receiver for a given 

DLMS 527D transaction.

(2) Modify current business rules and logic at DAAS to enable routing and 

validation of the PMR transaction by DoDAAC. Routing by DoDAAC will enable DAAS to 

route the DLMS 527D transaction by DoDAAC when the activity does not have an assigned 

RIC.

(a) Although the intent is to route the PMR by DODAAC, in the event the 

PMR contains a valid destination RIC and a DoDAAC, DAAS will route the transaction by RIC.

(b) DAAS will reject the PMR and notify the sender via the reject advice 

transaction when it lacks a valid destination DoDAAC or RIC. Refer to Enclosure 2 for routing 

validation logic. 
Attachment, ADC 1387

Page 3

(c) This functionality is only available for activities enabled to route 

transactions by DoDAAC under a DLMS environment. 

(d) Mark-for Party Identification: This change adds qualifier Z7 Markfor Party (2/N101/210) to identify the mark-for party. The mark-for party is the entity within the 

shipping address that will receive the materiel. This data element is limited to a total of 24-

character field length. The limitation is necessary to accommodate the Mark-for party in the DD 

Form 1348-1A or 1348-2 block 4. Refer to ADC 1009A (Reference 3.a.) for how this was 

previously done in the DLMS 511R, 856S 869A, and 869F transactions.

(3) Authorize existing reject advise codes, as applicable, to reject PMRs via the 

Reject Advise transaction. This will allow DPAS to properly cite the applicable reject advise 

code when the rejecting a PMR. DLM 4000.25 Vol. 2 Appendix 2.8 includes a list of all 

available reject codes. 

(4) Add the following reject advice codes to Appendix 2.8. These codes will 

support the reject of PMR as well as other transactions when conditions applied. 

(a) BB – Others, see remarks. This reject advice code provides some 

flexibility for supply systems to reject a given transaction and provide any necessary details 

when the reason for the reject is not covered under any other code available in Appendix 2.8. 

The system rejecting the transaction will use DLMS 824R, cite reject advice code BB, and 

provide the necessary details in segment 2/NTE02/080 for the originating system to address and 

re-submit. DAAS will reject any Reject Advice transaction where the originating system cited 

reject advice code BB and did not provide any comments in the NTE02 segment.

(b) BC – Rejected. Estimated Delivery Date Missing/Invalid. This reject 

code is available when the PMR has an estimated delivery date that is in the past or otherwise 

invalid or missing. The recipient of the reject transaction will need to make the necessary 

correction and resubmit. 

(c) BD – Rejected. Submitter in the PMR not found/Unknown/Inactive in 

the system rejecting the transaction. This reject advice code is available when the PMR 

transaction has a submitter (qualifier 41) identified in the N101 segment, but it is not 

recognized/registered by the system rejecting the transaction. The recipient of the reject 

transaction will need to make the necessary correction and resubmit. 

(d) BE – Rejected. Rejected. Distribution Code Missing/Invalid. This 

reject code is available when the PMR transaction is missing or does not include a valid 

distribution code. The recipient of the reject transaction will need to make the necessary 

correction and resubmit.

(5) To enhance the receiving organization’s ability to contact the weapons system

program, this change opens the G61 – Contact segment in the DLMS 527D. The G61 segment 

will allow the PMR to identify the United States Special Operations Command (USSOCOM) or 

U.S. Army fielding representative responsible for the shipment by phone and/or e-mail if 

provided. Use of the G61 segment is optional.
Attachment, ADC 1387

Page 4

d. Revisions to Defense Logistics Manuals: Add the following to Volume 2, Appendix 

2.8 Reject Advice Codes:

CODE EXPLANATION

BB Rejected. Others, see remarks.

BC Rejected. Estimated Delivery Date Missing/Invalid*.

BD Rejected. Submitter in the PMR not found/Unknown/Inactive in the system 

rejecting the transaction. 

BE Rejected. Distribution Code Missing/Invalid*.

* Approved for Army and DPAS. Requires coordination with other Services prior to 

implementation and use.

e. Approved Transaction Flow: This change does not modify the existing standard 

transaction flow for PMRs. Enclosure 2 includes a transaction flow that explains how DPAS and 

GCSS- Army intends to use the PMR transaction. 

f. Alternatives: None identified.

4. REASON FOR CHANGE: 

a. Army program executive offices (PEOs) require a method to field new equipment to 

locations/units to transmit the DLMS 527D PMR to ensure processing into various unit level 

supply systems. These locations/units can only send/receive transactions using their respective 

DoDAAC. Furthermore, the mark-for party is needed in the DLMS 527D to specify the exact 

unit to receive the material.

b. This change also serves as a pilot for DoDAAC routing. DPAS and GCSS-Army are 

both DLMS-capable systems that can exchange variable-length transactions beyond the 80-

record position constraints imposed by the legacy Defense Logistics Standard System (DLSS).

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: The ability for DAAS to route transactions by DoDAAC may 

eventually allow DoD Components to phase out the use of RICs for party identification in 

DLMS transactions.

b. Disadvantages: This functionality is limited as many systems are not capable to 

transmit or interpret transactions routed by DoDAAC.

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

DEVELOPMENT: This change was developed under the assumption that:

a. DPAS will only use the DoDAAC routing capability in the DLMS 527D with GCSSArmy, or with other DoD Components by agreement/coordination.
Attachment, ADC 1387

Page 5

b. DAAS has no logic to determine if the recipient system supports routing by 

DoDAAC. It will be up to the recipient to notify the system originator of the issue.

7. ADDITIONAL COMMENTS TO CONSIDER: This change does not intend to 

accommodate applications that require RICs. Therefore, if a DoDAAC is present, DAAS will 

route the transaction even if the RIC field is blank. 

8. ESTIMATED TIMELINE/IMPLEMENTATION TARGET: This change requires 

DAAS logic changes. Consequently, DAAS will provide an estimated date for implementation 

as part of the PDC formal coordination. Upon approval of this change DPAS and GCSS Army 

may begin implementation. However, testing between systems and DAAS may be necessary to 

ensure the routing works as intended.

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: There are no known cost savings associated to 

this change.

10. IMPACT: 

a. New / Change to Data Elements: Update the code list for Reject Advice Code per 

section 3.d. above.

b. Automated Information Systems (AIS): This change affects DPAS and GCSSArmy. Additional applications may implement this change with proper trading partner 

coordination prior to transacting by DODAAC.

c. Defense Automatic Addressing System (DAAS):

(1) DAAS update the DLMS 527D per Enclosure 1

(2) DAAS will update the Defense Automatic Addressing System Micro-Routing 

System (DMARS) to implement the logic contained in Enclosures 1 and 2.

d. Non-DLM Publications: No known changes to non-DLM publications. However, 

Participating Components should update any relevant Army policy and standard operating 

procedures (SOP).

11. PROPOSED DEFENSE LOGISTICS ENTERPRISE STANDARDS CHANGE (PDC) 

1387 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. U.S. Army SDR Concurs as written. As noted.

2. U.S. Army Supply Concurs as written. As noted.

3. U.S. Navy Concurs as written. None.
Attachment, ADC 1387

Page 6

4. U.S. Air Force Concur with comments.

ILS-S concurs with PDC - with the following comments 

concerns: 

1. Ref: Page 2, para c) The current ILSS logic in ILS-S 

assigns the to RIC on the DWA (527D) based upon the 

shipping destination RIC of the corresponding 

Shipment. If there is no RIC for the ship to DoDAAC -

then currently ILS-S would NOT produce a DWA 

(527D). This PDC (if approved) would require a 

modification in ILS-S to use the Outbound Shipment 

destination DoDAAC on the DLMS 527D. It is our 

understanding that when the there is a RIC for shipment 

destination - then there would be no change in the 

DWA (527D) transaction. Question: Is this correct?

2. (Ref: Page 2-3, para c.(d) This would require a 

change in ILS-S to add a mark-for party within the shipto address and an optional point of contact. 

Question: Is this additional information to be provided 

always required or is it on a case-by-case basis (for each 

shipment) and is the info provided to a particular 

DoDAAC/RIC always the same information?

3. (Ref Page 3, para c) No Change Required

4. (Ref: Page 3, para c) ILS-S Change required if we are 

adding new reject advice codes for the 824R. Question: 

are there new advice codes being added?

5. (Ref: Page 3-4, para c) ILS-S Change Required to 

accommodate new segment on the 527D.

DEDSO Response:

1. Correct, when there is a 

RIC for shipment 

destination - there would be

no change in the DWA 

(527D) transaction. Note: 

Routing by DoDAAC was 

required by DPAS/Army in 

a scenario involving end-use 

customers without a RIC. 

There is no change required 

in the established Wholesale 

PMR process. 

2. DPAS will only use the 

Mark for Party 

Identification and POC 

information with GCSSArmy, or with other DoD 

Components by agreement/

coordination.

3. Noted

4. This change adds four 

new Reject Advice Codes 

for use by DPAS and Army. 

Any additional use requires

additional agreement 

between Components.

5. The changes to the 527D 

indicate “Use only for Army 

and Defense Property and 

Accountability System 

(DPAS) materiel fielding” 

Any use outside to this 

scenario requires additional 

coordination/agreement 

between Components.
Attachment, ADC 1387

Page 7

5. U.S. Marine Corps Concurred with comment

Comment: The Marine Corps Inventory Control Point 

uses the Pre-Position Material Receipt (PMR) records to 

notify the receiving custodial sites of an incoming 

shipment and which Owning RIC the shipment is 

intended for. 

In all cases within the GCSS-MC system, the PMR 

record is release at the time the Shipping Confirmation 

if produced. The error logic within the PDC, in the case 

of the DLMS 824R reject codes of “BC” and “BE” 

should not be applicable at this time. Inclusion of this 

logic during processing will result in catastrophic

failure of our PMR records researching our DLA 

custodial site. Furthermore, the resulting affect would 

lead to Supply Discrepancy Reports, (SDRs) being 

released from DLA for missing PMR records.

As noted.

DEDSO Response:

Added a note to appendix 

2.8 so Reject Advice Code 

BE and BC are not 

applicable to USMC. 

6. DLA Concurs as written. As noted.

7. DAAS Concurs as written. As noted.

8. ODASD(L) Concur with comment.

Comments:

ODASD(Logistics) has reviewed the subject Proposed 

Standards Change (PDC) and concurs with comment. 

The PDC states, “Future expansion of the Department 

of Defense Activity Address Code (DoDAAC) routing 

concept is possible, but the ability of the Components to 

enforce a one-to-one relationship between Routing 

Identifier Codes (RIC) and DoDAAC is crucial to allow 

this to occur.” There is not a one-to-one relationship 

between the DoDAAC and the RIC, so how can this be 

crucial?

As noted.

DEDSO Response:

The wording, “Future 

expansion of the 

Department of Defense 

Activity Address Code 

(DoDAAC) routing concept 

is possible, but the ability of 

the Components to enforce a 

one-to-one relationship 

between Routing Identifier 

Codes (RIC) and DoDAAC 

is crucial to allow this to 

occur.” Was removed that 

sentence from the ADC as it 

had no impact on this 

change.
Enclosure 1, ADC 1387

Page 1

Enclosure 1, DLMS 527D IC Revision

# Location DLMS 527D Materiel Due-in and Receipt Reason

1. DLMS 

Introductory 

Notes

Add ADC 1387 to DLMS Introductory Note 6:

- ADC 1387, Materiel Receipt DoDAAC Routing and MarkFor Party Identification in Receipt-Related Transactions

Identifies changes 

made to the IC.

2. 1/G61/110 Mark G61 Segment (Contact) as Used and add DLMS Note:

DLMS Note: 

1. Use only for Army and Defense Property and 

Accountability System (DPAS) materiel fielding. Refer to 

PDC 1387

2. Use multiple repetitions to identify multiple points of 

contact or communication numbers. When using multiple 

communication numbers for a single point of contact, repeat 

the name cited in G6102.

3. DLMS enhancement; see introductory DLMS note 4a.

The G61 segment 

identifies one or 

more POCs.

3. 1/G6101/110 Mark Data Element G6101 (Contact Function Code) as Used 

and add the qualifier with DLMS Note:

PP Program Manager

DLMS Note: Use to identify the materiel fielding 

representative directing the shipment.

To identify the 

USSOCOM or U.S. 

Army fielding 

representative 

directing the 

shipment.

4. 1/G6102/110 Mark Data Element G6102 (Name) as Used and add DLMS 

Note:

DLMS Note: Use a job title or description instead of an 

individual’s name if security or privacy concerns do not 

permit the use of a name.

To identify the 

POC’s name.

5. 1/G6103/110 Mark Data Element G6103 (Communication Number 

Qualifier) as Used and add the qualifiers and DLMS Notes:

DLMS Note:

1. Use to identify the preferred method of communication in 

the first repetition. Use additional repetitions when 

identifying alternate communication methods.

2. Use to provide a commercial phone number and/or e-mail 

address to facilitate carrier deliveries or source of supply 

inquiries.

AU Defense Switched Network

DLMS Note: Use to identify the DSN telephone number.

EX Telephone Extension

DLMS Note: Use immediately following codes AU, IT, or 

TE to identify a telephone extension.

This data element 

includes the 

available 

communication 

methods.
Enclosure 1, ADC 1387

Page 2

# Location DLMS 527D Materiel Due-in and Receipt Reason

EM Electronic Mail

DLMS Note: Use to identify the e-mail address.

FX Facsimile

DLMS Note: Use to identify the facsimile (FAX) telephone 

number.

IT International Telephone

DLMS Note: Include the country and city code.

TE Telephone

DLMS Note: Use to identify a commercial phone number. 

Include the area code and number.

6. 1/G6104/110 Mark Data Element G6104 (Communication Number) as 

Used and add DLMS Note:

DLMS Note: Do not include blank space, dashes, or 

parenthesis between numbers.

This location 

identifies the 

contact’s phone 

number or e-mail.

7. 1/G6105/110 Mark Data Element G6105 (Contact Inquiry Reference) as 

Used and add DLMS Note:

DLMS Note: Use to indicate the office symbol or activity 

code for the party identified.

This location 

identifies the 

contact’s office 

symbol or activity 

code.

8. 2/N101/210 Revise DLMS Note 2 and add Note 3:

RC – Receiving Location

DLMS Note: 

1. Use in due-in transactions to identify the location to receive 

the materiel when the total due-in quantity referenced in the 

2/RCD/040 loop is due-in to one location only. When the 

quantity is stratified by receiving location, use the 2/QTY/310 

loop. 

2. Use in advance receipt information transactions prepositioned material receipt (PMR) to identify the receiving 

location.

To identify the 

DoDAAC as an 

option for 

addressing activities 

that do not have a 

RIC, in accordance 

with this PDC.

9. 2/N101/210 Add the Qualifier Code and DLMS Notes:

Z7 – Mark-for Party

DLMS Note: 

1. Use for Army and DPAS materiel fielding to identify the 

ultimate destination for the order when the activity is not the 

ship-to address.

2.DLMS enhancement; see introductory DLMS note 4a. 

To identify the 

mark-for party to 

receive the materiel.
Enclosure 1, ADC 1387

Page 3

# Location DLMS 527D Materiel Due-in and Receipt Reason

10. 2/N102/210 Add DLMS Note 2:

DLMS Note: 

1. Use to identify the delivery location (Qualifier DZ, 

2/N101/210). Field length is 30 positions maximum.

2. Use to identify the Mark-for Party (Qualifier Z7, 

2/N101/210). Total field length is restricted to a total of 24 

clear text characters. Refer to PDC 1387

To identify the data 

defined by N101/Z7
Enclosure 2, ADC 1387

Page 1

Enclosure 2

A. DAAS DoDAAC Routing Decision Chart
Enclosure 2, ADC 1387

Page 2

B. DPAS Route PMR by DODAAC Transaction flow