Manufacturing and quality on Databricks

Production schedule change on Databricks

Lets a planner move firmed production orders on a live schedule, shows the effect on components and customer dates, collects the signatures and writes the new dates to the ERP.

SCREENSDATA HANDLERSDATABRICKS · READ IN PLACES01 Change requestS02 ScheduleS03 EffectsS04 Production checkS05 Sales updateS06 ApprovalS07 Boarddh_production_orderProduction ordersilver.production_orderdh_planned_orderPlanned ordersilver.planned_orderdh_sales_order_lineSales order linesilver.sales_order_linedh_stock_positionStock positionsilver.stock_position · gold.stock_dailydh_routingRoutingsilver.routing_operationWRITE BACK TO DATABRICKSProduction order → MERGE INTO gold.lima_app_decisionsPlanned order → MERGE INTO gold.lima_app_decisionsSales order line → MERGE INTO gold.lima_app_decisionsrows stay in Databricks · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Databricks object it reads in place. Writes below the line go through MERGE into a Lima-owned table, with the operational write to the ERP of record.
5
objects read in place from Databricks
catalogue
7
screens on those rows
catalogue
7 days
to production-grade
estimate
3
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Databricks objects behind each handler

Delta tables in Unity Catalog are read in place through a SQL warehouse: the app sends only the filter and the columns it needs. The Backbone landing model (bronze, silver and gold) is the usual source, so history and aggregates are already prepared and lineage is registered in Unity Catalog.

ObjectRead fromFields the app usesFreshness
Production ordersilver.production_orderorder_id (number) · material_id (material) · order_qty (qty) · start_date (start)prepared by the Backbone; refreshed on its schedule
Planned ordersilver.planned_orderplanned_order_id (number) · material_id (material) · qty (qty) · start_date (start)prepared by the Backbone; refreshed on its schedule
Sales order linesilver.sales_order_lineso_number (number) · so_line (line) · customer_id (customer) · material_id (material)prepared by the Backbone; refreshed on its schedule
Stock positionsilver.stock_position · gold.stock_dailymaterial_id (material) · plant (plant) · storage_location (sloc) · on_hand_qty (on hand)prepared by the Backbone; refreshed on its schedule
Routingsilver.routing_operationrouting_group (group) · operation (operation) · work_center (work center) · setup_time (setup)prepared by the Backbone; refreshed on its schedule
The trigger

The start criterion in Databricks's own fields

In plain words: A planner or production lead starts a change on S01 for a work center and a window; a breakdown recorded on the floor screen starts one as well.

This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.

Start

A planner or production lead starts a change on S01 for a work center and a window; a breakdown recorded on the floor screen starts one as well. The instance then reads its rows from Databricks through the handlers above.

What the app writes back

Through MERGE and the system of record

Decisions are recorded in a Lima-owned gold table with MERGE INTO, so notebooks and dashboards see them next to the history. The operational write goes to the system of record through its released interface, and the app records the acknowledgement. For this app the operational change (start and finish dates changed through the production order interface) goes to SAP S/4HANA or Oracle Fusion through its released interface, and the pair pages for those systems show the exact call.

ObjectWhat changesInterface
Production orderstart and finish dates changed through the production order interfaceMERGE INTO gold.lima_app_decisions
Planned orderfirmed planned orders rescheduledMERGE INTO gold.lima_app_decisions
Sales order lineconfirmed dates updated on the affected customer ordersMERGE INTO gold.lima_app_decisions
Acknowledged and logged

Each write stores the identifier Databricks returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.

Access and prerequisites

What is in place before the first build

Unity Catalog grants and row filters are mapped to Lima access policies once, so a person sees the same rows in the app that they see in a notebook.

  • A service principal with SELECT on the silver and gold schemas and MODIFY on the Lima decision schema
  • A SQL warehouse (a small serverless warehouse serves most screens)
  • The Backbone landing model in place for the objects the app uses, or your own silver tables registered
  • The system of record connected for the operational write
Register the handlers5 objects from the catalog; each shows its rows at once.
Why the lake

History and aggregates, read where they land

This app reads production order from Databricks because the screens need history at scale: months of rows, aggregates by period, several versions. The Backbone lands the objects in the conformed model and refreshes them on a schedule, and the handler reads them in place with the filter and the columns pushed down. The person's grants in Databricks decide what they see.

The operational rows the person acts on can come live from the ERP in the same app: one handler per object per system, and a screen that shows both.

Readsconformed and history tables, in placeDatabricks
Decision recordMERGE into a Lima-owned tablebeside the history
Operational writeto the ERP of record through its interfaceacknowledged
GrantsDatabricks roles and row policies honouredat read time
Nearby

This app on other systems, and other apps on Databricks

Production schedule change on

Other apps on Databricks

Terms on this page

Firmed orderA production or planned order the planning run leaves in place; a person changes its dates and quantity.
Work centerThe machine or line where an operation runs; the routing states its setup and run time.
Read in placeThe rows stay in Databricks; the handler sends the filter and the columns and Databricks returns the matching rows.
Questions

Does this app copy data out of Databricks?

The screens read through handlers that leave the rows in Databricks. The conformed tables it reads were landed there by the Backbone from the ERP; the app reads them there.

What does Databricks need to allow?

The prerequisites above: an integration identity with read rights on the objects listed and write rights on the interfaces named, connectivity, and the scopes agreed with the process owner.

Can I run it on another system as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, and the app's other system pages show them.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.