Turns a service request into a dispatched visit: the dispatcher picks the engineer and parts, the engineer closes the job on mobile, and the service order is confirmed for billing.
Objects are read in place through the released REST resources, and bulk history through BI Cloud Connector extracts. The rows stay in Oracle.
| Object | Read from | Fields the app uses | Freshness |
|---|---|---|---|
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | OrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer) · ProductNumber (material) | live through the API |
| Warranty | Service Contracts REST: serviceContracts · installedBaseAssets | AssetNumber (equipment) · SerialNumber (serial) · StartDate (warranty start) · EndDate (warranty end) | live through the API |
| Customer master | Receivables REST: receivablesCustomerAccounts · TCA parties | AccountNumber (id) · PartyName (name) · Country (country) · BusinessUnit (sales org) | live through the API |
| Employee | HCM REST: workers · assignments | PersonNumber (id) · DisplayName (name) · DepartmentName (org unit) · PositionCode (position) | live through the API |
In plain words: A customer submits S01 on the portal screen, or the service desk logs a request 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.
A customer submits S01 on the portal screen, or the service desk logs a request from a call or from the service case in the CRM. The instance then reads its rows from Oracle Fusion through the handlers above.
Writes use the same released REST resources (POST and PATCH) with the integration user's data-security profile. Each call returns the document identifier or an error message, and the app records both beside the decision.
| Object | What changes | Interface |
|---|---|---|
| Sales order line | service order created with the visit, parts and labour lines; confirmed quantities and completion written when the engineer closes the job | POST/PATCH salesOrdersForOrderHub |
Each write stores the identifier Oracle Fusion returns beside the decision, the person and the time, so the log answers who changed what, and the reconciliation shows it arrived.
Oracle roles and data-security policies are mapped to Lima access policies once. A buyer scoped to a business unit in Oracle sees the same rows in the app.
On Oracle E-Business Suite the same objects live in the tables named beside each row and are read in place through JDBC with a read-only user; writes go through the open interface tables and public APIs, run by a concurrent program.
| Object | On Oracle Fusion | On Oracle E-Business Suite |
|---|---|---|
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | OE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL (write: OE_HEADERS_IFACE_ALL · OE_LINES_IFACE_ALL) |
| Warranty | Service Contracts REST: serviceContracts · installedBaseAssets | OKS_K_LINES_B · CSI_ITEM_INSTANCES |
| Customer master | Receivables REST: receivablesCustomerAccounts · TCA parties | HZ_PARTIES · HZ_CUST_ACCOUNTS (write: RA_CUSTOMERS_INTERFACE_ALL) |
| Employee | HCM REST: workers · assignments | PER_ALL_PEOPLE_F · PER_ALL_ASSIGNMENTS_F |
The screens read through handlers that leave the rows in Oracle Fusion. History the app needs at scale is landed in the lake by the Backbone, which is the exception by design.
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, listed above.
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.
