A blueprint is a ready pipeline you copy and adjust: sources, operators, checks and schedule already in place. Eight are available; each names what it is for, what it needs and what you change.
Reads a named set of SAP tables through the released function module in partitions, with a count and control total per table. Change: the table list and the session cap.
Keeps a copy current from a database log or SAP change pointers, with checkpoints and ordered replay. Change: the source, the target and the interval.
Consolidates the same entity from several systems into one governed record with a second person's approval. Change: the match rule and the survivorship rule.
Lands SAP or Oracle tables in Snowflake, Databricks, Fabric or object storage with types set, keys complete and deletes applied. Change: the target and the partition keys.
Refreshes dimension and fact tables in dependency order with history handling. Change: the tables and the history rule.
Writes corrected master data back to the owning system with confirmation and a ledger. Change: the objects and the approval rule.
Builds Part, PartSource, BillOfMaterial, OnHand, ScheduledReceipt and IndependentDemand from SAP or Oracle, in referential order, with the nine checks. Change: the production-version mapping.
Validates hierarchies and loads members before measures in a named version. Change: the hierarchy definitions and the grain.
Blueprints are versioned like any pipeline; a copy records which blueprint and version it came from. Usage counts are added when enough estates run each one to publish a meaningful number.