1) certainly can an archiving job run while users are using SAP. Just imagine companies who work around clock and around the globe, there is no time slot to do it without users in SAP.
2) never realized that any object would have such need. Usually there are object dependencies that demand to execute the archiving objects in a certain sequence for bigger success. Running them in parallel would rather have unpredictable results.
3) yes, other jobs do just their work like users do their work in SAP. In general you should not have an interference between the jobs as archiving should be carried out for data which is not needed anymore. Of course does a system not have unlimited capacity for batch jobs, so you should plan the start in a time where you affect less the work of others, because archiving jobs need their part of the performance and job capacity too.
4) this can vary from a second to several hours. Technical environment is just one tessera to the mosaic. It depends how much data you produce per month and how much you have in your selection, how big the object is (several hundred tables or just one), how heavy are the logical checks that all criteria and preconditions are met, when you run the jobs etc etc.
Just imagine utility companies who bill millions of customers each month, imagine supermarkets where each item on the sales slip is a movement. And on the other side you may have remote subsidiaries which just enter 30 sales orders in a month. A sample is not worth anything without knowing the parameters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.