2

Approved DLMS Change 69

DLMS Mapping for DLA Requisition Exception Data Transaction, DI Code YRZ

1. ORIGINATOR:

a. Service/Agency: Defense Logistics Agency

b. Originator: Supply PRC, Chair: Ellen Hilert, DLA DLMSO/J-673, Defense Logistics 

Management Standards Office (DLMSO), 703-767-0676 (DSN 427), ellen_hilert@hq.dla.mil

c. DLA Point of Contact: Mr. Bob Vitko, J-332 

2. FUNCTIONAL AREA:

Primary: Supply

3. REFERENCE: DLA Manual 4140.2, Vol II, Part 3, Appendix B-237

4. REQUESTED CHANGE:

a. Title: DLMS Mapping for Requisition Exception Data Transaction, DI Code YRZ

b. Description of Change: This change accommodates the Business Systems Modernization 

(BSM) SAP requirement for receiving requisition exception data. This change modifies the IC/DS 511R, 

Requisition, to transmit the data content of the DLA DI Code YRZ. The DLA DI Code YRZ passes 

from the requisitioner, under authorized conditions, to Inventory Control Point (ICP). Inclusion of these 

data elements supports DAAS conversion from the DLA unique transaction to the DLMS transaction 

required by BSM.

c. Procedures: 

(1) This transaction may be used to reflect four types of exception data. These types are 

technical exception information, CAGE/Part number data in excess of 15 positions, mark-for delivery 

information, or ship-to clear text addresses. Ship-to information for Foreign Military Sales requires two 

additional types of addresses, the notice of availability address and the in-country address. DAAS will 

prepare this transaction by associating the DLA DI Code YRZ with the requisition data to create a single 

transaction. This transaction will be prepared when a MILSTRIP requisition, DI Code A_E or A_5 is 

received with technical data that is required for procurement purposes. Additionally, this transaction will 

be prepared to reflect exception data when DAAS receives a MILSTRIP requisition with an entry in rp 70 

and exception data is entered in rp 71-80. [Note: This transaction does not include the purge code used 

on the DLA DI Code YRZ to remove exception data maintained on requisition file.]

(2) Add the following codes/notes to the 511R, Requisition:
3

# Location Revision Reason Federal IC

1 Introductory 

DLMS Notes 

(Cover Page)

Add note 3e:

3e. Data required to accommodate Component-unique 

transaction requirements (example: C-series 

transactions). Data does not apply to DLSS 

transactions.

Provides note of 

explanation for 

applicable IC/DS changes.

No change

2 2/NTE/120 Add notes and new code:

DLMS note: 1. Exception data associated with the 

requisition is a DLMS enhancement; see introductory 

DLMS note 3a. 

2. Use with Requisition Exception Data Transaction 

(DLA DI Code YRZ) to indicate technical exception 

information or extended part number. See 

introductory DLMS note 3e.

NTE01 Code ORI: Order Instructions. Add note:

DLMS Note: Use with Requisition Exception Data 

Transaction (DLA DI Code YRZ) to indicate technical 

exception information. Segment may be repeated up to 

20 times with same NTE01 qualifier. See introductory 

DLMS note 3e.

Add Code PDS and associated note: 

PDS Product Specification

DLMS Note: Use with Requisition Exception Data 

Transaction (DLA DI Code YRZ) to indicate an 

extended part number. DLMS note 3e.

Provides the ability to 

send exception data in 

the transaction set.

Federal IC revision

required.

3 2/LQ/140 Add new note 2 to LQ01 Code 0 Document 

Identification Code

2. Use two iterations to identify requisition DI Code 

and Requisition Exception Data Transaction (DLA DI

Code YRZ), when applicable.

Clarifies usage of DI 

Code.

No Change
4

4 2/N1/180 Add two codes and associated notes to N101 and add 

new DLMS notes to existing Codes DA and Z7:

Add DLMS note to code DA Delivery Address: Use 

for Requisition Exception Data Transaction (DLA DI 

Code YRZ) for exception ship-to address information. 

See introductory DLMS note 3e.

Add code IAD: Foreign Office. 

Add Federal Note: Use for clear-text exception data 

FMS in-country address. 

Add DLMS Note: Use for Requisition Exception Data 

Transaction (DLA DI Code YRZ) FOR FMS incountry mark-for address. See introductory DLMS 

note 3e.

Add code IF: International Freight Forwarder. 

Add DLMS Note: Use for Requisition Exception Data 

Transaction (DLA DI Code YRZ) Notice of Availability 

(NOA) address information. See introductory DLMS 

note 3e.

Add DLMS note to code Z7 Mark-for Party:

2. Use for Requisition Exception Data Transaction 

(DLA DI Code YRZ) to identify mark-for delivery 

information. See introductory DLMS note 3e.

Add DLMS note to N102:

6. Use for Requisition Exception Data Transaction 

(DLA DI Code YRZ) with N101 code DA, IAD, IF and 

Z7 to identify the exception address line 1. See 

introductory DLMS notes 3e.

Allows for a further 

breakdown of the address 

type.

Federal IC revision 

recommended to add 

new codes.
5

5 2/N2/190 Modify segment note:

DLMS Note: 1. Use for Requisition Exception Data 

Transaction (DLA DI Code YRZ) for mark-for, shipto, FMS in-country mark-for and notice of availability 

address information. See introductory DLMS note 

3e.

Add element note to N201:

Add DLMS note: Use for Requisition Exception Data 

Transaction (DLA DI Code YRZ) with N101 Codes 

DA, IAD, IF, and Z7 for address line 2. See 

introductory DLMS note 3e.

Add element note to N202:

Use for Requisition Exception Data Transaction (DLA 

DI Code YRZ) with N101 Codes DA, IAD, IF, and Z7 

for address line 3. See introductory DLMS note 3e.

Provides explanation 

regarding usage of 

segment.

No change.

6 2/N3/200 Modify segment note:

2. Use for Requisition Exception Data Transaction 

(DLA DIC YRZ) for mark-for delivery data. See 

introductory DLMS note 3e.

Add element note to N301:

DLMS Note: Use for Requisition Exception Data 

Transaction (DLA DI Code YRZ) with N101 code Z7 

to reflect line 4 of the mark-for delivery data. 

Provides explanation 

regarding usage of 

segment.

No change.
6

7 2/N4/1103 Modify segment note:

2. Use for Requisition Exception Data Transaction to 

reflect address information. See introductory DLMS 

note 3e.

Add note to N401:

DLMS Note: Use for Requisition Exception Data 

Transaction (DLA DI Code YRZ) with N101 Codes 

DA, IF, and IAD for the Requisition) to reflect the city 

name. See introductory DLMS note 3e.

Add note to N402:

DLMS Note: Use for Requisition Exception Data 

Transaction (DLA DI Code YRZ) with N101 code DA 

to indicate the state code associated with the ship-to 

address, when applicable. 

Add note to N403:

DLMS Note: Use for the Requisition Exception Data 

Transaction (DLA DI Code YRZ) with the N101 Codes 

DA, IF, and IAD to reflect the 11-position postal code. 

See introductory DLMS note 3e. 

Add note to N404:

DLMS Note: Use for the Requisition Exception Data 

Transaction (DLA DI Code YRZ) with the N101 Codes 

DA (when other than U.S.), IF, and IAD to reflect the 

country code. May reflect DLA 3-position country 

code. See introductory DLMS note 3e.

Provides explanation 

regarding usage of 

segment.

No change.

d. Alternatives: BSM could perpetuate use of the DI Code YRZ transaction as currently formatted.

5. REASON FOR CHANGE: This change supports component-level DLMS implementation. These 

data elements and codes were identified during a review of DLA-unique transactions required for implementation 

of the BSM. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Supports component-level DLMS implementation.

b. Disadvantages: None identified.

7. IMPACT:

a. Data Content/Procedures: May require minimal update to DAAS and DLA BSM mapping.
7

b. Publication(s): DoD 4000.25-M , DLMS; Federal IC 511R and corresponding DS. The DS 

revision requires corresponding revision of the Federal IC. All applicable revisions will be submitted to the 

EDISMC/Logistics Functional Work Group for coordination/approval.