ADC 128 

Revised SDR Transaction Exchange (Formats, Codes, and UID) 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Agency

b. Sponsor: Supply Process Review Committee, Chair: Ellen Hilert, DLA DLMSO/ 

J-6411, Defense Logistics Management Standards Office (DLMSO), 703-767-0676 (DSN 427), 

ellen.hilert@dla.mil

2. FUNCTIONAL AREA: Primary: Supply

3. REFERENCES: 

a. The official guidance for submission of SDRs is published in DLAI 4140.55/ 

AR 735-11-2/SECNAVINST 4355.18A/AFJMAN 23-215. The joint service publication is 

available at http://www.dla.mil/j-6/dlmso/Manuals/Default.htm. 

b. DOD 4140.1-R, May 23, 2003, DOD Supply Chain Materiel Management Regulation. 

This regulation requires automated SDR processing. This regulation is available at 

http://www.acq.osd.mil/log/logistics_materiel_readiness/organizations/sci/assetts/executive_info/

drid/p41401r.pdf. Refer to paragraph C3.8.1.6.4. 

c. Approved Defense Logistics Management System (DLMS) Change (ADC) 101, 

DLMS Mapping for Standard SDR/DOD WebSDR Output, DS 842A/W (Supply/SDR) (Staffed 

by PDC 97) 

d. Approved Defense Logistics Management System (DLMS) Change (ADC) 114, DS 

842A/R DOD Standard SDR Reply and Additional Data Content for the SDR Report 

(Supply/SDR) (Staffed by PDC 107) 

e. All DLMS Supplements listed in this memorandum are posted to the DLMSO web 

site at http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/x12.asp. Federal Implementation 

Conventions are available at http://fedebiz.disa.mil/cgi/advsearch.cgi. 

f. UII policy and associated documentation are available at: 

http://www.acq.osd.mil/UID/index.html.

4. REQUESTED CHANGE: 

a. Title: Revisions for SDR Transaction Exchange (Formats, Codes, and UID)

b. Description of Change: This update modifies both the SDR submission (842A/W) 

and the SDR Reply (842A/R) DS to make adjustments which are required to support desired 
functionality. This change establishes new discrepancy codes and new reply codes which 

support transactional exchange of SDRs. Since policy and procedures are not yet fully 

defined, the unique identification (UID) portion of this ADC is considered a planning tool for 

establishing techniques for accommodating UID within transactional exchanges under the 

DLMS. As procedures are developed, additional DLMS changes may be staffed. This 

document is provided as a first step in documenting changes which may be used to support 

business process improvements. Component system changes which are required to support 

the integration of the UID data requirements are not identified in this change. Specific 

revisions are identified below. Changes identified for the joint Component 

instruction/regulation will also be applied to the DLMS manual. 

c. Procedures: 

(1) Revise 842A/W and 842A/R DLMS Supplements as follows:

# Location Revision Reason 

842A/W 

1. DLMS 

Introductory 

Notes 

Added the following ADC title:

- ADC 128, Revision for SDR Transaction 

Exchange 

Administrative 

2. 1/BNR02/0200 Deleted the following DLMS notes:

DLMS Note: Use to identify the DoD WebSDR generated 

control number for this SDR. Field size restricted to 11 

positions.

Note: Enter "Z" to satisfy ANSI syntax when DoD 

WebSDR-assigned number is applicable. Other SDR 

report numbers are carried in the reference segment. 

WebSDR report number moved 

to REF segment – consolidated 

with other types of report 

numbers 

3. 1/N101/1200 Revise DLMS Notes as follows:

41 Submitter 

DLMS Note: Use to identify the DoDAAC of

organization submitting the SDR transaction. (The 

customer will be identified as the submitter unless 

using N101 Code Z6 or ZS.) 

Z6 Transferring Party 

DLMS Note: Use with BGR01 Code 47 to indicate 

the routing identifier of the action activity 

forwarding the SDR. (Identify the customer at 

2/N101/2800 Code LW.) 

ZS Monitoring Party 

DLMS Note: Use to identify the DoDAAC of the 

International Logistics Control Office (ILCO). 

(Identify the customer at 2/N101/2800 Code LW.) 

Clarification 
4. 2/REF01/0700 Revised DLMS note for qualifier “NN” to read:

NN Nonconformance Number 

DLMS Note: Use to identify the originator's SDR 

report control number. This will be the originator's 

system assigned number. When SDR was originated 

using the DOD WebSDR, this will be the webgenerated control number. Identify the originating 

system in REF03, e.g., WEBSDR, ADRS, ISDR, BSM, 

CDCS, AEPS, NSDRS, etc. Repeat the REF segment 

if more than one SDR report control number must be 

provided for the SDR.

SDR report numbers 

consolidated here - note 

expanded to provide clarification 

of intent 

5. 2/REF01/700 Added the following qualifier and DLMS note:

S2 Data Source 

DLMS Note: Use on SA SDR to identify Portal 

Submission Indicator indicating the activity 

submitting SDRs as authorized by SA customers, e.g., 

SA Customer Submission, STARR PC Submission, 

ILCO Submission (mailed copy submissions), Freight 

Forwarder Submission - as authorized by SA customer 

or Other Activity as authorized by SA customer. If 

other, use REF03 to provide an explanation. 

An ANSI data maintenance action will be taken to 

obtain a more appropriate code for use in a future 

version/release.

The SA Portal Submission 

Number is moved from the LQ to 

the REF to allow for 

identification of a narrative text 

in addition to the code when 

‘other’ is selected. 

6. 2/LQ01/1050 Deleted the following qualifier w/DLMS note:

KW Report Source Code

DLMS Note: Use on SA SDR to identify Portal 

Submission Indicator indicating the activity submitting 

SDRs as authorized by SA customers, e.g., SA Customer 

Submission, STARR PC Submission, ILCO Submission 

(mailed copy submissions), Freight Forwarder Submission 

- as authorized by SA customer or Other Activity as 

authorized by SA customer. 

An ANSI data maintenance action will be taken to obtain a 

more appropriate code for use in a future version/release.

Same as above. 

7. 2/N202/2900 Delete N202 Address data restructured to use 

distinct data fields (instead of 

address lines) per DoDAAF reengineering. 

8. 2/N301/3000 Revise N301 Note: 

DLMS Note: This equates to street address. Used 

when customer input for the reporting activity 

information or shipper's information is not available or 

differs from data extracted from the DODAAF. 

Same as above. 

9. 2/N401 & 

N404/4400 

Open N401 and N404: Same as above. 
N401 City Name 

N404 Country Code

 DLMS Note: Data element 1270, Code 85, Country 

and Activity Code, lists applicable code values. 

842A/R 

1. DLMS 

Introductory 

Notes 

Added the following ADC title:

- ADC 128, Revision for SDR Transaction 

Exchange 

Administrative 

PDC 132 changes are highlighted 

in the DS, but are not identified 

here. Refer to separate PDC 

documentation. 

2 1/BNR01/0200 Added the following qualifier and DLMS note:

CN Completion Notification 

DLMS Note: 

Use to indicate that action activity has closed the SDR record 

internally. (This may not mean that all associated actions have 

been completed.)

Allows ICP to provide identification 

of closed SDRs. 

3. 1/BNR02/0200 Deleted the following DLMS note:

DLMS Note: Use code to identify the DoD WebSDR 

generated control number for this SDR when applicable. 

Field size restricted to 11 positions. When not applicable,

Enter "Z" to satisfy ANSI syntax requirement. 

Additional report numbers are carried in the 2/REF/0700.

WebSDR report number moved 

to REF segment – consolidated 

with other types of report 

numbers 

4. 1/N101/1200 Revised DLMS note for qualifier “91” to read:

91 Action Party 

DLMS Note: 

Use to identify the Routing Identifier of the

organization providing the SDR response. 

GP Gateway Provider 

DLMS Note: 

Use to identify the Routing Identifier of the DAASC 

as the intended recipient for distribution or posting to 

the historical record under DOD WebSDR business rules. 

PK Party to Receive Copy 

DLMS Note: 

Use to identify the DoDAAC of the organization to 

receive a distribution copy of the SDR reply.

Clarification 

5. 1/N103/1200 Added the following qualifier and DLMS note:

10 Department of Defense Activity Address 

Code (DODAAC) 

Correction DoDAAC required 

for customer identification. 

6. 1/PER/1700 PER at 1700 opened and qualifiers and notes 

originally misplaced at position 4600 are moved up:

RZ Respondant. 

DLMS Note: Use to identify the action activity point 

of contact associated with this SDR Reply. An ANSI 

Correction. 
data maintenance request has been prepared to 

request a new data element 1270 code qualifier.

SE Service Organization 

DLMS Note: Use to identify the ILCO POC. An ANSI 

data maintenance request has been prepared to 

request a new data element 1270 code qualifier.

Followed by standard PER segment notes. 

7. 2/REF01/0700 Revised DLMS note for qualifier “NN” to read:

NN Nonconformance Number 

DLMS Note: Use to identify the originator's SDR 

report control number. This will be the originator's 

system assigned number. When SDR was originated 

using the DOD WebSDR, this will be the webgenerated control number. Identify the originating 

system in REF03, e.g., WEBSDR, ADRS, ISDR, BSM, 

CDCS, AEPS, NSDRS, etc. Repeat the REF segment 

if more than one SDR report control number must be 

provided for the SDR. 

(6K, Zone deleted) 

PO Purchase Order Number 

SDR report numbers 

consolidated here - note 

expanded to provide clarification 

of intent. 

 

Code 6K deleted – no current 

requirement. 

PO Number perpetuated from 

report if this was a controlling 

number for the order. 

8. 2/LQ01/1050 Revised DLMS note for qualifier “D” to read:

D Court Document Type Code 

DLMS Note: Use to identify the Type Document 

Code. This is a DLA unique data element. Code list is 

available in DLAH 4140.4, CDCS Handbook. 

An ANSI data maintenance action will be taken to 

obtain a more appropriate code for use in a future 

version/release. 

Administrative 

9. 2/AMT/2730 Code ECD, Postage Expenses, deleted Postage requirement is obsolete. 

10

. 

2/NTE01/3500 EAT, Asset Disposition deleted Separation of notes for different 

purposes created unnecessary 

workload for programming. 

Reply remarks merged under 

single field. 

11

. 

2/DTM01/3600 118, Requested Pick-up 

deleted 

446 Replacement 

DLMS Note: 

Use to identify the estimated date of reshipment of 

replacement material. 

No current requirement for this date. 

Similar capability is provided using 

reply code 149 with number of days 

in NDA04 

Note reworded for clarification. 
311 Latest Receiving Date/Cutoff Date 

DLMS Note: Requested material or documentation must 

be received by this date. 

Dates associated with codes 114 and 

117. 

12

. 

2/REF01/3700 Added the following qualifier and DLMS note:

08 Carrier Assigned Package Identification Number

DLMS Note: Use to identify the commercial carrier 

assigned number for material return. 

QE Replacement Customer Reference Number 

DLMS Note: 

Use to identify the document number for reshipment of 

replacement material when different from the original 

document number. 

16 Military Interdepartmental Purchase Request (MIPR) 

DLMS Note: Use to identify the MIPR for disposal of 

hazardous material.

Additional qualifier made available 

to provide requested functionality 

13

. 

2/N101/4100 Added the following qualifier and DLMS note:

LW Customer 

DLMS Note: Use to identify the SDR report initiator 

by DODAAC/MAPAC and/or clear text address (if not 

identified by 1/N101/1200/ZD) 

Repeats customer identification 

from the submission when reply 

is directed to other 

organization/system. 

14

. 

2/N103/4100 & 

N101 

Added the following qualifier and DLMS note:

A2 Military Assistance Program Address Code 

(MAPAC) 

DLMS Note: Use to identify the structured MAPAC. 

BT Bill To

DLMS Note: Use to identify the billing DoDAAC for 

disposal of hazardous material. 

X1 Mail to

DLMS Note: Use to identify the mailing address for 

documentation confirming disposal of discrepant 

material.

Same as above 

Bill To DoDAAC provided for 

HAZMAT 

15

. 

2/N202/2900 Delete N202 Address data restructured to use 

distinct data fields (instead of 

address lines) per DoDAAF reengineering. 

16

. 

2/N301/3000 Revise N301 Note: 

DLMS Note: This equates to street address. 

Same as above. 

17

. 

2/N404/4400 Open N404 and add DLMS Note:

Country Code

Description: Code identifying the country 

DLMS Note: Data element 1270, Code 85, Country 

and Activity Code, lists applicable code values. 

Same as above. 
18

. 

2/PER01/4600 Added the following qualifier and DLMS note:

IC Information Contact 

DLMS Note:Reserved for future use. 

Previously assigned codes moved 

up to position 1700. Future 

enhancement would allow POC 

information associated with the 

ship-to location. 

RZ, Respondant, and SE, Service 

Organization, were moved to 

table one. 

19

. 

2/LQ01/4650 Revise DLMS note: 

HD Discrepancy Status or Disposition Code 

DLMS Note: Use up to three repetitions to identify 

disposition/status. Also referred to as Reply Code. 

Clarification 

 
The following additional revisions are provided for the 842A/W to facilitate unique 

identification of discrepant items. 

1. 2/HL03/0100 Added the following qualifier and DLMS note:

I Item 

DLMS Note: Use to identify UID data consistent with 

UID data requirements. The UID data is carried in the 

REF and N1 segments; no other segments are used i 

n the UID loop. Use a separate UID loop for each 

item. Skip this level when not applicable.

Use of a new HL loop for each 

item simplifies the mapping for 

the individual UID data 

elements in the REF segment. 

2. 2/NCD/2300 Replace existing DLMS note at segment level: 

DLMS Note: Begin a new NCD loop for each UID 

loop. 

Clarification. Used for ANSI 

syntax. 

3. 2/NCD03/2300 Revise DLMS note: 

DLMS Note: Use as a counter to satisfy ANSI syntax. 

Cite numeric 1 EXCEPT where additional NCD loops 

are used to report multiple incorrect (wrong) items or 

missing component parts or when providing unique 

identification of discrepant items. In these instances, 

Increase incrementally by 1 for each wrong item, 

missing component, or uniquely identified item 

identified

Clarification. Used for ANSI 

syntax. 

4. 2/REF/2600 Add the following segment level notes. 

1. Use in 2/HL/0100 UID loop to provide UID 

information. Repeat the REF segment within each 

UID loop to identify relevant UID information. 

2. This transaction will support item identification 

based upon the UII or the serial number. Data 

elements associated with the UII may be identified 

separately. Use the appropriate data elements to 

satisfy the desired functionality.

Clarification. Allows for 

repetition of the REF segment 

for each applicable data 

element. Reduces the use of 

the composite element and 

removed duplication of batch 

number.

5. 2/REF01/2600 Revise UID note at data element level and make the 

following note revisions. 

2. Use codes separately or in combination, to identify 

appropriate information for unique item tracking (UIT) 

or reporting under UID policy. 

PM Part Number 

2. Use in UID loop to identify the applicable part 

number. This will be the original part number when 

associated with the UII. An ANSI data maintenance 

request has been prepared to request a new code 

qualifier for Original Part Number for future use. 

QW New Part Number 

Use in UID loop to indicate the current part number 

when different from the original part number 

identified in the UII.

Clarification.
(2) Revise Reporting of Supply Discrepancies, DLA 4140.55, et al, as follows:

 (a) Revise paragraph E.2.b(5) to provide better instructions for researching 

suspected shelf-life discrepancies prior to submission.

 (5) Report receipt of materiel for which the shelf-life either has expired (Type I nonextendible item) or the inspect/test date has lapsed (Type II extendible item), regardless of dollar value. 

 (a) For Type I DOD and GSA managed items: Submit an SDR. 

 (b) For Type II DoD-managed items: Prior to submitting an SDR, access the DoD 

6. 2/REF04/2600 Add new qualifier and note.

T0 Dealer Type Identification 

DLMS Note: Use to provide the UII Type, e.g., VIN, 

UID1, UID2, etc. Use with REF01 Code U3. An ANSI 

data maintenance request has been prepared to 

request a new code qualifier for UII Type for future 

use.

Moved from NCD segment. 

7. 2/N101/2800 Add note 2. 

IAT Party Executing and Verifying 

DLMS Note: 

1. Use to indicate the Enterprise Identifier (EID) 

responsible for the UII. An ANSI data maintenance 

request has been prepared to request a new code 

qualifier for Enterprise Identifier for future use. 

2 The value of the UID Issuing Agency Code (IAC) 

may be derived from the qualifier used for the 

Enterprise Identifier. Use only N103 qualifiers for 

which a corresponding IAC is noted.

Clarification. 

8. 2/N103/2800 Delete DLMS note at N103 and modify notes 

associated with the following qualifiers.

1 D-U-N-S Number, Dun & Bradstreet 

DLMS Note: Corresponds to IAC 'UN'. 

8 UCC/EAN Global Product Identification 

Prefix 

DLMS Note: Corresponds to IAC '0-9'.

10 Department of Defense Activity Address 

Code (DODAAC) 

DLMS Note:

1. Use with N101 code 91. 

2. IAC for DoDAAC will be provided when

available.

33 Commercial and Government Entity (CAGE)

DLMS Note: Corresponds to IAC ‘D'.

41 Telecommunications Carrier Identification 

Code 

DLMS Note:

Corresponds to IAC 'LB' (ANSI T1.220, 

Commercial Telecommunications 

Standards) 

Clarification. 
Shelf-Life Extension System (SLES) through the DoD Shelf-Life Program website at: 

http://www.shelflife.hq.dla.mil/ or through the shelf life program secure site if you have a .mil 

address. 

 (c) Type II items requiring laboratory test: Query the DoD Quality Status Listing 

(QSL) to determine if the specified Type II item is listed as having passed the required laboratory 

testing and has been extended. Items that are listed on the QSL as passed may be extended and 

remarked accordingly if the item has been stored in accordance with its storage standard. For items 

not on the QSL, prior to submitting a SDR, contact the DLA CALL CENTER at 1-877-DLA-CALL if 

the shipment originated from a DLA Storage Activity. 

 (d) Type II items requiring visual inspection: Query the Materiel Quality Control 

Storage Standards for the specified Type II item, perform visual inspection in accordance with the 

items storage standard, and extend and remark if the item has been stored in accordance with its 

storage standard. If the item fails the visual inspection, dispose of IAW local procedures. 

 

 (e) For Type II GSA-managed shelf-life items - Prior to submitting an SDR, 

contact the GSA Shelf-Life HOTLINE at 1-209-547-8613 to determine if the inspect/test date has 

been extended. 

 (b) Include new paragraph E.2.d. Discrepancies in Unique Identification Data (and 

renumber existing subsequent paragraphs). 

d. Discrepancies in Unique Identification Data. Report discrepancies involving 

unique item identification under Unique Item Tracking (UIT) program requirements or as 

contractually required under Unique Item Identification (UID) program policy. 

Discrepancies may be related to the packaging label, including automated information 

technology (AIT); the item marking, including AIT; supply documentation; the due-in 

record; and/or a mismatch between the item and any of these. The elements which may 

comprise unique identification are: unique item identifier (UII), UII type, issuing agency 

code, enterprise identifier (or manufacturer’s CAGE), part number (original or current), 

serial number, and 

Batch/Lot Number. The application of these elements will vary according the multiple 

factures such as the type of item, the specific contract requirements, and the degree of 

implementation. 

(3) Revise Reporting of Supply Discrepancies, DLA 4140.55, et al, Enclosure 1, 

Definitions, as follows:

Enterprise Identifier (EID). An activity identifier code assigned to the entity that is 

responsible for assigning the unique item identification to an item. EID codes are uniquely 

assigned by a registration (or controlling) authority (e.g., Dun & Bradstreet’s Data Universal 

Numbering System (D-U-N-S), Uniform Code Council (UCC)/European Article Number 

(EAN), Commercial and Government Entity (CAGE) code, NATO CAGE (NCAGE) Code. 

Issuing Agency Code (IAC). The IAC represents the registration authority that issued the 

enterprise identifier. The value for the IAC is assigned by the Registration Authority for 

ISO/IEC 15459-2, Registration Procedures. The current Registration Authority of ISO/IEC 

15459-2 is NEN – Nederlands Normalisatie-instituut. The IAC can be derived from the data 
qualifier for the enterprise identifier and does not need to be marked on the item or carried in 

the DLMS transaction. 

Unique Identification (UID) of Items. The application of a set of data elements that is 

globally unique and unambiguous, ensures data integrity and data quality throughout life, 

and supports multi-faceted business applications and users. 

Unique Item Identifier (UII). An identifier used in unique item tracking programs to 

uniquely identify an individual asset used within DOD. The UII may be derived from a DODapproved commercially-accepted identification methodology [e.g., Vehicle Identification 

Number (VIN)] or a composite structure defined by the DOD [refer to UID Construct 1 and 

UID Construct 2]. Formation of the UII relies upon two primary methods of serialization: 

(1) Serialization within the enterprise and (2) Serialization within the original part number of 

the enterprise. Regardless of which numbering system is used, the UII must include the 

Enterprise Identifier. Refer to OSD policy and supporting documentation for specific 

guidance at http://www.acq.osd.mil/UID/index.html. Refer to MIL-STD-130L for specific 

guidance marking of U.S. Military property.

Unique Item Identifier (UII) Type. A designator that identifies the specific structure and 

syntax of a type of UII. Specific examples of the UII Type are: Vehicle Identification Number 

(VIN), UID Construct I (UID1), UID Construct I (UID2).

Unique Identification (UID) Construct I. This is a concatenated UII based upon 

serialization within the enterprise. The UII contains the IAC, EID, and serial number.

Unique Identification (UID) Construct II. This is a concatenated UII based upon 

serialization within the part. The UII contains the IAC, EID, original part number, and serial 

number. For legacy material, a subset of UID Construct II (referred to as Construct IIA) 

contains a batch, lot number, or other production run number required for uniqueness of the 

serial number within the part.

(4) Revise Reporting of Supply Discrepancies, DLA 4140.55, et al, Enclosure 2, 

Instruction for Preparation of Standard Form (SF) 364, as follows:

Item 1 Date of Preparation. Use month, day, and four-position year format for the date the 

reporting activity prepares the SDR." 

(5) Revise Reporting of Supply Discrepancies, DLA 4140.55, et al, Enclosure 4, 

Typical Shipping and Packaging Discrepancies Listed by Discrepancy Code, as follows:

U01 Unique identification data on label missing or damaged/unreadable 

U02 Unique identification data on item missing or damaged/unreadable 

U03 Unique identification data on supply documentation missing or 

damaged/unreadable 

U04 Unique identification data not provided on shipping notice 

U05 Non-conformance to unique identification requirements under terms of 

contract 
U06 Multiple containers without separate unique identification data listings 

U07 Mismatch between unique identification data on item and label 

U08 Mismatch between unique identification data on item and shipping 

documentation 

U09 Mismatch between unique identification data on item and due-in or 

shipping notice. 

U10 Mismatched or missing unique identification discovered upon opening a 

sealed vendor’s pack. 

U11 Material unidentifiable; stock number missing or damaged 

U12 Duplicate unique identification 

(6) Revise Reporting of Supply Discrepancies, DLA 4140.55, et al, Enclosure 6, 

Typical Action Activity Responses Listed by Disposition Status Code, as indicated in the 

attachment 1.

5. REASON FOR CHANGE 

a. The 842 transaction mapping is evolving as the Components and DAASC attempt to 

implement it. This change represents further fine-tuning of the transaction data contents to 

accommodate both standard and Component unique requirements. 

b. Additional Disposition/Status Codes were identified by DLA while preparing for 

transition to DLMS SDR transaction exchange. The 300-series codes are already used 

internally in DLA. The additional 100-series codes represent replies which are commonly 

used, but not accommodated in the current list. 

c. The update to the instructions for preparation of SDR are provided for clarification. 

Some users have misinterpreted this date as the date the SDR is received at the action activity.

d. OSD policy for the UID states that the Unique Item Identifier shall be the primary 

pointer or key data element for the AIS in all computational functions including inventory 

acceptance, item accountability, storage, issue, receipt, valuation, maintenance, and disposal. 

In support of this requirement, future logistics transactions must identify the UII. This change 

is required to incorporate the UII as currently defined within DLMS logistics exchange 

transactions and provide maximum flexibility by authorizing all inclusion of all the data 

elements which may be associated with unique identification.

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports DLMS implementation and Business Initiatives Council 

(BIC) SDR Transformation Initiative. 

b. Disadvantages: None identified. 
7. IMPACT: 

 a. Data Content/Procedures: The capability to provide SDRs in the DLMS format 

must be incorporated in the Component system design. This change supports Component data 

requirements. For January 2005 implementation, DSS will use the basic 842 format as 

reflected in the DS, but some data content will be carried in note fields to minimize data base 

changes. A future revision of DSS will address defining additional specific data elements. 

b. Publication(s): 

 (1) The Federal IC 842A 

 (2) DOD 4000.25- M, DLMS