AutoSys and SAP S/4HANA Cloud

AutoSys Earns SAP Certification for S/4HANA Cloud

Product news · Broadcom AutoSys

Three glossy white tiles on glass pedestals over deep emerald, the center one with a glowing gold circled checkmark

At a Glance:

  • SAP certified AutoSys for SAP S/4HANA Cloud, private edition (Works with RISE with SAP) and SAP S/4HANA Cloud Public Edition (Works with GROW with SAP)
  • Both certificates are listed publicly in SAP’s Certified Solutions Directory, so the answer to the architecture review question is now a link
  • Broadcom names six SAP integrations, from S/4HANA application jobs and BTP Job Scheduling Service to Datasphere and Integration Suite
  • Four questions to put in your SAP migration plan before the first cutover

Somewhere in your S/4HANA Cloud project plan, a reviewer is going to ask whether your scheduler is certified for it. Until now, the answer took a paragraph. The AutoSys SAP certification changes that.

On November 18, Broadcom announced that SAP has certified AutoSys Workload Automation for SAP S/4HANA Cloud, in both its Public and Private Editions. Here’s what that means for the people who run it.

Certificates

2

One for private edition with RISE with SAP, one for Public Edition with GROW with SAP

Version named

24.2

The AutoSys version on the Public Edition certificate

SAP integrations

6

Named by Broadcom, from S/4HANA application jobs to Integration Suite

What SAP Certified, and What the Listing Says

Two certificates, both in SAP’s Certified Solutions Directory under AutoSys Workload Automation from Broadcom:

  • SAP S/4HANA Cloud, private edition. Certified October 27, 2026, with the “Works with RISE with SAP” designation.
  • SAP S/4HANA Cloud Public Edition. Certified October 29, 2026, for AutoSys 24.2, with the “Works with GROW with SAP” designation.

One point of accuracy, because your auditors will care: SAP’s directory says the designation is a technical statement about the solution, not the company, and that customers should still do their own due diligence. In other words, SAP certified the integration, not the vendor. Both certificates run through October 2027.

You can read the details in Broadcom’s announcement, which says the certification validates compatibility, enterprise-grade security, and reliable performance across modern SAP architectures.

Why the AutoSys SAP Certification Shortens the Review

Most of us have been in that meeting. Architecture review, procurement, or a security questionnaire, and one line reads “Is the scheduler certified for S/4HANA Cloud?” If the honest answer was “it has run our SAP jobs for years,” that’s a good answer and also a slow one.

Now the answer is yes, with a public listing the reviewer can open themselves. That does not make your migration easier. It does make one checkbox shorter, and I’ll take those where I can find them.

Where a Scheduler Fits in a Clean Core

Clean core is about keeping upgrades boring, and boring is the goal.

In my view, orchestration belongs outside the core. The schedule, the dependencies, the triggers, and the alerting sit in the scheduler, and SAP stays as close to standard as you can keep it. Broadcom ties the certification directly to SAP’s clean core and cloud-first strategies, and that is the role AutoSys plays: it sits outside the core and tells everything else when to go.

Six SAP Integrations Worth Checking Against Your Job List

Broadcom names these SAP integrations in its announcement:

  • SAP S/4HANA Application Jobs
  • SAP BTP Job Scheduling Service
  • SAP Datasphere, through an adapter
  • SAP Data Intelligence, through an adapter
  • SAP BusinessObjects BI, through an adapter
  • SAP Integration Suite, with native support for API-driven flows and B2B integrations into enterprise schedules

Set that list next to your own inventory of SAP jobs. Anything that lands on it has a defined path. Anything that does not is a conversation worth having before cutover, not after.

One Schedule Across SAP and Everything Else

Nobody’s batch estate is only SAP. Broadcom’s example is a chain you may recognize: a file lands in Amazon S3 or Azure Blob, a Databricks or Informatica transformation runs, an SAP S/4HANA Cloud application job follows, an SAP Datasphere model refreshes, and a Power BI dashboard updates. One platform governs, monitors, and audits the whole thing.

That is the real argument for keeping the scheduler separate from the application. When something runs late at 3 AM, you want one place to look, not five consoles and a conference bridge. The AutoSys integrations catalog lists what else connects, from cloud storage to Kubernetes.

Four Questions for Your SAP Migration Plan

Certification gets you through the review. These get you through the cutover. Bring them to your next planning session:

  1. Which jobs move? Not every job survives the trip, and some should retire instead.
  2. Which ones run as S/4HANA application jobs? That decides how they are defined, triggered, and monitored.
  3. What triggers what? Write down the dependencies before cutover finds them for you.
  4. Where does the audit trail live? If the answer is “it depends which system you ask,” that is the finding.

Then check your version. The Public Edition certificate lists AutoSys 24.2, so compare it with what you run today. If you’re behind, the upgrade belongs on the migration plan. Our write-up of What’s New in AutoSys 24.2 is a good place to start.

Where to Take It From Here

Start with the two public sources, SAP’s listing and Broadcom’s announcement, and forward them to whoever owns the review. Then look at your job inventory with the six integrations in mind.

Want another opinion on the plan? Bring it to a free 30-minute call with our team. Book a Free Call.

Is your scheduler ready for S/4HANA Cloud?

RMT helps AutoSys teams line up their job inventory, version, and dependencies with the move to SAP, starting with the plan you have today.