Reporting on the new PAN & RGN codes in the Time & Labor Codes

[Robin Wagner]

Hi, Everyone -

There were two new time sheet codes created to track time worked on Coronavirus related actrivities:  PAN & RGN.

I just ran the BO UM-Maintained report called  TL01 Time/Labor Payable Time by Static Group for a static group I know has used these codes for their time reporting.  However the codes are not showing up on the report for March payrolls.  Has anyone else experienced this problem - or are we looking for these codes in the wrong data warehouse table/report.

Many thanks!

- Robin

[rubyn]

Hi Robin,

Since the PAN code doesn't pay, you'll want to use the TL01 TimeLabor Reported Time reports out of BusinessObjects.  The Time & Labor data warehouse contains information about time reported and how it is incorporated into the payroll system, so it has a subset of the information that is captured in the transactional system.

If you have query viewer access M-Pathways and need more or real-time information, you can also run the MTL_RPTD_* or MTL_PAYABLE queries to view reported & payable time as well.  Specifically there is a MTL_PAYABLE_TIME_PAN_GROUP query that might meet your needs.

Hope this helps,

-Ruby

[Robin Wagner]

That worked!  THANK YOU VERY MUCH!  :)

[Chris Allan]

In case it's useful, I saved a report related to this in User-Shared > cjallan. I stripped out the ISRisms originally in it but it adds a little more to just pulling everything, like seeing RPN balances by person and percentage used against everyone paid. My assumption is every unit might be different so this generic pull might not meet everyone one's needs. I'm also no expert in the dataset but it looked straight-forward so if a more seasoned person wanted to review and provide feedback feel free. I'm just aware this matched the data ISR fed Time/Labor and there aren't a ton of qualifiers in the um-maintained reports so I felt comfortable with my approach.

I only have HR APPT VIEWER in M-Pathways, which doesn't include any PSQuery access. I assume other data pullers like me, not more directly involved in the HR/Payroll transactions, might find something like this useful.

[Robin Wagner]

Hi, Chris,

Good morning - and thank you SO MUCH for this BO report!  It seems to be working for Dearborn campus time reporting.  I will share with with others on our campus who may also need this report.  Thanks again!

- Robin

[Chris Allan]

You're welcome, Robin. The introduction of the PEL and PFL codes today spice things up a bit. We've been trying to make sure we understand how they will be used but have a few questions. I'll hold off saying how I think it will work for now to spare the potential of misinformation but adjust accordingly once a better understanding is acquired.

Chris

[Robin Wagner]

Good luck w/the new codes, reports, etc.  There's  probably no end to the new reporting and tracking we'll need to do for the next year!

[Caitlin Walton]

Thank you! I saved the report in my favorites hoping to modify it to include the new earnings codes rolled out yesterday. It appears they are not in the data set yet. I will look at it again tomorrow or early next week.

[Chris Allan]

You're welcome. I did adjust the version out there in User-Shared in anticipation of the new codes but will see how it shakes out when they start being used. I also footnoted the heck out of the About page to avoid liability. :-)

[Robin Wagner]

Thanks again, Chris!  I am working to modify your report to include Department Group, Department ID, and Job Code, re: temp or not temp.  Hoping to have a version to share by the end of the week!

[Chris Allan]

Good morning,

I wanted to make a quick note about the BusinessObjects report I shared earlier. With the introduction of PEL in April, the variable distinctly counting people was counting them per code. I've adjusted and compared to the Details in Excel and it looks distinct again.

I've updated the report's changelog in User-Shared > cjallan to mention this. Please consider grabbing a new copy of this if you've used it. Sorry if you've already been working with it.

As I mentioned before, mileage will vary with how your unit enters time, like with the concept of payable hours (there are a lot of codes that might not be for time worked), but if there's anything that looks to be flawed after you've looked through details in Excel, please let me know. My intention was to get something out there that can be useful as a start for others so that starting point would ideally be accurate in general, without any glaring flaws (whether from my own negligence or BusinessObjects funkiness).

Thanks,

Chris

 

[Caitlin Walton]

Thanks so much for these updates. I noticed that the shortcode in the 'Details' tab pulls the shortcode for combo codes entered on timesheets for mostly temps and a couple of biweekly employees. If I wanted to add a shortcode for all staff and faculty (monthly, biweekly, temps), I am guessing I would have to use the Payroll dataset, right?  

[Chris Allan]

Hi Caitlin,

You're welcome. Yes, the time/labor data is before the Dept Budget Earnings (DBE) is applied when payroll runs. The Time/Labor universe does have a DBE table to join that looks to use effective dates so theoretically one could try that, but I don't see any UM-Maintained reports out there that attempt it.

There is a "TimeLabor Distribution" report in the TL01 folder that looks to use Pay Ern Dist and is pretty simple. So something like that or another Payroll report using Pay Ern Dist would help in breaking down by where it was funded. 

The Ern Codes are a little more noisy than the Time Reporting Codes so on the payroll side you'll see RPN and RPT (temps). Once you pull the data down you'll have to review which are similar. The file on this page helps explain how TRCs become Ern Codes. The newer ones aren't in the file yet but you should be able to tell.

http://finance.umich.edu/finops/payroll/forms/timereportingcodesandearningscodesbyworkgroupnew

Good luck!

Chris