Finance on Oracle Fusion

Month-end close checklist on Oracle Fusion Cloud

Runs the close as a shared checklist per entity and day, with each task's status read from the ledger and every sign-off recorded.

SCREENSDATA HANDLERSORACLE FUSION · READ IN PLACES01 My tasksS02 Task detailS03 Entity sign-offS04 Cost center reviewS05 Close boardS06 Calendar setupdh_journal_lineJournal lineGeneral Ledger REST: journals · BICC GLjournal lines extractdh_supplier_invoiceSupplier invoicePayables REST: invoicesdh_capital_requestCapital requestFixed Assets REST: assets (CIP) ·Projects capital projectsdh_cost_centerCost centerGeneral Ledger: chart of accountssegment values (REST: valueSets)WRITE 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
7 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
Supplier invoicePayables REST: invoicesInvoiceNumber (number) · Supplier (vendor) · InvoiceAmount (amount) · PurchaseOrderNumber (lines) (po)live through the API
Capital requestFixed Assets REST: assets (CIP) · Projects capital projectsProjectNumber (capital) (request) · ProjectName (desc) · BudgetAmount (amount) · FiscalYear (year)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
The trigger

The start criterion in Oracle Fusion's own fields

In plain words: The close calendar starts on the last working day of each month for every entity, or when the accounting manager opens it early.

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

The close calendar starts on the last working day of each month for every entity, or when the accounting manager opens it early. 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 lineaccrual, reclassification and correction journals posted from a task through the released journal interface; the document number stored on the taskPOST 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)
Supplier invoicePayables REST: invoicesAP_INVOICES_ALL · AP_HOLDS_ALL (write: AP_INVOICES_INTERFACE)
Capital requestFixed Assets REST: assets (CIP) · Projects capital projectsFA_ADDITIONS_B (CIP) · PA_PROJECTS_ALL
Cost centerGeneral Ledger: chart of accounts segment values (REST: valueSets)GL_CODE_COMBINATIONS · FND_FLEX_VALUES
Nearby

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

Month-end close checklist on

Other apps on Oracle Fusion

Terms on this page

Working dayA counted day of the close calendar, starting at 1 on the first working day after period end.
Ledger checkA criterion on live ledger data that decides whether a task is complete, for example 0 supplier invoices left to post.
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.