Runs the monthly variance review on the live ledger: each cost center owner explains the lines above threshold, controllers consolidate, and the CFO sees the top 20.
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 |
|---|---|---|---|
| Budget line | Budgetary Control REST: controlBudgetBalances · EPM plans | Consumed / Available (plan amount) · BudgetAmount (amount) · ControlBudgetName (object) · PeriodName (year) | 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 |
| 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 |
| Employee | HCM REST: workers · assignments | PersonNumber (id) · DisplayName (name) · DepartmentName (org unit) · PositionCode (position) | live through the API |
In plain words: On working day 3 after a period closes, every cost center line whose actual differs from plan by more than 5 percent and more than 25,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 abs(BudgetAmount - Consumed / Available) > 0.05 * Consumed / Available and abs(BudgetAmount - Consumed / Available) > 25000 # the same criterion in canonical fields abs({budget.amount} - {budget.plan_amount}) > 0.05 * {budget.plan_amount} and abs({budget.amount} - {budget.plan_amount}) > 25000
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 |
|---|---|---|
| Budget line | revised forecast amount written to the forecast version of the planning system; explanation stored beside the 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 |
|---|---|---|
| Budget line | Budgetary Control REST: controlBudgetBalances · EPM plans | GL_BUDGETS · GL_BALANCES (budget) |
| Journal line | General Ledger REST: journals · BICC GL journal lines extract | GL_JE_HEADERS · GL_JE_LINES (write: GL_INTERFACE) |
| Cost center | General Ledger: chart of accounts segment values (REST: valueSets) | GL_CODE_COMBINATIONS · FND_FLEX_VALUES |
| 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.
