The enterprise
ConceptfoundationThe single legal and reporting boundary for the installation. Every division, legal entity, business unit, department, location, job and position is defined within it.
What people get wrong
The confusions are the difficulty. Each one is a belief that sounds right and is not.
- That an installation holds several enterprises. It holds one, and objects cannot be moved between installations.
- That the enterprise is the same thing as the legal entity. The enterprise is the boundary; the legal entity is one organisation inside it.
Recall it
What is the enterprise, and what is the one thing about it you cannot change?
The enterprise is the single legal and reporting boundary for the installation. Every division, legal entity, business unit, department, location, job and position is defined within it. An installation holds exactly one, and you cannot move objects between installations.
Memory hook: One wall, everything inside it. If you remember that the enterprise is a boundary rather than an object, you stop looking for a way to create a second one.
Rests on COREHR-ORDER-001.
Taught in
- Configuration order, and the failures it preventsSeven setup steps in dependency order, two of them decisions that can fail. Get the order wrong and the application rejects children without saying which parent it wanted.
- Three Structures, Three Functional Areas, and Where Each Setting LivesLegal, managerial and functional are three axes rather than one nesting — and their setup tasks are split across three functional areas, with one record that is created in one work area and revised in another.
Related
- Terminology glossary — what a term means, and what people get wrong when they use it