936 SDR processing suspended. Request DoD WebSDR provide an information copy of the original report. 937 Transaction rejected. DoD WebSDR/WebSQCR unable to provide requested SDR information copy. 938 Transaction rejected. Missing or invalid transaction set purpose code. 939 Transaction rejected. Missing, invalid, or inappropriate discrepancy report document type code. 940 Transaction rejected. Improper or Missing either contract number or contractor-assigned shipment number on SDR associated with vendor shipment. 941 Transaction failed during processing. SDR cannot be transmitted electronically to the designated action activity. 942 Transaction rejected. Unauthorized use of reply code. The 200-series reply codes may only be used for Security Assistance SDRs. 943 Transaction rejected. Fund Code or Standard Line of Accounting (SLOA) data elements do not match SFIS Fund Code to Fund Account Conversion Table. 944 Transaction rejected. Forwarding transaction not properly formatted. AP7.28.5 DISCREPANCY REPORT DOCUMENT TYPE CODES AP7.28.5.1. The following codes are used to identify report categories for appropriate automated processing. Discrepancy Report Document Type Codes and DLA Disposition Services SDR Type Codes are one position alphanumeric codes. AP7.28.5.2. The Discrepancy Report Document Type Code (DLMS Qualifier D) is used on SDRs to identify the type of discrepancy report and type of shipment involved. In the context of SDR processing, this data element may be referred to as an SDR Document Type; however, are many other code values assigned that are not applicable to SDRs. This data element is mandatory on SDR transactions. AP7.28.5.3. The DLA Disposition Services SDR Type Code (DLMS Qualifier ST) is used as a sub-type code in conjunction with the SDR Document Type to further clarify the shipment scenario. This data element may be referred to as an SDR Sub-Type Code. This data element is conditional; it is used when applicable. SDR DOCUMENT TYPE Available for DoD WebSDR and Component-Sponsored SDR applications: 6 Customer originated, direct vendor/contractor delivery 7 Customer originated, depot/lateral shipment/other
936 SDR processing suspended. Request DoD WebSDR provide an information copy of the original report. 937 Transaction rejected. DoD WebSDR/WebSQCR unable to provide requested SDR information copy. 938 Transaction rejected. Missing or invalid transaction set purpose code. 939 Transaction rejected. Missing, invalid, or inappropriate discrepancy report document type code. 940 Transaction rejected. Improper or Missing either contract number or contractor-assigned shipment number on SDR associated with vendor shipment. 941 Transaction failed during processing. SDR cannot be transmitted electronically to the designated action activity. 942 Transaction rejected. Unauthorized use of reply code. The 200-series reply codes may only be used for Security Assistance SDRs. 943 Transaction rejected. Fund Code or Standard Line of Accounting (SLOA) data elements do not match SFIS Fund Code to Fund Account Conversion Table. 944 Transaction rejected. Forwarding transaction not properly formatted. AP7.28.5 DISCREPANCY REPORT DOCUMENT TYPE CODES AP7.28.5.1. The following codes are used to identify report categories for appropriate automated processing. Discrepancy Report Document Type Codes and DLA Disposition Services SDR Type Codes are one position alphanumeric codes. AP7.28.5.2. The Discrepancy Report Document Type Code (DLMS Qualifier D) is used on SDRs to identify the type of discrepancy report and type of shipment involved. In the context of SDR processing, this data element may be referred to as an SDR Document Type; however, are many other code values assigned that are not applicable to SDRs. This data element is mandatory on SDR transactions. AP7.28.5.3. The DLA Disposition Services SDR Type Code (DLMS Qualifier ST) is used as a sub-type code in conjunction with the SDR Document Type to further clarify the shipment scenario. This data element may be referred to as an SDR Sub-Type Code. This data element is conditional; it is used when applicable. SDR DOCUMENT TYPE Available for DoD WebSDR and Component-Sponsored SDR applications: 6 Customer originated, direct vendor/contractor delivery 7 Customer originated, depot/lateral shipment/other
v2a7.28_draft.docx