Finance on Oracle Fusion

Manual journal entry approval on Oracle Fusion Cloud

Takes a manual journal entry with its support documents through checks, review and approval by amount band, and posts it to the ledger on approval.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 New entryS02 ChecksS03 ReviewS04 ApprovalS05 Posting resultS06 Logdh_journal_lineJournal lineGeneral Ledger REST: journals · BICC GLjournal lines extractdh_cost_centerCost centerGeneral Ledger: chart of accountssegment values (REST: valueSets)dh_budget_lineBudget lineBudgetary Control REST:controlBudgetBalances · EPM plansdh_employeeEmployeeHCM REST: workers · assignmentsWRITE BACK TO ORACLE FUSIONJournal line → POST journals (ERP Integration Service, FBDI)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.
4
objects read in place from Oracle Fusion
catalogue
6
screens on those rows
catalogue
4 days
to production-grade
estimate
1
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
Journal lineGeneral Ledger REST: journals · BICC GL journal lines extractJournalBatchName / JournalName (document) · AccountCombination (account) · EnteredDr − EnteredCr (amount) · Segment (cost center) (cost center)live through the API
Cost centerGeneral Ledger: chart of accounts segment values (REST: valueSets)Value (id) · Description (name) · Attribute (owner) (owner) · Ledger / legal entity (company)live through the API
Budget lineBudgetary Control REST: controlBudgetBalances · EPM plansControlBudgetName (object) · BudgetAmount (amount) · PeriodName (year) · BudgetVersion (version)live through the API
EmployeeHCM REST: workers · assignmentsPersonNumber (id) · DisplayName (name) · DepartmentName (org unit) · PositionCode (position)live through the API
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: A preparer submits S01 with lines that balance to 0 and at least 1 support document.

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 preparer submits S01 with lines that balance to 0 and at least 1 support document. 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
Journal linejournal document posted through the ledger interface with lines, text and the support reference; reversal posted in the next period when scheduledPOST journals (ERP Integration Service, FBDI)
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 handlers4 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
Journal lineGeneral Ledger REST: journals · BICC GL journal lines extractGL_JE_HEADERS · GL_JE_LINES (write: GL_INTERFACE)
Cost centerGeneral Ledger: chart of accounts segment values (REST: valueSets)GL_CODE_COMBINATIONS · FND_FLEX_VALUES
Budget lineBudgetary Control REST: controlBudgetBalances · EPM plansGL_BUDGETS · GL_BALANCES (budget)
EmployeeHCM REST: workers · assignmentsPER_ALL_PEOPLE_F · PER_ALL_ASSIGNMENTS_F
Nearby

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

Manual journal entry approval on

Other apps on Oracle Fusion

Terms on this page

Manual journal entryA posting to the ledger that a person creates, with accounts, amounts, text and support documents.
AccrualAn entry that records a cost in the period it belongs to, before the invoice arrives, and reverses in the next period.
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.