This article contains questions frequently asked about UCPath Funding and the answers to those questions.
If you receive an error when entering the chartstring in UCPath, be sure that you are typing in the correct values. Also, any chart segment that has an all-zero value in OFC should be left blank in UCPath.
If a chartstring value associated with an existing Project has changed, you will need to request a new Project or Task. According to the 5/10/22 Budget and Finance newsletter, under "Changes to Project Financial Setup,"
Effective immediately, to ease the reconciliation of projects and improve controls, departments must request a new project or task when a change in Fund, Function, Program, Location or Project Organization is needed.
If the Task value is not valid or if the Project has exceeded its end date, the chartstring combination will not be sent to UCPath. Verify in PPM that the Task and Project you want to use is still valid and not expired.
If you request changes to an existing chart segment, the new chartstring might not be available in UCPath until 2-3 days after you receive confirmation that it has been entered in OFC.
Beginning 10/1/21, the use of sponsored Funds is NOT allowed in the Default Funding Profile in Funding Entry and is NOT allowed for the Over-the-Cap in Direct Retro. No sponsored Funds can be used for Over-the-Cap (cap gap) in UCPath, even if allowed by the private agency/award.
If a sponsored Fund was previously entered in the Default Funding Profile, it will remain until there is a change made to the MCOP/salary cap worksheet. At that point, an error message will appear and the Default Funding Profile must be corrected before the funding update can be submitted.
The most likely reason is that the chartstring used in UCPath Funding Entry does not contain a Fund that UCPath recognizes as associated with a federal or federal-flow-through sponsored project. To resolve this issue, use the UCSD-DSH Project Information Lookup/Project Information Lookup Panorama report in bah.ucsd.edu/financial to look up the Project COA.
You will need to update position funding to use the chartstring(s) containing the correct UCPath Fund, as well as perform Direct Retro transaction(s) to complete the reconciliation. Find the steps needed in the Payroll Reconciliation Toolkit.
This happens when Position Funding in UCPath contains a sponsored project Fund but the Project, Task and/or Funding Source field is blank. PPM requires that all three fields contain data. To resolve this issue, find the complete UCPath-specific Fund chartstring associated with your sponsored project using this KBA: How to Determine a Chart String (COA Reference Guide) and the Project COA Lookup report. You will need to update position funding, as well as perform Direct Retro transaction(s) to complete the reconciliation. Find the steps needed in the Payroll Reconciliation Toolkit.
The Funding Distribution Preview has rows with chartstrings that include the OTC indicator for capped funds and those combo codes differ from the chart segment combinations (chartstrings) that don’t have the OTC indicator. The system adds the OTC indicator segment value to the original chartstring which makes it a different combination and thus is assigned a different combo code. A combo code that has an OTC indicator cannot be used anywhere else because it is specific to one chartstring and its place in a particular MCOP worksheet (notice that the N-OTC001 row goes with the Y-OTC001 row/s).
The defects that caused the missed or incorrect assessments were identified and resolved in Jan. and Apr. 2021. The correct assessments for April 2020-April 2021 will be posted in Oracle only so be aware that the Labor Ledger/DoPE report will not reflect these adjustments. The target for OFC corrections is the September 2021 accounting period.
Funding Entry does not allow effective-dated entries that precede the first effective-dated entry. For example, if the first funding entry on a position is effective 7/15/2020, you cannot enter an update effective 7/1/2020. This only applies to the first effective-dated entry.
If needed, you can use the MCOP worksheet to insert a row with an earlier effective date. Refer to the following UCPath Job Aid How to Update Position Funding with the Salary Cap/MCOP Worksheet.
In the past, you could search for a fund or index with the EPET tool and quickly EPET many employees' salaries in a single transaction. This is not possible in UCPath. The way to move multiple lines of salary from one funding source to another is by submitting a case to the UCPath Center. The process is explained in this UCPath knowledge article - How do I request a mass cost transfer?
You will need to complete a Mass Cost Transfer Request form from the Forms Library and attach it to the case.
The requirements for a mass cost transfer are as follows:
Note: This mass cost transfer process is not to be used for sponsored projects (contracts & grants). Per OPAFS, cost transfers for sponsored projects must be done individually using Direct Retro in UCPath.
Make sure that the Direct Retro has completed the approval workflow. If the DR is high risk, it may be pending final approval from OPAFS/SPF. Approved DR’s are processed in UCPath according to the pay processing calendar but will not be visible on the DOPE/LL report until the pay run labor ledger detail is sent to UCSD (generally 3 business days after pay confirm). Direct Retro approval deadlines by pay cycle can be found here.
UCPath has specific funds that allow for required functionality in UCPath related to Federal flow-thru-funds, Work-Study funds and Sponsored Research Capped funds. This functionality is not handled in this manner in OFC, instead these UCPath funds are translated per the table below, prior to OFC posting. Non-UCPath expenditures (procurement, travel, supplies, etc.) must use the associated OFC designated funds, rather than the UCPath Specific funds.
|UCPath Specific Fund|
(only usable in UCPath)
|Sponsored Project OFC Fund|
(for non-UCPath expenses)
UCPath generates a funding reallocation log when there are changes to either the Total UC Salary or Compensation Rate Components for an employee and the position associated to the job record has funding distributions that were set up on the Funding Entry page using the Salary Cap/MCOP Funding Worksheet. The guidance given by UCPC is that the department should check the funding distribution to make sure that it is correct. Once the review has been completed, the record can be marked as "worked."
The salary cap worksheet is not working correctly for BW/hourly positions that are less than 1.0 FTE, where a capped Fund is used, and the employee's hourly rate exceeds the cap rate.
Because of this issue, starting 2/7/2022, the link to the salary cap worksheet has been disabled for hourly/BW positions where a capped Fund is used. This means that you will have to calculate the under-the-cap & OTC percentages and enter them into the main Funding Entry page. When the person’s hourly rate changes or the cap rate changes, you will have to change the percentages in Funding Entry accordingly. Note: this is only necessary when the person’s hourly rate exceeds the annual cap rate/2088 hrs.
The removal of the link and the need to calculate the under-the-cap and over-the-cap also applies to direct retros. Again, this is only necessary for employees whose hourly rate exceeds the annual cap rate/2088 hrs.
We’ll be working on a job aid for this but, in the meantime, if you have any questions please submit a case at support.ucsd.edu/path.
As long the total split percent for each earn code adds up to 100%, you can do as many split fund transactions as you need to in a Direct Retro transaction.
Any cost transfers needed for fiscal year 2020 must be done in Oracle only due to the conversion from IFIS. Please see How to Perform a Full or Split Cost Transfer Transaction in Oracle.
Example: OFC PPM Original Transaction Reference: 200731M0X.PJ00000959.912
OFC Original Transaction Reference = UCPath DOPE/LL
200731M0X = Pay Run Code
PJ00000959 = Salary Journal ID
912 = Salary GL Journal Line Number
OFC GL column = UCPath DOPE/LL column
REFCOL1 = JOURNAL_ID
REFCOL2 = JOURNAL_LINE
REF1 = RUN_ID