Attachment ADC 358, Page 1 

ADC 358 

SDR Transaction Content/Business Rule Revisions/ 

Clarification and Administrative Updates 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Defense Logistics 

Management Standards Office (DLMSO), Ms. Ellen Hilert, Chair, Supply Process Review 

Committee and DoD SDR System Administrator, 703-767-0676; DSN 427-0676; or, E-Mail: 

Ellen.Hilert@dla.mil. 

2. FUNCTIONAL AREA: Supply/DoD WebSDR 

3. REFERENCES:

4. PROPOSED CHANGE: Revisions subsequent to PDC staffing are identified in yellow 

highlighting. 

a. Description of change: This change addresses multiple issues associated with the 

content of SDR transactions and associated guidance, where applicable, as follows:

(1) Updated mapping and guidance for use of various types of materiel identification 

used in SDR transactions. 

(2) Removal of obsolete, unused data elements established as placeholders during 

DLMS development. 

(3) Inclusion of the vendor shipment number on the SDR reply format. 

(4) Expansion of reply remarks from 500 to 750 characters. 

(5) Miscellaneous updates to DLMS notes to provide clarification of expected data 

content. 

(6) Assignment of a new reply code value and revision to the text explanation for 

another, as indicated below. 

(7) WebSDR routing rule for Discrepancy Code T8 for incorrect part number to 

require routing to the item manager. The definition of T8 is also expanded for clarification. 

(8) New business rules to updated vendor shipment information contained in SDR 

replies to be used for data base update without forwarding to the customer applicable to SDRs 

submitted with Action Code 3B (no reply to submitter required). 

(9) Clarification of use of a “pseudo shipment number” on SDRs prepared by 

distribution depots for new procurement receipts where the actual vendor shipment number is not 

available. 

(10) Opening of additional materiel identification data element mappings to 

accommodate mixed use of data elements and prevent XML transaction failure. 
Attachment ADC 358, Page 2 

(11) Add clarification of responsibility for monitoring of the SDR program applicable 

to transshipper-prepared SDRs. 

(12) Administrative corrections to the DLMS Supplements. 

b. Procedures: Yellow highlighting is used to identify changes subsequent to initial staffing 

of the proposal. 

(1) Revise DoD 4000.25-M, Volume 2, as shown in Enclosure 1. This includes 

guidance for construction and inclusion of pseudo shipment numbers and data content on SDR 

replies. It also updates the guidance for management evaluation. 

(2) New Reply Code 308. This code is reserved for deferred implementation. This 

code is intended to be used by Distribution Depots on SDR replies to DLA under DLA 

Continuous Process Improvement (CPI)-directed process changes. A joint implementation date 

will be coordinated separately; the new code will not be published/made available until the 

implementation schedule is known and procedures confirmed. The new code will be published 

as an addendum to this ADC. It is currently envisioned that procedures for Reply Code 308 will 

be comparable to other 300-series reply codes. Under this process, the SDR reply will be sent to 

the customer (and other distribution copy addresses per the original report or Component rules if 

applicable), and to the action activity now responsible for disposition. The distribution depot 

will designate the Routing Identifier of the new action activity (via pop-up window in WebSDR 

or as the “To” address in the DLMS 842A/R transaction). When using Reply Code 308, the 

distribution depot will record the results of their research in the remarks block. 

308 - Discrepancy confirmed; SDR forwarded for disposition by DLA as 

indicated.

(3) Revise Reply Code 144. The text for Code 144 is revised to clarify intended use. 

144 – Recorded for information only. No financial action taken. 

(4) Establish WebSDR routing rule for Discrepancy Code T8 for Web-entered 

SDRs to route these SDRs to the manager if known. Do not allow customer to over-ride by 

directing the SDR to the shipping activity. SDR transactions prepared outside WebSDR must be 

properly routed by the submitting application. Revise text for Discrepancy Code T8: 

T8 - Incorrect part number (suspected shipment of unauthorized part number 

for NSN). 

(5) New business rules for SDR Replies associated with Action Code 3B 

(Discrepancy reported for corrective action and trend analysis. No reply required). New 

business rules require Components to prepare historical reply transactions even though a reply is 

not required by the customer when shipment information required for metrics as contained in the 

original SDR is incorrect or left blank. Under this requirement, Components using automated 

SDR applications would generate historical replies (Transaction Set Purpose Code 49) when the 

original SDR content, such as the applicable contract number, vendor CAGE, shipment number, 

is incorrect or blank. This business process is not available to WebSDR responding activities at 
Attachment ADC 358, Page 3 

this time. This will update the WebSDR metrics table used to produce reports without 

forwarding a copy of the reply to the customer. These replies may be system generated to 

reflect valid shipment information and Reply Code 144, Recorded for information and trend 

analysis (as modified by PDC 356). Additional data elements for the shipping activity and the 

owner/manager are being made available in the reply transaction and WebSDR direct input to 

capture shipment information for where not identified or incorrect on the original submission. 

(6) WebSDR Input Screen Adjustments: Data entry fields shall be made available 

in the SDR reply for the contract number, shipping activity, and owner/manager. In addition, the 

field name for the shipping activity must be clarified in the SDR submission screen. Currently 

the web screen says “SHIPPING: Shipper’s Name.” Revise to read Shipping: Shipping 

Activity.” 

(7) Revise DLMS Supplement 842A/W, SDR, Follow-up, Correction, 

Cancellation, & Reconsideration Request, as shown in Enclosure 2. 

(8) Revise DLMS Supplement 842A/R, SDR Reply, as shown in Enclosure 3. 

5. REASON FOR CHANGE: 

a. Clarification of guidance for preparation of SDRs, SDR replies, and use of SDRs in 

management evaluation. 

b. Requirements for SDR data content has matured and obsolete data elements should be 

removed from the DLMS format to eliminate a source of confusion. 

c. Notes better identify field length and availability of data elements. 

d. Administrative updates are identified including corrections to the SDR reply format to 

remove erroneous points of contact that are only applicable to the report format. 

e. Reply Code. DLA requests new Reply Code 308 in addition to existing Reply Code 307. 

Having two distinct codes will provide a means of distinguishing which SDRs are forwarded by 

the distribution depot to DLA without review (e.g. SDRs applicable to vendor shipments, but 

mistakenly routed to a depot) and those which have been confirmed by depot research, but 

require further review by the ICP in order to provide materiel disposition and financial resolution 

to the customer. The new code may be used for metrics and clarification of the status of the 

SDR. This supports CPI recommendations which define which SDRs must be referred to the 

manager for resolution. Depots will be able to provide research/findings on the SDR reply which 

will be made available to the customer and the manager. 

f. Business Rules for Action Code 3B. The WebSDR data base (metrics table) cannot 

provide appropriate results for management reports and queries without valid information 

regarding the shipment. Users of the Action Code 3B are often transshippers who do not have or 

are not required to populate all the SDR data content. This type of user doesn’t want reply 

transactions since no immediate action is needed from the responding activity. Existing 

capability for creation of a historical reply will allow for updating the data base without 

overloading the customer with unnecessary replies. Additional data elements for the shipping 
Attachment ADC 358, Page 4 

activity and the owner/manager are being made available in the reply to capture shipment 

information. 

g. Incorrect Item. DLA requested WebSDR and AFSAC, which are the primary sources of 

T8 discrepancies, ensure that these SDRs are sent directly to the manager. This rule is applicable 

to all Components. This will eliminate forwarding delays since these SDRs are not worked by 

the shipping activity and so would always require forwarding. 

h. Reply Remarks Field Length. Currently systems with higher or no character length for 

SDR responses are sending responses that cannot be fully transmitted through DAASC. This 

results in the customer receiving incomplete disposition on SDRs. This change will expand the 

available length within WebSDR to better match that available in most Component SDR 

applications. Since reply remarks may contain detailed information, such as a clear text ship-to 

location, it is important to allow the extra space which better utilizes the capability already 

available to most applications. 

i. WebSDR Screen Adjustments. The use of the term “shipper’s name” is misinterpreted 

by transshippers due to differences between supply and transportation terminology. The goal is 

to capture the actual shipping activity such as the distribution depot, retail base for lateral 

movements, or the vendor’s CAGE for direct vendor delivery and new procurement. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Allows new implementers and existing users to better understand the 

transaction content requirements. Addition of the new reply codes and business rules for Action 

Code 3B will improve development of metrics/statistics for SDR management reporting 

capabilities. 

b. Disadvantages: None identified. 

7. IMPACT: 

a. DLMS Transactions: Updates are identified for the 842A/W and 842A/R DLMS 

Supplements. Applications must ensure that changes will not cause transaction failure. 

b. New DLMS Data Content: There are no new data elements established in this PDC. 

However, SDR Completion Date (in lieu of shipper’s completion date) s deferred for future 

implementation under this revised name. The SDR Reply Code set is modified as follows: Reply 

Code 308 is approved, but deferred. The text explanation associated with Reply Code 144 is 

revised. 

c. Changes/Removal to Existing Data Content: Field length, code values, and mapping 

for multiple DLMS data elements are modified as indicated above and in Enclosures 2 and 3. 

Three data elements applicable to the report format will be made available in the reply format: 

contractor-assigned shipment number, owner/manager Routing Identifier, and shipper 

identification. This change will also remove multiple data elements from the SDR report and 

reply. (Where the SDR is the only identified requirement for these elements, the data element 

will be removed from the DLMS dictionary.) 
Attachment ADC 358, Page 5 

(1) The following data elements will no longer be associated with the SDR report 

(X12 qualifier name provided where “creative” mapping was used due to lack of an equivalent 

data element in X12): 

 Quality Assurance Point of Contact (POC) 

 Project Code 

 Date Packed (In UID Loop) 

 Shelf Life Expiration (In UID Loop) 

 NSN of Correct Container (X12 Ocean Container Number) 

 NSN of Incorrect Container (X12 Container Sequence Number) 

 Cubic Container Volume Received (X12 Gas Volume) 

 Cubic Container Volume Requested (X12 Water Volume) 

 UII Type (X12 Dealer Type Identification) 

 New Part Number (in UID Loop) 

 Enterprise Identifier (in UID Loop) 

 Internal ICP Costs (X12 Operating Expenses) 

 Total Costs 

 Container Replacement Cost 

 Action Office (X12 Action Party) 

(2) The following data elements will no longer be associated with the SDR reply (X12 

qualifier name provided where “creative” mapping was used due to lack of an equivalent data 

element in X12): 

 Quality Assurance (POC) 

 Purchase Order Number 

 Gain or Loss Indicator Code 

 Quantity in Float 

 Quantity on Hand 

 Total Inventory 

 Book Inventory 

 Packaging Instructions (type of note text) 

 Date Requested for Cataloging Action 

 Causative Research Indicator (X12 Cause Lookup) 

 Changed by POC 

 Forwarder Contact (POC) 

 Preparer (POC) 

 Report Preparer (POC) (mapped to two locations) 

 Requestor (POC) 

 Submitting Contact (POC) 

d. Implementation Schedule: 

(1) DLMS Supplement changes are effective upon publication. Changes are approved 

for phased implementation with the following exceptions. 
Attachment ADC 358, Page 6 

(a) Reply Code 308 will be deferred until a preferred implementation date is 

identified by DLA. The text explanation revision for Reply Code 144 is effective immediately. 

(b) WebSDR screen updates (other than expanded reply remarks) are 

requested for December 2010. 

(c) The expanded field length for reply remarks will be made available for use 

via DLMS transactions and WebSDR screen input June 2011.

(d) Business rule updates associated with requested Action Code 3B shall be 

implemented as soon as feasible within Component applications/processes. 

(2) DoD Components should coordinate with DAASC for implementation of XML 

schema updates. 

e. Publications: Potential impact on updating the DTR for inclusion of management 

evaluation requirements. 
Enclosure 1, DLMS Manual, page 1 

Enclosure 1, DoD 4000.25-M, Volume 2, 

1. Chapter 17, Supply Discrepancy Reporting. Update the following paragraphs as shown in 

bold italics:

 a. Insert guidance for pseudo shipment numbers: 

C17.3.1.2. Shipment Information. SDRs must contain a document number. Identify the original 

requisition document number when known; otherwise a constructed document number is 

required. A constructed document number identifying the receiving distribution depot is 

required for depot receipts reported electronically including new procurement receipts. A 

constructed document number may also be prepared by a transshipper based upon the CCP or 

port DoDAAC. Additional information, such as transportation numbers (TCN, bill of lading 

number, etc.) or procurement information (procurement instrument number, line item number, 

vendor shipment number) shall be provided in accordance with the DS DLMS transaction

format/SF 364. When reporting new procurement receipts, the distribution depot shall site a 

“pseudo shipment number,” equivalent to that cited on the receipt, when the actual vendor 

shipment number is not available from shipping documentation. The pseudo shipment 

number will be constructed to identify the receiving depot and a constant 01 (that is, the serial 

number will not be incremented; therefore, the pseudo shipment number will not be unique). 

In order to systemically identify pseudo shipment numbers the third position must be numeric 

(vendor assigned shipments use a three digit alpha prefix to identify the vendor). For 

example, pseudo shipment numbers prepared by Distribution Depot San Joaquin, California 

(DDJC), will be reported as DD1JC01. 

b. Insert guidance for incorrect part (renumber subsequent paragraph): 

C17.3.2.10. Technical Data. Report missing and/or incomplete item technical information, e.g., 

name plate, operating handbook, logbook, precautionary markings, warranty data, engineering 

drawings and associated lists, specifications, standards process sheets, manuals, technical 

reports, catalog item identifications, and related information that are missing, illegible, 

incomplete and/or incorrect regardless of dollar value. When reparables are returned and the 

appropriate historical information/documentation, operator/maintenance logbooks, engine oil 

analysis, etc., as required by Government regulations, and/or technical manuals are not included, 

the receiving activity shall submit an SDR regardless of dollar value. Any additional costs 

incurred by the repairing depot/arsenal because of the missing data shall be charged to the 

originating activity. Submitter will ensure that the specific description of what documentation is 

missing is included in the remarks section. Report as an incorrect part when technical data 

markings for the part number appear to be inconsistent with the specified NSN. Incorrect 

part discrepancies shall be submitted directly to the item manager. (Do not use to report an 

incorrect item received as described below. Refer to W-series discrepancy codes for most 

appropriate discrepancy code.) 

 c. Clarify guidance for action activities preparing SDR replies: 

 C17.3.11.1.3. Replies. Responsible activities shall reply to SDRs under DLMS by 

submission of a DS 842A/R to DAAS/WebSDR or direct WebSDR input. Pending 

implementation of DLMS, other previously authorized approved SDR response formats may be 
Enclosure 1, DLMS Manual, page 2 

used indicating the appropriate disposition, e.g., acknowledgment of the report, disposition of the 

materiel, validation of the report with authorization of financial adjustment, and/or instructions 

for repackaging, repair, or other types of corrective action. SDR replies must contain the 

appropriate discrepancy code consistent with all information provided by the customer. This 

may require updating of the discrepancy codes used by the customer to assign the appropriate 

discrepancy code for the scenario described in the SDR remarks. Pending final resolution, the 

action activity may identify the interim disposition/status using up to three codes 

disposition/status (reply) codes. Applicable codes are available published from in the DLMS 

Logistics Qualifier list. If no coding exists to specifically identify the reasons for the delay, 

indicate Reply Code 137 and provide a clear-text explanation. Supplemental information is 

provided in accordance with the DS/SF 364. Shipment information applicable to direct vendor 

deliveries, new procurement, etc., must be completed by the action activity where incomplete or 

inaccurate on the customer’s original report. This includes identification of the shipping activity 

or vendor (by CAGE), contract number, and identifying shipment numbers. DLMS compliant 

applications must also ensure that direct vendor delivery shipments are identified by Document 

Type Code 6 on the SDR reply, regardless of what the customer originally designated. 

Historical replies (transactions citing Transaction Set Purpose Code 49) shall be used to fulfill 

these requirements where the submitter indicated that an SDR reply was not required. 

 d. Update guidance for management evaluation: 

C17.4. MANAGEMENT EVALUATION

 C17.4.1 Purpose. The supply discrepancy reporting program is designed to promote 

evaluation, correction, and improvement of logistics operations. To accomplish this objective, 

discrepancies as specified in this publication must be reported and investigated in accordance 

with established policies and procedures. DoD Components shall institute SDR quality 

programs that will include periodic reviews to assess the accuracy and quality of work processes 

applicable to supply discrepancy processing. In addition, DoD Components shall require, as a 

minimum, semi-annual summary reporting to an appropriate headquarters for review and 

analysis. The DoD Components unable to support the full scope of the required data collection 

under legacy systems shall incorporate this reporting requirement under business system 

modernization efforts. The DoD WebSDR management reports and canned queries may be 

used to supplement internally-prepared reports. DoD Components and USTRANSCOM shall 

monitor SDR program performance applicable to transshipper SDRs. Data collected must be 

sufficient to enable monitoring activities to: 

 C17.4.1.1. Identify trends 

 C17.4.1.2. Establish volume and dollar values of SDRs. 

 C17.4.1.3. Bring management attention to problems with shipping activities as 

necessary. 

 C17.4.1.4. Prevent recurrence of discrepancies. 

 C17.4.1.5 Measure quality and responsiveness of action activities. 
Enclosure 1, DLMS Manual, page 3 

2. Appendix 4, Instructions for Preparation of Standard Form 364: 

 a. Delete the following paragraph from Item 12, Remarks:

Information Contact. Include name and communication numbers, e.g., DSN and commercial 

telephone numbers, facsimile number, and E-mail address of the person to be contacted for 

additional information if different from that entered in Item 14a. 
Enclosure 2, SDR Report, page 1 

Enclosure 2, DLMS Transaction: Standard SDR, Follow-up, Correction, Cancellation, 

& Reconsideration Request 

# Location DS 842A/W 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 358 to DLMS Introductory note 5: 

- ADC 358, SDR Transaction Content/Business Rule 

Revisions/Clarification

Identifies DLMS Changes 

included in the DLMS 

Supplement 

2. 1/PER01/1700 Remove qualifier “QA” and note:

QA Quality Assurance Contact 

DLMS Note: Use to identify an alternative point of contact when 

reporting a product quality deficiency or expired shelf life 

discrepancy.

This is a secondary POC. 

The requirement was based 

upon original SF 364 

instructions. This secondary 

POC was never 

implemented by ICP 

applications and is no longer 

considered necessary. 

Corresponding change will 

be made in the DLMS 

manual 

3. 2/LIN02/0200 Revise note:

ZZ Mutually Defined 

DLMS Note: 

1. Use to identify material by other than NSN or part number 

(includes management control number or 

locally assigned material identification control numbers). 

2. Packaging Discrepancies reported by transshippers may use 

“UNKNOWN” or “MIXED” when specific materiel identification 

is not available or the shipment level SDR applies to mixed 

content. 

3. For ZZ: WebSDR field length = 50 15

Clarification and correction 

of the field length. 

Staffing Note: Components 

should provide comment if 

there is a known 

requirement for a field 

length longer than 15. 

4. 2/LIN04/0200 Add data element level note and revise qualifier level notes:

Federal Note: Use to further identify an item. Use multiple 

Product/Service ID pairs as needed. 

DLMS Note: The sequence of data content for secondary 

materiel identification is dependent upon the applicable primary 

materiel identification. The referred sequence of secondary 

information is: end item description or next higher assembly 

(applicable only to SA product quality) part number; 

manufacturer’s CAGE; nomenclature. However, part number, 

manufacturer’s CAGE, and nomenclature may be cited in any 

order without causing transaction failure. 

CN Commodity Name 

DLMS Note: 

1. Use to identify the nomenclature associated with the item 

Clarification. 

Under original DLMS 

design, the mapping of 

materiel identification 

values was unspecified. As 

design evolved, new 

qualifiers were added and 

made available without 

assigning a specific location. 

To ensure that transactions 

do not fail, systems must be 

capable of receiving these 

values regardless of location 

in the LIN. This is required 

to prevent re-programming 

within various SDR 

applications which would 
Enclosure 2, SDR Report, page 2 

# Location DS 842A/W 

Revision 

Reason 

identified above. 

2. For CN: WebSDR field length = 13 25.

MG Manufacturer's Part Number 

DLMS Note: 

1. Use to identify the part number when NSN is also provided

primary materiel identification is previously identified. 

2. For MG: WebSDR field length = 32. 

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note: Use to identify manufacturer associated with a

previously identified part number identified above. 

require a synchronized 

implementation without a 

gain in functionality. 

Reprogramming is not 

envisioned for this change – 

this is primarily to 

accommodate XML 

applications where lack of 

specific LIN mapping has 

caused transaction failure in 

the past. 

Field length for commodity 

name/nomenclature was 

miss-identified in the current 

DLMS supplement. 

5. 2/LIN06/0200 Add data element level note and revise qualifier level notes:

DLMS Note: The sequence of data content for secondary 

materiel identification is dependent upon the applicable primary 

materiel identification. The referred sequence of secondary 

information is: end item description or next higher assembly 

(applicable only to SA product quality) part number; 

manufacturer’s CAGE; nomenclature. However, part number, 

manufacturer’s CAGE, and nomenclature may be cited in any 

order without causing transaction failure. 

CN Commodity Name 

DLMS Note: 

1. Use to identify the nomenclature associated with the item 

identified. 

2. For CN: WebSDR field length = 13 25.

MG Manufacturer's Part Number 

DLMS Note: 

1. Use to identify the part number when primary materiel 

identification is previously identified. 

2. For MG: WebSDR field length = 32. 

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note: Use to identify manufacturer associated with a 

previously identified part number.

Same as above. 

6. 2/LIN08/0200 Add data element level note and revise qualifier level notes:

DLMS Note: The sequence of data content for secondary 

materiel identification is dependent upon the applicable primary 

materiel identification. The referred sequence of secondary 

information is: end item description or next higher assembly 

Same as above. 
Enclosure 2, SDR Report, page 3 

# Location DS 842A/W 

Revision 

Reason 

(applicable only to SA product quality) part number; 

manufacturer’s CAGE; nomenclature. However, part number, 

manufacturer’s CAGE, and nomenclature may be cited in any 

order without causing transaction failure. 

CN Commodity Name 

DLMS Note: 

1. Use to identify the nomenclature associated with the item 

identified. 

2. For CN: WebSDR field length = 13 25.

MG Manufacturer's Part Number 

DLMS Note: 

1. Use to identify the part number when primary materiel 

identification is previously identified. 

2. For MG: WebSDR field length = 32. 

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note: Use to identify manufacturer associated with a 

previously identified part number.

7. 2/DTM01/0600 Revise DLMS notes as follows

868 Last Follow-up 

DLMS Note: 

Use to identify the date of the customer's follow-up for status of a 

previously submitted SDR. 

881 Request 

DLMS Note: 

Use to identify the date of the customer's request for

reconsideration. 

 

909 Contestability 

DLMS Note: 

Use to identify the date on which the FMS customer contested the 

action activities response to an SDR subsequent to a 

reconsideration request. 

Administrative updates and 

clarification. 
Enclosure 2, SDR Report, page 4 

# Location DS 842A/W 

Revision 

Reason 

8. 2/REF01/0700 Revise DLMS note for qualifier NN as follows:

NN Nonconformance Report Number 

DLMS Note: 

1. Use to identify the originator's SDR report control number. This 

will be the originator's system assigned number. Identify the 

originating system in REF03 (see REF03 for values). 

2. When If the SDR was originated using the DoD WebSDR, this 

will be the web-generated control number. A WebSDR control 

number will also be assigned to transactions during processing. 

WebSDR transaction processing will repeat the REF segment to 

include each previously identified if more than one SDR report 

control number on the outgoing transaction. 

3. For NN: WebSDR maximum field length = 20 (actual length 

for originating applications will differ) 

Clarification. 

9. 2/LQ01/1050 Remove qualifier “78” and note:

78 Project Code

DLMS Note: Use to identify special programs, exercises, projects, 

operations, and other purposes

Although implemented by 

AFSAC, this data element is 

not available in other 

Component SDR 

applications. Consensus of 

Components is that it is not 

needed in the SDR 

transaction. It should not be 

perpetuated if submitted to 

WebSDR. 

DAASC should notify 

AFSAC if/when inclusion 

of the Project Code will 

cause transaction failure. 

10. 2/NTE01/2400 Revise note as indicated:

WHI Warehouse Instruction 

DLMS Note: 

1. Use to identify Instructions to Depot remarks. May be used by 

the material owner to provide instructions or additional 

information to the distribution depot. 

2. This is a separate additional remarks block reserved for use in 

association with SDR reports forwarded transactionally by the 

primary action activity to a distribution depot for research using 

Beginning Segment Code 47. 

Clarification. DSS has 

capability to receive this 

remarks block, although it is 

not currently in use. This 

capability would be 

applicable to the Army or 

USMC ICP forwarding an 

SDR transactionally. Use of 

the Beginning Segment 

Code 47 would trigger the 

depot to respond to the ICP 

(and not to the submitting 

customer). 
Enclosure 2, SDR Report, page 5 

# Location DS 842A/W 

Revision 

Reason 

11. 2/NTE02/2400 Revise note:

Description (remarks block) 

DLMS Note: 

1. Use multiple repetitions of NTE, with up to 80 positions for 

each line. WebSDR maximum field for note = 500. 

2. Special characters are not allowed except as identified. Valid 

characters are: @ # $ ( ) - = + , / & ; and . 

Clarification 

12. 2/DTM01/2500 Remove qualifiers 510 and 511:

510 Date Packed

511 Shelf Life Expiration

These data elements are in 

the IUID loop. No 

requirement is known 

requiring these data 

elements to be associated 

with a UII. 

13. 2/DTM01/2500 Add note to qualifier 512:

512 Warranty Expiration 

DLMS Note: Reserved for future use. Not available at this time.

Clarification for future use. 

14. 2/REF01/2600 Remove the following qualifier and note:

OC Ocean Container Number 

DLMS Note: 1. Use to identify the NSN of the correct container 

required by not used when reporting a packaging discrepancy 

(Reflected in the packaging data screen- Enhancement not 

applicable at this time).

2. Reserved for future use (pending development of procedures).

3. For OC: WebSDR field length = 50

This element was originally 

requested as a unique Army 

requirement. It is now 

withdrawn as not applicable 

to the DoD SDR 

submission.

15. 2/REF01/2600 Remove the following qualifier and note:

QW New Part Number

DLMS Note: 1. Use in UID loop to indicate the current part 

number when different from the original part number identified in 

the UII. This is a future enhancement.

2. Reserved -not currently available.

This element was 

established as a placeholder 

during early IUID planning. 

It is now withdrawn as not 

applicable to the SDR. 

16. 2/REF0401/ 

2600 

Remove the following qualifier and note:

SQ Container Sequence Number

DLMS Note: Use to identify the NSN of the incorrect container 

actually received when reporting a packaging discrepancy 

(Reflected in the packaging data screen - Enhancement not 

applicable at this time).

2. Reserved for future use (pending development of procedures).

3. For SQ: WebSDR field length = 50

This element was originally 

requested as a unique Army 

requirement. It is now 

withdrawn as not applicable 

to the DoD SDR 

submission.
Enclosure 2, SDR Report, page 6 

# Location DS 842A/W 

Revision 

Reason 

17. 2/REF0401/ 

2600 

Remove the following 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. This is a future enhancement. An 

ANSI data maintenance request has been prepared to request a new 

code qualifier for UII Type for future use.

This element was 

established as a placeholder 

during early IUID planning. 

It is now withdrawn as not 

applicable to the SDR.

18. 2/QTY01/2700 Remove the following qualifiers and notes:

GV Gas Volume

DLMS Note: 1. Use to identify the cubic container volume of the 

container received. 

A data maintenance action was approved in version 5010. The 

approved code/name is CPD - Discrepant Container or Packaging 

Number.

2. Reserved for future use (pending development of procedures).

3. For GV: WebSDR field length = 50

WV Water Volume

DLMS Note:

1. Use to identify the cubic container volume of the container 

requested. 

A data maintenance action was approved in version 5010. The 

approved code/name is CPR - Required Container or Packaging 

Number.

2. Reserved for future use (pending development of procedures).

This element was originally 

requested as a unique Army 

requirement. It is now 

withdrawn as not applicable 

to the DoD SDR 

submission.

19. 2/AMT01/2730 Remove the following qualifiers and notes:

2H Operating Expenses

DLMS Note: 1. Use to indicate internal ICP costs when reporting a 

packaging discrepancy (reflected in the packaging data screen).

2. Reserved for future DLMS Enhancement; not currently 

available in WebSDR.

This element was not 

implemented and there are 

no known plans for its use. 

(Alternative cost fields are 

already available.) 

20. 2/AMT01/2730 Remove the following qualifiers and notes:

UI Total Costs

DLMS Note: 1. Use to indicate the sum of material costs, labor 

costs, and container costs, as reflected in the packaging data 

screen. Required entry for U.S. Army only.

2. Reserved for future DLMS Enhancement; not currently 

available in WebSDR.

CRC Container Replacement Cost

DLMS Note: 1. Use to indicate container costs as reflected in the 

packaging data screen. Required entry for U.S. Army only.

2. Reserved for future DLMS Enhancement; not currently 

available in WebSDR. 

This element was originally 

requested as a unique Army 

requirement. It is now 

withdrawn as not applicable 

to the DoD SDR 

submission.

21. 2/N101/2800 Remove the following qualifier and note: This was an element 
Enclosure 2, SDR Report, page 7 

# Location DS 842A/W 

Revision 

Reason 

91 Action Party

DLMS Note: 1. Use to identify the Action Office responsible for 

processing the SDR. The code is used for assigning suspense; 

internal routing; and determining complaint location.

2. Reserved for future DLMS Enhancement; not currently 

available in WebSDR.

originally provided for DLA 

legacy system interface. It 

is not used in the current 

interface with DLA. It 

should not be perpetuated if 

submitted to WebSDR. 

DAASC should notify 

AFSAC if/when 

inclusion of the Action 

Party will cause 

transaction failure. 

22. 2/N101/2800 Remove the following qualifiers and notes: 

IAT Party Executing and Verifying

DLMS Note: 1. Use to indicate the Enterprise Identifier (EID) 

responsible for the UII. This is a future enhancement.

A data maintenance action was approved in version 5020. The 

approved code/name is "EID - Department of Defense Enterprise 

Identifier".

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.

This element was 

established as a placeholder 

during early IUID planning. 

It is now withdrawn as not 

applicable to the SDR. 

# Location DS 842A/W SDR Report 

Administrative Revision Not Previously Identified

Reason 

1. 2/LQ01/1050 Revised DLMS note for qualifier “TG” as follows:

TG Title Document Code List 

DLMS Note: 

1. Use on SA SDR to identify the SA Document Number 

Requirement Type as one of the following: Follow-on Support 

Requirement (FSR), Government Furnished 

Equipment/Materiel (GFE), System Sale (SYS), 

Repair/Replace Requirement (RRP), Repair/Return 

Requirement (RPT), or World Wide Redistribution System 

Requirement (WWR). An ANSI data maintenance action will 

be taken to obtain a more appropriate code for use in a future 

version/release. 

2. For TG: WebSDR field length = 3

Administrative update: 

To keep names consistent 

when used internally and 

other systems. 

Inserts authorized code 

values in note. 
Enclosure 3, SDR Reply, page 1 

Enclosure 3, DLMS Transaction: SDR Reply 

Item 

# 

Location DS 842A/R 

Revision 

Reason 

 DLMS 

Introductory 

Notes 

Add ADC 358 to DLMS Introductory note 4: 

- ADC 358, SDR Transaction Content/Business Rule 

Revisions/Clarification

Identifies DLMS Changes 

included in the DLMS 

Supplement 

1. 1/PER01/1700 Remove qualifier “QA” and note:

QA Quality Assurance Contact

DLMS Note: Use to identify an alternative point of contact 

when reporting a product quality deficiency or expired shelf life 

discrepancy.

This is a secondary POC. 

The requirement was based 

upon original SF 364 

instructions. This 

secondary POC was never 

implemented by ICP 

applications and is no 

longer considered 

necessary. Corresponding 

change will be made in the 

DLMS manual 

2. 2/LIN04/0200 Add data element level note and add qualifiers/revise qualifier 

level notes:

Federal Note: Use to further identify an item. Use multiple 

Product/Service ID pairs as needed. 

DLMS Note: The sequence of data content for secondary 

materiel identification is dependent upon the applicable 

primary materiel identification. The referred sequence of 

secondary information is: part number; manufacturer’s 

CAGE; nomenclature. However, part number, 

manufacturer’s CAGE, and nomenclature may be cited in any 

order without causing transaction failure. 

CN Commodity Name 

DLMS Note: 

1. Use to identify the nomenclature associated with the item 

identified above. 

2. For CN: WebSDR field length = 13 25.

MG Manufacturer's Part Number 

DLMS Note: 

1. Use to identify the part number when NSN is also provided

primary materiel identification is previously identified. 

 2. For MG: WebSDR field length = 32. 

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note: Use to identify manufacturer associated with a

previously identified part number identified above. 

Clarification. 

Same as corresponding 

change to the SDR report 

format. 

Field length for commodity 

name/nomenclature was 

miss-identified in the 

current DLMS supplement. 
Enclosure 3, SDR Reply, page 2 

Item 

# 

Location DS 842A/R 

Revision 

Reason 

3. 2/LIN06/0200 Add data element level note and the following qualifiers w/ 

DLMS notes:

DLMS Note: The sequence of data content for secondary 

materiel identification is dependent upon the applicable 

primary materiel identification. The referred sequence of 

secondary information is: part number; manufacturer’s 

CAGE; nomenclature. However, part number, 

manufacturer’s CAGE, and nomenclature may be cited in any 

order without causing transaction failure. 

CN Commodity Name 

DLMS Note: 

1. Use to identify the nomenclature associated with the item 

identified. 

2. For CN: WebSDR field length = 13 25. 

MG Manufacturer's Part Number 

DLMS Note: 

1. Use to identify the part number when primary materiel 

identification is previously identified. 

 2. For MG: WebSDR field length = 32. 

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note: Use to identify manufacturer associated with a 

previously identified part number.

Same as above. 

4. 2/LIN08/0200 Open LIN08-09; Add data element level note and qualifier level 

notes:

DLMS Note: Use of LIN08 is optional. The sequence of data 

content for secondary materiel identification is dependent upon 

the applicable primary materiel identification. The referred 

sequence of secondary information is: part number; 

manufacturer’s CAGE; nomenclature. However, part 

number, manufacturer’s CAGE, and nomenclature may be 

cited in any order without causing transaction failure. 

CN Commodity Name 

DLMS Note: 

1. Use to identify the nomenclature associated with the item 

identified. 

2. For CN: WebSDR field length = 13 25. 

MG Manufacturer's Part Number 

DLMS Note: 

1. Use to identify the part number when primary materiel 

identification is previously identified. 

 2. For MG: WebSDR field length = 32. 

Same as above. This will 

allow for same 

combination of values used 

in the report (that is, a 

primary materiel ID, plus 

part number, CAGE, and 

commodity name.) 

Staffing note: Since 

secondary materiel 

identification is optional, 

applications which cannot 

currently receive LIN08 

may drop this last entry as 

long as it does not cause 

transaction failure. 
Enclosure 3, SDR Reply, page 3 

Item 

# 

Location DS 842A/R 

Revision 

Reason 

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note: Use to identify manufacturer associated with a 

previously identified part number.

5. 2/REF01/0700 NN Nonconformance Report Number 

DLMS Note: 

1. Use to identify the originator's SDR report control number. 

This will be the originator's system assigned number. Identify 

the originating system in REF03 (see REF03 for values). 

2. Must use a second REF segment to identify the applicable 

DoD WebSDR control number when one was provided on the 

SDR report. 

3. A WebSDR control number will also be assigned to 

transactions during processing if not previously assigned. 

WebSDR transaction processing will repeat the REF segment if 

to include each previously identified SDR report control number 

is be provided for the SDR on the outgoing transaction;

Component applications need not repeat all applicable values. 

4. For NN: WebSDR maximum field length = 20 (actual 

length for originating applications will differ) 

Clarification. 

6. 2/REF01/0700 Remove qualifier “PO” and note:

PO Purchase Order Number

DLMS Note: For PO: WebSDR field length = 13

The requirement for this 

element was based upon 

original SF 364 

instructions. It was not 

implemented and 

alternative values are 

available. Component 

consensus is that there is no 

need for a unique qualifier 

for the PO number. 

7. 2/REF01/0700 Add new qualifier and corresponding DLMS note:

SI Shipper’s Identifying Number for Shipment (SID) 

DLMS Note: DoD action activities responsible for contracted 

vendor shipments are required to populate the contractorassigned Shipment Number when applicable.

This field was 

inadvertently left out of the 

available contractor 

shipment information on 

the reply. Corresponding 

guidance for use of this 

field was added to the 

DLMS manual. 

8. 2/CS/0750 Add segment-level note:

DLMS Note: Action activities are required to populate the 

contractor shipment information when applicable. 

Clarification and added 

emphasis. 

9. 2/LQ01/1050 Remove qualifier “GD” and note:

GD Gain or Loss Indicator Code

DLMS Note: Use with 1/BNR01/0200 Code 06. Used by the 

distribution depot to provide results of investigation to the 

material owner (Navy requirement).

This element was 

associated with a legacy 

requirement that has not 

been established in the 

current Navy interface with 

WebSDR. 
Enclosure 3, SDR Reply, page 4 

Item 

# 

Location DS 842A/R 

Revision 

Reason 

10. 2/QTY01/2700 Remove the following qualifiers and notes:

14 Quantity in Float

DLMS Note: 1. Use with 1/BNR01/0200 Code 06 to identify the 

quantity in float. Used by the distribution depot to provide 

results of investigation to the material owner (Navy 

requirement).

2. For 14: WebSDR field length = 7

17 Quantity on Hand

DLMS Note: 1. Use with 1/BNR01/0200 Code 06 to identify

the adjusted on-hand quantity. Used by the distribution depot to 

provide results of investigation to the material owner (Navy 

requirement).

2. For 17: WebSDR field length = 7

26 Total Inventory

DLMS Note: 1. Use with 1/BNR01/0200 Code 06 to indicate 

physical inventory count. Used by the distribution depot to 

provide results of investigation to the material owner (Navy 

requirement).

2. For 26: WebSDR field length = 7

BI Book Inventory

DLMS Note: 1. Use with 1/BNR01/0200 Code 06 to indicate 

record balance. Used by the distribution depot to provide results 

of investigation to the material owner (Navy requirement).

2. For BI: WebSDR field length = 7 

These elements were 

associated with a legacy 

requirement that has not 

been established in the 

current Navy interface with 

WebSDR.

11. 2/N101/2800 Add qualifiers and corresponding DLMS notes:

SH Shipper 

DLMS Note: Use to identify the shipping activity by Routing 

Identifier, DoDAAC, or vendor CAGE. 

SUS Supply Source 

DLMS Note: Use to identify the owner or manager by Routing 

Identifier; this is the party that directed the shipment (Source 

of Supply) when applicable to wholesale requisitions. 

Equivalent to the report 

format. Allows for 

identification of the actual 

shipping activity and 

Source of Supply on the 

reply when not included or 

incorrectly identified on the 

SDR report. DAAS Note: 

Metrics Table update 

required if different from 

submitter input. 

12. 2/N103/2800 Add qualifiers:

10 DoDAAC 

M4 RIC

Allows for identification of 

the applicable DoDAAC or 

RIC (only CAGE is 

currently listed in the reply 

at this position) 
Enclosure 3, SDR Reply, page 5 

Item 

# 

Location DS 842A/R 

Revision 

Reason 

13. 2/NTE01/3500 Remove qualifier and note:

PKG Packaging Instructions

DLMS Note:

1. Use to provide information related to packaging 

discrepancies.

Obsolete. 

Standard remarks block is 

sufficient to provide 

disposition instructions. 

14. 2/NTE02/3500 Revise note:

Description (remarks block) 

DLMS Note: 

1. Use multiple repetitions of NTE, with up to 80 positions for 

each line. WebSDR maximum field for note = 500. 

2. General reply remarks (Qualifier AES) will be expanded to 

750 positions in a future release. The expanded length is 

reserved for future implementation planned for June 2011. 

3. Special characters are not allowed except as identified. 

Valid characters are: @ # $ ( ) - = + , / & ; and . 

This expands available 

field length for reply 

remarks. 

Staffing Note: 

Components must notify 

DLMSO if June 2011 

implementation date is not 

acceptable. 

15. 2/DTM01/3600 Replace existing note:

198 Completion 

DLMS Note: Use for Shipper's SDR Completion Date when the 

shipper closed the SDR (providing disposition) on the incoming 

side (Navy requirement).

Reserved for future use. Not available at this time.

This data element is not used 

at this time. A tentative 

requirement has been 

identified to provide an SDR 

completion date to WebSDR. 

This element will be reserved 

for future use to support this 

requirement when associated 

procedures are defined. 

16. 2/DTM01/3600 Remove the following qualifiers and notes:

992 Date Requested

DLMS Note: Use to identify the date the action activity 

requested cataloging action. 

These element was 

associated with a legacy 

requirement that has not 

been established in the 

current interface with 

WebSDR.

17. 2/LQ01/4650 Remove qualifier “CLP” and note:

CLP Cause Lookup

DLMS Note: Use to identify the Causative Research Indicator 

(Navy requirement). An ANSI data maintenance request has 

been prepared to request a new data element 1270 code qualifier.

This element was 

associated with a legacy 

requirement that has not 

been established in the 

current Navy interface with 

WebSDR.

# Location DS 842A/R SDR Reply 

Administrative Revisions Not Previously Identified

Reason 

1. 1/PER01/1700 Remove the following qualifiers and DLMS notes:

CB Changed By

DLMS Note: Use to identify the preparing official's 

Administrative 

correction. 

These POC Qualifiers 

are not applicable to the 
Enclosure 3, SDR Reply, page 6 

# Location DS 842A/R SDR Reply 

Administrative Revisions Not Previously Identified

Reason 

information as associated with modified SDR.

FC Forwarder Contact

DLMS Note: Use to identify a point of contact at the action 

activity forwarding the SDR.

PI Preparer

DLMS Note: Use to identify the preparing official's

information as associated with cancelled SDR. An ANSI 

data maintenance request has been prepared to request a 

new data element 1270 code qualifier.

PU Report Preparer

DLMS Note: Use to identify the preparing official's 

information as associated with a new SDR submission.

RQ Requestor

DLMS Note: Use to identify preparing official's 

information as associated with a contested SDR (ILCO 

POC for contested SDR or request for reconsideration is 

identified using Qualifier SE).

SM Submitting Contact

DLMS Note: Use to identify submitting contract as 

associated with an SDR follow-up.

Reply and were 

inadvertently picked up 

in an earlier Supplement 

update. There is no 

known programming 

change associated with 

removal of identified 

values. 

2. 2/N101/4100 Revise DLMS note to read:

ST Ship To 

DLMS Note: 

1. Use to identify the location to which material must be 

shipped/ returned. Location may be identified by code 

(DoDAAC, RIC, or CAGE when using N103 value) and 

by clear text address. 

2. Pending full implementation of discrete data elements 

for the ship-to address, clear text addresses must be 

repeated in the remarks block to assure that all users will 

receive the specified address.

Clarification provided 

for system design under 

DLMS. Removes 

incorrect reference to 

field length which is 

now re-located to the 

proper data element. 

3. 2/N102/4100 Add DLMS note 2:

Name 

Identifies WebSDR field 

length for the first line 

of the ship-to address. 
Enclosure 3, SDR Reply, page 7 

# Location DS 842A/R SDR Reply 

Administrative Revisions Not Previously Identified

Reason 

DLMS Note: 

1. This is the activity name and equates to address line 1. 

2. For ST: WebSDR field length = 35. 

4. 2/PER01/4600 Remove the following qualifier and DLMS note:

PU Report Preparer

DLMS Note: Use to identify the preparing official's 

information as associated with a new SDR submission.

Administrative 

correction. 

This POC Qualifier is 

not applicable to the 

Reply and was 

inadvertently picked up 

in an earlier Supplement 

update. There is no 

known programming 

change associated with 

removal. 
Enclosure 3, SDR Reply, page 1 

Enclosure 4, Comment Resolution 

 Submitter Comment DLMSO Response 

1. Army 1. The Army (National Level Community) concurs 

with PDC 356. 

2. Army detail comments are: 

 a. SCE-BTL - concur; concur with Enclosure 3, 

Item 13 – additional separate remarks block for 

Packaging (would be very useful if field will be 

compatible with LMP). 

 b. WR - Concur for the APS/War Reserve Storage 

sites. SDR's and PQDR's are used by APS/War 

Reserve Sites, there is no special logic or processes for 

APS/War Reserve Business Processes. 

 c. LOGSA - Concur. 

CASCOM, Enterprise Systems Directorate has 

reviewed proposed changed and concurs. This change 

will not apply to legacy STAMIS. 

Regarding packaging remarks: 

Although potentially useful, due 

to limited implementation, 

DLMSO is recommending that 

this field not be retained. The 

existing remarks block is 

available for all types of 

disposition remarks. 

2. Air Force The Air Force concurs with PDC 356 without 

comments. 

3. DLA DDC J3M concurs. 

4. Navy The Navy concurs with PDC 356 as written and 

submits no additional changes or amendments. 

5. DMLSS 

Program, 

JMFLDC 

We have reviewed and concur with the proposed 

DLMS addendum dated November 24, 2009 for the 

PDC 356. 

6. USTRANSCOM 

DEDO/DTEB 

Will coordinate with our IPT representative to update 

DTR (regarding management report evaluation 

requirements for transshipper SDRs) 

7. DLMSO Typo in pseudo shipment number format. 

Proposed structure must include a numeric value in 

the first three positions so that it will not duplicate 

alpha prefixes assigned to vendors. 

Yes, pseudo shipment numbers 

are not unique and are 

perpetuated from the receipt to 

the SDR to retain the association. 

Guidance will be updated as 
Enclosure 3, SDR Reply, page 2 

Expand clarification: Does this mean that pseudo 

shipment numbers don’t have to be unique and that 

they’re just filling a mandatory data element that is 

missing? 

follows: When reporting new 

procurement receipts, the 

distribution depot shall site a 

“pseudo shipment number,” 

equivalent to that cited on the 

receipt, when the actual vendor 

shipment number is not available 

from shipping documentation. 

The pseudo shipment number 

will be constructed to identify the 

receiving depot and a constant 

01 (that is, the serial number will 

not be incremented; therefore, 

the pseudo shipment number will 

not be unique). In order to 

systemically identify pseudo 

shipment numbers the third 

position must be numeric 

(vendor assigned shipments use 

a three digit alpha prefix to 

identify the vendor). For 

example, pseudo shipment 

numbers prepared by 

Distribution Depot San Joaquin, 

California (DDJC), will be 

reported as DD1JC01.

8. AFSAC 

Questions/concerns with Enclosure 2: 

#5 2/LIN/0200: On the data element CN for 

commodity name, is 13 positions correct? Our noun 

field is 40 positions long. However, I did a query of 

our database, and I didn't see any records where we 

had more than 20 positions. We do however; 

routinely have 20 positions and WebSDR displays the 

full 20 positions when we pass it. (EX. WebSDR 

Control #20093001274). 

#6 2/LIN08/0200: We pass all these fields but I think 

they are recommending a certain order to pass them 

but not requiring that order. I am not clear on the 

preferred order the way it is written. We pass as FS, 

CN, F8 and F7 (if Q discrepancy), MG, ZB. Based on 

your understanding of the paragraph, do we have to 

change this order? There is once again a reference to 

the CN segment being only 13 positions versus 20. 

#9 2/LQ01/1050: We do pass if filled the LQ01 78 

Field length for CN corrected to 

25 characters. 

Regarding the order of materiel 

ID data elements: There is no 

change for X12 EDI applications. 

The new mapping will help XML 

applications. 

ADC is asking that 78 (project 

code) and 91 (Action Office) be 

removed from the format/not be 

forwarded, but we are asking 

DAAS to accept your transaction 

or work with you for best 

opportunity to update your 

format. 

If shipment number is available to 

you, it would be good to include 

it, but we are focusing on the 
Enclosure 3, SDR Reply, page 3 

segment; however, it is not a required field and doesn't 

serve much purpose. We must know our drop dead 

date to remove it if passing it will cause EDI failure. 

#22 2?N101/2800: We always pass the N101 = 91 

(pos 2800 of record) and associated N102/N103/N104 

segments. However, it appears we also pass the same 

N101 info in the N101 = ZD segment (position 1200 

of record). Just need to coordinate an implementation 

time so we do get EDI failures after field removed. 

Questions with Enclosure 3: 

#2 2/LIN04/0200: Another CN reference with a field 

length of 13 (recommend this be updated to 20). 

WebSDR displays 20 and we frequently pass 20 

today. 

#3 2/LIN06/0200: Another CN reference with a field 

length of 13 (recommend this be updated to 20). 

WebSDR displays 20 and we frequently pass 20 

today. 

#4 2/LIN08/0200: Another CN reference with a field 

length of 13 (recommend this be updated to 20). 

WebSDR displays 20 and we frequently pass 20 

today. 

#7 2/REF01/0700: I also wanted to clarify in the 842 

reply transaction the new Ref01/0700 ref segment 

field REF/SI . . . is this only in the reply record? Does 

it have to be in all reply records (e.g. our rejected 

replies) or does it pass only if filled? We don't have 

any logic today to pass this in the submission either . . 

. should we? 

#13 2/NTE01/3500: PKG . . . We have logic to accept 

this, but a quick look at our history indicates we 

haven't ever processed one. 

I don't think there is anything drastic other than a 

clarification of the CN field length because the item 

name in the catalog is definitely longer than 13 

positions and I know that we transmit to Sean up to 20 

positions now and he displays it. Also, I need to know 

the date I have to have the deleted fields removed 

from our logic so we don't have EDI failure. 

ICP/IMM applications and DSS 

to populate this field (in reports or 

replies), since shipment number is 

a key data element for vendor 

shipments in those applications. 
Enclosure 3, SDR Reply, page 4 

9 DLMSO 

PDC 356 was reviewed in detail during weekly 

teleconferences with the Component SDR 

implementation team. During these calls DLA 

withdrew the request for Reply Code 520, Reply Code 

308 was deferred, and minor revision to the text of 

Reply Code 144 were agreed to. 

Components were requested to notify DLMSO if any 

of the presumed obsolete data elements were still 

needed. 

The new text field for original reply remarks on a 

forwarded SDR was questioned. 

Reply Code 308 will be adopted 

at a later date. DLA will notify 

DLMSO when implementation is 

planned. 

None of the obsolete elements 

were identified as required. 

Research showed that the original 

reply was dropped on 504 replies 

which result in new (00) SDRs. 

However, the value of these notes 

was not found to be sufficient to 

justify the programming impact.