Skip to end of metadata
Go to start of metadata

Introduction

  • SAP S/4 HANA includes the SAP Job Scheduling Service that implements the SAP Job Scheduling Service REST API to manage and to operate SAP Jobs.
  • This JITL Job implements a JS7 adapter for SAP S/4 HANA® Jobs.
  • The JS7 adapter is not certified with SAP but makes use of the publicly available SAP REST Web Service.

Feature Status

This feature will be available with a later release after general availability of JS7, see JS7 - Roadmap

Integration Scenario

Authentication

  • The JS7 JITL Job makes use of SAP user/password authentication.
  • Support for OAuth 2.0 authentication is a future option.

Job Scheduling

SAP Jobs are configured with the SAP S/4 HANA system. The JS7 JobScheduler implements a JITL Job to execute SAP Jobs.

  • A 1:1 mapping of a JS7 JITL Job and an SAP Job applies. This allows parameterization on a per job basis.
  • The JS7 JITL Job is added to JS7 - Workflows that are configured
    • to execute individual SAP Jobs or
    • to execute a number of jobs including SAP Jobs and any JS7 - Jobs with any registered JS7 Agent.
    • This allows cross-platform scheduling with SAP Jobs being integrated into a sequence of jobs that is executed for SAP systems and for other platforms.
  • The JS7 JITL Job makes use of JS7 - Calendars and Schedules.
    • The JS7 - Schedules determine the parameters and the point in time for which the SAP Job is started.
    • SAP Jobs therefore are started immediately from the point of view of SAP Job configuration. The JS7 manages any schedules and connects to the SAP S/4 HANA system at the point of time of job execution to launch the SAP Job.

Job Execution

SAP Jobs can be executed synchronously and asynchronously. This is decided by the SAP transaction.

JS7 has to know the type of scheduling supported by the respective SAP transaction:

  • Synchronous Execution
    • When the SAP Job is started by the JS7 JITL Job then the response to this call is delayed until the SAP Job is completed. Only then additional calls to request the SAP Job execution result and log output are performed.
  • Asynchronous Execution
    • When the SAP Job is launched by the JS7 JITL Job then there is an acknowledging response that returns the SAP Job run identification. The JS7 JITL Job has to repeatedly check the SAP Job execution status. The interval for status checks by the JS7 JITL Job is configurable.

Job Control

The JS7 JITL Job acts as a shadow job for the SAP Job allowing user interventions such as to start or to stop an SAP Job by performing the respective operation on the JS7 JITL Job from the GUI.

  • Starting the JITL Job makes the SAP Job start.
    • Job parameters as available from the SAP Job configuration can be forwarded when starting the SAP Job.
      • JS7 supports the following parameter data types: String, Number, Boolean.
      • The same applies to return values of an SAP Job. Any return values of SAP Jobs are made available to subsequent JS7 jobs in the workflow.
  • Checking the JITL Job status and job logs returns the SAP Job status and log output with the JS7 JOC Cockpit GUI.
    • Note that the SAP REST API offers job logs after execution only.
    • No running log is available from the SAP Job as typically available with JS7 jobs.
  • Stopping the JS7 JITL Job results in the respective SAP REST API call to
    • complete a running SAP Job and then to fail the JS7 Order:
      • Execution of JS7 - Orders can be cancelled by using the CANCEL operation from the JS7 GUI. This allows the currently executed SAP Job to complete and removes the JS7 order from the workflow.
      • Execution of JS7 orders can be suspended by using the SUSPEND operation from the JS7 GUI. This allows the currently executed SAP Job to complete and puts the JS7 order to a SUSPENDED state.
    • kill running SAP Jobs:
      • Execution of JS7 orders can be cancelled with a KILL option to abort the currently running SAP Job and to remove the JS7 order from the workflow. 
      • Execution of JS7 orders can be suspended with a KILL option to abort the currently running SAP Job and to put the JS7 order to a SUSPENDED state.
  • Error handling includes that the JS7 JITL Job checks the execution result reported by the SAP REST API. In case of successful execution the JS7 order is continued and otherwise is failed.




  • No labels
Write a comment…