DPAS SCR: 01696



  • SCR Number
    01696
  • Title
    Incorporate DLMS 824R Functionality
  • DPAS Module
    Enterprise
  • Reporting Organization
    Leidos
  • State
    Done
  • History
    Submitted: 4/26/2021
  • Description

    Description
    DPAS does not provide support for the DLMS 824R (Reject Advice).  The Army is planning to implement DLMS 824R generation/reporting of data errors for TPF transactions (DLMS 527D) that GCSS-Army does not successfully inbound by August 2021.  This SCR is to develop the processes DPAS requires to support the DLMS 824R Transaction Set.

    1. The DLMS 824R supports the of MILSTRAP related DLMS transactions, and  other DLMS supply, contract administration and logistics bills transactions, but does not replace procedures for error identification addressed by the DLMS 140A Small Arms and Light Weapons (SA/LW) Reporting, DLMS 870S Supply Status, or DLMS 842A/R DoD Supply Discrepancy Report Reply. The DLMS 824R is also used by DLA Transaction Services for narrative message type rejects for all DLMS transactions subject to rejection by DAAS narrative messages
    2. This transaction set is not used to reject a DLMS transmission due to ASC X12 syntax errors that DAAS reports via email.  The DLMS 824R that will be received will come from the trading partner system from their inability to process the transaction for reasons other than what is currently supported by the DoD Supply Discrepancy Report (SDR) process (DLMS 842). 

    Recommended

    1. Modify the DLMS inbound process to inbound the DLMS 824R notifying DAAS of the support and desired format that DPAS anticipates accepting the DLMS 824R transaction set (XML).
    2. Develop logic to route the Reject Advice to the correct module / recipient (PA, WM, MM, DPAS Admin) using the DLMS Transaction Set and Document Nbr of the transaction set that was rejected, and the reason for the reject. 
    3. Provide a user view of the rejected transaction to the user (code and text) provided in the DLMS 824R along with pertinent info from the original DLMS transmission, with the capability to mark the transaction as New (Default when a new reject is added), Read (when a user has viewed the transaction), In Process (provide the user with a text field to denote who was assigned to action the reject advice), and Resolved (with a text field for the user to denote action taken) - drops off the view when marked resolved. 
    4. The dashboard of each module should be updated to include open DLMS rejects.
    5. The design for supporting the DLMS 824R Reject Advice transaction set should provide methods for making the DPAS user as well as the receiving system that generated the reject advice ‘whole’.  This may include providing for the modification of the original data that caused transaction to be rejected, and the resubmission of the DLMS transaction, and in other instances it may include providing the capability to reverse/void the original action the user took providing the appropriate DLMS transactions to the receiving system to make them whole. The actual development of the processes required to make both parties whole may not be in scope for the initial fielding of this SCR given the number of transaction sets that can be rejected via the 824R.  When resources are available, the initial implementation of this capability should be to support the DLMS 527D reject notices.

    Mission Critical
    Yes. To support DPAS DLMS compliance, DPAS needs to inbound 824Rs

    Benefits
    Provide DPAS and its customer with visibility and resolution of DLMS data errors.

    Users
    This change affects customers/users who are generating DLMS transactions as part of the  business processes.

     

    Completed - Release 2021.3 - 10 September 2021