P6 Web Services Creates EPS Nodes with Incorrect Id after Upgrade
(Doc ID 3019876.1)
Last updated on MAY 01, 2024
Applies to:
Primavera Web Services - Version 23.12 to 23.12.2.0 [Release 23.12]Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 23.12 to 24.2 [Release 23.12 to 24.2]
Information in this document applies to any platform.
Symptoms
Creating EPS nodes using P6 Web Services causes all the EPS nodes except for 1 to be created with the wrong Id. The Name is correct.
This causes several issues in the P6 EPPM applications.
-P6 Web displays correctly because it pulls from projwbs.wbs_short_name.
-P6 Professional displays the EPS nodes as WBS elements and they all have the same Id. P6 Professional is using project.proj_short_name.
-P6 Web Services uses project.proj_short_name and so the Id shows the wrong value when using the ReadEPS operation.
The following error is also returned in the P6 Web Services response.
ERROR
-----------------------
IntegrationFault
<ns::ErrorType>General</ns::ErrorType>
<ns::ErrorCode>0</ns::ErrorCode>
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create multiple EPS nodes using CreateEPS
<v1:CreateEPS>
<v1:EPS>
<v1:Id>TEST-L</v1:Id>
<v1:Name>TEST-L</v1:Name>
<v1:OBSObjectId>940</v1:OBSObjectId>
<v1:ParentObjectId>3741</v1:ParentObjectId>
</v1:EPS>
<v1:EPS>
<v1:Id>TEST-U</v1:Id>
<v1:Name>TEST-U</v1:Name>
<v1:OBSObjectId>940</v1:OBSObjectId>
<v1:ParentObjectId>3741</v1:ParentObjectId>
</v1:EPS>
<v1:EPS>
<v1:Id>TEST-B</v1:Id>
<v1:Name>TEST-B</v1:Name>
<v1:OBSObjectId>940</v1:OBSObjectId>
<v1:ParentObjectId>3741</v1:ParentObjectId>
</v1:EPS>
<v1:EPS>
<v1:Id>TEST-M</v1:Id>
<v1:Name>TEST-M</v1:Name>
<v1:OBSObjectId>940</v1:OBSObjectId>
<v1:ParentObjectId>3741</v1:ParentObjectId>
</v1:EPS>
</v1:CreateEPS>
2. Check P6 Web and the EPS nodes will display correctly in the EPS view.
3. Check P6 Professional and the first EPS node is correct but the others all have the Id equal to the Parent EPS Id. They also have a WBS icon.
4. Read the values using P6 Web Services and the results show the wrong Id for 3 of the EPS nodes created in Step #1.
For example: Results of Read EPS operation using P6 Web Services:
<EPS>
<Id>TEST-L</Id>
<Name>TEST-L</Name>
<OBSObjectId>940</OBSObjectId>
<ObjectId>8869</ObjectId>
<ParentObjectId>3741</ParentObjectId>
</EPS>
<EPS>
<Id>TEST</Id>
<Name>TEST-U</Name>
<OBSObjectId>940</OBSObjectId>
<ObjectId>8870</ObjectId>
<ParentObjectId>3741</ParentObjectId>
</EPS>
<EPS>
<Id>TEST</Id>
<Name>TEST-B</Name>
<OBSObjectId>940</OBSObjectId>
<ObjectId>8871</ObjectId>
<ParentObjectId>3741</ParentObjectId>
</EPS>
<EPS>
<Id>TEST</Id>
<Name>TEST-M</Name>
<OBSObjectId>940</OBSObjectId>
<ObjectId>8872</ObjectId>
<ParentObjectId>3741</ParentObjectId>
</EPS>
Cause
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
Symptoms |
Cause |
Solution |
References |