Plan in OmniBridgeX. Execute in SAP. Know every outcome.
Manage the full lifecycle of OmniBridgeX jobs and use AI-assisted failure patterns, runtime insights and log summaries to monitor the wider SAP background-job landscape without taking ownership of it.
Manage what OmniBridgeX owns. Observe the rest.
A precise scope prevents accidental changes to jobs that belong to SAP operations or another scheduling process.
Created or imported into OmniBridgeX
- Create and maintain job definition
- Change the schedule
- Review steps and variants
- Run permitted jobs on demand
- Retire future occurrences
- Preserve completed execution history
Other jobs discovered in SAP
- View current status and history
- Review execution duration
- Inspect job steps and variants
- See logs where authorized
- No schedule changes
- No delete or retirement action
Keep scheduling and execution responsibilities explicit.
Everything needed to operate scheduled work.
Job catalogue
Search jobs by system, ownership, program, status and schedule with clear managed-versus-monitored classification.
Steps and variants
Review ABAP program steps, sequence, user, language and variant parameters before execution.
Recurring plans
Maintain immediate, date/time, periodic and calendar-based schedules for managed jobs.
Run history
Track SAP job count, status, start, end, duration, server and return information.
Logs and exceptions
Bring job log details and operational exceptions into a tenant-level support view.
Retirement
Stop future occurrences while keeping completed executions, decisions and audit evidence available.
Fetch what changed—not the same history again.
OmniBridgeX polling uses stable SAP execution keys and a persisted watermark to make monitoring efficient and duplicate-safe.
Persist a high-water mark
Store the last successful change timestamp or SAP execution cursor per system and polling scope.
Use a safe overlap window
Re-read a small time overlap to catch delayed updates, then upsert by the stable SAP job identity.
Upsert, do not append blindly
Update an execution when status or end information changes instead of creating duplicate history rows.
Advance only after success
Move the watermark only after the complete polling batch has been persisted successfully.
Move from portfolio health to execution detail.
Operational dashboard
See scheduled, running, successful, cancelled and failed executions with trends and jobs needing attention.
Managed job lifecycle
Create or import authorized jobs, review SAP configuration, edit the schedule and retire future execution.
Execution evidence
Drill from the SAP job run into step results, spool/log information and the variant that actually executed.
Connections and polling
Maintain authorized SAP connections, monitoring intervals, retention and operational policies by tenant.
A practical boundary between OmniBridgeX and SAP.
Operate SAP background jobs with one clear control model.
Give business and IT teams visibility without weakening SAP ownership.