Price/Units Fields Keeps Old Values And It Cannot Be Refreshed Via Web Service
(Doc ID 2703312.1)
Last updated on SEPTEMBER 28, 2020
Applies to:Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 18.1 and later
Information in this document applies to any platform.
While attempting to create a custom integration for updating the price of some resources assigned to a certain project, a client has discovered an issue related to the Price/Units field of P6 at the resource assignment level.
When a resource is assigned to an activity, the Price/Units field is filled with the price/unit defined in the resource, but something that it is correct.
If this value is modified using P6 web service, then the change performed works by modifying other related fields like the planned cost, but the field Price/Units keeps the old value and it generates undesired behaviors.
Normally, the Price per Unit should be updated from P6 WS successfully, just as it is in P6 Web client.
STEPS TO REPRODUCE
1. The Price/unit of the resource in P6 is 1E
2. Assign this resource to an activity. In the assignation, the Price/unit is still 1E, which is correct.
3. Assign, via web service, a Price/unit of 5E, in the mentioned assignation
4. Return to P6 and check the assignation: The planned cost is recalculated with the new price (correct), but the field Price/unit remain with the old value of 1E, which is incorrect
The bad side of this behavior is that if you are in P6 and refresh the information of the assignation by moving the cursor through the fields, it will recalculate the planned cost with the old Price/units, that has reminded in the screen, losing the changes performed via web services
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