rc9 Trusted Contributor.
Trusted Contributor.

(PPM) Support Tip: Troubleshooting details when cost is not rolling up on PPM entities

Cost rollup service is a heavy service is responsible for asynchronously updating the cost data of projects, proposals, and assets and update
this information into the financial summary.

The driving table for this service is ITG_PENDING_ROLLUPS table. The driving columns for Cost Rollup service

The rows with rollup_type_code = 'COST' indicate rows related to cost rollup.

SOURCE_ENTITY_ID & TARGET_ENTITY_ID indicate the entity, for example Project, Asset etc

SOURCE_ENTITY_PRIMARY_KEY & TARGET_ENTITY_PRIMARY_KEY will indicate primary key of the entity i.e PROJECT_ID, ASSET_ID or financial summary id.

When the cost rollup service is not rolling up the cost, follow the below steps and capture the details and add to the support case.

1. Go to Dashboard -> Open -> Administration -> View Services Audit Page
    Check if the Cost RollUp Service is running as per the interval by checking Last Complete Run and Next Scheduled Run. The default interval for this service is 1 hour.

2. Check how many rows are stuck in ITG_PENDING_ROLLUPS table with the rollup_type_code = 'COST'

    Export the data into excel spreadsheet with column names included.
3. In order for support to investigate for cost rollup service not rolling up the cost on entities like projects or financial summaries

3.1. enable the debugging in logging.conf under <PPM_HOME>/conf

a. Add the following parameter
    com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL = com.mercury.itg.core.cost, DEBUG
b. Set the parameter com.kintana.core.logging.SYSTEM_THRESHOLD to DEBUG and save the changes to     logging.conf
c. Let the cost rollup service to run and collect the kSupport.sh output.

The serverLog.txt should capture error messages similar to the following.

ERROR :ppmHeavyServiceListenerContainer-1:(AbstractRollupService.java:108):2016/07/01-11:46:01.966 EDT: cost rollup with id 35321 failed.

4. Once the logs are captured, turn off the debugging in logging.conf by doing the following
   -- Comment out the parameter com.kintana.core.logging.PRODUCT_FUNCTION_LOGGING_LEVEL = com.mercury.itg.core.cost, DEBUG

Labels (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.