Manufacturing and quality on Snowflake

Supplier quality incident (8D) on Snowflake

Turns a quality notification against a supplier into an 8D case the supplier works on a portal screen, with blocked stock, return delivery and closure recorded in the ERP.

SCREENSDATA HANDLERSSNOWFLAKE · READ IN PLACES01 IncidentsS02 Incident detailS03 8D reportS04 VerificationS05 CommercialS06 Boarddh_quality_notificationQuality notificationCONFORMED.QUALITY_NOTIFICATIONdh_supplier_masterSupplier masterCONFORMED.VENDORdh_inspection_lotInspection lotCONFORMED.INSPECTION_LOTdh_goods_receiptGoods receiptCONFORMED.GOODS_MOVEMENTdh_stock_positionStock positionCONFORMED.STOCK_POSITION ·HISTORY.STOCK_DAILYdh_purchase_order_linePurchase order lineCONFORMED.PURCHASE_ORDER_LINE ·HISTORY.PO_LINE_VERSIONSWRITE BACK TO SNOWFLAKEQuality notification → MERGE into LIMA.APP_DECISIONSStock position → MERGE into LIMA.APP_DECISIONSPurchase order line → MERGE into LIMA.APP_DECISIONS · PO change to the ERProws stay in Snowflake · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Snowflake 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.
6
objects read in place from Snowflake
catalogue
6
screens on those rows
catalogue
6 days
to production-grade
estimate
3
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Snowflake objects behind each handler

Tables are read in place through the native Snowflake connector: the app sends only the filter and the columns it needs, Snowflake returns the matching rows. The Backbone landing model (RAW, CONFORMED and HISTORY schemas) is the usual source, so history and aggregates are already prepared.

ObjectRead fromFields the app usesFreshness
Quality notificationCONFORMED.QUALITY_NOTIFICATIONtype (type) · vendor_id (vendor) · notification_id (number) · material_id (material)prepared by the Backbone; refreshed on its schedule
Supplier masterCONFORMED.VENDORvendor_id (id) · name (name) · country (country) · blocked_flag (block)prepared by the Backbone; refreshed on its schedule
Inspection lotCONFORMED.INSPECTION_LOTlot_id (lot) · material_id (material) · origin (origin) · result (result)prepared by the Backbone; refreshed on its schedule
Goods receiptCONFORMED.GOODS_MOVEMENTdocument_id (document) · po_number (po) · material_id (material) · qty (qty)prepared by the Backbone; refreshed on its schedule
Stock positionCONFORMED.STOCK_POSITION · HISTORY.STOCK_DAILYmaterial_id (material) · plant (plant) · storage_location (sloc) · on_hand_qty (on hand)prepared by the Backbone; refreshed on its schedule
Purchase order lineCONFORMED.PURCHASE_ORDER_LINE · HISTORY.PO_LINE_VERSIONSpo_number (number) · po_line (line) · vendor_id (vendor) · material_id (material)prepared by the Backbone; refreshed on its schedule
The trigger

The start criterion in Snowflake's own fields

In plain words: A quality notification of the supplier type created in the ERP, from a rejected inspection lot at goods receipt or from the floor.

The criterion runs in Snowflake 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 Snowflake fields
type = supplier and vendor_id is present

# the same criterion in canonical fields
{qn.type} = supplier and {qn.vendor} is present
What the app writes back

Through MERGE and the system of record

Decisions are recorded in a Lima-owned table in Snowflake through stage, COPY INTO and MERGE, so analytics 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 (8D disciplines recorded as tasks with status and dates) 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
Quality notification8D disciplines recorded as tasks with status and dates; notification set to complete at D8MERGE into LIMA.APP_DECISIONS
Stock positionaffected quantity moved to blocked stock and returned to the supplier with a return deliveryMERGE into LIMA.APP_DECISIONS
Purchase order linereplacement quantity added to the order lineMERGE into LIMA.APP_DECISIONS · PO change to the ERP
Acknowledged and logged

Each write stores the identifier Snowflake 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

Snowflake roles and row-access policies are mapped to Lima access policies once, so a person sees the same rows in the app that they see in a worksheet.

  • A Snowflake role for the connector with SELECT on the conformed schemas and INSERT and MERGE on the Lima decision schema
  • A warehouse sized for the app's queries (an X-Small serves most screens)
  • The Backbone landing model in place for the objects the app uses, or your own conformed tables registered
  • The system of record connected for the operational write
Register the handlers6 objects from the catalog; each shows its rows at once.
Why the lake

History and aggregates, read where they land

This app reads quality notification from Snowflake 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 Snowflake 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 placeSnowflake
Decision recordMERGE into a Lima-owned tablebeside the history
Operational writeto the ERP of record through its interfaceacknowledged
GrantsSnowflake roles and row policies honouredat read time
Nearby

This app on other systems, and other apps on Snowflake

Supplier quality incident (8D) on

Other apps on Snowflake

Terms on this page

8DA problem-solving method in 8 steps: team, problem, containment, root cause, corrective action, validation, prevention and closure.
Inspection lotThe ERP record for a set of goods inspected at receipt, holding the results and the usage decision.
Read in placeThe rows stay in Snowflake; the handler sends the filter and the columns and Snowflake returns the matching rows.
Questions

Does this app copy data out of Snowflake?

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

What does Snowflake 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.