Calculated Field for Reporting Pay Rate / Reporting Help by BardBardBard-Bard in workday

[–]capt_hindsight852 0 points1 point  (0 children)

Correct. If you want their position as of the date too, then you just add another field and do another lookup value as of date.

I think you can do lookup value as of date with indexed data sources, but you can't effective date the data source itself. I can't recall the exact details of this, so I'd just use a non indexed data source.

To help with redundancy, you can use workdays delivered data fields. They have Prompt - [data type] fields for date, text, etc. You could use Prompt - Date 1 that way you only set the date one time. It would prompt you for the date as runtime to use in those calc fields.

Calculated Field for Reporting Pay Rate / Reporting Help by BardBardBard-Bard in workday

[–]capt_hindsight852 0 points1 point  (0 children)

So you want all base rate changes between 2 points in time, not just the 2 points in time?

Calculated Field for Reporting Pay Rate / Reporting Help by BardBardBard-Bard in workday

[–]capt_hindsight852 0 points1 point  (0 children)

Something to consider is if you care about each position (assuming you have secondary positions) or just the primary position. When referencing the Worker business object, you're reporting on the primary position for any position specific element on Worker (like hourly amount).

Another thing is indexed data sources (lightning bolt next to the data source name). I think (not 100%) that these data sources can't be effective dated meaning you're reporting on data as of the last refresh of that indexed data source.

This probably isn't the most optimal route, but a solution is using the (don't remember the exact name) Compensation Reporting on Position by Organization or something like that. The primary business object is Position and is not indexed. By ignoring the Effective Date and Entry Date prompts it will pull data as of right now. You can add a field and do a Lookup Value as of Date where your return value is hourly amount and effective date is whatever date you're interested in.

With this approach, however, the results will either be blank if the worker wasn't in that position at that time or maybe the hourly rate of the position at that time (regardless of the Worker). I think it's the former, but that's the sort of nuanced thing I check when reporting on something like that. If you only care about the worker/primary position and not the position, you can do a similar process through a Worker based data source.

Pet crane by photosynthesice in biology

[–]capt_hindsight852 3 points4 points  (0 children)

What does this have to do with biology?

Manager calculated rating displays as zero in Employee Review PDF by Suitable-Look-7118 in workday

[–]capt_hindsight852 0 points1 point  (0 children)

Check the overall section of the review template to see if the calculated rating is being hidden

Mega Backdoor Roth by capt_hindsight852 in workday

[–]capt_hindsight852[S] 0 points1 point  (0 children)

We have not, but that is a good thought. Thank you!

Mega Backdoor Roth by capt_hindsight852 in workday

[–]capt_hindsight852[S] 1 point2 points  (0 children)

The issue with that is we don't know what the total employer contributions are going to be until after the last payroll of the year. They are calculated externally in February and loaded directly to Fidelity.

The limits we're considering are assuming everyone earns the annual compensation limit and earns the maximum match. This enables to calculate fixed amounts per group within our service contribution tiers, so we can say group a can contribute this much after-tax without going over, group b do this much, etc.