What is Job Scheduling Management?
Event Based Job Scheduling Management
Moreover Event based Job Monitoring is also supported by SAP Solution Manager Job Scheduling Management standard, monitoring is only triggered as soon as the event is scheduled in the managed system. Hence Job Scheduling Management supports creation as well monitoring of jobs based on event from the managed systems.
Business Case – 1: Materials Requirements Planning
Business growth drives the materials planning at each minute level, but organization wide, consolidation is must. Hence, It raises a question for a situation, where planning can be optimized through automation. For example, there are multiple plants in an organization and planning is carried out at each plant level. Once planning is over for all the plants, system should generate a consolidated planning file for all the plants.
We have come out with the proposed solution with the concept of JSM in Solution Manager and Event Based Job Scheduling in managed system. Below is a flow diagram for planning jobs.
- Customized ABAP program which is created in managed system (i.e. in ERP) is run through on the basis of job with respective variants of Event – ZN1 and ABAP program of all the above 3 jobs. The Scheduling information of that job is as under. This job will check that whether all the 3 pertaining jobs which is the base for the 4th job. If all the 3 jobs are in the status finished then this will run event ZN1 as defined in the program. This job will run every 10 minutes.
Custom Program for triggering an event:
- The fourth job will be the base for the all the 3 jobs which are completed and hence this will be triggered based on the event. E.g. ZN1 in our case
- Job Execution has been checked by Monitoring in Solution Manager ensuring timely completion of all the jobs which are required to be run in parallel as well as the job which is to be running subsequently all the jobs as required. E.g. In our case 3 parallel jobs as well the 4th successor job which is required to run only when all the 3 predecessor jobs are completed.
Execution of Parallel Jobs
- Job which runs based on event
Job Execution of Successor Job
- All the jobs are monitored through Solution Manager to ensure that all parallel jobs as well as subsequent jobs have been completed on timely basis
Business Case – 2: Consolidation of MIS report
In many of the organizations, work is distributed according to business unit needs. For example, an MIS (Management Information System) report is required for each business unit. But at corporate level, only consolidated information is important.
Here, there are three main components for MIS: Production Report, Stock Report and Dispatch Report. These reports are generally executed at plant level. Now, to consolidate it at company level, all information needs to be dumped in to excel and then reformatted. But this again depends on emails getting from each plant.
To overcome these, suggested solution is to generate series of jobs and based on that identify whether each job is completed and then run the final Job for consolidation. The same requirements can be catered in a way explained in earlier business case. We can create three different jobs for three different reports and then finally consolidated in to one customized report and that will be scheduled in background.
Concluding the scenario, we can understand that how Job Scheduling Management of SAP Solution Manager can be used to cater to the requirement of parallel scheduling of jobs as well as triggering a subsequent job which collects the data executed by its preceding parallel running jobs.
Successor job will be scheduled only when all the preceding jobs are completed which has been based on event based job scheduling by SAP Solution Manager. The role of Z Program in managed system is to trigger an event only when all the parallel jobs are completed. Job Documentation and Job Monitoring capabilities are also delivered integrated into the existing scenario which is catered by Job Scheduling Management standard.