Ansicht
Dokumentation

/PF1/R_SLA_ANALYZE - Archiving Object SLA: Analysis Program

General Material Data   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Starting Pre-Processing Program for Archiving SLAs

The pre-processing program is the main program used to prepare the archiving process and to determine whether or not data records can be archived.

At first the program starts the package profile formation procedures. One such archiving object-specific procedure examines the dataset of the archiving object and generates as even a package profile as possible. This means that the package limits are set so that all packages contain approximately the same volume of data. The preprocessing program uses this package profile and stores it in the database.

Once package profiles have been generated, they can be used (several times) by the parallel jobs in the analysis and write run. To this end, you must deactivate the Package Formation at Runtime indicator and enter the name of the Package Profile Formation Procedure below it. You do this in the Global Control of Archiving IMG activity.

To ensure optimum usage of system resources in parallel processing during the analysis and write run, the data records to be archived must be distributed as evenly as possible between the individual packages in parallel processing. The value distribution of the first key attribute in the master table of the archiving object determines whether or not the use of a previously generated package profile is recommended: If the data is distributed equally within the possible value range, such as in the case of GUIDs, it is generally sufficient to form the packages at runtime. However, if the data is distributed unevenly (such as for keys formed from number ranges) or if there is a sequence of several GUIDs in a primary key, it makes sense to form package profiles.

Note: The entry supplied by SAP for this archiving object in the global control of archiving makes a recommendation, but you do not have to accept it. If this is not the case in your particular scenario, the system will output a message.

After the package creation, a check of the resubmission time is executed. This check is only required for performance reasons and prevents that a data record that has been analyzed already and shall not be archived yet, will be analyzed again.

Afterwards the residence time is checked. If no particular residence time has been defined in Customizing, a default value will be used. If the residence time lies in the past, the status of the attributes SLA Statusand Release Status is checked.

If the corresponding status of these attributes are Flagged for Deletion and Released the status of the data records is set to Archivable. Otherwise the status of the data records is set to Not Archivable and the resubmission time of the data record will be re-calculated.

During the process, the preprocessing program generates an application log containing statistical data and writes the current status in an activity log. You can view both logs using the archiving monitor, which also enables you to monitor the current progress.

To run the preprocessing program, the following prerequisites must be met:

You are authorized to execute the archiving process. For more information, refer to the Basic Settings -> Authorizations section of the Implementation Guide.

You must have implemented at least one package profile formation function module for the archiving object and stored it in the Global Control of Archiving: Package Formation Procedures Customizing settings.

Depending on the archiving mode in the global Customizing settings, the system either saves the generated package limits in the database or displays them as a list.

For more information about this archiving object, see the document Archiving Object SLA.

CPI1466 during Backup   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5002 Date: 20240420 Time: 043532     sap01-206 ( 90 ms )