Clarity

Expand all | Collapse all

Updating Project Assignment ETC via XOG

  • 1.  Updating Project Assignment ETC via XOG

    Posted 04-12-2015 01:01 PM

    Team:

     

    I am able to update the ETC of a project's task assignment via XOG for a resource. However, when I go to the timesheets of the same resource where the task is used. I see that the ETC value I xogged in is not showing up there in the ETC column.

     

    However, if I manually enter the ETC on the project's task assignment from the front end, it works as expected on the timesheet.

     

    Any ideas?



  • 2.  Re: Updating Project Assignment ETC via XOG

    Posted 04-12-2015 11:37 PM

    After updating the ETC via XOG, please run the investment allocation job from the CA PPM UI and check if that can help and sync the new ETC value in the Timesheet as well, for that specific resource.

    Thanks,

    Abhisek



  • 3.  Re: Updating Project Assignment ETC via XOG

    Posted 04-14-2015 01:32 PM

    What does it show when looking at the task in the project? I'm curious is its listed as a pending ETC that needs to be accepted maybe?



  • 4.  Re: Updating Project Assignment ETC via XOG

    Posted 04-19-2015 05:07 PM

    Team, thanks for the answers. I was finally able to get the xml to work.

     

    Now I have arrived at a new problem. Based on our calculations, I am arriving at an ETC of -1.25 and I am trying to xog this in. XOG is successful but I do not see -1.25, I only see zero. Any ideas? I was hoping negatives would go in like it goes into cost and budget plans. What am I doing wrong

     

    XML as follows:

     

        <NikuDataBus xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../xsd/nikuxog_project.xsd">

          <Header action="write" externalSource="NIKU" objectType="project" version="13.3.0.286"/>

          <Projects>

            <Project active="true" name="Antony's Organic Milk Farm" projectID="milkmancometh">

              <Tasks>

                <Task key="true" lockedForScheduling="true" milestone="false" name="3.75 and 7.5 hour Increments Only"

                  openForTimeEntry="true" orderID="8" outlineLevel="1" status="1" summary="false" taskID="2015_milk_products">

                  <Assignments>

                        <TaskLabor estMax="1" estPattern="3" lastUpdatedBy="WHOLE_MILK" lastUpdatedDate="2015-04-19T14:45:25" resourceID="SKIMMED_MILK" remainingWork="-1.25">

                          <EstCurve>

                            <Segment finish="2015-12-31T23:33:57" start="2015-01-01T00:00:00" sum="70"/>

                          </EstCurve>

                          <CustomInformation>

                            <ColumnValue name="partition_code">DAIRY</ColumnValue>

                          </CustomInformation>

                        </TaskLabor>

                  </Assignments>

                  <CustomInformation>

                    <ColumnValue name="partition_code">DAIRY</ColumnValue>

                  </CustomInformation>

                </Task>

              </Tasks>

              <CustomInformation>

                <ColumnValue name="partition_code">DAIRY</ColumnValue>

              </CustomInformation>

            </Project>

          </Projects>

        </NikuDataBus>



  • 5.  Re: Updating Project Assignment ETC via XOG

    Posted 04-19-2015 05:12 PM

    Est curve value is 70 because skimmed_milk has posted 71.25 actual hours thus far.

     

    70 is the allowed vacation hours.

     

    So, the logic is like, Allowed Vacation Hours - Total actuals = ETC

     

    In this case, 70 - 71.25 = -1.25. That would alert the PM and the RM that the resource is posting more vacation and he needs to be turned off for time for this vacation task.

     

    But what is actually happening is, xog is unable to do a negative, so ETC is being set to 0. And EAC takes the value of the total actuals, which is 71.25. This is okay, I just want to know if a negative is possible to be xogged. Am I making any sense? Long working sunday. Pardon me.