Frequently asked questions

It is software that watches Oracle Fusion ESS scheduled processes, alerts the right people when a job fails or is late, and keeps fix context. orping.io polls watched jobs continuously, opens a thread on failure, sends notifications (email and optional Jira or ServiceNow), and remembers resolutions for repeat errors.

orping.io monitors Enterprise Scheduler (ESS) jobs across all Oracle Fusion modules — Financials, Supply Chain, HCM, Projects, and custom processes. When a job you watch fails or misses its window, it appears on your centralized dashboard with a thread and notification. Optional Jira or ServiceNow notify. Auto-escalation on Growth and Enterprise. Every fix is remembered for the next occurrence.

Connect orping with your Fusion hostname and REST credentials. Pick the ESS jobs you care about — orping continuously polls status in the background and automatically fetches failure details when something goes wrong, so your team does not need to watch Fusion job consoles all day.

All Fusion modules that run ESS scheduled processes — including Financials (GL, AP, AR, close), Supply Chain (inventory, costing, orders), HCM (payroll, benefits), Projects, and any custom jobs your team runs in Fusion.

No. orping focuses exclusively on Oracle Fusion ESS scheduled processes. We do not monitor Oracle Integration Cloud (OIC) or third-party integration runtimes.

Yes. You can optionally route alerts to Jira Cloud or ServiceNow per monitor list — alongside the orping thread and email notifications.

Yes on Growth and Enterprise plans. Set a response window per job based on criticality. If the thread is still open when time runs out, orping escalates to the next owner in your matrix automatically.

Yes. Critical Fusion jobs often run with different ledgers, periods, business units, or submission parameters. Add each combination you care about; orping polls them separately and opens a thread when that specific run fails or is late.

Yes. Add any ESS job involved in period close, quarter-end, or financial close — including GL, AP, AR, FA, SCM costing, and custom processes. Teams use orping to shorten close cycles and reduce fire drills.

orping.io is designed for Oracle Fusion Cloud (SaaS) ESS and scheduled processes accessed via the standard REST API. On-prem EBS batch monitoring is on our roadmap — join the waitlist to influence priority.

No OCI agent and no desktop install. orping uses outbound HTTPS from our servers to your Fusion tenant. If your environment restricts API access by IP, add orping's egress IP to your OCI allow list (we provide it at setup). Rarely, a corporate firewall may need to allow outbound HTTPS to your fa-*.oraclecloud.com hostname.

Whitelist orping's egress IP in your OCI IP access policy (or equivalent Fusion restriction). No agent is required — email hello@orping.io during setup for the current IP. If connection still fails, check that outbound HTTPS to your Fusion hostname is allowed through your corporate firewall.

Starter ($129/mo, $1,290/yr): 15 users, 50 ESS jobs. Growth ($249/mo, $2,490/yr): 200 ESS jobs, thread per failure, intelligence layer, auto-escalation, up to 3 instances. Enterprise is custom — starts from $499/mo.

Yes — Starter and Growth have fixed annual prepay ($1,290 / $2,490). Enterprise is custom — contact us for annual terms. Half-year contracts available for Starter and Growth.

Yes. We offer a free 2-month pilot so you can try orping.io before paying anything. Book a demo.

Oracle Fusion customer teams — controllers, accounting shared services, SCM and HCM operations, ERP IT, and Fusion admins — who own scheduled processes and need one dashboard when ESS jobs fail.

The failure appears on your centralized dashboard. orping opens a thread for your assigned team member with logs and context. You can optionally notify Jira or ServiceNow. The team fixes it and closes with a note — saved to the intelligence layer for next time.

It remembers how your team fixed each error and suggests that fix when the same issue arises again — using your past resolutions, Oracle documentation, and any SRs you raised. It does not run jobs or change Fusion for you.

Yes. Assigned owners and their teams chat in the thread, tag colleagues, share updates, and document the fix — replacing scattered email and chat about Oracle job failures.