My Oracle Support Banner

Primavera P6 Web Services ActivitySpread Shows Incorrect Values For Planned Cost and Planned Units When Including Baselines (Doc ID 2769181.1)

Last updated on APRIL 15, 2021

Applies to:

Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 21.1 and later
Information in this document applies to any platform.

Symptoms

When running an ActivitySpread the values for the current project do not match P6 when including baselines.
For example, August has a Planned Cost of 90.250 when baselines are included. When baselines are excluded August shows a Planned Cost of 2166.0. 2166.0 is the correct value.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create an ActivitySpread SOAP request with baseline fields.
<ReadActivitySpread xmlns="http://xmlns.oracle.com/Primavera/P6/WS/Spread/V1">
<ActivityObjectId>1214464</ActivityObjectId>
<PeriodType>Month</PeriodType>
<SpreadField>PlannedTotalCost</SpreadField>
<SpreadField>BaselineActualTotalCost</SpreadField>
<SpreadField>BaselineActualNonLaborUnits</SpreadField>
<SpreadField>BaselinePlannedTotalCost</SpreadField>
<SpreadField>BaselinePlannedNonLaborUnits</SpreadField>
<SpreadField>Baseline1ActualTotalCost</SpreadField>
<SpreadField>Baseline1ActualNonLaborUnits</SpreadField>
<SpreadField>Baseline1PlannedTotalCost</SpreadField>
<SpreadField>Baseline1PlannedNonLaborUnits</SpreadField>
<SpreadField>PlannedLaborUnits</SpreadField>
</ReadActivitySpread>

2. Check the values for PlannedLaborUnits, PlannedTotalCost. They will NOT match the spread in P6.
Period 2020-08-01T from response:
<Period>
<StartDate>2020-08-01T00:00:00</StartDate>
<EndDate>2020-09-01T00:00:00</EndDate>
<Baseline1ActualNonLaborUnits>0.0</Baseline1ActualNonLaborUnits>
<Baseline1ActualTotalCost>0.0</Baseline1ActualTotalCost>
<Baseline1PlannedNonLaborUnits>0.0</Baseline1PlannedNonLaborUnits>
<Baseline1PlannedTotalCost>90.25000000000038</Baseline1PlannedTotalCost>
<BaselineActualNonLaborUnits>0.0</BaselineActualNonLaborUnits>
<BaselineActualTotalCost>941.7391304347826</BaselineActualTotalCost>
<BaselinePlannedNonLaborUnits>0.0</BaselinePlannedNonLaborUnits>
<BaselinePlannedTotalCost>90.24996739784984</BaselinePlannedTotalCost>
<PlannedLaborUnits>0.08333333333333369</PlannedLaborUnits>
<PlannedTotalCost>90.25000000000038</PlannedTotalCost>
</Period>

3. Run the ActivitySpread request again without the Baseline fields.
<ReadActivitySpread xmlns="http://xmlns.oracle.com/Primavera/P6/WS/Spread/V1">
<ActivityObjectId>1214464</ActivityObjectId>
<PeriodType>Month</PeriodType>
<SpreadField>PlannedTotalCost</SpreadField>
<SpreadField>PlannedLaborUnits</SpreadField>
</ReadActivitySpread>

4. Check the values for PlannedLaborUnits, PlannedTotalCost. They will match the spread in P6.
Period 2020-08-01T from response:
<Period>
<StartDate>2020-08-01T00:00:00</StartDate>
<EndDate>2020-09-01T00:00:00</EndDate>
<PlannedLaborUnits>2.0</PlannedLaborUnits>
<PlannedTotalCost>2166.0</PlannedTotalCost>
</Period>

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.