Does the agent need inbound network access to my SAP hosts?

No. The agent is outbound-only. It polls Farrenio over HTTPS for its config and pushes metrics the same way. No new firewall rules, no exposed ports on your SAP boxes.

Can my service desk see alerts without touching production?

Yes. The service_desk role is read-only on alerts and incidents, with no SAP transaction access, no config changes and no token reveal. Granular per-action RBAC means you can carve out exactly what each team sees.

How long does a proof of concept take?

A 30-minute call to scope. We typically have one production SID streaming live metrics within an hour of agent install, and the rest of the landscape follows as fast as you can roll out the package.

Background jobs · 03

The job that failed at 02:14 is rarely discovered at 02:14

The background job that cancelled at 02:14 is usually discovered at 08:30, when finance asks why the overnight postings are missing and someone opens SM37 on the right system, with the right filter, for the right user.

Request a demo All insights

Critical work, monitored by habit

Background processing is where much of the business-critical SAP work happens: billing runs, interfaces, period-end chains and data loads. Yet in many landscapes job monitoring is still a manual morning routine, repeated per system.

The manual routine has predictable gaps. A job that never started does not appear as cancelled. A chain that failed on one system looks fine from another. And the person who knows what a particular job does is not always the person on shift.

Rules that make job monitoring work

Watch every system in one place
Not one SM37 session per SID.
Keep the job log with the alert
The first person who looks should already see why it failed.
Separate failed from never started
They need different responses, and only one of them shows up as cancelled.
Route to the owner
Send the alert to the team that owns the process, not only to Basis.

How FCC handles background jobs

Cancellations across the landscape

Job status read continuously from every connected system.

The job log, on hand

The log of a failed job can be read from the platform, so the cause travels with the alert.

Alerts that reach people

Escalation by severity and time, delivered to email, Slack, Microsoft Teams or webhooks.

From alert to incident

Any alert can be promoted into an incident with its history intact.

None of this is new to experienced teams. What changes things is having it done continuously, for the whole estate, without anyone needing to remember to look.

Go deeper

Topic

SAP Basis monitoring

SM37 and the other transactions FCC reads across systems.

Topic

SAP Basis automation

Guided, audited procedures for routine work.

Common questions

Does FCC schedule jobs?

Scheduling stays in SAP. FCC watches the outcome across every system and alerts the right people when a job fails.

Can alerts go to the business team that owns a process?

Yes. Alerts route by severity and escalation policy to the channels each team already uses.

Know about failed jobs before anyone asks.

Connect one system and see its background processing in the FCC console. FCC is in Beta.

Request a demo See pricing

"SAP" and SAP product names are used descriptively. Farrenio Cloud Control is a Farrenio product and implies no partnership with or endorsement by SAP.