How to stop jobs after a system copy
After doing a system copy from the Production system to some test system, all the jobs that are supposed to be triggered in the production server will also trigger in the test system which is not good.
For example, If we have a payroll running every month. After i do a system copy the same payroll will also be triggered in the test server which is un acceptable.
How do we go about it and what are all the steps that we need to follow after a system copy?
Points will be rewarded.
Michael Teubner replied
you surely need background processes in a running system.
But you can start a SAP system without any background processes.
When the system is up you go to sm37 and delete (or de-release) all the jobs you don't need in the target system. Then set the number of batch processes to the amount you want and restart the system.
Alternatively you can prepare your source system accordingly with the SAP System Copy Guide - Section 3.2 Technical Preparations:
"Set all released jobs from Released to Scheduled:
Tools -> CCMS -> Background Processing -> Jobs - Overview and Administration (transaction SM37)
You also need to do this for jobs that must run periodically (see SAP Note 16083).
Select all jobs (include start after event) as follows:
Job -> Released -> Scheduled"
I think the best way for you is to read this guide!
Everything is explained very well there.
In the left tree select:
-> SAP Netweaver
-> SAP Netweaver in Detail
-> Software Life-Cycle Management
-> System Copy & Migration
-> Media Library
There are all the Guides for the current releases.
Message was edited by: