PeopleSoft Enterprise Program Management: AFTER CORRECTING TRANSFORMATION ERROR PGM_ERR_CHK ABENDS (Doc ID 1405185.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

PeopleSoft Enterprise FIN Program Management - Version 9 to 9.1 [Release 9]
Information in this document applies to any platform.
***Checked for relevance on 27-Jan-2014***

Symptoms

Create a project in PeopleSoft using a project type which does not exist in Primavera. Run the Sync New Projects. The system returns a transformation error, because it could not transform the project type.

Create the project type in Primavera and run the Sync New Projects again. The project is not selected. The reason why the system did not select the project is because the previous synchronization, which returned transformation errors, already updated the XREF table. However, the project does not exist yet in Primavera.

As the XREF table has been updated, the user has to run the Sync Existing Projects. This is confusing to the user, as the project does not exist yet in Primavera. The user does not know that the XREF table has already been updated, so he assumes that after correcting the transformation error he has to run the Sync New Projects again.

Run the Sync Existing Projects. The synchronization runs correctly and the project is exported to Primavera. However, the PGM_ERR_CHK abends at the step "P6_COMMN_LIB.GUID.PopGUID" with an unique constraint:

A unique constraint was violated while attempting to insert data. Insert failed. (18028,2165) EOTF_C ORE.Xref.MapData.OnExecute Name:PopulateData PCPC:49868 Statement:778 Called from:EOTF_CORE.Xref.Functions.OnExecute Name:PopulateData Statement:353 Called
from:P6_INTEGRATION.ProcessControl.OnExecute Name:PopulateGuid Statement:683 Called
from:P6_COMMN_LIB.GUID.GBL.default.1900-01-01.PopGUID.OnExecute Statement:1

Changes

When a project is exported for the first time with a Project Type that does not exist in Primavera, the project is considered "processed". Therefore, after adding the project type in Primavera, the project will have to be re-processed using the engine Synchronize Existing Projects.

To make this clear, we have enhanced the original error message indicating the Project Type is invalid to also tell the user to use the engine Synchronize Existing Projects to re-process the project. When re-processing the project using the engine Synchronize Existing Projects, we have corrected the code, so that the engine PGM_ERR_CHK no longer abends.

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