28 July 2022_ per Kristie Dionne email, cancelling this SCR.

Description
The IGC program is a partnership between the U.S. Transportation Command and the Defense Logistics Agency. USTRANSCOM's Global Transportation Network (GTN) and DLA's Enterprise Business System have "converged" to provide DOD with an integrated set of networked, end-to-end visibility, deployment, and distribution capabilities.  Prior the Air Force sunset of their APSR AFEMS, AFEMS fed the IGC.  With their transition to DPAS, it was not known if there was a requirement to continue the interface of Air Force equipment in the custody of their users.  Recently, the IGC requested the Air Force restore this interface.  This SCR is to provide the IGC with the Air Force equipment that resides within the DPAS. 

Recommended
Provide the IGC with data feed of Air Force items in DPAS using the DPAS standard agency asset extract as tasked by the DPAS PM.  The extract is to execute weekly as an overlay.

Mission Critical
This feed is considered mandated by the IGC with the Air Force concurring with the feed of their asset information.  The Air Force POC is Greg McCoy, Air Force HAF  AF A4LR.  Email: This email address is being protected from spambots. You need JavaScript enabled to view it.

Benefits
Improves visibility of assets for the Department for those users of the IGC.

Users
This change will likely not affect any user of DPAS.

Description
DLMS ADC 1400 provides CICPs to report a missing cost element e.g. Updated MAC, or LAC via the DLMS 947I.  When materiel is received by a CICP, often times then Latest Actual Cost is not known due to the item having to go through their accounting system to have contract approved overhead costing applied.  This change is to provide the CICP a method for reporting the LAC post the applying of the overhead and other costs that may not be known at the time of the receipt, updated MAC and the item's Standard Price, as needed. This ADC also contains an administrative change for the DLMS 527R receipt that should be reviewed for possible changes to the DPAS user documentation.

Recommended
With DPAS currently support the Air Force CICP programs for financial reporting of the inventory held by the contractor, DPAS will need to be modified to use the updated LAC / revised MAC in its valuation of the inventory and financial reporting of the inventory.  Upon receipt of the 947I, DPAS will need to review and make the necessary valuation adjustment as needed.

Mission Critical
Yes - This SCR requires implementation to accurately report the financial value of the inventory held by the contractor.  This SCR is being submitted to implement DLMS ADC 1400.

Benefits
The benefits of this SCR is the improved accuracy in the financial reporting of the cost of goods managed by a CICP contractor.

Users
All components using DPAS to financially account for inventory in the custody of a CICP.

Completed – Release 2021.4 – 17 December 2021

Description
U.S Treasury TFM USSGL Chart of Accounts implemented USSGL 1995 (General Property, Plant, and Equipment Permanently Removed but Not Yet Disposed).  It is also covered in : Accounting for the Disposal of General Property, Plant and Equipment from FFATR, No. 14. DPAS needs to add support for this USSGL.

Recommended
Incorporate USSGL 1995 within the DPAS Chart of Accounts as part of the DPAS Modernization effort.

Mission Critical
Yes. DPAS must be compliant with U.S Treasury Chart of Accounts

Benefits
Financial Compliance

Users
Yes.  Used for equipment that is no longer of need to the component / agency

Description
Allow LPs the ability to configure the text that displays at the bottom of Warehouse forms (Issue and Return receipts). Currently, the Issue and Return forms display text specific to being held to USMC judicial system if the member is required to pay back any prices for the issued items. This request came in as a old Help Desk ticket (31739) from the DISA LP but should consider this for the tech refresh in the Warehouse Module as we bring more and more on board to use the issue and return processes.

Recommended
Allow users to configure the texts that display at the bottom of the Issue and Return receipts based on what the LP would like to see displayed to their users.

Mission Critical
N/A

Benefits
Benefits non-USMC elements using Warehouse.

Users
All

Description
The registry manages SA/LW by Stock Nbr / Serial Nbr.  A single shipment may include many items. The requirement to close each intransit singularly is time consuming.  USSOCOM, a user of the DPAS SA/LW registry, is requesting the capability close outstanding shipments by entering a Document Nbr.   This is required as there are many intransit shipments that are not being auto-closed.

Recommended
The system should allow the user to enter the Document Nbr for the shipment, review the outstanding items (they would all be checked as the default), permitting the user to un-check any item that has not been confirmed as received, then select update with the system closing all items associated with the Document Nbr.  This change would improve the process and reduce the amount of time required to close intransits.

Mission Critical
The current process is very time consuming and takes resources that could be performing other mission duties.

Benefits
This change will reduce the time to manually close an intransit that was not auto-closed.

Users
All users of the SA/LW registry will benefit from this change.

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

Description
USMC MCCS has a need to systematically update their Real Property that is being managed with DPAS with critical information that is maintained and is available from the USMC real property system.  The data that MCCS requires is not available from the RPIM / DAIS data that DPAS currently imports, or is only updated once a year which does not meet the MCCS requirement in managing its real property facilities / projects.

Recommended
DPAS will develop a real-time import process that provides the capability to upload real property data that will be validated, then applied to existing real property records.

Mission Critical
Yes, without this information DPAS does not fully support USMC MCCS's business needs. It has been endorsed by the DPAS PM as part of supporting USMC NAF.

Benefits
Provides additional information for the customer's real property records and improves the accuracy of those records

Users
Yes, all USMC Real Property users.  It should also be usable by Defense Agencies that utilize USMC facilities that are managing their portion of the Real Property using DPAS.