Routes every quote whose discount passes the band to the sales manager and then pricing, and returns the approved status and discount to the quote.
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 |
|---|---|---|---|
| Quotation | Oracle CPQ REST: transactions (quotes) | TotalAmount (value) · DiscountPercent (discount) · TransactionNumber (number) · CustomerName (customer) | live through the API |
| Customer master | Receivables REST: receivablesCustomerAccounts · TCA parties | AccountNumber (id) · PartyName (name) · Country (country) · BusinessUnit (sales org) | live through the API |
| Price condition | Pricing REST: priceLists · priceListItems | ItemNumber (material) · Customer (pricing strategy) (customer) · BasePrice (amount) · PricingUOM (unit) | live through the API |
| Sales order line | Order Management REST: salesOrdersForOrderHub · lines | OrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer) · ProductNumber (material) | live through the API |
In plain words: A quote saved with a line discount above 15 percent, or a quote value above 250,000.
The criterion runs in Oracle Fusion 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 Oracle Fusion fields DiscountPercent > 15 or TotalAmount > 250000 # the same criterion in canonical fields {quote.discount} > 15 or {quote.value} > 250000
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 |
|---|---|---|
| Quotation | approval status, approved discount per line and approver note written to the quote; a returned quote goes back to draft with the note | PATCH transactions (approval status) |
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 |
|---|---|---|
| Quotation | Oracle CPQ REST: transactions (quotes) | ASO_QUOTE_HEADERS_ALL · ASO_QUOTE_LINES_ALL |
| Customer master | Receivables REST: receivablesCustomerAccounts · TCA parties | HZ_PARTIES · HZ_CUST_ACCOUNTS (write: RA_CUSTOMERS_INTERFACE_ALL) |
| Price condition | Pricing REST: priceLists · priceListItems | QP_LIST_HEADERS_B · QP_LIST_LINES |
| 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) |
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.
