Runs quality rules on live master data, routes each failing record to its steward with the fix options, and writes the correction back to the ERP.
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.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Material master | silver.material | status (status) · planned_lead_time (lead time) · material_id (id) · description (desc) | prepared by the Backbone; refreshed on its schedule |
| Supplier master | silver.vendor | payment_terms (terms) · vendor_id (id) · name (name) · country (country) | prepared by the Backbone; refreshed on its schedule |
| Customer master | silver.customer | sales_org (sales org) · customer_id (id) · name (name) · country (country) | prepared by the Backbone; refreshed on its schedule |
| Purchase order line | silver.purchase_order_line · gold.po_line_versions | po_number (number) · po_line (line) · vendor_id (vendor) · material_id (material) | prepared by the Backbone; refreshed on its schedule |
In plain words: A record that fails one of the active quality rules, such as an active material with a lead time of 0, a supplier with empty payment terms, or a customer with an empty sales organisation.
The criterion runs in Databricks through the data handler, so only the matching rows return. The editor shows the rows it selects, and their count, as it is written.
# start criterion in Databricks fields (status = 'active' and planned_lead_time = 0) or payment_terms = '' or sales_org = '' # the same criterion in canonical fields ({material.status} = 'active' and {material.lead_time} = 0) or {vendor.terms} = '' or {customer.sales_org} = ''
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 (field corrected through the material interface) goes to SAP S/4HANA or Oracle Fusion through its released interface, and the pair pages for those systems show the exact call.
| Object | What changes | Interface |
|---|---|---|
| Material master | field corrected through the material interface; exception flag recorded beside the record | MERGE INTO gold.lima_app_decisions · operational write to the ERP |
| Supplier master | payment terms, country or purchasing data corrected; duplicate flagged for deletion | MERGE INTO gold.lima_app_decisions |
| Customer master | sales organisation data completed or corrected | MERGE INTO gold.lima_app_decisions |
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.
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.
This app reads material master 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.
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.
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.
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.
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.
