ADC 423, EBS requires that a supply Approved for DLA’s Revise DLMS 527D to Allow Use condition code (SCC) be included in implementation of Supply Condition Code with a DDX/DFX LR Memorandum Due-In (Procurement Instrument Due-In transactions. MILSTRAP Source) and Specifically with currently requires the SCC in record Logistics Reassignment position (rp) 71 of DI Code DF_, Memorandum Due-In due-in from nonprocurement (MILSTRAP DDX) (Supply) instrument source. For DI Code (Staffed as PDC 288) DD_, rp 71 is a multiuse field. 09/29/11 However, DLA indicates that Johnson Service legacy systems provided the DLA SCC in DI Code DDX to SAMMS, and DLA believes this proposed change should not require a change to Service legacy systems, but rather supports an existing interface requirement. ADC 424, This change approves interim and Approved for DOD Activity Address Directory longer term procedures to correct implementation (DoDAAD) Modification to Break inconsistent Break Bulk Points Bulk Point (BBP) (BBPs) for TAC1 and TAC2 (DoDAAD/Supply) (Staffed as addresses. PDC 443) 05/09/11 Hammond PRC Chair ADC 425, - This change establishes/documents Approved for Revised Supply Discrepancy Report enhanced procedures for improving implementation. (SDR) Codes and Procedures data integrity and facilitating proper Discrepancy and including Incorrect Part Number identification of activities and disposition/reply Discrepancy Codes and DoD communication of information. codes revisions WebSDR Data Edits and - This change replaces existing are effective Forwarding Enhancements Discrepancy Code T8, Incorrect November 15, (staffed as PDC 403) (Supply/SDR) Part Number, with two new 2011. Phased 10/04/11 Discrepancy Codes. and staggered Hilert - This change harmonizes data implementation is DLA/PRC Chair content associated with incorrect authorized for all item identification among DoD other revisions. Component SDR applications and DoD WebSDR. This change also documents DoD WebSDR procedures for mediating the differences related to incorrect item reporting among the various Component SDR applications.
ADC 423, Revise DLMS 527D to Allow Use of Supply Condition Code with Due-In (Procurement Instrument Source) and Specifically with Logistics Reassignment Memorandum Due-In (MILSTRAP DDX) (Supply) (Staffed as PDC 288) 09/29/11 Johnson DLA DLA’s EBS requires that a supply condition code (SCC) be included in a DDX/DFX LR Memorandum Due-In transactions. MILSTRAP currently requires the SCC in record position (rp) 71 of DI Code DF_, due-in from nonprocurement instrument source. For DI Code DD_, rp 71 is a multiuse field. However, DLA indicates that Service legacy systems provided the SCC in DI Code DDX to SAMMS, and DLA believes this proposed change should not require a change to Service legacy systems, but rather supports an existing interface requirement. Approved for implementation ADC 424, DOD Activity Address Directory (DoDAAD) Modification to Break Bulk Point (BBP) (DoDAAD/Supply) (Staffed as PDC 443) 05/09/11 Hammond PRC Chair This change approves interim and longer term procedures to correct inconsistent Break Bulk Points (BBPs) for TAC1 and TAC2 addresses. Approved for implementation ADC 425, Revised Supply Discrepancy Report (SDR) Codes and Procedures including Incorrect Part Number Discrepancy Codes and DoD WebSDR Data Edits and Forwarding Enhancements (staffed as PDC 403) (Supply/SDR) 10/04/11 Hilert DLA/PRC Chair - This change establishes/documents enhanced procedures for improving data integrity and facilitating proper identification of activities and communication of information. - This change replaces existing Discrepancy Code T8, Incorrect Part Number, with two new Discrepancy Codes. - This change harmonizes data content associated with incorrect item identification among DoD Component SDR applications and DoD WebSDR. This change also documents DoD WebSDR procedures for mediating the differences related to incorrect item reporting among the various Component SDR applications. Approved for implementation. Discrepancy and disposition/reply codes revisions are effective November 15, 2011. Phased and staggered implementation is authorized for all other revisions.
FinalDLMSStatusReport2011.docx