Project Costing Funds Distribution Creates A Duplicate Row
(Doc ID 2046499.1)
Last updated on JULY 21, 2020
Applies to:PeopleSoft Enterprise FIN Project Costing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The Funds Distribution process, PC_FND_DIST, is creating a duplicate reversal row if the "Run for Incoming Transactions" funds distribution option is enabled on the Project Costing Integration Installation Options and the funds distribution rule includes a rateset.
We have funds distribution setup for a given project activity. This setup includes a burden rateset to create a new PROJ_RESOURCE row with a different analysis type that is then a source for the funds distribution rules. This setup has two targets, one of which is set for budget check and reversals, the other is creating a new PROJ_RESOURCE row with a different analysis type. When cost collection is processed, we are finding that two FDR reversal rows are created and processed to commitment control.
This is causing the available budget to be overstated. If funds distribution is processed again using the 'Reprocess Distributed Transactions' then one of the reversals is removed.
The issue can be reproduced at will with the following steps:
- Go to Set Up Financials/Supply Chain > Install > Installation Options > Project Costing Integration and select all the Funds Distribution Option checkboxes. Enter a balancing analysis type 'FDR'.
- Create a billing/cost rate set that will create a burden row for incoming ACT transactions (FDS is the target in this example).
- Create a project and activity.
- Create a funds distribution rule for the activity and enter the above rate set.
- Check the Group Target Definitions checkbox and then create two target groups, one for the original analysis type(s) and the second for the burden row created by the rate set. The first group target should have the Reversals checkbox checked.
- Create a new ACT transaction for the project/activity and run cost collection. The result will include two reversal rows when there should only be one.
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