Skip to content

Core systems

Core systems are the unit DataMaker Cloud plans are priced in. A Team plan includes one, Enterprise includes up to ten, and additional systems are priced per contract. Settings → License shows how many you have declared against your plan’s allowance.

What counts as a core system

A core system is one business application DataMaker serves, for example an SAP S/4HANA landscape or an Oracle Fusion instance.

Every environment of one application is one core system. Dev, QA and production are three connections pointing at the same business application, and that application is what your plan is billed for. Connecting a second environment does not consume a second system.

The large-system multiplier

A core system serving more than 5,000 named users counts as three. Named users here means users of your SAP or Fusion system, not users of DataMaker.

The threshold is strict: exactly 5,000 named users counts as one, 5,001 counts as three.

Where no named-user figure has been declared for a system, it counts as one. The multiplier is a charge, and applying it needs a number to apply it to.

Your declaration governs

DataMaker cannot reliably observe your landscape. Middleware such as SAP Cloud Integration can hide system identifiers from inspection, and a system DataMaker cannot see is still one you are served for. So the count is what you declare, not what the product detects.

Automators records your declared systems against your licence. Contact your Automators contact to add, change or withdraw one.

What DataMaker does observe, it reports beside the declaration as supporting evidence for your review:

  • Observed systems, counted from the connections you have tagged with a system key.
  • Untagged connections, reported as untagged rather than folded into a count. An untagged connection might be a system of its own or a third environment of one already counted, and guessing would produce a number that looks authoritative and is not.

A difference between the declared and observed figures is not an error. It is the thing your account review is there to talk about.

Going over the allowance

Nothing is blocked. Sustained use above the allowance is an upgrade conversation at your next review, never an outage. Your workspaces, connections and scenarios keep working exactly as before.

See also