Dependencies
The validated setup dependencies that unlock downstream configuration and operation.
Configuration dependencies
Configuration Artifacts are not authored in any order an organization likes. They form a dependency graph: a downstream artifact only becomes available once the artifacts it depends on have been validated. This page is that graph — shown as a diagram, walked as a sequence, and fixed as exact prerequisites.
How It Works
Unlock is gated by the configuration governance lifecycle, not by draft existence. A downstream Configuration Artifact becomes available only when its prerequisites are VALIDATED; a DRAFT prerequisite does not unlock anything.
CA-CUSNED and CA-UNITYP have no prerequisites and are visible from the start. Everything else hangs off them. CA-OFFNAT and CA-GTMACC sit on separate branches: there is deliberately no edge between them in either direction. CA-BUSEQU is embedded inside CA-OFFNAT and is not a standalone node in the graph.
Unlock Sequence
The same graph read as the order of unlocks the standard defines:
- CA-CUSNED and CA-UNITYP are visible at start.
- CA-CUSNED plus CA-UNITYP validated unlocks CA-OFFNAT.
- CA-UNITYP validated unlocks CA-UNILIF.
- CA-UNILIF validated unlocks CA-PLMGMT.
- CA-PLMGMT validated unlocks CA-SHRSVC, only when the organization uses shared service providers.
- CA-CUSNED plus CA-UNITYP plus CA-UNILIF validated unlocks CA-GTMACC.
The CA-UNILIF shortcut
CA-UNILIF is optional as an explicitly authored area. If it is omitted, the effective lifecycle collapses to a single default stage — and that implicit single-stage basis still counts as the effective validated CA-UNILIF state for unlocking CA-PLMGMT and CA-GTMACC. Either way, lifecycle-sensitive downstream behavior always has an effective lifecycle basis to rely on.
Statements
The statements below state each prerequisite precisely.
- CA-CUSNED has no prerequisite.
- CA-UNITYP has no prerequisite.
- CA-OFFNAT requires CA-CUSNED and CA-UNITYP validated.
- CA-BUSEQU is selected inside CA-OFFNAT and is not a separate unlock node.
- CA-UNILIF requires CA-UNITYP validated.
- CA-PLMGMT requires the effective CA-UNILIF lifecycle basis.
- CA-SHRSVC requires CA-PLMGMT validated, only when shared service providers exist.
- CA-GTMACC requires CA-CUSNED, CA-UNITYP, and the effective CA-UNILIF lifecycle basis.
- CA-OFFNAT and CA-GTMACC are separate, independent configuration branches.
- A downstream Configuration Artifact unlocks only on a VALIDATED prerequisite basis, never on DRAFT existence.
Why It Matters
The order is part of the standard, not a convenience. Each artifact gives meaning to the ones after it — there is no meaningful Offering Nature before customers and units exist, and no settled financial governance before a lifecycle basis exists. Following the graph guarantees every configuration choice rests on a basis that is already true.
Related
- Grammar — the common rules and states behind unlock semantics.
- Operational Readiness — the validated minimum this graph leads to.
- CA-UNILIF — the optional artifact and its single-stage default.
- CA-BUSEQU — why it is embedded in CA-OFFNAT, not a node here.