Logistics and warehouse on Oracle Fusion

Warranty check and claim on Oracle Fusion Cloud

Looks up a serial number, shows the coverage from the warranty and the sale, decides the claim and creates the service order for the repair or replacement.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 Serial lookupS02 Coverage detailS03 Customer portalS04 Claim decisionS05 Service orderS06 Boarddh_warrantyWarrantyService Contracts REST: serviceContracts· installedBaseAssetsdh_customer_masterCustomer masterReceivables REST:receivablesCustomerAccounts · TCApartiesdh_sales_order_lineSales order lineOrder Management REST:salesOrdersForOrderHub · linesdh_return_orderReturn orderOrder Management REST:salesOrdersForOrderHub (return lines) ·returnOrdersdh_quotationQuotationOracle CPQ REST: transactions (quotes)WRITE BACK TO ORACLE FUSIONWarranty → PATCH serviceContracts · POST serviceRequestsReturn order → POST salesOrdersForOrderHub (return)Quotation → PATCH transactions (approval status)rows stay in Oracle Fusion · access rules applied at read time · each write acknowledged and logged
The screens of the app, the data handler behind each, and the Oracle Fusion object it reads in place. Writes below the line go through released interfaces with an acknowledgement.
5
objects read in place from Oracle Fusion
catalogue
6
screens on those rows
catalogue
5 days
to production-grade
estimate
3
objects written back
catalogue
0
rows copied to build it
product
What the app reads

The Oracle Fusion objects behind each handler

Objects are read in place through the released REST resources, and bulk history through BI Cloud Connector extracts. The rows stay in Oracle.

ObjectRead fromFields the app usesFreshness
WarrantyService Contracts REST: serviceContracts · installedBaseAssetsAssetNumber (equipment) · SerialNumber (serial) · StartDate (warranty start) · EndDate (warranty end)live through the API
Customer masterReceivables REST: receivablesCustomerAccounts · TCA partiesAccountNumber (id) · PartyName (name) · Country (country) · BusinessUnit (sales org)live through the API
Sales order lineOrder Management REST: salesOrdersForOrderHub · linesOrderNumber (number) · LineNumber (line) · BuyingPartyNumber (customer) · ProductNumber (material)live through the API
Return orderOrder Management REST: salesOrdersForOrderHub (return lines) · returnOrdersOrderNumber (number) · BuyingPartyNumber (customer) · ProductNumber (material) · OrderedQuantity (qty)live through the API
QuotationOracle CPQ REST: transactions (quotes)TransactionNumber (number) · CustomerName (customer) · TotalAmount (value) · ExpirationDate (valid to)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: A service agent or a customer enters a serial number and a fault description on S01.

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 service agent or a customer enters a serial number and a fault description on S01. The instance then reads its rows from Oracle Fusion through the handlers above.

What the app writes back

Through released interfaces

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.

ObjectWhat changesInterface
Warrantyclaim decision recorded against the warranty of the serial; a service order created through the service order interface for a covered repair or replacement, with fault, priority and engineerPATCH serviceContracts · POST serviceRequests
Return orderreturn order created with the serial and reason code when the unit comes backPOST salesOrdersForOrderHub (return)
Quotationrepair quotation created for a chargeable fault and sent to the customer for acceptancePATCH transactions (approval status)
Acknowledged and logged

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.

Access and prerequisites

What is in place before the first build

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.

  • An integration user with the REST resource roles for the objects the app reads and writes
  • BI Cloud Connector offerings enabled for the objects that need history at scale
  • Allowed IP or private connectivity to the pod
  • Business-unit and inventory-organisation scopes agreed with the process owner
Register the handlers5 objects from the catalog; each shows its rows at once.
Also on Oracle E-Business Suite

The same app on Oracle E-Business Suite

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.

ObjectOn Oracle FusionOn Oracle E-Business Suite
WarrantyService Contracts REST: serviceContracts · installedBaseAssetsOKS_K_LINES_B · CSI_ITEM_INSTANCES
Customer masterReceivables REST: receivablesCustomerAccounts · TCA partiesHZ_PARTIES · HZ_CUST_ACCOUNTS (write: RA_CUSTOMERS_INTERFACE_ALL)
Sales order lineOrder Management REST: salesOrdersForOrderHub · linesOE_ORDER_HEADERS_ALL · OE_ORDER_LINES_ALL (write: OE_HEADERS_IFACE_ALL · OE_LINES_IFACE_ALL)
Return orderOrder Management REST: salesOrdersForOrderHub (return lines) · returnOrdersOE_ORDER_LINES_ALL (LINE_CATEGORY_CODE = RETURN)
QuotationOracle CPQ REST: transactions (quotes)ASO_QUOTE_HEADERS_ALL · ASO_QUOTE_LINES_ALL
Nearby

This app on other systems, and other apps on Oracle Fusion

Warranty check and claim on

Other apps on Oracle Fusion

Terms on this page

Serial numberThe identifier of one physical unit of a product; the equipment record in the ERP carries it.
Master warrantyThe warranty terms attached to the equipment record: start, end and the faults it covers.
Read in placeThe rows stay in Oracle Fusion; the handler sends the filter and the columns and Oracle Fusion returns the matching rows.
Questions

Does this app copy data out of Oracle Fusion?

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.

What does Oracle Fusion 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 Oracle E-Business Suite as well?

Yes. The screens, criteria and roles stay; the handlers are re-bound to the other system's objects, listed above.

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.