Domain catalogue Products on Databricks

Bill of materials on Databricks

One governed structure per product per plant: components, quantities, effectivity, alternates and phantoms, consistent with the golden materials.

SOURCES, READ IN PLACEDatabrickslakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN BILL OF MATERIALSBill of materialsone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
The objects the domain reads in place on Databricks, the assembly steps, and who reads the result. Writes go through MERGE INTO a governed catalog.
2
objects read in place from Databricks
catalogue
4
attribute groups assembled
catalogue
5 days
to production-grade
estimate
1
write path, acknowledged and logged
catalogue
0
rows copied to start
product
What the domain reads

The Databricks objects behind the golden record

Delta tables are read in place through Unity Catalog with filters and aggregates pushed down; nothing is copied out.

ObjectRead fromFields the domain usesFreshness
BOM headersilver.bombom_id · material_key · plant · usage · alternative · base_qty · statusas fresh as the landing pipeline; live for governed tables
BOM componentsilver.bom_componentbom_id · position · component_key · quantity · uom · valid_from · valid_to · phantomas fresh as the landing pipeline; live for governed tables
The keys

How bill of materials records match, in this system's fields

parent item + plant + usage + alternativecomponent item + positionchange number

The first object above carries the strong keys; the standardised attributes come from the same rows. Components resolve to golden materials first, so every component points at the golden item.

What is written back

Through the interfaces Databricks supports

Golden records and their history are written with MERGE INTO into a governed catalog, registered in Unity Catalog with lineage.

InterfaceUsed forResult
MERGE INTO gold.bom on the golden key; history in gold.bom_history; registered in Unity Cataloggolden values approved for write-back: header; components; effectivitythe id or error Databricks returns, stored beside the change

Write-back is off per object until a test write succeeds, and approval rules can require a person per object. Reconciliation compares the source row with the golden value on a schedule.

Access and prerequisites

What is in place before the first build

Unity Catalog grants and row filters are honoured; Lima adds its own layers on top.

Register the objects2 objects from the connector catalogue; each shows its rows at once.
Nearby

This domain on other systems, and other domains on Databricks

Bill of materials on

Other domains on Databricks

Terms on this page

EffectivityThe date or serial range from which a component belongs to the structure.
PhantomAn assembly that exists in the design and is passed through in production; its components explode straight through.
Read in placeThe rows stay in Databricks; Lima sends the filter and the columns and Databricks returns the matching rows.
Questions

Does this domain copy data out of Databricks?

The golden record reads the objects above in place. History the pivot needs at scale is landed in your lake by the Backbone, under the same keys, security and audit.

What does the Databricks team need to do?

Grant the read access and the write interfaces listed above and agree the refresh method. Nothing is installed in Databricks.

Can we start with reads only?

Yes. Write-back stays off per object until a test write succeeds; the golden view, the API and the pivots work from day one on reads.

See your first domain built on your data

Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.