Map every Workday organisational primitive — Company, Cost Centre, Region, Supervisory Organisation and the rest — to D365 legal entities, operating units, financial dimensions and organisation hierarchies.
Workday's organisational model is tighter, flatter, and more integrated than the fifteen-field lattice that SAP practitioners are accustomed to. It is, however, considerably more unusual in one respect: many Workday organisational objects are themselves Worktags.
Workday's Financial Management configuration uses the following organisational objects. A practitioner coming from SAP will notice immediately that the list is shorter and that the objects serve fewer roles each.
The feature that distinguishes Workday's org model from conventional ERP designs is that organisational objects are themselves first-class Worktags. A Cost Centre is not only a node in the Cost Centre Hierarchy — it is also a valid Worktag Type value that can appear on any transactional line, including lines on documents that have…
The table below summarises the mapping from every Workday organisational primitive to its D365 equivalents.
D365's organisation hierarchy model is purpose-driven: a single hierarchy tree can be assigned one or more purposes, and different D365 modules read different purposes. The main purposes relevant to a Workday migration are:
Workday's organisational model is smaller than SAP's but more unusual in one respect: organisational objects are themselves Worktags, serving simultaneously as hierarchy nodes, approval-routing anchors, and dimensional values on postings.