Reference data sets

Sets partition set-enabled workforce objects — grades, jobs, departments and locations among them. The common set is shared; additional sets are local. The design rule: start with everything in the common set. Create additional sets only when a country or operating unit genuinely needs its own catalogue. The cost: a new grade created once per set, a job catalogue maintained three times — multiplied by however many sets were created for tidiness. The genuine use case: a country whose job titles, grades or location structures are legally or culturally distinct and will never be shared. Then the build: create a set, assign it to a business unit as the default, create a set-enabled object in each set, and demonstrate the visibility difference from two business units — which is the payoff. Set assignment is per business unit and per object type. That granularity is useful and very easy to configure…

In this module: Module 4 · Legal Entities, LDGs, PSUs, TRUs and Business Units

1. 1What we are building
2. 2The decisions you cannot undo
3. 3The object map
4. 4Legislative data groupsFree preview
5. 5Legal employers, PSUs and TRUs
6. 6Running the structure design workshop
7. 7Four worked country models
8. 8Legal jurisdictions and authorities
9. 9Creating legal entities
10. 10Designating legal employers, PSUs and TRUs
11. 11Creating legislative data groups
12. 12Business units
13. 13Reference data sets
14. 14Associating business units with legal employers
15. 15Deduction levels and calculation cards
16. 16Proving the structure works
17. 17What breaksFree preview
18. 18Lab briefing: the Northwind structure
19. 19Lab solution walkthrough