This article serves as a guide to address chartstring combination code validation errors encountered while entering funding transactions in UCPath. It provides step-by-step instructions and troubleshooting tips to help ensure transactions process smoothly.
Beginning in November 2023, a new chartstring web-service validation runs behind the scenes. This change increases the chance of incorrect CoA combinations, so it’s important to verify you’re using the correct elements. If a Project value is entered, only PTF is sent to PPM for validation; if no Project value is entered, all elements except PTF are validated.
Transactors can use the Project COA Lookup within the Project Information Lookup Panorama Report in the Business Analytics Hub to verify the UCPath Fund for their project.
Error Message | Problem | Cause | Solution |
“Project not allowed on MED Center, Population Health or Physician Group Entity.” | Error received during chartstring validation. | Health System Entity 16143, 16144, or 16242 was used in a chartstring with a Project. Health system entities do not use projects. | Ensure you’re entering the correct chartstring elements. Use the COA Lookup Report to confirm the full chartstring for the Project, and enter each element as it appears on the report. |
“Expenditure item date isn’t within the {date range}.” | Error received during chartstring validation. | The expenditure item date (or earnings end date) in UCPath is not within the project task period in Oracle PPM. |
Use another project task, or:
|
“Invalid Combo Code.” | Error received during chartstring validation in Direct Retro (old tool). | One or more elements of the chartstring are not valid with another segment(s). | Confirm that the chartstring is valid using the Combo Code and Chartstring Validation report. If invalid, select another valid chartstring. |
“The expenditure failed project-level transaction controls.” | Error received during chartstring validation. | The expenditure type is not allowed on the project due to transaction control. | Contact SPF (Sponsored) or ICA (General) to review transaction controls if the cost is appropriate to the project. |
“The expenditure item date is outside the project dates.” | Error received during chartstring validation. | The expenditure item date is not within the project/task period. |
Use another project task, or:
|
“Can’t charge to the Project because the Project Status doesn’t allow you to create transactions.” | Error received during chartstring validation. | The project has been closed in Oracle. |
Use another project, or:
|
“Can’t charge to the {TASK_NUMBER} task because it’s defined as a nonchargeable task.” | Error received during chartstring validation. | The task is not chargeable. |
Use another project task, or:
|
Cross Validation Rule (CVR) Errors |
One of these errors was received during chartstring validation:
| Oracle Cross Validation Rules prevent certain chartstring elements from being used together for compliance, reporting, or other reasons. | Follow the error message prompt and adjust your chartstring accordingly. |