BMC Software

When I joined IBM at the beginning of my career, I saw firsthand how reliable, available, scalable, and secure the mainframe was for customers. Over the years, I have watched as concepts like virtualization were pioneered on the mainframe and how mainframe technology has consistently evolved to enhance its importance to the enterprise. According to IBM, mainframes now manage up to 19 billion encrypted transactions a day.

What SAP BW process chains are An SAP Business Warehouse (BW) process chain is a sequence of automated steps — data loads, transformations, activations, and housekeeping tasks — defined and maintained in transaction RSPC. A chain strings together processes such as InfoPackage loads, data transfer processes (DTPs), and attribute change runs so that data moves from source system to report-ready InfoProvider in a defined, repeatable order. Native monitoring is where the limits start.

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.

If your organization schedules SAP jobs through SAP Central Process Scheduling by Redwood, the ground has shifted. The product line CPS belongs to has reached end of support, which means the software running your business-critical batch processing no longer receives updates or fixes.

If your batch schedule runs on SAP ECC, the platform underneath it is approaching a critical maintenance expiry date. Most guidance on the 2027 deadline treats the ERP migration as a whole — the data model, the custom code, the functional scope. This guide is narrower and more operational: it’s the plan for the team that owns the jobs.

What the BTP Job Scheduling Service is The SAP BTP Job Scheduling Service is the job scheduler built into SAP Business Technology Platform (BTP). It lets you define and run jobs (one-time or recurring) against applications and services deployed on BTP.

What SM36 and SM37 do SAP ships with a complete, native toolset for background processing. SM36 is where a job is defined: its steps, program variants, start conditions, and recurrence. SM37 is the job overview, where administrators monitor, analyze, and troubleshoot runs. Two companion transactions manage the events that trigger them: SM62 and SM64 handle event definition and administration. These transactions are well designed for the work they were built for, and that work is substantial.

Enterprise Automation has entered the AI era For decades, automation focused on making predictable processes faster and more reliable. That remains essential, but it is no longer enough. Enterprises must now orchestrate applications, data, and AI across increasingly complex hybrid environments, without compromising security, resilience, or human control.

Learn how Control-M orchestrates a production-grade AI governance pipeline with Amazon Bedrock, Snowflake, DataBrew, SES, and QuickSight — reliably. Getting an AI agent to produce a compelling response in a playground is straightforward. Getting that same agent to produce reliable, trustworthy output every quarter – on fresh data, in the right sequence, with results delivered to the right people and systems – is an entirely different problem.

The challenge with putting AI agents into production Getting an AI agent to produce a compelling response in a playground is straightforward. Getting that same agent to produce reliable, trustworthy output every quarter – on fresh data, in the right sequence, with results delivered to the right people and systems – is an entirely different problem. The gap between a demo and a production AI workflow usually is not the agent itself.