Configuration

CA-SHRSVC · Shared Services

The payment model for shared service providers inside an O2A organization.

Configuration artifact

CA-SHRSVC configures the shared-services payment model. It is conditional: it is required only when the organization has shared service providers whose economics the setup basis must recognize.

How It Works

CA-SHRSVC configures the shared-services payment model used by shared-service offerings. It builds on settled financial governance, so it requires CA-PLMGMT first and only becomes available once CA-PLMGMT is validated. It enters operational readiness only for organizations that use shared service providers.

Billing model. Each shared-service offering is billed through one of three billing types — percentage-of-revenue, number-of-employees, or fixed amount. Choosing the type is an explicit act; no type is pre-selected. CA-SHRSVC defines default values per billing type that pre-fill the chosen type's parameters, adjusted per offering. Measures are taken on the consuming node: its revenue for percentage-of-revenue, its headcount for number-of-employees. Each consuming node's charge is borne by that node's resolved payer — SELF, PARENT, or ORGANIZATION — set per node, never as one organization-wide setting. Charges materialize through a periodic billing run as ledger events, with one shared cadence for every shared service.

Dependency role. CA-SHRSVC is conditional — relevant only if shared service providers exist. Its prerequisite is CA-PLMGMT validated. It unlocks no further configuration artifact; it completes the financial branch when shared services are in use.

Statements

  • CA-SHRSVC means Shared Services.
  • CA-SHRSVC configures the shared-services payment model.
  • The shared-services payment model applies to shared-service offerings.
  • A shared-service billing type is percentage-of-revenue, number-of-employees, or fixed amount.
  • CA-SHRSVC defines default values per billing type.
  • Shared-service measures are taken on the consuming node.
  • A consuming node's shared-service charge is borne by its resolved payer: SELF, PARENT, or ORGANIZATION.
  • Shared-service charges materialize through a periodic billing run as ledger events.
  • CA-SHRSVC is required only when shared service providers exist.
  • CA-SHRSVC requires CA-PLMGMT validated.

Why It Matters

Shared service providers move value between units in a way the financial model must account for. When they exist, the setup basis is incomplete until their payment model is configured; when they do not, this artifact does not apply.