When you evaluate a workload automation or job-scheduling tool for SAP, you run into a wall of credentials: SAP-certified, SAP Store listed, SAP partner, SAP Endorsed App. They sound like rungs on one ladder, and vendors tend to present them that way. They aren’t quite. Each represents something different, and only some of them affect whether a tool can schedule and monitor jobs in your SAP landscape. This guide defines each term plainly, explains what each certification verifies, and gives you a short checklist that tells you more than any badge.
SAP credentials
Four terms come up most often, and it helps to separate them:
- SAP-certified integration: SAP has tested the product against a specific SAP interface and confirmed it works as documented. It’s tied to that interface—for schedulers, the background-processing interface—not to the whole product.
- SAP Store listing: the product has a validated listing in SAP’s marketplace. A listing signals a real, purchasable integration and typically follows certification.
- SAP partner: the vendor has a commercial relationship with SAP to build, sell, or service. This is about the business relationship, not a technical test.
- SAP Endorsed App: SAP’s premium tier—a distinct, curated category of solutions that SAP has validated beyond baseline certification and actively co-markets.
Partner status and certification usually come before a Store listing or endorsement, so the idea of a “ladder” is loose. Treat these as distinct signals rather than strict steps.
What certification tests
For a scheduler, the credential that governs whether it can drive SAP background jobs is certification on SAP’s External Interface for Background Processing—XBP, designated BC-XBP in SAP’s certification catalog. SAP exposes XBP to certified vendors through its Computing Center Management System (CCMS). A scheduler certified on XBP can schedule, start, and monitor classic ABAP background jobs from outside SAP NetWeaver, and certification is granted against a defined scenario: background-processing job scheduling for SAP S/4HANA.
Certification comes in versions, and the version tells you what was tested. XBP 2.0 is the mandatory baseline, covering the core job lifecycle an external scheduler needs—defining and scheduling a job, starting it, monitoring it through to completion or failure, and retrieving job logs and spool output. XBP 3.0 layers on top of that baseline and adds the job-interception model, which lets an external tool govern jobs that users scheduled directly inside SAP: interception rules hold those jobs so the external scheduler can attach conditions and dependencies, and extraction mirrors otherwise unmanaged SAP jobs into central governance.
So “certified on XBP 3.0” is a more precise and more useful statement than “SAP-certified” alone—it tells you which interface version and which capabilities were tested.
Two things certification does not do: it doesn’t move job execution outside SAP’s control, and it doesn’t change who is allowed to run a job. That leads to the credential everyone asks about: endorsement.
What endorsement adds—and doesn’t
SAP Endorsed App is a real distinction and worth understanding accurately. It is SAP’s premium validation tier: beyond baseline certification, SAP applies added security review, deeper testing, and benchmark measurement, and promotes the solution through its own go-to-market. As of 2026, RunMyJobs by Redwood is the only workload automation platform that holds SAP Endorsed App status.
Here is the part that matters for a technical evaluation: endorsement is a premium-certification and go-to-market designation, not a technical prerequisite for scheduling jobs in a RISE with SAP environment. XBP is exposed to any certified vendor through CCMS, and job execution is bounded by SAP’s own authorization model regardless of a vendor’s tier—only a user with the correct SAP roles can run or monitor a job, managed through transaction codes PFCG and SU01 and inheriting SAP Governance, Risk, and Compliance (GRC) controls. Certification for integration with RISE with SAP is held by multiple vendors, not only endorsed ones. A certified scheduler runs jobs under SAP’s own security, as if they were managed inside SAP; endorsement adds validation and go-to-market weight on top of that, not additional capability.
Where Control-M stands
Stated plainly, Control-M is SAP-certified on XBP 3.0, is listed on the SAP Store, and carries the “SAP Certified — Integration with RISE with SAP S/4HANA Cloud” designation. It is fully compatible with RISE with SAP and works through SAP-certified interfaces with no changes to existing SAP job logic. Control-M is an SAP-certified application and data workflow orchestration platform; it is not an SAP Endorsed App. Execution inherits SAP’s roles and GRC governance through XBP, so orchestration stays audit-compliant under SAP’s own security model.
Five questions worth more than a badge
When you compare schedulers for SAP, these tell you more than tier:
- Which interface does it use? For classic background processing, look for certified XBP over Remote Function Call (RFC), secured with Secure Network Communications (SNC).
- Which RISE topologies does it support? XBP stays exposed under RISE Private Cloud, secured with SNC, and RISE with SAP Business Technology Platform (BTP) adds the platform’s cloud services alongside the certified core.
- What’s the path for GROW with SAP? S/4HANA Public Cloud has no classic XBP, so ask which interface the tool uses there—SAP’s External Scheduler API, communication scenario SAP_COM_0948, reached over OData/REST and secured with OAuth 2.0 and Transport Layer Security (TLS). XBP certification alone does not answer this.
- Does execution inherit SAP’s authorization model? Jobs should run under SAP roles (PFCG and SU01) and inherit GRC governance, not under a separate credential store outside SAP’s control.
- Is there conversion tooling? Moving an existing estate (from another scheduler, or from ECC to S/4HANA) is far cheaper when the tool imports existing job definitions instead of requiring a manual rebuild.
Frequently asked questions
Which workload automation tools are SAP Endorsed Apps, and what does that certification verify?
As of 2026, RunMyJobs by Redwood is the only workload automation platform that holds SAP Endorsed App status. SAP Endorsed Apps are a distinct, premium-certified category in SAP’s partner ecosystem: beyond baseline certification, SAP applies added security review, deeper testing, and benchmark measurement, and actively co-markets the solution. It is a strong validation and go-to-market signal, but it is not a technical prerequisite for driving SAP background jobs. SAP’s certified background-processing interface—the External Interface for Background Processing, or XBP—is exposed to any certified vendor through the Computing Center Management System (CCMS), and job execution is always bounded by SAP’s own authorization model (transaction codes PFCG and SU01, inheriting SAP Governance, Risk, and Compliance controls) regardless of a vendor’s tier. Several schedulers, including Control-M, hold SAP certification for integration with RISE with SAP; Control-M is SAP-certified on XBP 3.0, listed on the SAP Store, and fully compatible with RISE with SAP, though it is not an Endorsed App. When comparing tools, the more decisive questions are which SAP interface each one is certified on, which RISE and GROW topologies it supports, and whether job execution inherits SAP’s roles and GRC governance.
Next steps
If you’re comparing schedulers on what their credentials actually verify, the next step is checking each one against the interface it’s certified on. Explore Control-M for SAP or access the Control-M demo library.
These postings are my own and do not necessarily represent BMC's position, strategies, or opinion.
See an error or have a suggestion? Please let us know by emailing blogs@bmc.com.
