Sales and service on Snowflake

Customer complaint resolution on Snowflake

Takes a customer complaint from the first contact to a resolution the customer has been told about, with the order lines and prices checked in place.

SCREENSDATA HANDLERSSNOWFLAKE · READ IN PLACES01 Raise complaintS02 Complaint queueS03 InvestigationS04 ResolutionS05 Customer updateS06 Complaint boarddh_customer_masterCustomer masterCONFORMED.CUSTOMERdh_sales_order_lineSales order lineCONFORMED.SALES_ORDER_LINEdh_price_conditionPrice conditionCONFORMED.PRICE_CONDITIONdh_return_orderReturn orderCONFORMED.RETURN_ORDERWRITE BACK TO SNOWFLAKESales order line → MERGE into LIMA.APP_DECISIONSReturn order → MERGE into LIMA.APP_DECISIONSrows 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.
4
objects read in place from Snowflake
catalogue
6
screens on those rows
catalogue
5 days
to production-grade
estimate
2
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
Customer masterCONFORMED.CUSTOMERcustomer_id (id) · name (name) · country (country) · sales_org (sales org)prepared by the Backbone; refreshed on its schedule
Sales order lineCONFORMED.SALES_ORDER_LINEso_number (number) · so_line (line) · customer_id (customer) · material_id (material)prepared by the Backbone; refreshed on its schedule
Price conditionCONFORMED.PRICE_CONDITIONmaterial_id (material) · customer_id (customer) · amount (amount) · currency (unit)prepared by the Backbone; refreshed on its schedule
Return orderCONFORMED.RETURN_ORDERreturn_id (number) · customer_id (customer) · material_id (material) · qty (qty)prepared by the Backbone; refreshed on its schedule
The trigger

The start criterion in Snowflake's own fields

In plain words: A complaint is submitted on S01 by the customer, or logged by customer service from a call or from the service case in the CRM.

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 complaint is submitted on S01 by the customer, or logged by customer service from a call or from the service case in the CRM. The instance then reads its rows from Snowflake through the handlers above.

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 (credit memo request or replacement order line created as a sales document with the complaint number as reference) 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
Sales order linecredit memo request or replacement order line created as a sales document with the complaint number as referenceMERGE into LIMA.APP_DECISIONS
Return orderreturn order created for pickup of the goods in disputeMERGE into LIMA.APP_DECISIONS
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 handlers4 objects from the catalog; each shows its rows at once.
Why the lake

History and aggregates, read where they land

This app reads customer master 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

Customer complaint resolution on

Other apps on Snowflake

Terms on this page

Credit memo requestA sales document that asks finance to credit the customer; it becomes a credit note once released.
Return orderThe sales document that authorises goods to come back and tells the warehouse to expect them.
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.