**SDR Transaction Business Rules**

**Updated during SDR IPT**

**September 23, 2004**

**1.  Original SDR Submission Rules:**

**a. Authorized Initiator(s):  Requisitioning activity or authorized intermediary for Requisitioner (ILCO).**

**b. Transaction data requirement: Initial SDR transactions must contain data in accordance with DS 842A/W Nonconformance Report Transaction Set.**

**c.   Business Rules:  The originator’s system assigned SDR report control number will be the inviolate unique number assigned to identify the SDR.  For SDR submitted via the DoD WebSDR, this will be the web-generated control number.  DAAS will also assign a control number for transactional interface.  Components should perpetuate the DAAS-assigned control number when assigned.   If this is not feasible, DAAS will use alternative control numbers to locate the appropriate record.**

**d. DAASC/Recipient System Automated Edits: Applicable codes highlighted.**

901Transaction rejected.  Item shipped/billed by another supply source.  

               Not a DAASC edit

902Transaction rejected.  Invalid action code for type of discrepancy submitted.~~~~ Not a DAASC edit

~~903Transaction rejected.  Invalid SDR for combination of requisitioned quantity and canceled quantity.~~ Deleted 

904Transaction rejected.  Open suffix must be closed before SDR can be reopened.

~~905Transaction rejected.  Simplified Nonstandard Acquisition Program (SNAP) requisitions can only be processed by TACOM and transaction Routing Identifier Code (RIC) indicates another source of supply.~~   Deleted.  Army will provide additional information if still required.

906        Transaction rejected.  Record already closed.

907Transaction rejected.  Record closed, canceled, or a final reply has been provided.

908Transaction rejected.  Record is currently open and cannot be reopened until current suffix is closed.

909Transaction rejected.  SDR must be reopened with suffix R as a reconsideration before it can be contested using suffix C.

910Transaction rejected. ***Missing or*** invalid document number.  Mandatory for non FMS

911Transaction rejected.  ***Missing or*** invalid Security Assistance case designator.

912Transaction rejected.  ***Missing******or*** invalid SDR number.

~~913Transaction rejected.  Invalid SDR suffix.~~  Deleted

~~914Transaction rejected.  Invalid preparation/submission date.~~  Deleted (not sufficient cause for rejection – use current date if invalid or missing)

915Transaction rejected.  ***Missing or*** invalid ~~type of~~ discrepancy code.

916Transaction rejected.  Invalid action desired code.

917Transaction rejected.  ***Missing or*** invalid discrepant quantity. (must be numeric, may be edited according to specific discrepancy condition)

918Transaction rejected.  Invalid quantity received.  (must be numeric)

~~919Transaction rejected.  Invalid interim statement number.~~     Deleted

920Transaction rejected.  ***Missing*** point of contact name.

921Transaction rejected.  ***Missing or*** invalid point of contact phone number ***or email*** (DSN or commercial – must be numeric)

~~922Transaction rejected.  Invalid document to follow indicator.~~  Deleted – will 

                reconsider at a later date.

923Transaction rejected.  Invalid transaction date.

924Transaction rejected.  Narrative missing.  (e.g., used with Discrepancy Code Z1)

~~925         Transaction rejected.  Invalid narrative attached indicator~~****Deleted will      

                reconsider at a later date.

926         Transaction rejected.  No record found****

**2. Correction/Change Rules:**

**a.  Authorized Initiator(s):  SDR submitter or SDR submitter’s organization.**

**b.  Transaction data requirement: Correction Transactions will require all data  that was in the original SDR with the exception of the changed data.  In addition to the changed data being carried in the appropriate data segment, a narrative entry is required to highlight/identify the changed data.**

**c.   Business Rules:**

**(1).  An SDR must be in an open or interim status for a correction transaction to be submitted.**

**(2).  With the exception of the originators system assigned SDR report control number all data on the original SDR is eligible for correction/change.**

**(3).  Correction SDRs that are unmatched to the recipient’s records will be treated as an original SDR.**

**d. DAASC/Recipient System Automated Edits*: Applicable codes highlighted.**

901Transaction rejected.  Item shipped/billed by another supply source.

902Transaction rejected.  Invalid action code for type of discrepancy submitted.

903Transaction rejected.  Invalid SDR for combination of requisitioned quantity and canceled quantity.

904Transaction rejected.  Open suffix must be closed before SDR can be reopened.

905Transaction rejected.  Simplified Nonstandard Acquisition Program (SNAP) requisitions can only be processed by TACOM and transaction Routing Identifier Code (RIC) indicates another source of supply.

906        Transaction rejected.  Record already closed.

907Transaction rejected.  Record closed, canceled, or a final reply has been provided.

908Transaction rejected.  Record is currently open and cannot be reopened until current suffix is closed.

909Transaction rejected.  SDR must be reopened with suffix R as a reconsideration before it can be contested using suffix C.

910Transaction rejected.  Invalid document number.

911Transaction rejected.  Invalid case designator.

912Transaction rejected.  Invalid SDR number.

913Transaction rejected.  Invalid SDR suffix.

914Transaction rejected.  Invalid preparation/submission date.

915Transaction rejected.  Invalid type of discrepancy code.

916Transaction rejected.  Invalid action desired code.

917Transaction rejected.  Invalid discrepant quantity.

918Transaction rejected.  Invalid quantity received.

919Transaction rejected.  Invalid interim statement number.

920Transaction rejected.  Invalid point of contact name.

921Transaction rejected.  Invalid point of contact phone number.

922Transaction rejected.  Invalid document to follow indicator.

923Transaction rejected.  Invalid transaction date.

924Transaction rejected.  Narrative missing.

925         Transaction rejected.  Invalid narrative attached indicator****

926         Transaction rejected.  No record found****

*** Correction Transactions being treated as original SDRs are susceptible to all the reject edits associated with an original SDR.**

**3.  Reconsideration Rules:**

**a.  Authorized Initiator(s):  SDR submitter or SDR submitter’s organization.**

**b.  Transaction data requirement: Reconsideration Transactions will require all data that was in the original SDR.  Additionally, a narrative entry is required to support the requested disposition change. Reconsideration Date and POC also required**

**c.  Business Rules:**

**(1).  An SDR must be in a closed status before a request for reconsideration can be submitted.**

**(2).  When Service/Agency edits at DAASC redirect reconsideration requests from the original action activity to a designated adjudicating activity, they must have procedures in place to ensure the adjudicating activity receives an information copy of the contested response/disposition.**

**d. DAASC/Recipient System Automated Edits: Applicable codes highlighted.**

901Transaction rejected.  Item shipped/billed by another supply source.

902Transaction rejected.  Invalid action code for type of discrepancy submitted.

903Transaction rejected.  Invalid SDR for combination of requisitioned quantity and canceled quantity.

904Transaction rejected.  Open suffix must be closed before SDR can be reopened.

905Transaction rejected.  Simplified Nonstandard Acquisition Program (SNAP) requisitions can only be processed by TACOM and transaction Routing Identifier Code (RIC) indicates another source of supply.

906        Transaction rejected.  Record already closed.

907Transaction rejected.  Record closed, canceled, or a final reply has been provided.

908Transaction rejected.  Record is currently open and cannot be reopened until current suffix is closed.

909Transaction rejected.  SDR must be reopened with suffix R as a reconsideration before it can be contested using suffix C.

910Transaction rejected.  Invalid document number.

911Transaction rejected.  Invalid case designator.

912Transaction rejected.  Invalid SDR number.

913Transaction rejected.  Invalid SDR suffix.

914Transaction rejected.  Invalid preparation/submission date.

915Transaction rejected.  Invalid type of discrepancy code.

916Transaction rejected.  Invalid action desired code.

917Transaction rejected.  Invalid discrepant quantity.

918Transaction rejected.  Invalid quantity received.

919Transaction rejected.  Invalid interim statement number.

920Transaction rejected.  Invalid point of contact name.

921Transaction rejected.  Invalid point of contact phone number.

922Transaction rejected.  Invalid document to follow indicator.

923Transaction rejected.  Invalid transaction date.

924Transaction rejected.  Narrative missing.

925         Transaction rejected.  Invalid narrative attached indicator****

926         Transaction rejected.  No record found****

**4.  Follow-Up Rules:**

**a.  Authorized Initiator(s):  SDR submitter or SDR submitter’s organization**

**b.  Transaction data requirement:**

**(1).  If no response received to original SDR submission, then the follow up will require all data in original SDR.**

**(2).  If an interim response has been received, then only data sufficient to identify the SDR for which the follow-up is intended is required. (Specific streamlined data elements TBD).**

**(3).  Follow-up Date and POC also required.  Follow-up narrative is optional.**

**c.  Business Rules:**

**(1).  Follow-ups will be submitted using timeframes specified in the Reporting of Supply Discrepancies Joint Regulation.**

**(2).   SDR follow-ups containing complete original SDR data that are unmatched to the recipient’s records will be treated as an original SDR.**

**(3).  Streamlined SDR follow-ups that are unmatched to the recipient’s records will be rejected.**

**d. DASAC/Recipient Automated Edits*: Applicable codes highlighted.**

901Transaction rejected.  Item shipped/billed by another supply source.

902Transaction rejected.  Invalid action code for type of discrepancy submitted.

903Transaction rejected.  Invalid SDR for combination of requisitioned quantity and canceled quantity.

904Transaction rejected.  Open suffix must be closed before SDR can be reopened.

905Transaction rejected.  Simplified Nonstandard Acquisition Program (SNAP) requisitions can only be processed by TACOM and transaction Routing Identifier Code (RIC) indicates another source of supply.

906        Transaction rejected.  Record already closed.

907Transaction rejected.  Record closed, canceled, or a final reply has been provided.

908Transaction rejected.  Record is currently open and cannot be reopened until current suffix is closed.

909Transaction rejected.  SDR must be reopened with suffix R as a reconsideration before it can be contested using suffix C.

910Transaction rejected.  Invalid document number.

911Transaction rejected.  Invalid case designator.

912Transaction rejected.  Invalid SDR number.

913Transaction rejected.  Invalid SDR suffix.

914Transaction rejected.  Invalid preparation/submission date.

915Transaction rejected.  Invalid type of discrepancy code.

916Transaction rejected.  Invalid action desired code.

917Transaction rejected.  Invalid discrepant quantity.

918Transaction rejected.  Invalid quantity received.

919Transaction rejected.  Invalid interim statement number.

920Transaction rejected.  Invalid point of contact name.

921Transaction rejected.  Invalid point of contact phone number.

922Transaction rejected.  Invalid document to follow indicator.

923Transaction rejected.  Invalid transaction date.

924Transaction rejected.  Narrative missing.

925         Transaction rejected.  Invalid narrative attached indicator****

926         Transaction rejected.  No record found****

*** Follow-up Transactions being treated as original SDRs are susceptible to all the reject edits associated with an original SDR.**

**5. Cancellation Transaction Business Rules.**

**a. Authorized Initiator(s):  SDR submitter or SDR submitter’s organization**

**b. Transaction data requirement:  Only data sufficient to identify the SDR requiring cancellation is required. (Specific streamlined data elements TBD)**

**c. Business Rules: Cancellation transactions may be submitted against SDRs in an open or interim status.**

**d. DASAC/Recipient Automated Edits: Applicable codes highlighted:**

901Transaction rejected.  Item shipped/billed by another supply source.

902Transaction rejected.  Invalid action code for type of discrepancy submitted.

903Transaction rejected.  Invalid SDR for combination of requisitioned quantity and canceled quantity.

904Transaction rejected.  Open suffix must be closed before SDR can be reopened.

905Transaction rejected.  Simplified Nonstandard Acquisition Program (SNAP) requisitions can only be processed by TACOM and transaction Routing Identifier Code (RIC) indicates another source of supply.

906        Transaction rejected.  Record already closed.

907Transaction rejected.  Record closed, canceled, or a final reply has been provided.

908Transaction rejected.  Record is currently open and cannot be reopened until current suffix is closed.

909Transaction rejected.  SDR must be reopened with suffix R as a reconsideration before it can be contested using suffix C.

910Transaction rejected.  Invalid document number.

911Transaction rejected.  Invalid case designator.

912Transaction rejected.  Invalid SDR number.

913Transaction rejected.  Invalid SDR suffix.

914Transaction rejected.  Invalid preparation/submission date.

915Transaction rejected.  Invalid type of discrepancy code.

916Transaction rejected.  Invalid action desired code.

917Transaction rejected.  Invalid discrepant quantity.

918Transaction rejected.  Invalid quantity received.

919Transaction rejected.  Invalid interim statement number.

920Transaction rejected.  Invalid point of contact name.

921Transaction rejected.  Invalid point of contact phone number.

922Transaction rejected.  Invalid document to follow indicator.

923Transaction rejected.  Invalid transaction date.

924Transaction rejected.  Narrative missing.

925         Transaction rejected.  Invalid narrative attached indicator****

926         Transaction rejected.  No record found****

6.  FMS Contested U.S. Government Decision:

a. Authorized Initiator(s):  ILCO for SDR submitter or SDR submitter’s organization.

b. Transaction data requirement:  FMS Contested Decision Transactions will require all data that was in the original SDR.  Additionally, a narrative entry is required to support the requested disposition change.  FMS Contested Decision Date and POC also required.

c. Business Rules:

(1). An SDR must be in a closed status before a contested decision request can be submitted.  A previous request for reconsideration must apply.

(2). When Service/Agency edits at DAASC redirect requests from the original action activity to a designated adjudicating activity, they must have procedures in place to ensure the adjudicating activity receives an information copy of the contested response/disposition. 

901Transaction rejected.  Item shipped/billed by another supply source.

902Transaction rejected.  Invalid action code for type of discrepancy submitted.

903Transaction rejected.  Invalid SDR for combination of requisitioned quantity and canceled quantity.

904Transaction rejected.  Open suffix must be closed before SDR can be reopened.

905Transaction rejected.  Simplified Nonstandard Acquisition Program (SNAP) requisitions can only be processed by TACOM and transaction Routing Identifier Code (RIC) indicates another source of supply.

906        Transaction rejected.  Record already closed.

907Transaction rejected.  Record closed, canceled, or a final reply has been provided.

908Transaction rejected.  Record is currently open and cannot be reopened until current suffix is closed.

909Transaction rejected.  SDR must be reopened with suffix R as a reconsideration before it can be contested using suffix C.

910Transaction rejected.  Invalid document number.

911Transaction rejected.  Invalid case designator.

912Transaction rejected.  Invalid SDR number.

913Transaction rejected.  Invalid SDR suffix.

914Transaction rejected.  Invalid preparation/submission date.

915Transaction rejected.  Invalid type of discrepancy code.

916Transaction rejected.  Invalid action desired code.

917Transaction rejected.  Invalid discrepant quantity.

918Transaction rejected.  Invalid quantity received.

919Transaction rejected.  Invalid interim statement number.

920Transaction rejected.  Invalid point of contact name.

921Transaction rejected.  Invalid point of contact phone number.

922Transaction rejected.  Invalid document to follow indicator.

923Transaction rejected.  Invalid transaction date.

924Transaction rejected.  Narrative missing.

925         Transaction rejected.  Invalid narrative attached indicator****

926         Transaction rejected.  No record found****

**7.  SDR  Response Rules:**

**a.  Authorized Initiator(s):  Original Action Activity or transferred to (secondary) Action Activity.**

**b.  Transaction data requirement:  SDR response transactions must contain data in accordance with DS 842A/R Nonconformance Report Transaction Set.**

**????????????????????????????????????????????????????????????????????????**