Clarity

  • 1.  Project Cost Plan issue

    Posted Jun 14, 2016 04:52 AM

    Hi All,

     

    In Clarity we don’t use the timesheet data to get the actuals as we sends the timesheet posted data into SAP and SAP convert time into pounds and project actual are send back to Clarity via an interface.

     

    As per business requirement we should select the Entry type as ‘Imported’  on  ‘Post to Wip’ page for processing however s ‘ALL’(Imported, PPM) accidentally was selected and posted into Clarity. Due to this the project actuals are almost doubled for every project on cost plan page and now projects are out of governance.

     

    As per requirement ppa_wip table should have entry only for SAP actual (source module=50) however now we have data for timesheet actual (source module 51) as well as SAP actual (source module 50) and around 800K timesheet transactions have been committed so it’s not an easy job to do the ‘WIP Adjustment’ for all the timesheet transactions.

     

    Please let me know if someone else has come across with same situation and what is the best way to fix this issue in order to correct the issues caused.                                                                                                                                                                                              

    Much appreciate your suggestions and thanks for your help in advance.

     

    Regards,

    Ravi



  • 2.  Re: Project Cost Plan issue

    Posted Jun 14, 2016 07:11 AM

    Hello Ravi,

     

    I think WIP adjustments would be recommended here. Manually adjusting it for such a high volume will be tedious, but if you have access to DB, you will be able to do it programmatically.

    Check out the following link: WIP Adjustments & Approvals Using SQL Script v14.3

     

    -Sankhadeep



  • 3.  Re: Project Cost Plan issue

    Posted Jun 14, 2016 08:14 AM

    Ravi,

     

    Before you step any further, I'd advise that you raise this with CA.

    The use of the stored procedures listed in the linked thread is totally unsupported.

    I'd step very carefully unless you want even more mess



  • 4.  Re: Project Cost Plan issue

    Posted Jun 16, 2016 03:50 PM

    Just remember to test your scripts/stored proc in a lower environment and then test them in a lower environment that has the same data you want to correct. Validate once completed, and a backup of prod taken, run your scripts/stored proc, validate. If all is fine, continue. if issues, try to fix, worse case restore the backup prior to business start of day.