Clarity

Dear All,

The value of ETC on OWB and the Slice table is not matching. Here the Slice job has successfully completed.

For a specific week the value on OWB is coming as 16 but on Slice table the value is showing as 8.

So what could be the possible reason.

    SELECT SLICE

                  FROM PRJ_BLB_SLICES

                 WHERE     SLICE_REQUEST_ID = 300 /*This is for WEEKLYRESOURCEBASECURVE Slice Request*/

                              (SELECT ID

                                 FROM PRJ_BASELINE_DETAILS

                                WHERE OBJECT_ID = PRASSIGNMENT.PRID    /*passing a particular Assignment ID */

                                             AND OBJECT_TYPE = 'ASSIGNMENT')

                       AND SLICE_DATE = t_date) /* Passing a date instead of t_date date */

If the above query is not correct also please suggest me.

Thanks in advance.

Best Regards,

Lalatendu

Is there just one baseline for the project?

Is that the only record with the missmatch?

There are more than 100 records we are getting mismatch value.

Best Regards,

Lalatendu

If the slices are not correct then they can be regenerated (which will regenerate all slices for the request), soft reset or resliced for one object instance only.

Search the discussion.

(Can't do search now myself)

Check this -

https://communities.ca.com/message/118381606#118381606

And, as urmas has suggested - "If the slices are not correct then they can be regenerated (which will regenerate all slices for the request), soft reset or resliced for one object instance only."

NJ

Also this -

Time slices not being updated

https://communities.ca.com/message/108599471#108599471

NJ

This would be useful as well -

Mismatch: Project Assignments v OWB

https://communities.ca.com/message/101522274

As per @Jenn_Rinellla -

=====================================================================

You can do a soft reset of the internal ETC slices with the following steps:

1. Pause the scheduled Time Slicing job

2. Run the following update statement:

UPDATE PRJ_BLB_SLICEREQUESTS

SET EXPIRATION_DATE=NULL,

REQUEST_COMPLETED_DATE=NULL

WHERE ID in (103, 108, 113) --daily, weekly, monthly internal  estimates slice

3. Manually run the time Slicing job

4. Un-pause the scheduled time slicing job

Once the time slicing job has completed again, check your values in Clarity. If you are still having an issue, please open a ticket with Support.

Regards,

Jenn

=====================================================================

NJ

There's this as well -

How to manually force a slice job to run?

https://communities.ca.com/message/101931661#101931661

NJ

Thanks NJ and Urmas.

My issue got resolved after following Jenn_Rinellla's Suggsted steps.

Best Regards,

Lalatendu

Great ! She is one of the best

Please mark the thread as resolved, and wish you a Happy and Prosperous New Year

NJ

Wish you Happy New year, NJ

Lala