Careful consideration, best practices, and use cases must be vetted carefully before designating cost centers to fields in this application.
IMPORTANT INFORMATION: Each cost center can only map to a roster time and labor field in this application once.
Workforce Ready offers nine cost center trees. Each and any cost center tree can be used to uniquely pair with one and any of the thirty-five designated fields in this application.1
For example, suppose that you have chosen to map the organizational level of Unit in this application to Cost Center 1 with special event activities paid through Cost Center 2. A special event is an organizational Unit deployed on the Roster which encompasses two cost centers in this use case. Which cost center should own the Unit field?
Whether Cost Center 1 or Cost Center 2 should own the Unit field depends on your business rules, workflow, given configuration, staffing requirements, other overlaps, and whether or not a different field in this application is a better fit for Cost Center 1 or Cost Center 2. The end result here is to always send a Workforce Ready timesheet data for time records with a cost center association.
Use Cases and Considerations
EXAMPLE 1:Suppose in this use case, you found that employees working a special event are given a work code time entry with a Detail Code. In which case, the Detail Code field could then be mapped to Cost Center 2.
EXAMPLE 2: Suppose that later on in the planning phase of the integration you found that employees can request overtime pay for a report writing task using a Detail Code.
In this scenario, the employee works eight hours of regular pay in Unit 1, stays in Unit 1 and works two hours of overtime to finish a report. The Overtime work code requires Detail Code input, and Report Writing is listed as a Detail Code. Report Writing is paid through Cost Center 3. Here we have the Detail Code pointing to Cost Center 3, whereas in the previous scenario the Detail Code pointed to Cost Center 2.
In either case, the Detail Code can only belong to one cost center. You will need to explore and choose any of the remaining thirty-five fields to reference and pair the Detail Code to Cost Center 2 or Cost Center 3.
In the image below, the Detail Code field was paired with Cost Center 3. Note Cost Center 1 was referenced twice by Unit 1 in the export to correctly show each time entry record along with the cost center associated.
Other Considerations
- An Off-Roster record’s external ID, looks like this {off}, the text off displays enclosed in curly brackets {}.
- An unassigned record looks like this {una}, the text una displays enclosed in curly brackets.
- A suppressed position varies and dependent on the position’s abbreviation but always prefaced with a period, so a Lead position with the abbreviation of ‘Le’ looks like this: {.Le}, the text.Le is enclosed in curly brackets.