PC_FND_DIST Update FND_DIST_STATUS To G Incorrectly When Apply Burden Rates Is Selected
(Doc ID 2306331.1)
Last updated on MAY 16, 2019
Applies to:PeopleSoft Enterprise FIN Project Costing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
On : 9.2 version, Functionality
FND_DIST_STATUS updated incorrectly to G when Apply Burden Rates is selected
During Funds Distribution processing, if the Apply Burden Rates is selected but transactions are bypassed because of no active matching target sequence is found, it updates the FND_DIST_STATUS to G incorrectly for the source rows preventing further processing of those rows. The only thing to do at that point is to run a sql update to update the FND_DIST_STATUS back to N for those rows.
FND_DIST_STATUS should not be updated to G since no target rows are created
The issue can be reproduced at will with the following steps:
1) Create 2 transactions in AP/GL or somewhere else with Analysis Type ACT or GLE against the Source Activity and run Cost Collection to bring those transactions into PROJ_RESOURCE.
One of the transactions should have an Accounting Date that falls within the Funds Distribution Target Dates. In this example, the target dates are between 11/15/2015 and 12/31/2016. The other transaction should have an Accounting Date of after the end date of the Funds Distribution Target page. In this example, that would be an Accounting Date after 12/31/2016.
2) Set up your Funds Distribution page with target has end date of 12/31/16. Make sure you select a Rate Set/Plan that will create for example an IND row based on an ACT or GLE row.
3) Run Funds Distribution as follows. Notice the From and Through Accounting Date so that it only picks up the first transaction. Verify that the first transaction was distributed correctly.
4) Run Funds Distribution again as follows. Notice the From and Through Accounting Date so that it attempts to distribute the second transaction and Apply Burden Rate is checked--> it sets FND_DIST_STATUS = G incorrectly
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