Collects each function's view of a new material on its own screen, checks duplicates and completeness, and creates the record in the ERP when every view is released.
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 | material_id (id) · description (desc) · material_type (type) · plant (plant) | prepared by the Backbone; refreshed on its schedule |
| Bill of materials | silver.bom_component | parent_material (parent) · component_material (component) · component_qty (qty) · valid_from (valid from) | prepared by the Backbone; refreshed on its schedule |
| Supplier master | silver.vendor | vendor_id (id) · name (name) · country (country) · blocked_flag (block) | prepared by the Backbone; refreshed on its schedule |
| Price condition | silver.price_condition | material_id (material) · customer_id (customer) · amount (amount) · currency (unit) | prepared by the Backbone; refreshed on its schedule |
In plain words: A requester submits S01.
This app starts from a screen, so the first read happens when the instance opens; the criteria on the arrows use the fields above.
A requester submits S01. The instance then reads its rows from Databricks through the handlers above.
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 (material master created with basic, plant, purchasing, sales and accounting views 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 | material master created with basic, plant, purchasing, sales and accounting views through the material interface; status set to active when every view is complete | MERGE INTO gold.lima_app_decisions · operational write to the ERP |
| Price condition | initial sales price condition created for a sold material with its validity | 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.
