The status export, wired for every night

One query, one REST call, one poll loop, one file in your warehouse. This is the route that turns close-day status collection into something nobody does by hand, with the exact calls an implementer copies.

Note: ARCS, Oracle's account reconciliation module, knows the status of every reconciliation, but only inside the application. This page is the supported route for getting that status out to a database you own, on a schedule.

One question this page answers: what exactly do I call, in what order, to get every reconciliation and its status out nightly? The whole module is mapped on the Account Reconciliation index.

RuleSubmit async, poll the job, name files per run, and gate the landed file before anything reads it. The export is a pipeline, not a download.

Nevership the query without $ARM_SECURITY_CLAUSE$, and never let two runs share a file name. Both fail quietly, which is the worst way.

◆ The four steps, exactly, query, submit, poll, collect, each doc-linked.

Step	The call, exactly
1 · query	Build the report query per Oracle's guide: ARM_RECONCILIATIONS aliased ReconciliationEO, $ARM_SECURITY_CLAUSE$ in the WHERE, status and preparer columns. Wrap it in a report with a CSV template.
2 · submit	POST /arm/rest/fcmapi/v1/report with groupName, reportName, generatedReportFileName, runAsync true. Both name parameters are required; missing either is an error, per the API doc.
3 · poll	GET /arm/rest/fcmapi/v1/job/RC/{jobId} until complete, per the job-status API. Module is RC for compliance, TM for matching.
4 · collect	Download the file from the applicationsnapshots endpoint the response links, land it in the star, run the gates.

◆ The request body, and three decisions, copy the JSON, then name, async, and format.

The same route, three ways: the REST body above for anything that polls, the Pipeline's Generate Report job type for orchestration inside EPM since 25.08, or two lines of EPM Automate for a cron job. The request body implementers copy:

{
  "groupName": "Close Reports",
  "reportName": "Status Export",
  "generatedReportFileName": "status_2026-06-17.csv",
  "runAsync": "true"
}

Three decisions that save a rework. Name the file per run date; a reused name collides on the file system. Set runAsync true; Oracle recommends it for large reports. Pick CSV over CSV2 unless you need template formatting; CSV2 formats and takes longer, per the report doc. Since September 2025 the Balance Report Summary, Balance Report Transactions, and Cosmetic Changes reports run over REST too, one reconciliation and date per call, useful for drill evidence, not for the population export.

THE USE CASE, SIMPLIFIED

The problem: Status collection is a manual exercise nobody remembers to run.

What we build: The query, the REST call, and the poll loop are wired as a nightly pipeline.

What you get: The file arrives every morning, and nobody has to ask for it.

Want this running before your next close?

We build the query, wire the nightly pipeline into your warehouse, and close week starts with the footed status file instead of a collection exercise.

Talk to us

Terms on this page

runAsync: True for large reports. Submit, poll, collect.
RC / TM: The module in the job-status path: compliance or matching.
CSV2: Template-formatted CSV. Prettier, slower. Default to CSV.
gate: An assert on the landed file. No gate, no trust.