[Datamart-News] Workday Payroll Datamart Tables/Queries (update)

[WALLACE Aaron * DAS]

OBIEE Workday users:

There has been a lot of concern and confusion around the new Workday information. One of the main topics is 'How best to pull and filter the data'. I wanted to assure you that DAS FBS is hard at work to help users with this issue. We have multiple teams working on creating some helpful reports in OBIEE. Once complete, I plan to load them to the OBIEE repository.

We do not have an estimated completion date; however, I assure you we are working hard to help all users with this information.

We will keep you posted on any updates or changes as soon as it is available.

Thanks for your patience and understanding,
Aaron Wallace
Sr. Datamart Business Analyst

From: Datamart-News <datamart-news-bounces at omls.oregon.gov> On Behalf Of WALLACE Aaron * DAS via Datamart-News
Sent: Thursday, January 19, 2023 12:42 PM
To: datamart-news at omls.oregon.gov
Subject: [Datamart-News] Workday Payroll Datamart Tables/Queries

Payroll/Workday users,

We wanted to clarify how Workday Payroll Datamart data is stored compared to OSPA Datamart data. In addition, how to filter effectively so that you are able to compare Workday data with SFMS data.

Per the Workday (WD) team, the new system does not process pay the same way that OSPA did in regards to pay period dates associated with Run 1 and Run 2. Unlike OSPA, which closed the pay period after Run 2, the pay period in WD is closes after Run 1, so the December period closed when WD payroll ran December Run 1 on December 28th.  Any adjustments made to the December pay period after that closed date are then considered "retro" entries and are processed in the open pay period; in this case January.  Therefore, if it is Dec Run 2, it is a "retro" to the December pay period and the data comes over to SFMA with a 01/31/#### pay period date, but may still have a 12/31/#### effective date. Take note, there will be a "retro period" assigned to those entries that will reflect December dates though, with one caveat.

The way that retro-active entries are processed in WD, for instance adding OT that wasn't paid on the December pay period, will show as results for the January pay period, with a December retro period, but the incremental employer taxes will be calculated in January and will never have the retro period associated with it. WD does not calculate taxes retroactively. Those data rows will have a January pay period and a blank retro period.

In order to isolate Run 1 and Run 2 data, the key is going to be to filter by the 'report effective date'. This is the date the data was loaded into OBIEE.  All the results from the mid-January effective date (1/11/23) would be for corrections to December, or for January pay for a term employee (typical Run 1 fair). Since December is closed, WD can't calculate results with a regular period end date of 12/31, it just doesn't work that way.

Again, with some exceptions, if users' filter by the 'report effective date', it will match SFMS, since WD generates the Datamart reports and the SFMA reports using the same completion dates from WD. Also, now that WD is loading two times a month, users can filter by the 'report effective date' to see all the data that was loaded for a specific run. You are able to verify the two runs, during a month, on the Workday or Datamart calendars, on the respective websites.

If you have additional questions about WD data, please contact WD support.
Aaron Wallace
Sr Datamart Business Analyst

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omls.oregon.gov/pipermail/datamart-news/attachments/20230316/127e6492/attachment.html>