Support SAP S/4HANA Clean Core “Application Jobs” lifecycle in IBM Workload Scheduler (IWS)

Support SAP S/4HANA Clean Core “Application Jobs” lifecycle in IBM Workload Scheduler (IWS)

Product: IBM Workload Scheduler – SAP Plug-in / SAP Integration (XBP)

Current behavior

In SAP S/4HANA (Public and Private Cloud) using the Clean Core–compliant Fiori “Application Jobs” framework, jobs are automatically promoted directly to “Released” status and executed by the SAP internal dispatcher.

The current IBM Workload Scheduler SAP Plug-in (based on the XBP 3.0 interface) only intercepts and monitors jobs in “Scheduled” status, assuming ownership of the job lifecycle before releasing it.

As a result, SAP Application Jobs:

• Execute successfully in SAP
• Are not visible, monitored, or controlled by IWS
• Cannot be integrated into IWS dependency chains or operational monitoring

This behavior has been confirmed by IBM L3 support as a structural incompatibility between the current IWS SAP integration and the SAP Clean Core job lifecycle.

Expected behavior / Enhancement request

IBM Workload Scheduler should support SAP S/4HANA Clean Core Application Jobs, including jobs that:

• Are created via the Fiori “Application Jobs” framework
• Transition directly to “Released” status without passing through “Scheduled”
• Are executed by the SAP dispatcher rather than being initiated by IWS

Specifically, we request:

• The ability for IWS to discover, monitor, and manage SAP jobs in “Released” status, or
• An alternative Clean Core–compatible integration mechanism that allows IWS to:
  • Track execution status
  • Capture job outcomes (success/failure)
  • Integrate these jobs into IWS scheduling dependencies and monitoring dashboards

Business impact

SAP S/4HANA Clean Core is now the recommended and increasingly mandatory approach for SAP customers, especially in cloud environments.

The current limitation:

• Prevents customers from using Clean Core–compliant Application Jobs together with IWS
• Forces a choice between:
  • Clean Core compliance, or
  • Centralized enterprise scheduling and monitoring via IWS
• Creates operational blind spots for critical batch processes

This impacts customers running:

• SAP S/4HANA Public Cloud
• SAP S/4HANA Private Cloud
• Clean Core–aligned on-premise S/4HANA systems