This is relevant only for OutBoard with storage management. To setup data movement jobs for the different storage locations in line with the different aging profile definitions, the user should initiate ad-hoc data location a data movement job for this to be successfully executed.

Ad-hoc data location can be set up in OutBoard Cockpit and enter Setting → Storage management → Aging profile assignment. In Edit mode assign profile with the target storage and Save.

To initiate movement, go to OutBoard Cockpit and enter the Browser. Take the Storage update button on the header.

_{Switch to storage view button → Storage update button in OutBoard Object Browser}

In the Storage update scheduler setup, you are prompted to indicate an earlier specified Aging profile and an existing Object to give this operation a target. Entering multiple choices and ranges is available.
You may set a number of parallel jobs for the storage updates in Number of parallel jobs. A high number of parallel processes may overload your system.

_{Schedule update of request storage}

Executing the Storage movement job, completes the storage location changes predefined in the Aging profile on the selected Objects.

Scheduling periodic data movement jobs is a pre-requirement for the continuation of the movement scenarios defined in the aging profiles.

You can update storage locations also by calling a report /DVD/NL2_REQ_STORAGE_MASS_UPD via transaction SE38.

Request deletion via storage update

It is possible to set up an aging profile to delete old data based on conditions:

OutBoard Browser:

If the request is marked as 'will be deleted on next update' the storage update has to be executed for request, storage and it will automatically delete the request from the archive.

Browser not supported