Enterprise Service Automation (ESA) - PSFT (MOSC)

MOSC Banner

PeopleSoft Project Costing Express Capitalization and Proj_Resource table size

edited Feb 6, 2015 10:27AM in Enterprise Service Automation (ESA) - PSFT (MOSC) 2 commentsAnswered

We are encountering issues with the  Express Capitalization process in Financials 9.0 (and have duplicated in 9.2) increasing the size of the Proj_Resource table dramatically

We have been able to identify that it has been caused after projects are mapped to several assets per record in PROJ_RESOURCE, and the Express Capitalization is run and then Rejected under Review Assets. The rows created in Proj_Resource from the initial capitalization remain after the rejection and are then used the next time Express Capitalization runs. In an instance where we had one project mapped to 9 assets with 200 costs transactions, the initial capitalization created 2,200 lines in Proj_Resource, the second capitalization after the rejection resulted in 22,200 rows. We then needed to run a second Reject on the same Project. The third capitalization after rejection results in 222,200 rows. Given our volumes this process is making PROJ_RESOURCE quickly become unmanageable.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center