Very often we hear concerns raised like -
MY TIMESHEET IS IN POSTED STATUS BUT I DON'T SEE ALL THE HOURS IN THIS TIMESHEET IN INVALID TRANSACTIONS LIST (IMP_TRANSACTIONIMPORT TABLE) OR IN READY FOR POST TO WIP LIST (PPA_TRANSCONTROL) OR IN PPA_WIP TABLE!!
MY ACTUAL HOURS ARE MISSING!!
ACTUALS MISSING IN WIP (PPA_WIP)
When the post timesheet job runs, the PRTIMEENTRY.PRRMEXPORTED column flags to 1 and the timesheet record moves to imp_transactionimport table(Invalid Transactions list). But for various reasons like project against which the timesheet is logged is financial closed or if the Resource trackmode got changed to a value other than Clarity, then the PRRMEXPORTED will remain as 0 and the timesheet record is not promoted to Invalid Transaction list.
As of now, from the GUI, there is no way to check if a record is stuck in PRRMEXPORTED=0 for a posted timesheet other than checking from backend tables.This is not going to help a PMO or Application Administrator who does not have access to DB or someone who is not so expertised in writing queries and pulling data from DB.
Attached is the query and portlet XML which you can either run directly in DB or XOG into the system and use it as a portlet.
We also have a KB article created for this with more details
If you feel, its great to have an OOTB portlet to show thr Invalid Timesheets, go to the below IDEA and vote for this
Disclaimer: This is an initial query and has not been tested as per CA Standards. You can use this as an example and build on top of this. Suggestions for improvement are welcome both here and in the IDEA.