My Oracle Support Banner

EPC: Funds Distribution Is Incorrectly Overwriting KK (Commitment Control Expense) When Processing ODL Transactions. (Doc ID 2756835.1)

Last updated on MARCH 06, 2021

Applies to:

PeopleSoft Enterprise FIN Project Costing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


PC_FND_DIST process is not creating the correct expenses in commitment control when processing ODL transactions. The total expenses shown in the PS_PROJ_RESOURCE table do not tie with the expenses shown in commitment control.

Replication Steps:

  1. Enable Commitment Control for General Ledger and Project Costing products.
  2. Create a Project ID.
  3. Create Project Activities.
  4. Create Funds Distribution Source Rule for GLE analysis type.
  5. Create Funds Distribution Target Rule. 80 % FDF and 20 % FDS with a threshold amount of say $10. FDS has the reversal and budget check turned on and is associated with a different account.
  6. Create a Budget Journal and post that is enough to capture all expenses for the project.
  7. Create a GL Journal for $21 amount with PC chart fields.
  8. Edit and Post GL Journal.
  9. Run Project Costing > Cost Collection > General Ledger (PC_GL_TO_PC).
  10. Review budgets using Commitment Control > Review Budget Activities > Budgets Overview. Expense show up as $21.
  11. Process Funds Distribution (PC_FND_DIST). PROJ_RESOURCE data - ODL - $11, FDF - $8, FDS - $2, FDR - $2.
  12. Review Commitment Control – Budgets Overview – Expense of $21.
  13. Increase Threshold Amount to 21 from 10 to Clear ODL row.
  14. Process Funds Distribution (PC_FND_DIST). PROJ_RESOURCE data - FDF - $8 and 8.8, FDS - $2 and 2.2, FDR - $2 and 2.2.
  15. Review budgets using Commitment Control > Review Budget Activities > Budgets Overview. This is where the issue is. According to commitment control, there is only $19 in the expense section which is incorrect. It should have been $21. The expense amount for FDS associated account should show $4.2 instead of $2.2.

Replication Steps


The issue started happening after upgrading to PUM 35 from an earlier release of PUM 25 or earlier.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.