SAP NW Newbie

If you have multiple application servers, change and set the parameter rdsip/btctime to a different value on each one eg. 56, 57,58,59 etc. The job scheduler "SAPMSSY2" runs every "rdisp/btctime" seconds (60 by default) and looks for all the pending jobs in the job queue and assigns them to the available free batch work processes in the system. If there are other batch work processes waiting while the jobs are in the ready status, ensure that you have not over-allocated batch WPs for Class A jobs only. You can change such allocation from the transaction RZ04. If you find that WPs are not over-allocated to Class A jobs, it could be that a job is blocking access to the WPs. Run temse check as explained below and kill/restart the WPs that are in waiting status to get the WP working. Run Transaction SM65 Select Goto > Additional tests Select these options: Perform TemSe check Consistency check DB tables List Check profile parameters Check host names ...

Enterprises using multiple ERP systems look for a a job schedulers that can work with SAP and other ERP or DW vendors alike. Third party tools are not advisable if the Enterprise runs purely on SAP ERP. They increase the TCO, increase delays in problem correction, create high dependencies among technologies, and increase chances of miscommunication. If varied technologies are being used, investing in a third party scheduler is useful to have a centralized scheduler. Here are some popular schedulers: Control-M by BMC Cronacle by Redwood ORSYP by Dollar Universe Tidal Enterprise Scheduler by Cisco Tivoli Workload Scheduler (Maestro) by IBM  UC4 Global by UC4