The transaction codes SM36 and SM37 are classic transactions for job planning in SAP. But modern SAP ecosystems demand more. Find out how professional workload automation can automate your processes in SM36 efficiently and securely.<\/p>\n\n\n\n
Many companies continue to use standard SAP transactions such as SM36 and SM37 to control their background processing. These tools provide a SAP-specific way to schedule and monitor background jobs – ideal for simple, repetitive processes such as IDOC processing or spool outputs or file transfers in the respective system. Both transactions help to define and monitor system-specific jobs.<\/p>\n\n\n\n
However, for more complex processes such as complete payment runs or material requirements analyses, the SM36 already becomes confusing and unreliable. If a core process also runs across systems, there is no common basis.<\/p>\n\n\n\n
In addition, modern IT landscapes – characterized by SAP S\/4HANA, hybrid cloud models and non-SAP systems – require a whole new level of control, transparency and security, away from system silos.<\/p>\n\n\n\n
The reality is that traditional job scheduling with SM36 is no longer enough.<\/p>\n\n\n\n
SM36 can schedule individual jobs, but important functions are missing:<\/p>\n\n\n\n
Of course, experienced SAP admins have workarounds for scheduling many processes in several systems, even without dependencies. For example, by creating additional plans with SM36 in each individual system and adding buffers. However, this can be very fragile and time-consuming. Let’s take a closer look at this:<\/p>\n\n\n\n
System limitations in SM36 lead to manual intervention, sources of error and a lack of transparency – a serious risk for critical business processes. In the event of an error, the IT expert has to laboriously check the logs in the respective system. This time expenditure then leads to a further loss of time simply by searching for the job error (and the subsequent job) in the SM37 list view. The faulty job then has to be restarted manually, which can lead to delays, failures or incomplete key figures in reports.<\/p>\n\n\n\n
An error in material requirements planning can cause production delays and jeopardize the timely supply of replenishments. In payment runs, the SAP Payment Run, error-free delivery of payment information is also key to a company’s compliance.<\/p>\n\n\n\n
\nBefore using BatchMan, our job planning was carried out exclusively via SM37 – without central control and with a great deal of manual effort. It was difficult to recognize dependencies between processes. With BatchMan, we now have a central platform for job planning and control that offers us significantly more transparency and efficiency.<\/strong><\/h4>\nDetlev Louis Motorrad-Vertriebsgesellschaft <\/em><\/cite><\/blockquote>\n\n\n\n