All posts · BI Reports

Scheduling Reports in Oracle Fusion Cloud

How to automate report delivery in Fusion Cloud — using Scheduled Processes (ESS), OTBI Agents, and BIP scheduling for time-based and event-driven distribution.

Anurag Jangra · February 5, 2026 · 5 min read · ... views

Three ways to schedule reports in Fusion

1. BIP Scheduler: built into BI Publisher, runs reports on a time schedule and delivers output via email, FTP, or content server.

2. Oracle ESS (Enterprise Scheduler Service): submits BIP reports as enterprise batch jobs. Used for standard Fusion reports — accessible via Scheduled Processes work area.

3. OTBI Agents: monitors data conditions and triggers OTBI analyses delivery when conditions are met (data-driven scheduling).

BI Publisher scheduling

In BIP: open a report → Schedule. Configure:

  • Schedule: one-time, hourly, daily, weekly, monthly, custom cron
  • Parameters: set fixed values or prompt users before each run
  • Delivery: email recipients with subject/body, FTP location, or BIP server
  • Output format: PDF, Excel, CSV

Scheduled jobs appear in BIP’s Job History — check here for failures and output files.

ESS Scheduled Processes

For standard Oracle reports (payroll runs, PO import, period close):

  1. Navigator → Tools → Scheduled Processes
  2. Schedule New Process → search for the process name
  3. Set Advanced parameters → Recurrence (frequency) and Notify (email on completion/failure)

Most Fusion batch reports are submitted this way. The Scheduled Processes work area shows status, output, and logs.

OTBI Agents: condition-based delivery

An OTBI Agent runs an analysis and delivers results when data meets defined conditions:

  1. Create an analysis with a filter (e.g. Invoice Status = OVERDUE)
  2. Create an Agent: Shared Folders → New → Agent
  3. Configure: analysis to run, condition (deliver only when rows > 0), schedule, delivery
  4. Recipients receive an email with the analysis results attached or as a link

Agents are ideal for exception reporting — “notify me when overdue invoices exceed threshold.”

Output delivery for compliance

For audit and compliance scenarios, configure BIP to deliver reports to Oracle Content Management (UCM) rather than email — this creates an immutable, searchable archive of all generated reports with timestamps.

Monitoring and alerting

For critical scheduled reports (period-end financial reports, payroll), set up notifications on both success and failure. A missed run is as bad as a failed run — the ESS notification configuration emails the submitter’s manager on failure.

Think Beyond the Implementation

Questions worth sitting with after reading this

01

Why is this architecture appropriate for this specific context — and where would it be the wrong choice?

02

What assumptions did we make that aren't stated explicitly? What happens if those assumptions are wrong?

03

What would break first if the requirements changed — volume doubled, a third system was added, or the deadline halved?

04

What alternatives did we reject, and why? Was the decision made on evidence — or habit?

AJ
Anurag Jangra
Oracle Cloud PaaS Consultant · OIC & VBCS Specialist

4.5+ years delivering enterprise Oracle Cloud integrations and VBCS applications across manufacturing, IT services, and financial sectors. OCI Certified — writes about real-world OIC, VBCS, SQL, and BI Publisher patterns from production experience.

Chat on WhatsApp