Takes a capital request with its business case through plant controller, division and group approval, checks the investment budget, and creates the appropriation in the ERP.
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 |
|---|---|---|---|
| Capital request | Fixed Assets REST: assets (CIP) · Projects capital projects | ProjectNumber (capital) (request) · ProjectName (desc) · BudgetAmount (amount) · FiscalYear (year) | live through the API |
| Budget line | Budgetary Control REST: controlBudgetBalances · EPM plans | ControlBudgetName (object) · BudgetAmount (amount) · PeriodName (year) · BudgetVersion (version) | live through the API |
| Cost center | General Ledger: chart of accounts segment values (REST: valueSets) | Value (id) · Description (name) · Attribute (owner) (owner) · Ledger / legal entity (company) | live through the API |
| Journal line | General Ledger REST: journals · BICC GL journal lines extract | JournalBatchName / JournalName (document) · AccountCombination (account) · EnteredDr − EnteredCr (amount) · Segment (cost center) (cost center) | live through the API |
In plain words: A requester submits S01 with an amount and a business case.
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 requester submits S01 with an amount and a business case. 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 |
|---|---|---|
| Capital request | appropriation request created with amount by year, cost center and category; status set as each level approves | POST projects (capital) · PATCH budgets |
| Budget line | released amount recorded against the investment budget line | POST budgetEntries (FBDI) |
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 |
|---|---|---|
| Capital request | Fixed Assets REST: assets (CIP) · Projects capital projects | FA_ADDITIONS_B (CIP) · PA_PROJECTS_ALL |
| Budget line | Budgetary Control REST: controlBudgetBalances · EPM plans | GL_BUDGETS · GL_BALANCES (budget) |
| Cost center | General Ledger: chart of accounts segment values (REST: valueSets) | GL_CODE_COMBINATIONS · FND_FLEX_VALUES |
| Journal line | General Ledger REST: journals · BICC GL journal lines extract | GL_JE_HEADERS · GL_JE_LINES (write: GL_INTERFACE) |
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.