NetWeaver

SAP Industry Solutions are purpose-built extensions that addressSAP Integration Suite is a modern, scalable integration plaSAP NetWeaver is the prior-generation, on-premises application and integration platform that serves as the technical foundation for SAP Business Suite 7, including SAP ERP Central Component (ECC). It provides the runtime environment for core business logic, supporting ERP, supply chain and industry-specific solutions. NetWeaver offers essential services for connecting SAP and non-SAP systems to ensure transactional consistency across distributed environments.

Designed to support both ABAP and Java development, NetWeaver enabled the deployment of web services and composite applications. Key components include tools for user interface management, business intelligence (SAP Business Warehouse (BW)) and process integration (SAP PI/PO).

In the context of workload automation, NetWeaver traditionally managed background processing through standard ABAP transactions such as SM36 and SM37, or via process chains in data warehousing (RSPC). As organizations transition to SAP S/4HANA and SAP Cloud ERP, these centralized NetWeaver functions are evolving into service-oriented architectures, such as SAP Business Technology Platform (BTP), necessitating a more agile approach to cross-platform job scheduling.

The evolution of SAP job scheduling

Historically, NetWeaver served as the primary engine for automating the high-volume background tasks essential to business operations. However, as organizations modernize, the limitations of scheduling directly within the NetWeaver stack have become more apparent:

• Siloed job execution: NetWeaver scheduling via transactions like SM36 or RSPC is SAP-centric. While it handles tasks within a single instance well, it can’t natively orchestrate a process that starts in an SAP ERP, moves to a third-party cloud warehouse (e.g., Snowflake) and finishes in a reporting tool. This creates “black holes” in the end-to-end automation chain.
• Lack of advanced triggering: Scheduling in NetWeaver is largely time-based at the local system level. Modern job scheduling requires more sophisticated logic, such as cross-system file triggers or API-based starts, which often require custom-coded ABAP workarounds when managed through legacy SAP transactions.
• Limited visibility into interdependencies: In a complex environment, a job in one NetWeaver-based system may depend on the successful completion of a job in another. Native SAP tools lack a centralized graphical view of these cross-system dependencies, making it difficult for IT teams to troubleshoot stuck processes before they impact the business.
• Resource contention and overload: Because NetWeaver scheduling runs on the same application server as the business logic, heavy background job volumes can compete for system resources (work processes). Modern scheduling strategies seek to offload this orchestration to external platforms to protect the performance of the core ERP.

By shifting these scheduling responsibilities away from the NetWeaver layer, organizations can achieve a more robust and scalable automation strategy that aligns with SAP’s clean core principles.

Why job scheduling is changing with S/4HANA, Cloud ERP and RISE with SAP

The transition to SAP S/4HANA represents a fundamental shift in how background processes are managed. Organizations moving from SAP ECC or BW to S/4HANA must modernize how core jobs are orchestrated across their landscape.

The legacy tools used within the NetWeaver stack, including transactions like SM36 and RSPC, were designed for a world with full OS-level access. In a cloud-first environment, SAP restricts the installation of third-party agents and custom “Z-program” scheduling wrappers to protect system stability. This shift significantly impacts IT teams responsible for:

• API-driven integration: Moving from OS-level job execution to modern, SAP-certified API interactions
• Clean core compliance: Adhering to SAP’s mandate to keep the core ERP stable by moving automation logic to an external, specialized platform
• Hybrid orchestration: Managing workflows that span across S/4HANA, legacy on-premises systems and non-SAP cloud platforms
• SLA reliability: Ensuring time-critical processes like the financial close or demand forecasting remain consistent during and after the cloud migration

As SAP Cloud ERP introduces new runtime models, traditional workload automation must evolve. It now requires an external orchestration layer that integrates natively with SAP APIs while providing a single point of control for the modern tech stack.

“We found that RunMyJobs provides the transparency and control required to align all three applications, no matter where or when production management issues may arise.”

Raymond Wooninck, SAP Technology Manager and Template Team leader

Supporting the shift from NetWeaver scheduling

As mainstream maintenance for legacy NetWeaver-based systems approaches its conclusion and cloud adoption accelerates, traditional SAP job scheduling methods are becoming obsolete. Legacy tools like CCMS or SM36 were not designed for the API-first architecture of SAP S/4HANA Cloud or SAP BTP, which prioritize system stability by limiting custom code and OS-level agent installations.

RunMyJobs offers a purpose-built orchestration platform that aligns with SAP’s clean core strategy. It enables centralized scheduling across both legacy NetWeaver environments and modern cloud landscapes without requiring custom code to be embedded within the ERP core.

Key benefits for the modern enterprise include:

• Native, agentless integration: Connects to SAP and non-SAP systems via certified APIs, eliminating the need for OS-level maintenance
• Part of the RISE with SAP reference architecture: A secure gateway architecture made available and offered through SAP ECS-managed and RISE environments, ensuring compliance with strict cloud security standards
• Modern SAP connectors: Out-of-the-box integration for the latest SAP innovations, including SAP Datasphere, SAP Integration Suite, SAP Data Services and SAP Analytics Cloud
• Proactive orchestration: Real-time monitoring and SLA tracking across distributed job chains, replacing reactive manual checks with automated oversight

By replacing fragmented scripts and isolated legacy tools with a unified automation fabric, RunMyJobs provides a future-proof foundation that supports the long-term evolution of the SAP landscape.

Modernizing workload automation for cloud-first SAP environments

Legacy workload automation tools embedded in on-premises systems typically depend on direct OS-level access and fixed, time-based schedules. These methods do not scale in modern environments like SAP Cloud ERP, where OS access is restricted and customization is limited to maintain a clean core.

Modern automation must support distributed systems and dynamic workflows without adding to an organization’s technical debt. RunMyJobs addresses this architectural shift by providing:

• API-first orchestration: Native integration with SAP and non-SAP systems via certified APIs (REST, OData), ensuring compatibility with RISE with SAP and GROW with SAP landscapes
• End-to-end observability: Built-in support for complex job chaining, real-time SLA monitoring and automated error handling across the entire enterprise stack
• Flexible connectivity: A secure gateway architecture that provides agentless integration for cloud services while maintaining lightweight agents for necessary OS-level tasks in hybrid environments
• Managed connectivity and enhanced service options: SAP ECS-managed RunMyJobs services that ensure operational continuity while running complex job scheduling and file movement scenarios securely within RISE with SAP, as well as application-level monitoring and technical remediation options
• SaaS-native delivery: A fully managed platform that eliminates the need for customers to manage their own automation infrastructure or perform manual updates

This model allows IT teams to replace fragmented, siloed tools with a consistent automation fabric. By moving scheduling logic out of the application layer and into a dedicated orchestration platform, businesses gain the agility to innovate while ensuring their core ERP remains stable and upgrade-ready.