Clarity

  • 1.  How is PRRMEXPORTED field on PRTIMEENTRY updated?

    Posted Aug 12, 2009 02:09 AM
    Hi All  We came across a problem where some project costs were not appearing when we expected them to.   Timesheets had been approved and posted and the actuals appeared in Clarity and in OWB.       We discovered that o ne of the resource's timesheets has 4 PRTIMEENTRY records, 3 for the project concerned and 1 for another.   The field PRRMEXPORTED exists on the PRTIMEENTRY table.   However the value of PRRMEXPORTED for the 3 records  was 0, the other record for another project was 1.   There were no costs for the 3 records in WIP although post transactions to financials had been run.   Re-running the 'post timesheets' and 'post transactions to financials' job corrected this "error" and set all the values to 1 and ultimately gave us costs. [left]   [left] We  have noticed that there are thousands of records with 0 in this field, however the majority are indirect rows so this could be correct, but there are some project time entries which do appear to be ok and should at first look have been processed. [left] We have raised a support call but would appreciate any information from the wider community on How PRRMEXPORTED is populated and why we might get a value of 0. [left] Many thanks [left] Owen [left]


  • 2.  Re: How is PRRMEXPORTED field on PRTIMEENTRY updated?
    Best Answer

    Posted Aug 12, 2009 03:54 AM
    OK folks, I think this one is solved.   Here is what CA advised us:  If a project is inactive or financial status is Closed before a timesheet is posted then PRRMEXPORTED is left at 0.   This does not show as an invalid transaction because that screen only shows errors after posting (from IMP_TRANSACTIONIMPORT and PPA_TRANSCONTROL tables).   Until the posting the financials don't exist here.  So we find ourselves with posted time entries which have not been financially posted.   We are going to search these out, open the projects and repost.   We haven't helped things by having a large number of open time periods, where users can go back and adjust time on an inactive/financially closed project.  There is an Enhancement in to stop projects being closed or deactivated if there are outstanding items but this is not currently scheduled for immediate release even in v13.   So we are going to see if we can put something in place to check for these closed projects prior to posting, reopen them, post and then close them again.   Obviously we are also going to address our numbers of open time periods too.  Hope this is of use to any one who has the same problem.  Owen