In the administration of an archiving request, you can execute additional processing steps using the respective last status.
An icon in the four status columns Copy Status, Verification Status, Deletion Status and Overall Status becomes a pushbutton with which you can execute further processing steps if there is no longer an active process for the request and the request can be continued or repeated (after an error) in the corresponding phase. When you press the pushbutton, a dialog appears in which the request can be continued.
The columns Copy Status, Verification Status and Deletion Status show
The Overall Status column shows
The information below explains what is executed when a particular status is set and what you need to consider when doing this
1. Lock Status
You can lock the selected data area of the archiving request to prevent any changes. This is necessary before data archiving begins. This step can be executed in dialog mode.
2. Copy Status
The data to be archived is copied into near-line storage or the archive. This step is to be executed in the background.
When the write phrase is complete, the archiving request can be marked as invalid if your requirements have changed in the meantime. The data to be archived is still available in the InfoProvider.
3. Verification Status
In the verification phase, the system checks that the write phase was successful and that the data can be deleted from the InfoProvider.
The archive file assigned to the process is opened in test mode and read completely. This ensures that the archive file is complete and can be accessed. If the check is successful, this is noted in a separate status table for the archive file.
4. Deletion Status
When the archived data is deleted from the InfoProvider, the archiving process is complete.
The archived data is deleted from the InfoProvider with the same selection conditions used to copy the data from the InfoProvider. Once the data has been successfully deleted from the InfoProvider, all the archive files from the archiving run are confirmed using the ADK. The archive files are opened in productive mode and closed again immediately. When storing the data in near-line storage, the process is similar.
You can now rebuild InfoCubes with a BWA index. However we also recommend that you add this step to the process chain as a separate process. Otherwise it is not logged.
5. Overall Status
When all the steps of the archiving request have been completed, you can no longer change the status of the request. You can only reload the data. To do this, you can create another request for the reload.