Overview

---

This article serves as a guide to address chartstring combination code validation errors encountered while entering funding transactions in UCPath. It provides users with step-by-step instructions and insights to troubleshoot and resolve issues, ensuring a smoother process for entering funding transactions without encountering validation errors.

Next Steps

---

If you receive the Combination Code Validation Error Message, "Project not allowed on MED Center, Population Health Or Physician Group Entity":

• Problem: 
  • You receive this error message during chartstring validation: "Project not allowed on MED Center, Population Health Or Physician Group Entity."
• Cause: 
  • Health System Entity 16143, 16144, or 16242 was used in a chartstring with a Project. Health system entities do not use projects. 
• Solution: 
  • Ensure that you are entering the correct chartstring elements. Use the COA lookup report to confirm the full chartstring for the Project. Enter each chartstring element as it appears on the report. 

---

If you receive the Combination Code Validation Error Message, "Expenditure item date isn’t within the {date range}":

• Problem: 
  • You receive this error message during chartstring validation: "The expenditure item date isn't within {AWARD_START_DATE} and {AWARD_END_DATE} date range of the 311100-00001 award. The expenditure item date isn't within the {TASK_TXN_START_DATE} task transaction start date and {TASK_TXN_END_DATE} task transaction end date." 
• Cause: 
  • The expenditure item date (or earnings end date) in UCPath is not within the project task period in Oracle PPM.
• Solution: 
  • Use another project task or
    • If Sponsored, contact Sponsored Project Funds (SPF) as needed to review the dates if the cost is appropriate to the project or
    • If General, use Project and Award Data Update Application (PADUA) to update the start and/or end dates if appropriate. 

---

If you receive the Combination Code Validation Error Message, "Invalid Combo Code":

• Problem: 
  • You receive this error message during chartstring validation in Direct Retro (old tool): "ComboCode not found in I280 table."
• Cause: 
  • One or more elements of the chartstring is not valid with another segment(s) of the chartstring. 
• Solution: 
  • Confirm that the chartstring is valid by using the Combo Code and Chartstring Validation report. If it’s not valid, then choose another valid chartstring. 

---

If you receive the Combination Code Validation Error Message, "The expenditure failed project-level transaction controls.":

• Problem:
  • You receive this error message during chartstring validation: "The expenditure failed project-level transaction controls."

• Cause:
  • Expenditure type is not allowed on the project due to transaction control.

• Solution:
  • Contact Sponsored Project Funds (SPF) (sponsored) or ICA (general) as needed to review the transaction controls if the cost is appropriate to the project.

---

If you receive the Combination Code Validation Error Message, "The expenditure item date is outside the project dates. Update the project start and finish dates or the expenditure item date of the transaction.":

• Problem: 
  • You receive this error message during chartstring validation: "The expenditure item date is outside the project dates.” 
• Cause: 
  
  • Expenditure item date on the cost is not within the dates of the TO project/task period.
• Solution: 
  • Use another project task or
    •  If Sponsored, contact Sponsored Project Funds (SPF) as needed to review the dates if the cost is appropriate to the project or
    • If General, use Project and Award Data Update Application (PADUA) to update the project start and/or end dates if appropriate.

---

If you receive the Combination Code Validation Error Message, "Can’t charge to the Project because the Project Status doesn't allow you to create transactions.":

• Problem:
  • You receive this error message during chartstring validation: "Can’t charge to the Project because the Project Status doesn't allow you to create transactions.”

• Cause:
  • The project has been closed in Oracle.

• Solution:
  • Use another project or
    • If Sponsored, contact Sponsored Project Funds (SPF) as needed to review if the cost is appropriate to the project or
    • If General, use Project and Award Data Update Application (PADUA) and Sponsored Project Funds (SPF) to update the project status if appropriate.

---

If you receive the Combination Code Validation Error Message, "Can't charge to the {TASK_NUMBER} task because it's defined as a nonchargeable task":

• Problem:
  • You receive this error message during chartstring validation: "Can't charge to the {TASK_NUMBER} task because it's defined as a nonchargeable task.”

• Cause:
  • The task is not chargeable.

• Solution:
  • Use another project task or
    • If Sponsored, contact Sponsored Project Funds (SPF) as needed to review if the cost is appropriate to the project task or
    • If General, use Project and Award Data Update Application (PADUA) to update the project task if appropriate.

---

If you receive any of the Cross Validation Rule (CVR) error messages below (where no POETAF is involved):

• Problem:
  
  • You receive any of these error messages during chartstring validation: 
    • The account and activity code selected cannot be used together.
    • The function and account code selected cannot be used together.
    • The Teaching Hospital Function can only be used with the Medical Center Entity. 
    • The Entity and Financial Unit selected cannot be used together.
    • The Account and Financial Unit selected cannot be used with the Foundation Agency Fund.
    • Function cannot be '000' for expenses.
    • The account and gift fund used cannot be used together.
    • The Fund, Financial Unit, and Account code selected cannot be used together.
    • The sponsored Fund selected requires a project to be used.
    • The Account code cannot be used with the Fund selected.
    • The Sponsored Research Fund and Function selected cannot be used together.
    • The Sponsored Research Fund and Account Code selected cannot be used together.
    • Entity 00000 cannot be used on this transaction. Use a different Entity.
    • Financial Unit 0000000 cannot be used on this transaction. Use a different Financial Unit.
    • Fund 00000 cannot be used on this transaction. Use a different Fund.
    • The Entity and Function selected cannot be used together.
    • The Account code cannot be used with the Function selected. 
    • the Medical Center must use the Teaching Hospital Function on expenses.

• Cause:
  • A Cross Validation Rule has been specifically set up in Oracle so that you cannot use certain chartstring elements with others for reporting, compliance and or other reasons.

• Solution:
  • Follow the message prompt instructions and make applicable updates to your chartstring.