Overview
UCOP retired the Direct Retro (DR) tool in UCPath for UC San Diego effective October 1, 2025, due to maintenance concerns and the availability of the Salary Cost Transfer (SCT) tool (launched in November 2023) as the replacement.
After September 16, 2025, users were instructed not to submit Direct Retros; any entries submitted between September 17–30, 2025 were deleted by the UCPath Center. Attempting to process a DR after this date generates the following error:
“Old DR transactions are not eligible. Consult campus GL admin for a manual Journal Entry option.”
Going forward, payroll cost transfers must be completed using the SCT tool in UCPath or, if the transaction is not SCT-eligible, through Oracle PPM. This article provides current guidance for processing both sponsored and non-sponsored project cost transfers now that DR is no longer available.
Critical Concepts
Salary Cost Transfer (SCT) in UCPath
Use the SCT tool in UCPath for most payroll cost transfers, except in the following cases:
- Payroll transactions with an earnings period end date before October 4, 2021.
- Payroll transactions that were previously moved using the DR tool and now require an additional correction (i.e., a Direct Retro on a Direct Retro).
If your transaction is not eligible for SCT, you must process the transfer in Oracle PPM.
Steps to Take
Cost Transfers in Oracle PPM (Sponsored Project)
If the cost transfer involves a sponsored project (either from or to), follow these steps:
Step 1: Compliance Documentation
- Submit a Services & Support (S&S) ticket.
- Include:
- Effort Certification (ECERT) (required for federal and federal flow-thru awards):
- Obtain the ECERT document for both “from” and “to” projects.
- If it’s within ±5% effort → note this in the ticket (no adjustment required).
- If an adjustment is required, manually update the effort, obtain PI signature on the revised ECERT copy, and attach signed ECERT copies.
- Once you complete this step, you must complete Step 2.
Step 2: Identify All Payroll-Related Costs
Step 3: Cost Transfer Execution
- Process the cost transfer in Oracle PPM.
In the transfer justification dialog box (max 1000 characters), include:
- The S&S ticket number.
- The reason for the transfer.
- If your full comments cannot fit, abbreviate, but reference the ticket with the full justification.
Step 4: Reporting & Tracking
- For SPARCM (Sponsored Projects Accounts Receivable and Cash Management) Financial Expense Reports, reference all Oracle transaction number(s) (from Step 2) on the project you are moving payroll and related transactions from, and include the ticket number in the Pending Expenses column in SPARCM.
- Monitor pending cost transfers in:
- Pending Costs tab in the Transaction Details Report, or
- Project Cost Transfer Panorama Workflow Details report.
- View completed cost transfers with justifications in the Project Cost Transfer Panorama.
Note: The labor ledger (DOPES) will not fully align with PPM and payroll reconciliation reports.
Step 5: Post-Audit Review
- SPF will conduct quarterly post-audits of completed cost transfers on sponsored projects.
- You may see variances on the UCPath-Oracle Salary Reconciliation Report; this is a result of correcting in OFC only and not in UCPath. Nothing further can be done to resolve this variance.
Cost Transfers in Oracle PPM (Non-Sponsored Project)
If the cost transfer involves a non-sponsored project (general/default projects):
Step 1: Identify All Payroll-Related Costs
Step 2: Cost Transfers in Oracle PPM
Step 3: Confirm Transactions Are Correctly Processed
- Review pending cost transfers in:
- Pending Costs tab in Transaction Details Report.
- Project Cost Transfer Panorama Workflow Details report.
- View completed cost transfers with justifications in the Project Cost Transfer Panorama.
Note: The labor ledger (DOPES) will not fully align with PPM and payroll reconciliation reports.