1 of 12 

Attachment 

ADC 218 

ATTACHMENT TO ADC 218 

Revise DLMS Supplement (DS) 527R and MILSTRAP Receipt Transactions to Document Use of 

Distribution Standard System Operations Control Number and Additional Z4/Z6 Requirements 

(Supply/MILSTRAP. Staffed by PDC 233) 

1. ORIGINATOR: 

a. Service/Agency: HQ Defense Logistics Agency (DLA)

b. Originator: Mr. Terry Simpson, HQ DLA, Distribution Programs Office (J-3752)

2. FUNCTIONAL AREA: Supply/Logistics

3. REFERENCES: 

a. DLMSO memorandum, October 20, 2006, subject: PDC 233, Revise DS 527R and MILSTRAP 

Receipt Transactions to Document Use of Distribution Standard System Operations Control Number 

and Additional Z4/Z6 Data Requirements

b. DLMSO memorandum, November 7, 2006, subject: Approved DLMS Change (ADC) 216, 

Revise DS 527R Receipt in Support of Commercial Asset Visibility (CAV) and Administrative 

Change for Army Medical Material Agreement

4. REQUESTED CHANGE: 

 a. Title: Revise DLMS Supplement (DS) 527R and MILSTRAP Receipt Transactions to Document 

Use of Distribution Standard System Operations Control Number and Additional Z4/Z6 Data 

Requirements (Supply/MILSTRAP) 

 

b. Description of Change (this change was staffed by referenced PDC 233): 

 (1) Revise: 

 (a) DS 527R, as revised by referenced ADC 216, to provide for Distribution Standard 

System (DSS) entry of the Operation Control Number (OCN) in receipt transactions regardless of 

materiel owner, to support current use of OCN by Army, Navy, and Mapping. DLMS 527R 

documentation currently limits DSS use of the operations control number to DLA-owned materiel. 

 (b) MILSTRAP Document Identifier (DI) Code D4_, Materiel Receipt – 

Procurement Instrument Source (DOD 4000.25-2-M, Appendix 3.1) to document that for DLAowned materiel, select Navy activities, select Army assets, and Mapping, DLA storage activities cite 

the DSS OCN in record positions 60-66, rather than the vendor shipment number. DLMSO’s 

understanding is that the DSS use of OCN in D4_ receipts, rp 60-66, is currently agreed to by the 

parties. 
Att 

ADC 218 

2 of 12

 (c) MILSTRAP DI Code D6_, Materiel Receipt – Other Than Procurement 

Instrument Source (DOD 4000.25-2-M, Appendix 3.2) to document that DLA storage activities shall 

enter the DSS OCN in record positions 60-66 for inter-DOD Component use, and for intra-DLA use. 

 (d) DAASC mapping for 527R to accommodate new data requirements and to allow 

DAASC to generate the DLA DSS DI Code Z4S/Z6S and Z6T supplemental receipt transactions 

which DSS currently creates to accompany MILSTRAP DI Code D4S/D6 receipt transaction based on 

trading partner agreements with the DOD Components.

(2) DLA notes that this change is necessary to implement the data elements and provide for 

DAASC creation of Z4/Z6 transactions to ensure that the transactions and/or data can be properly 

recorded in both the DLA and Services legacy and Enterprise Resource Planning (ERP) systems. 

(3) Under DLMS, DLA storage activities shall provide both the Vendor Shipment Number 

(MILSTRAP D4_, rp 60-66) (also known to DSS as the Shipper Identification Number) and the 

Operations Control Number (OCN) when both are available, on the DLMS 527R receipt transaction 

and let the trading partners decide if they want to use the information or not. Under the constraints of 

the 80-record position MILSTRAP receipt transactions, the OCN and the Vendor Shipment Number 

occupy the same record positions in MILSTRAP and are therefore mutually exclusive, and never on 

the same MILSTRAP transaction. 

o OCN is a number randomly assigned by DSS to systemically identify a specific receipt 

transaction. The OCN is used by select DSS trading partners, specifically Navy, Army and Mapping, to tie 

the MILSTRAP D4_ (and Component Z4_) transaction together in their systems. 

o Vendor Shipment Number is used in conjunction with Procurement Instrument 

Identification Number (PIIN), Call/Order Serial Number and Contract Line Item Number (CLIN) to identify 

a contractor shipment to DOD and is generated at the time of shipment, for procurement source receipts. 

o The OCN is a seven-position Alpha/Numeric and Optional. The vendor shipment number is 

also a seven-position Alpha/Numeric field, optional and includes a shipment number suffix column 

containing a “Z” when the last shipment on the contract is shipped. Since both fields are seven-position 

Alpha/Numeric, they cannot be differentiated based on format. However in DLMS 527R, each data element 

has a distinct data qualifier. In MILSTRAP, use is determined by trading partner agreement requirements as 

shown in subparagraph 4.b.(4) below. 

(4) Based on trading partner agreement, DLA storage activities currently create a 

corresponding DI Code Z4S/Z6S, or for Mapping, Z6T, along with the MILSTRAP D4S/D6K or, for 

mapping, D6T receipts. In the near future, DSS will be implementing DLMS 527R for receipts, which 

includes both D4/D6 and Z4/Z6 data requirements. At that time, there will be a need for DAASC to 

convert the DSS-generated DLMS 527R to MILSTRAP D4_/D6_ receipt transactions for trading 

partners still operating under the Defense Logistics Standard Systems (DLSS) (also known as MILS). 

In addition, DAASC would begin generating the Z4/Z6 transactions previously generated by DSS. As 

background information, DLA DSS states that they created a corresponding Z4S, Z6S or Z6T (for 

Mapping) when: 

 Never for Air Force

 Create for Navy when RI Code TO is Navy (starts with N, P, Q, R, or V) and RI Code FROM is 

Navy (depot RI Codes SDF, SDM, SDX, SEB, SCJ, SCQ, SCF, SCH, SDH, SLM, and SCN). 
Att 

ADC 218 

3 of 12

 Create for Army when Local procurement (receipt type L) 

 Create for Mapping when RI Code TO is HM8 (Mapping). 

If the Receipt Type is: Transaction created: Type of Receipt: 

‘L’ Z4S Local Procurement 

‘P’ Z4S Wholesale Procurement 

‘R’ Z6S Returns Non-Procurement 

‘M’ Z6S Maintenance Turn-Ins 

‘N’ Z6S Wholesale Non-Procurement 

‘D’ Z6S DepMeds 

‘S’ Z6S MTIS 

‘C’ Z6T Mapping 

 

(5) DAASC logic for creation of Z4S/Z6S/Z6T to accompany D4S/D6K (or, for mapping, 

D6T): DSS states that DAASC will not have to be concerned with the Receipt Type Code. DSS 

indicates that: 

o For Mapping, DAASC shall create a Z6T for every D6T they send to RI Code HM8. 

o For Navy, DAASC shall create Z4S/Z6S when RI Code TO is NAVY (starts with N, P, 

Q, R, or V) and the RI Code FROM is also Navy. The Depot RI Codes (RI Code FROM) 

for NAVY are: 

 Norfolk SDF 

 San Diego SDX 

 Jacksonville SDM 

 Puget Sound SEB 

 Pearl Harbor SCJ 

 Nuclear Hi SCQ 

 Yokosuka Japan SCF 

 Sasebo Japan SCH 

 Cherry Point NC SDH 

 Sigonella Italy SLM 

 Guam SCN 

 

o For Army, DAASC shall create Z4S/Z6S when the receipt is a Local Procurement. In 

order for DAASC to determine when a receipt is Local Procurement, DSS will send both 

the 2/CS/20 for CONTRACT NUMBER (PIIN), CALL AND CLIN and a 2/N901/90/X9 

for DOCUMENT NUMBER. The D4 will have the CONTRACT NUMBER and the Z4 

will contain the DOCUMENT NUMBER DAASC will be able to determine when to 

send Z4S to Army for Local Procurement because Army Local Procurement will be the 

only DSS generated 527R receipt transactions with both CONTRACT NUMBER in 

2/CS01/20 and a DOCUMENT NUMBER in 2/N901/90/X9. 

 (6) Based on DLA Systems Integration Office (DSIO) input, both DSS and DAASC will need 

to implement the PDC changes to ensure current requirements to DSS trading partners are fulfilled. 

Changes will be required as follows: 

o DSS shall always send a DLMS 527R versus MILSTRAP D4/D6 with corresponding 

DSS Z4S, Z6S or Z6T. 
Att 

ADC 218 

4 of 12

o DAASC shall ensure the 527R transaction sent from DSS is broken down into a MILS 

D4/D6 and, when required, DSS Z4/Z6 if the DSS trading partner’s system does not 

accept the DLMS 527R receipt. 

o In DLSS, the OCN and the Shipper Identification Number are mutually exclusive, 

never on the same DLSS transaction, and they occupy the same record positions in 

DLSS. DSS will include both numbers, when applicable, on the DLMS 527R. 

 c. Procedures: 

 (1) Revise DS 527R to allow use of OCN in (2/N901/90/6R) with receipt of Service-owned 

materiel. Currently 527R use of OCN in limited to DLA-owned materiel: 

# Location DS 527R Revision Reason Federal 

IC 

Impact 

1. DLMS 

Introductory 

notes 

Revise DLMS note 1 last sentence to include 

Z4S/Z6S: 

1. ... This transaction encompasses the functionality 

of MILSTRAP Document Identifier (DI) Codes D4_, 

D6_, DRA, DRF, DXA, DXB, DXC, and DXD. This 

transaction also accommodates the functionality of 

non-DLSS DI Codes as follows: DI Codes C2J, 

C2K, and C3D in support of Medical requirements;

and non-DLSS DI Code BAY in support of Army 

Total Package Fielding; and Distribution Standard 

System DI Codes Z4S, Z6S, and Z6T 

supplemental receipt data . 

To document that Z4/Z6 data 

requirements are incorporated in DLMS 

527R. 

No 

revision 

required 

2. DLMS 

Introductory 

notes 

Add ADC 218 to DLMS introductory note 7. 

-- ADC 218, Revise DS 527R and MILSTRAP 

Receipt Transactions to Document Use of 

Distribution Standard System Operations Control 

Number and Additional Z4/Z6 Requirements 

To identify changes in the DS. No 

revision 

required 

3. 2/N901/90 Revise note for qualifier 6R-Provider Control 

Number, as follows: 

DLMS Note: Used in receipt, and historical 

receipt, transactions to identify the Distribution 

Standard System Operations Control Number. 

Authorized DLMS migration enhancement. See 

DLMS introductory note 5.g.*

To expand use of DSS Operations 

Control Number to Service owned 

materiel. 

Also cites new enhancement note which 

acknowledges enhanced data authorized 

for implementation in DLMS. 

Current DLMS Note which is being 

revised: 

For DLA-owned materiel, including 

mapping products use to identify the 

Operations Control Number. DLMS 

Component-unique enhancement. See 

introductory DLMS note 5e. 

No 

revision 

required 
Att 

ADC 218 

5 of 12

# Location DS 527R Revision Reason Federal 

IC 

Impact 

* DLMS introductory note 5.g was being added to 527R by ADC 216:

5.g. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS 

migration. This data (including expanded field sizes) should be adopted during, or subsequent to, modernization when 

applicable to the Component’s business process. Prior coordination is not required. Components should ensure that 

inclusion of this data in a DLMS transaction does not cause inappropriate rejection of the transaction. 

4 2/N901/90 For qualifier ‘W8-Suffix Code’, delete DLMS note 2: 

1. Use in conjunction with the transaction number 

cited in the 2/N9/030 segment. Use in 

nonprocurement source receipts, MRAs, and 

inquiries for delinquent MRA, to identify the suffix 

code assigned when a partial supply action 

previously occurred. 

2. Future streamlined data; see introductory 

DLMS note 5c.

Administrative update. This suffix 

equates to the suffix code used with 

MILSTRIP document numbers such a 

when an ICP releases a partial quantity 

in response to a requisition, as such it is 

not future streamlined data. 

No 

revision 

required 

5. 2/N901/90 Add qualifier ‘X8-Secondary Suffix Code 

Indicator’ with DLMS note: 

X8 Secondary Suffix Code Indicator 

DLMS note. 

1. This is the suffix code used in MILSTRAP 

receipt transactions to differentiate transactions 

when all data elements, other than quantity, are 

the same except for the Supply Condition Code 

(SCC) of the material being received. When 

required, consecutive receipt suffix codes are 

assigned beginning with A. Use of multiple RCD 

loops, rather than multiple transactions with suffix 

codes, should be planned for future 

implementations. 

2. Future streamlined data; see introductory 

DLMS note 5c. Under DLMS, the RCD loop can 

be used to accommodate multiple SCCs within a 

single receipt transaction, rather than use 

multiple transactions with suffix codes. 

Adds a qualifier that equates to the 

MILSTRAP DI Code D4_/D6_ receipt 

transaction suffix code used to 

differentiate transactions when all other 

information is the same except for the 

SCC and quantity of the materiel being 

received. Under the constraints of 80 rp 

MILS, a separate transaction was required 

for each SCC being receipted. The suffix 

differentiated the transactions which were 

otherwise the same (except for SCC and 

quantity). Use of this suffix code is not 

necessary in DLMS as different SCCs for 

a given receipt can be accommodated 

within the same transaction through use of 

the RCD looping structure. Systems 

implementing DLMS should plan to use 

the RCD loop to accommodate multiple 

SCCs within a single DLMS 

transaction, rather than rely on the 

MILSTRAP suffix code to differentiate 

multiple transactions. However DLA 

indicates that the initial DSS 

implementation will only send one 527R 

per SCC. If a given receipt has two or 

more SCC, DSS will send each SCC as a 

separate 527R. 

No 

revision 

required 
Att 

ADC 218 

6 of 12

# Location DS 527R Revision Reason Federal 

IC 

Impact 

6. 2/N901/90 Modify Note 1, add a new DLMS note 2, revise 

renumbered note 3, and delete current note 3: 

X9 Internal Control Number 

DLMS Note 1. Use in procurement source receipt 

and historical receipt transactions when a transaction 

number (document number) is needed in addition to 

the contract number for transaction tracking 

purposes. Identify the controlling contract number in 

the 2/CS/020 segment. DLMS enhancement; see 

introductory DLMS note 5a.

 

2. DSS uses to identify the transaction number 

(document number) associated with Army Local 

procurement receipts (per DSS DI Code Z4S). The 

controlling contract number is in 2/CS/20. This use 

is an authorized DLMS migration enhancement. See 

DLMS introductory note 5g. 

2. Use in CAV receipts to assign a unique contractor 

reference number. Use by CAV is an authorized 

DLMS migration enhancement. See DLMS 

introductory note 5.g.

Documents DSS use of a document 

number in addition to a contract number 

associated with Army Local 

Procurement receipts. 

No 

revision 

required 

7. 2/N901/90 Add DLMS Note below to ‘A3-Assignment 

Number’, and delete current DLMS note. 

Assign a sequential number to receipt transactions 

for each 2/RCD/40 loop iteration used with the 

controlling number identified in either the 2/CS/20 

segment or 2/N9/30 segment. In the first 2/RCD/40 

loop iteration for a single controlling number, cite 

numeric 1; increase incrementally by one in each 

subsequent loop iteration for that controlling 

number. When reversing a receipt transaction, must 

cite the previously assigned number in the original 

receipt transaction in conjunction with the 

controlling number, for the RCD loop being 

reversed. This use is an authorized DLMS 

migration enhancement. See DLMS introductory 

note 5.g. 

Reinstates a DLMS note for A3 which 

was inadvertently omitted over time. 

DLMSO NOTE: This data was included 

in the original design of 527R receipt. 

The intent of this data is to assign a 

number to each RCD loop iteration, so 

that when reversing a receipt transaction, 

it is not necessary to reverse the entire 

receipt when the reversal only applied to 

the quantity in a given RCD loop. You 

can reverse select RCD loops and this 

assignment number identifies which ones 

are being reversed. 

No 

revision 

required 
Att 

ADC 218 

7 of 12

# Location DS 527R Revision Reason Federal 

IC 

Impact 

8. 2/AMT/100 Revise AMT segment DLMS note 1, and delete 

note 2, as revised by ADC 216. ADC 218 

changes are in highlighted: 

DLMS Note: Use as needed in receipt and 

historical receipt transactions for Army Medical 

Material Agreement (AMMA), for Commercial 

Asset Visibility (CAV), and when agreed to by 

trading partners. Use of this segment as noted is 

an authorized DLMS migration enhancement. 

See introductory DLMS note 5.g. 

2. Use by other than AMMA or CAV is a DLMS 

enhancement. See introductory DLMS note 5.a.

Documents requirement for unit price 

information in receipts as agreed to by 

trading partners. 

No 

revision 

required 

9. 2/AMT01/100 Add AMT01 level DLMS note: 

DLMS Note: 1. DLMS transactions authorize 

an expanded unit price field size of 9 digits for 

dollars and 2 digits for cents. This is expressed 

as “R9.2” (R is the data element type indicating 

a decimal numeric data element). The decimal 

point is passed within the transaction; leading 

and trailing zeros are not transmitted. Use of 

the expanded field size is an authorized DLMS 

migration enhancement. See DLMS 

introductory note 5.g. 

2. Until the expanded unit price field size is 

fully implemented, a field size exceeding 7 

positions (5 digits dollars and 2 digits cents) 

may not be received or understood by the 

recipient’s automated processing system. DAAS 

will truncate the price for MILS users. 

Administrative update to moves notes 

on expanded price field size and 

authorized DLMS migration 

enhancement (which were added by 

PDC 233) to AMT01 level. 

No 

revision 

required 

10 2/AMT01/100 Add qualifier ‘29-Estimated Price’ with DLMS 

note: 

29 Estimated Price 

DLMS Note: Use when needed in receipt and 

historical receipt transactions to cite the 

estimated unit price of the item received. 

Provides qualifier for estimated unit 

price as required by trading partner 

agreements with DSS. 

No 

revision 

required 
Att 

ADC 218 

8 of 12

# Location DS 527R Revision Reason Federal 

IC 

Impact 

11 2/AMT01/100 Revise notes 1, 3, and 5 for Qualifier NT, as 

revised by ADC 216. ADC 218 changes are 

highlighted. 

NT Unit Value 

DLMS Note 1. Use when needed in CAV receipt 

and historical receipt transactions to cite the 

standard unit price of the item received. 

2. DLMS transactions authorize an expanded unit 

price field size of 9 digits for dollars and 2 digits for 

cents. This is expressed as “R9.2” (R is the data 

element type indicating a decimal numeric data 

element). The decimal point is passed within the 

transaction; leading and trailing zeros are not 

transmitted.Í Moved to AMT01 DLMS note1.

3. Use of unit price in CAV receipts and use of the 

expanded field size are is an authorized DLMS 

migration enhancement. See DLMS introductory 

note 5.g.ÍMoved to AMT01 level DLMS note 1. 

3. Until the expanded field size is fully implemented, 

a field size exceeding 7 positions (5 digits dollars 

and 2 digits cents) may not be received or 

understood by the recipient’s automated processing 

system. DAAS will truncate the price for MILS users. 

Í Moved to AMT01 level DLMS note 2.

2. CAV temporarily uses 2/FA201/346 qualifier ZZ 

to identify the standard unit price, but this use 

conflicts with the intended DLMS purpose for 

qualifier ZZ. CAV shall transition to use of the AMT 

segment for standard unit price in lieu of 

2/FA201/346/ ZZ. Supports CAV requirement for 

a unit price in the receipt.

Revises DLMS notes to expand use of 

standard unit price. Under ADC 216 it 

was restricted to use by CAV. 

No 

revision 

required 

12 Various For the following, remove the DLMS note for 

DLMS enhancement introductory note 5.a., and 

replace with the following DLMS note: 

Authorized DLMS migration enhancement. See 

DLMS introductory note 5.g.

2/CS04/20/FJ (Line Item Control Number) 

2/CS15/20 (Unit Price) 

2/N901/30/11 (Account Number) 

2/N907/30/5B (Supplemental Account Number) 

2/G6201/50/07 (Map Effective Date) 

2/N901/90/6G (Map Number) 

2/N901/90/6E (Map Reference) 

2/N901/90/FS (Final Sequence Number) 

2/N901/90/QQ (Unit Number) 

2/N901/90/VR (Vendor ID Number) 

2/LQ01/130/EQ (CIIC) 

Administrative update to identify 

authorized DLMS migration 

enhancements in 527R. 

No 

revision 

required 
Att 

ADC 218 

9 of 12

 (2) Revise DOD 4000.25-2-M, MILSTRAP: 

 (a) Front matter: Abbreviations and Acronyms. Add 2 new acronyms: 

 DLA Defense Logistics Agency 

 DSS Distribution Standard System 

 (b) Appendix 3.1, Document Identifier Code D4_, Materiel Receipt- Procurement 

Instrument Source, record positions 60-66, revise to acknowledge DSS current use of OCN as follows 

(changes are in bold italics): 

Field Legend Record Position(s) Entry and Instruction 

Shipment Number 

or 

DSS Operations 

Control Number 

(OCN)

60-66 Enter vendor shipment number shown on shipping document, preceding 

significant digits with zeros, unless trading partner agreement requires 

entry of the Distribution Standard System (DSS) OCN. The OCN is 

randomly assigned by DSS to systemically identify a specific receipt 

transaction. The OCN is used to link DI Code D4S to the 

corresponding DI Code Z4S which is created based on Trading 

Partner Agreement with DSS. The DSS Z4S Supplemental Receipt 

Data transaction contains both the OCN and the vendor shipment 

number. Trading partner agreements for use of OCN are as follows: 

 Army: OCN is used when Local procurement. 

 Air Force: OCN is never used. 

 Navy: OCN is used when RI Code TO is Navy (starts with N, P, Q, 

R, or V) and RI Code FROM is Navy (depot RI Codes SDF, SDM, 

SDX, SEB, SCJ, SCQ, SCF, SCH, SDH, SLM, and SCN). 

 Mapping: OCN is used when RI Code TO is HM8 (Mapping). 

 

 (c) Appendix 3.2, Document Identifier Code D6_, Materiel Receipt-Other Than 

Procurement Instrument Source, record positions 60-66, delete footnote 4 and revise the Entry and 

Instructions as follows (changes are in bold italics): 

Field Legend Record Position(s) Entry and Instruction 

Dual-Use 

Multiuse 

or

Operations 

Control Number

60-66 

(60-66) 

(60-66) 

For intra-DoD Service use, enter data prescribed by Component. 

For inter-DoD Component use, and intra-DLA use, DLA storage 

activities will enter the DSS Operations Control Number, 

otherwise leave blank.

 d. Alternatives: No known alternatives. 
Att 

ADC 218 

10 of 12

 

5. REASON FOR CHANGE: 

a. This change documents procedures and data requirements to ensure that the transfer of 

information between DSS and their trading partners flows seamlessly for receipt processing as DSS 

implements the DLMS 527R receipt transaction. 

 b. Currently DSS generates DI Code Z4S/Z6S or Z6T transactions when creating the D4S/D6_ 

receipts, for select customers based on agreement. These supplemental transactions evolved years ago 

between DSS and select trading partners, to accommodate data requirements not in the MILSTRAP 

D4S/D6_ receipt transaction. As DSS prepares to implement the DLMS 527R receipt, this change is 

necessary to assure that the data provided in unique DSS transactions by agreement in the past, will 

still be provided. This change assures that Z4/Z6 data requirements are incorporated in the 527R 

receipt transaction, allowing the data to be transmitted in a standard receipt under DLMS. The change 

also documents the requirement that as DSS implements the DLMS 527R receipt transaction, DAASC 

will create, when required, the Z4S/Z6S/Z6T transaction currently generated by DSS, for customers 

still operating under DLSS.

6. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Seamless flow of information between DSS and their trading partners for receipt 

processing as DSS implements DLMS 527R receipt. 

 b. Disadvantages: None known.

7. IMPACT/INTERFACE: 

a. Data Content/Procedures: Documents MILSTRAP and DLMS use of OCN, and documents 

data requirements in DLMS 527R receipt previously accommodated by DLA DI Codes Z4S, Z6S, 

and Z6T. 

b. Perpetuate to DLMS XML 

c. Publication(s): Changes to DOD 4000.25-2-M, MILSTRAP and DLMS 527R.

d. AIS: Component should determine if any Automated Information Systems (AIS) updates are 

required. 

e. DAASC Mapping: Updates are required for DAASC mapping for OCN use in D4_/D6_ / 527R; 

and to identify mapping for DLMS 527R to Z4/Z6 formats as required. 

(1) Following is the Z4S/Z6S format originated by DSS which DAASC shall generate when 

required for an interim period in a mixed DLSS/DLMS environment: 
Att 

ADC 218 

11 of 12

Z4S/Z6S Supplemental Receipt Data in Format DAASC to create when required 

FIELD LEGEND RP ENTRY & INSTRUCTIONS 527R DATA LOCATION 

DI Code 1-3 Document Identifier Code (Z4S/Z6S) 1/BR02/20/ qualifier D4 = Receipt 

2/CS01/020 = procurement source (2nd

position of DI code (i.e. D4/Z4)) 

 

2/N901/030 with code TN - Transaction 

Number (Document Number) = Other 

than procurement source (2nd position of 

DI Code (i.e. D6/ Z6)) 

RI Code TO 4-6 The RIC Code of the ICP to which 

this transaction is being forwarded 

2/N101/210/Z4 

2/N103/210/M4 

2/N104/210 RIC value

2/N106/210/TO 

Shipment Number 7-13 Vendor Shipment Number 2/N901/90/SI 

2/N902/90 = value 

Filler 14-29 Ignore these positions, but need as 

space holder 

NA 

Document Number/PIIN 

 Document Number (Z6S) 

 or 

 Procurement Instrument 

Identification Number (Z4S) 

30-43 

Document Number used only for Z6S 

PIIN used only for Z4S 

2/N901/30/TN (Transaction Number 

(Document Number)) 

2/N902/30 = value 

2/CS01/20 (Contract Number (PIIN)) 

Filler 44 Ignore these positions, but need as 

space holder 

NA 

Unit Price 45-54 The actual Standard or estimated 

price of the item 

2/AMT01/100/NT-Unit Value = 

Standard Unit Price (’NT’ was added by 

ADC 216)

No qualifier for ‘estimated price’ is 

currently in 527R. ADC 218 adds 

2/AMT01/100/29 –Estimated Price for 

estimated unit price. 

2/AMT02 = Monetary Amount 

OCN 60-66 DSS Operations Control Number - 

Designates receipt of materiel 

2/N901/90/6R (OCN) 

2/N902/90 = OCN value 

RI Code From 67-69 RI Code from of the activity where the 

item was received 

1/N101/70/RC 

1/N103/70/M4 

1/N104/70 RIC value 

1/N106/70/FR 

Receipt Suffix Code 70 Used when necessary to add 

uniqueness to Document Number 

Qualifier being added by PDC: 

2/N901/90/X8 = receipt suffix code 

2/N902/90 = receipt suffix code value 

Blank 71 Leave blank NA 

Blank 72-73 Leave blank NA 
Att 

ADC 218 

12 of 12

Z4S/Z6S continued 

FIELD LEGEND RP ENTRY & INSTRUCTIONS 527R DATA LOCATION 

Shipper ID 74-76 Shipper ID of the Navy shipping 

activity 

2/N101/210/CI (Consignor) 

2/N103/210M4 (RIC) 

2/N104/210 RIC value 

Blank 77-78 Leave blank NA 

Blank 79-80 Leave blank. NA 

(2) Following is the Z6T format originated by DSS which DAASC shall generate when required for 

an interim period in a mixed DLSS/DLMS environment. 

Z6T Supplemental Receipt Data format to be created by DAASC (Z6T is used for Mapping only) 

FIELD LEGEND RP ENTRY & INSTRUCTIONS 527R DATA LOCATION 

DI Code 1-3 Document Identifier Code (Z6T) 1/BR02/20/ qualifier D4 = Receipt 

2nd position of DI Code D6/Z6: 

2/N901/030 with code TN - Transaction 

Number (Document Number) = Other 

than procurement source.

 

3rd pos of DI Code Z6T =LIN01 code S 

RI Code TO 4-6 The RIC Code of the ICP to which this t

being forwarded 

2/N101/210/Z4 

2/N103/210/M4 

2/N104/210 RIC value

2/N106/210/TO 

OCN 7-13 OCN 2/N901/90/6R (OCN) 

2/N902/90 = OCN value 

WS-MAP-EDITN-NBR 14-16 Map Edition Number 2/N901/90/6G (Map Number) 

2/N902/90 = value 

DT-EFFCTV 17-23 Map effective date 2/G6201/50/07 (Effective Date) 

2/G6202 = date 

WS-MAP-CIIC 24 CIIC 2/LQ01/130/EQ (CIIC) 

2/LQ02/130 = value 

WS-MAP-OVERRIDE-CD 25 Leave blank NA 

WS-MAP-NRN 26-40 NIMA Reference Number (NRN) 2/N901/90/6E (Map Reference) 

2/N902/90 = value 

Blank 41-80 Leave blank NA