Using Express Capitalization After Rejecting Assets Causes Exponential Growth In Volume Of PROJ_RESOURCE Rows (Doc ID 2036911.1)

Last updated on JULY 08, 2016

Applies to:

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

Symptoms

The volume of rows in the PROJ_RESOURCE table in Project Costing increases exponentially under certain conditions when using Express Capitalization.


Problem occurs when projects are mapped to several assets per record in PROJ_RESOURCE, and the Express Capitalization is run and then rows are 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 one example where one project was mapped to nine assets with 200 cost transactions, the initial capitalization created 2,200 lines in PROJ_RESOURCE.  Those rows were rejected under the Review Assets page. The next express capitalization run after the rejection resulted in 22,200 rows. The rows were rejected again and a third express capitalization resulted in 222,200 rows.

This can be reproduced as follows:

  1. Set Asset Integration Rules for Project
  2. Project XXX and Activity XXX was mapped to 9 assets by percent. Each asset had the same Transaction Date, Accounting Date and Service Date.
  3. Express Capitalization process PC_AM_EXPRSS was run with Summarize' option and a Defined Date.
  4. The user chose to reject the transactions on the Review Assets page in order to add additional transactions before capitalizing.
  5. The PC_REJECT_AM process ran, deleting the records that had been inserted into PROJ_AM for the initial but it did not delete any records from PROJ_RESOURCE, but instead updated all of the applicable records with AM_DISTRIB_STATUS from 'P', to 'N'.


Due to this issue, there is a potential exponential growth in the volume of asset-related transactions in PROJ_RESOURCE and PC_EXPRSS_AM is taking many hours to complete.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms