ADC 282A 

CCP-Originated SDRs including Noncompliant WPM Procedures 

with Cost Breakdown and New Procedures for Closing WPM and Passive RFID SDRs 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

 a. Functional POC: Defense Distribution Center (DDC), CML 717-770-4561; 

DSN 771-4561; FAX 771-6997 

2. FUNCTIONAL AREA: Supply (SDR)

3. REFERENCE: 

a. DLMSO memorandum dated May 8, 2008, subject: Approved DLMS Change (ADC) 

282, Consolidation and Containerization Points (CCP)-Originated SDRs including Noncompliant 

Wood Packaging Material (WPM) Procedures and Shipment Hold Code. This ADC identifies data 

content and process changes supporting generation of electronic DLMS SDRs by the CCP. The 

initial implementation is planned for DSS Release 8.2 and will apply to shipments using 

noncompliant WPM and shipping through the CCPs to OCONUS sites. 

b. DLMSO memorandum dated August 14, 2006, subject: Approved DLMS Change 

(ADC) 206, Discrepancy Reporting for Wood Packing Material (WPM). 

4. REQUESTED CHANGE: Revisions/clarifications subsequent to the ADC 282A proposal 

are highlighted. This change:

a. Identifies two additional DLMS SDR transaction data elements to report material and 

labor costs for repackaging to be used optionally when reporting packaging discrepancies. 

b. Expands the field length of the current data element for total repackaging cost.

c. Establishes procedures for closing SDRs with passive Radio Frequency Identification 

(pRFID) and WPM discrepancies thereby reducing manual workload. In association with this and 

the submitter process which is allows closure upon SDR generation, there are new procedures for 

DAAS/WebSDR to post action activity replies to history without forwarding to the SDR submitter. 

d. Establishes an option for forwarding SDRs with Document Type W, CCP-originated 

transshipment, to the action activity by email when standard procedures require transaction 

exchange. 

5. BACKGROUND: 

a. Scenario for which the new data elements are used: The new data elements will be 

used on CCP SDRs for noncompliant WPM, but may be used for other packaging discrepancies as 

well. The cost may be estimated or actual depending upon the scenario in which they are used. 

b. Procedures, transactions, data elements, processing details in use today: 

(1) The DLMS SDR currently includes an actively used data element for total 

repackaging cost, and two inactive data elements for the labor and material costs previously 

identified as reserved for future use. This change allows the planned DLMS enhancements to be 

used during transaction exchange. 
(2) Within DLA, WPM and pRFID discrepancies are closed upon receipt by packaging 

specialist personnel, and the information later extracted via report, so that specialists may verify the 

discrepancy under terms of the contract, where applicable, and pursue corrective action or 

recoupment from vendors. 

6. DATA AND PROCESS CHANGES: 

a. Approved procedures: 

(1) The labor and materiel costs to remediate noncompliant WPM will be carried in 

the SDR. Under existing rules, dollar values may be expressed in whole dollars (with no decimal) 

or in dollar and cents (with a decimal included). The field length will be 12 positions. 

(2) The total repackaging cost data element maximum field length is currently 

established in DoD WebSDR as 7 positions. It will be expanded to 12 positions to be consistent 

with Distribution Standard System (DSS) current use and the two new elements as designed for 

DSS. 

(3) New procedures are documented for optional processing SDRs for WPM and 

passive RFID using a report-driven process as an alternative to working each SDR independently. 

The SDR may be auto-closed upon receipt using Reply Code 716, SDR recorded for information 

and possible corrective action (this is done today, but requires manual intervention). On a 

monthly/as needed basis (timing must be compatible with SDR response time), a report listing 

discrepant SDR content will be prepared for research. An action activity representative will employ 

the report to pursue corrective action with the shipper or vendor (possibly recoupment) after first 

verifying the terms of the contract. This process is only authorized for WPM SDRs generated by 

CCPs and RFID SDRs generated by Distribution Depots where the no response is expected back to 

the submitter. The receipt must be identified in Supply Condition Code A. The SDR reply must be 

addressed to DAAS (RIC SGA). Under these circumstances, the Distribution Standard System will 

close the SDR record after transmission to the action activity, so supply source replies would fail to 

process. DAAS/WebSDR will post the reply to history, but not forward SDR replies to DDs or 

CCPs for WPM or RFID discrepancies containing Reply Code 716, SDR recorded for information 

and possible corrective action when addressed to DAAS/WebSDR. When the SDR was submitted 

by another party, and, therefore, the reply is directed to other than a DD or CCP, an SDR reply for 

WPM/RFID will be prepared and forwarded according to standard rules so that the record will not 

remain open in the sender’s application/log. If further research determines that the basis of the SDR 

prepared by the CCP or DD is not valid, e.g., the vendor was not required by terms of the contract 

to use pRFID, the action activity will prepare a second reply using Reply Code 151, 

Replacement/revised disposition/status; prior response is superseded. Additional reply codes will 

be used to provide the updated response. In the situation noted, Reply Code 145, No contractor 

liability found, would be used along with Reply Code 701, SDR rejected. See remarks/disposition 

provided. DAAS will post to history, but not forward SDR replies to a DD or CCP and SDR reply 

for WPM or RFID discrepancies containing Reply Code 145 when addressed to DAAS/WebSDR. 

(4) The option for email communication of CCP-generated SDRs is to be provided 

based upon ICP request. Owner/managers requiring email distribution must provide an email 

address for this purpose. Note: The Military Services have not identified email addresses for these 

SDRs at the time of ADC publication. DLA has identified e-mail address: DSCCWPM@dla.mil. 

b. Update Discrepancy Status or Disposition (Reply) Code text name as follows.

Reply Code 701, SDR rejected. See other reply codes or remarks for clarification. 
c. Management Reports. DLMSO recommends that reports used to capture average 

processing time for SDRs processing not include auto-close responses for RFID and WPM where 

there are a substantial number of SDRs, as this will skew the results. 

d. Update SDR procedures (DLMS Manual and joint publication) as follows:

C17.3.20. DAAS SDR Processing 

 C17.3.20.1. Under DLMS, SDRs shall be integrated with standard logistics transaction 

processing through DAAS. DAAS shall perform the following actions: 

(Intervening text not shown) 

 C17.3.20.1.8. DAAS shall convert CCP-generated SDRs for email distribution 

pending owner/manager ability to process electronically. 

 C17.3.20.1.9. DAAS shall post for history, but not forward SDR replies to the SDR 

submitter (i.e., Distribution Depots or CCPs) identifying passive RFID or WPM discrepancies 

based upon addressing to the DAAS/WebSDR routing identifier (SGA). This will suppress 

unnecessary transmission of SDR transactions where the SDR submitter has closed the SDR with 

no expectation/requirement for a reply under these conditions. 

e. Revise the DLMS Supplement (DS) 842A/W as follows:

Item Location Revision to 4030 842A/W Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 282A to DLMS Introductory note 5: 

- ADC 282A, Addendum to ADC for Consolidation Containerization 

Points (CCP)-Originated Supply Discrepancy Reports (SDRs) 

including Noncompliant Wood Packaging Material (WPM) with 

Cost Breakdown and New Procedures for Closing WPM and Passive 

RFID 

To identify DLMS 

changes included in 

supplement. 

2. 2/AMT02/2730 Revise DLMS Note for Qualifier Z1 and Z2: 

Z1 Repackaging Labor Cost 

DLMS Note: 

1. Use to indicate repackaging labor costs as reflected in the 

packaging data screen. Cost may be estimated. See ADC 282A.

Required entry for U.S. Army only.

2. Reserved for future DLMS Enhancement; not currently available in 

WebSDR. 

2. For Z1: WebSDR field length = 12 

Z2 Repackaging Material Cost 

DLMS Note: 

1. Use to indicate repackaging material costs as reflected in the 

packaging data screen. Cost may be estimated. See ADC 282A.

Required entry for U.S. Army only.

2. Reserved for future DLMS Enhancement; not currently available in 

WebSDR.

2. For Z2: WebSDR field length = 12 

RPC Repackaging Cost 

DLMS Note: 

1. Use to include the estimated dollar value for corrective action. 

Establishes 

repackaging labor 

cost and 

repackaging 

material cost as 

available data 

elements for use on 

DLMS SDRs. 

Increases field 

length to 12 
Include material and labor needed to complete a packing, packaging, 

preservation, palletization and/or marking project. Cost may be 

estimated. See ADC 282A. 

2. For RPC: WebSDR field length = 12

positions. 

f. Alternatives: Use only the existing data element for total repackaging cost; use only 

existing reply codes.

7. REASON FOR CHANGE: 

a. Documentation and completion of programming in support of ADC 282. The text 

update for reply code 701 better supports current practice of using the reply code without narrative 

remarks, but instead, with other reply codes that complete the meaning of the disposition response. 

Documents DAAS processing to terminate unnecessary transaction flow. Documents procedures so 

that the process is understood and properly handled for metrics. 

b. DAAS email distribution for CCP-generated SDRs is made available because the 

structure of the transaction may differ significantly when provided at the TCN-level. This will 

support early DSS implementation prior to system changes by other SDR applications. 

 
8. ADVANTAGES AND DISADVANTAGES: 

a. Advantages (tangible/intangible): 

(1) Allows better visibility of cost detail. 

(2) The use of the auto-closure eliminates a manual step and large backlog of open 

SDRs, and is a valid approach when combined with the monthly report verification/corrective 

action process. The second reply is needed so that metrics for RFID discrepancies will not be 

inflated by invalid SDRs. The DAAS block for replies bound for DDs/CCPs is required since these 

SDRs were auto-closed after submission and no reply is necessary. 

b. Disadvantages: None identified. 

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: DLMS Change should take 

place on or before implementation of System Change Request #136415, slated for the Distribution 

Support System (DSS) 8.2 Increment. 

10. COMMENT RESOLUTION: 

# Submitter Comment DLMSO Response 

1. USA 

SDR Team Leader 

AMSTA-LC-LSDL 

Paragraph 6a(3). Non-concur for 

documenting SDRs for WPM and 

RFID discrepancies by a report-driven 

system. This proposed change is 

difficult to understand. If we are to 

receive just a report then this will 

create additional work because the 

SDR will still have to be input into our 

system. It is my understanding with 

this change proposal that the CCP 

would take the initiative to contact the 

contractor to resolve the WPM and 

RFID discrepancies? This is the 

responsibility of the contracting 

officer, not the CCPs. In conclusion, 

paragraph 6a(3)needs to be re-written. 

This management report-driven process is 

optional and will not impact Army 

procedures. The auto-close w/subsequent 

report review will not be applicable to 

SDRs submitted by receiving activities 

other than the CCP or DD for pRFID or 

WPM. The process which DLA plans to 

use is documented here because it requires 

some DAASC intervention and 

clarification of the process. SDRs for 

WPM or pRFID prepared by other 

receiving locations will require a standard 

review process/reply from DLA. The 

paragraph identified has been updated to 

state more clearly that this option is not 

intended for use with Military Service 

customers requesting disposition or other 

action on WPM/pRFID discrepancies. 

2. DLA HQ DLA provided the e-mail address for 

CCP SDRs addressed to DLA ICP 

(SMS) as DSCCWPM@dla.mil 

(provided because these will not 

process within EBS until 

programming changes are in place) 

Added 

3. DAASC DAASC requested specific business 

rules for reply transactions to be 

blocked by DAAS/WebSDR under 

new DLA auto-close process for 

Added 
RFID/WPM discrepancies. 

10. IMPACT: 

b. Interface Issues. 

(1) Components receiving SDR transactions may choose not to implement the changes 

to accommodate the cost breakdown, as long as the transaction containing total repackaging cost 

will process successfully. The DSS will generate the SDR with dollars and cents. If the expanded 

field size for total cost is too large for existing SDR applications, the cents may be dropped. 

(2) The DAAS processing of reply transactions for the new auto-close process will be 

based upon the following criteria. Transactions will be post to history and not forward to the 

originating activity. 

3⁄4 Transaction is a reply (Transaction Purpose Code = 11) 

3⁄4 To activity is DAAS/WebSDR (vice initiating activity) (RIC SGA) 

3⁄4 Any From activity -- the DAAS/WebSDR process will not be supply source 

specific. (DLA will be initial user, but this process is available for others under 

future automation.) 

3⁄4 Any reply code -- the DAAS/WebSDR process will not be reply code specific. It 

will be up to the supply source to program appropriately. 

3⁄4 Discrepancy Code is one of the following: 

P314, Passive RFID tag is missing 

P315, Passive RFID tag is visibly damaged and unreadable 

P316, Passive RFID tag is present but unreadable (not visibility damaged) 

P317, Passive RFID tag read has no corresponding advance shipment notification 

P318, Passive RFID tag read duplicates previously used tag identification 

P215, Non-conformance to specified requirements for WPM 

(3) All Components should update text name for Reply Code 701 for better 

understanding of intent when this code is used in combination with other reply codes rather than 

with narrative text. 

(4) CCP DoDAACs are defined as follows: 

 > SW3123 for New Cumberland. 

 > SW3225 for San Joaquin. 

 > SW3185 for Norfolk Hub. The Norfolk Hub is currently expected to come 

online around October (assuming there are no delays or rearranging of priorities). 

 > Two additional CCPs are planned, but DoDAACs are not available. 

 b. DoD WebSDR. 

(1) As stated in ADC 282, WebSDR screens/edits supporting CCP SDRs will not be 

available for initial implementation. Modification of the web submission process shall be identified 
as a future low priority enhancement, pending identification of requirements for WebSDR use by 

other transhippers. 

(2) DAAS will post to history, but not forward SDR replies meeting the following 

criteria: 

(a) Discrepancy code is P314, P315, P316, 317, P318, or P215 (Passive RFID 

and WPM) 

(b) The reply transaction is directed to a DD or CCP 

(c) The reply code is 716 or 145.