XOG-3926 XOG-3927 XOG-3909 Warning Messages When XOG Of Project Allocation Segments

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

When XOG in of projects, the output XML contains the following messages.
What does it mean and how to resolve the messages?

PRJ_EXAMPLE1
XOG-3926: ActCost segment start on TaskLabor /aaaaaa earlier than project start.
XOG-3926: ActCost segment start on TaskLabor /bbbbbb earlier than project start.
XOG-3926: ActCost segment start on TaskLabor /cccccc earlier than project start.
XOG-3926: ActCost segment start on TaskLabor /dddddd earlier than project start.

PRJ_EXAMPLE2
XOG-3927: ActCost segment finish on TaskLabor /aaaaaa is later than project finish.

PRJ_EXAMPLE3
XOG-3909: AllocCurve segment finish on Resource aaaaaa is later than project finish.
XOG-3909: AllocCurve segment finish on Resource bbbbbb is later than project finish.
XOG-3909: AllocCurve segment finish on Resource ccccccc is later than project finish.
XOG-3909: AllocCurve segment finish on Resource eeeeee is later than project finish.
XOG-3909: AllocCurve segment finish on Resource ffffff  later than project finish.
XOG-3909: AllocCurve segment finish on Resource gggggg is later than project finish.
XOG-3909: AllocCurve segment finish on Resource hhhhhh is later than project finish.
XOG-3909: AllocCurve segment finish on Resource iiiiii is later than project finish.
XOG-3909: AllocCurve segment finish on Resource jjjjjj is later than project finish.
XOG-3909: AllocCurve segment finish on Resource kkkkkk is later than project finish.

Environment

Clarity 16.3.0

Cause

The XOG exceptions are warnings and not errors, hence the project write will succeed but infromation will be missing/inaccurate.

XOG-3926: ActCost segment start on TaskLabor /aaaaaa earlier than project start.


The actuals for the specified resource aaaaaa, starts before the project start date.

<TaskLabor actualThrough="2023-02-06T00:00:00" actualWork="624" estMax="1" estPattern="3" finish="2022-04-28T17:00:00" lastUpdatedBy="admin" lastUpdatedDate="2023-02-03T17:16:04" remainingWork="0" resourceID="aaaaaa" start="2022-01-03T08:00:00" unpostedActuals="0">

<Baselines/>

<EstCurve/>

<ActCurve>

<Segment finish="2022-01-08T00:00:00" start="2022-01-03T00:00:00" sum="40.0000"/>

 

Project Start Date from the XML

start="2022-01-03T08:00:00"

The Start date is the same, however the timestamp is different.

The actual start time is represented as 12 AM, while the project start time is 8 AM, hence the failure.

 

Resolution

1. Xogout the project.
2. Review the project start date and segment timestamps.
    Compare and confirm the project start date timestamp is after the segment timestamp.
3. Change the timestamp of the project start from 8AM to 12 AM.
4. Xogin the updated write file.