cancel
Showing results for 
Search instead for 
Did you mean: 

deleting in sara creates inconsistent # of jobs

0 Kudos

Hi,

When our archiving functional marks 3 ranges to be deleted in SARA, 15 jobs get created in sm37, which is abnormal because the 3 ranges used to create only 6 jobs. This , of course is undesired behaviour because those 15 jobs suck up the wp assigned to background. Could find nothing in google...

Please advise, TIA

Claudio

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

in customizing of the archiving object you define the size of an archive file, there are actually 2 alternative parameters, either by number of records or by MB.

Dependent on the selected data in an write job SAP writes 1 or more archives based on the above mentioned sizing.

Also depending on the customizing of the archiving object SAP either automatically starts the deletion jobs when the write jobs have finished or the write job just finishes without kicking the deletion jobs, then the user has to start the deletion from SARA menu.

If SAP starts the deletion jobs automatically then it creates as much jobs as archives have been written. Yes worst case they block all batch work processes.

if you start the deletion manually from SARA then you can select the archives for deletion and can schedule by yourself.

If you create smaller packages in the write job then you get more write jobs, but you can schedule them for different starting times.

At the very end you have in total probably the same number of deletion jobs, but based on the different schedule time for the write jobs they will not start all at the same time.

Answers (0)