Skip to main content

System Status: 

Chapter 8: Resolving Unprocessed Costs in PPM

Resolving Unprocessed Costs in PPM

PPM Cost has embedded controls to ensure accurate financial accounting. When Costs are Imported to PPM, if any costs fail, they are reflected as Unprocessed Costs. There are various reasons why Costs fail and various ways to correct. The business owner of the cost is responsible for correcting the error or the cost timely to ensure proper recording and accounting. Only central offices can correct unprocessed costs in PPM.

The Project team is working with ITS and Oracle to streamline the current error resolution process.

  • Error Resolution Process:

This image describes the Cost Process Flow. This process begins when a cost file is submitted via API (e.g., recharge units, ISIS, UCPath, or Recharge Plus). The system first validates the file using PTF and MCI Builder. If validation errors are found, the file must be corrected and resubmitted. If validation passes, the system checks for load errors; if any occur, the file is corrected and resubmitted. If no load errors exist, costs are imported into PPM. The system then checks for unprocessed cost errors. If no errors are found, the process ends and the cost is successfully posted. If errors are identified, the initiator is notified via API output or staff email, with monitoring supported by Splunk. Errors are then reviewed to determine the issue type (such as a date-ended project or other issue). The initiating department submits a request to delete unprocessed costs and/or makes any necessary corrections. Budgetary control is applied, and fixes are completed by either Sponsored Projects (SPF) or General/Capital Accounting (GA), depending on the project type. Corrected costs are reimported through a nightly automated job, and the process concludes once the cost is successfully posted.

Find answers, request services, or get help from our team at the UC San Diego Services & Support portal.