A data handler provides data to an app as rows with columns, and takes rows back.
| Handler | Defined on | Reads | Writes | Typical use |
|---|---|---|---|---|
| Table handler | A federated table registered in the catalog: an ERP table, a lake table, an application object | The rows that match the filter, with the columns the screen needs, in place | Through the source's released interface: BAPI, REST, MERGE | Order lines, vendors, stock, claims, tickets |
| Query handler | A saved query across one or several sources, with parameters | The query result, computed in the sources with pushdown | Usually read-only; writes go to the underlying tables | Stock by plant, consumption against contract, history by month |
| Pipeline handler | The result of a Backbone pipeline or a data-science pipeline | A prepared, checked result set, refreshed on the pipeline's schedule | Results can be written to a target the pipeline owns | Projected stock, supplier scores, forecast error, a model's prediction |
| API or file handler | A REST endpoint, a CSV or Excel file, a document | Rows parsed from the answer or the file | Calls the endpoint; writes a file | Screening services, carrier APIs, uploads from suppliers |
| Device feed handler | An IoT or event stream | The latest values or a window | Commands where the device allows | Temperature on a batch, a scan at a dock, a counter on a line |
A table handler is the workhorse: it is the federated table itself, seen through a filter and a column list, so a screen on it shows live rows and a write on it goes to the source. A query handler saves a question, for example stock by plant and material with its cover in weeks, and lets screens and criteria reuse it with parameters. A pipeline handler is for results that take preparation: the Backbone lands them, checks them and refreshes them on a schedule, and the app reads the prepared rows.
API, file and device handlers cover the rest of the world: a sanctions screening service, a carrier's tracking API, a spreadsheet a supplier uploads, the temperature feed on a cold room. Their rows look like any other rows to the screens and the expressions.
Handlers are registered once per app, with their operations and their audit information, and listed on a screen that shows where each one is used. A handler can be shared between apps through the catalog, so a vendor handler defined for onboarding serves the scorecard and the invoice apps too, with its lineage recorded.
The catalog is the same one the Data Fabric and the Backbone use, so a table registered for a pipeline is available to an app the same day, and the lineage of an app's screen shows the source columns it came from.
Because the handler reads in place, an app is possible on the day the source is connected, and it shows what the source shows. The Data Fabric page explains federated queries and pushdown; the point for an app builder is simpler: a screen is a filter on a handler, and the source does the work.
Where a screen needs history at scale, a year of stock positions or five years of journals, the pipeline handler reads it from the lake where the Backbone landed it. The catalogue's pair pages say, per app and per system, which objects are read live and which come prepared.
A write on a handler goes through the source's released interface: a BAPI or IDoc for SAP, a REST resource for Oracle Fusion, Salesforce and ServiceNow, a web-service operation for Workday, a MERGE for a lake table. The handler maps the screen's values to the interface's fields, calls it under the acting person's identity and the app's grants, waits for the acknowledgement, and stores the document number or the error message beside the decision in the log.
Write-back is off by default per application and object. It is switched on after a confirmed test write in the target, and each object can carry an approval rule: a price change above a band waits for a second person before the interface is called. The Backbone write-back page has the ledger, the reconciliation and the SAP and Oracle interfaces in detail.
| Source | Write path | Acknowledgement |
|---|---|---|
| SAP S/4HANA and ECC | Released BAPIs and IDocs | Document number and return messages |
| Oracle Fusion Cloud | REST resources (POST, PATCH) | Resource ID and status |
| Oracle E-Business Suite | Open interface tables and public APIs, run by a concurrent program | Request ID and interface status |
| Snowflake · Databricks | Stage and COPY, MERGE INTO a Lima-owned table | Rows merged |
| Salesforce · ServiceNow | REST API under the integration user | Record ID |
| Workday | Web-service operations | Workday ID |
A handler is available wherever an expression is: a start criterion selects rows from it; a validation compares a field to it; a decision node asks it whether the new date covers demand; an action reads a row from it or writes one to it. Variables can be instantiated from a handler at load, so an app variable holds the customer's credit limit from the first screen onward.
This is what makes an app one thing: the rows a person sees, the rule that routes their decision and the write that records it all speak to the same handler.
# decision node: does the supplier's new date cover demand? let need = dh_planned_orders.min(start) where material = app.material and plant = app.plant if app.new_date <= need then 'covered' else 'gap' # action outcome: write the confirmed date and store the acknowledgement dh_po_lines.update(number = app.po, line = app.line, confirmed_date = app.new_date) → BAPI_PO_CHANGE · 4500012345 · RETURN: S · logged 14:06:12
A table handler is the federated table seen through a filter and a column list. The rows stay in the source and are read when a screen needs them. A pipeline handler is the exception by design: a prepared result the Backbone lands and refreshes.
As fast as the source answers a filtered query on its indexed columns, usually within seconds for operational screens. The showcase estate answers a question across four systems in 2.1 seconds. History at scale goes through a pipeline handler on the lake.
Business configurators define table and query handlers from the catalog by picking objects and columns. Pipeline, API and device handlers are usually set up once by an application team and then reused.
Sixty connectors exist and new ones are built from the same operator library in weeks. An API or file handler covers many cases in the meantime.
Bring one 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.