Transfer of Archived Data to Retention Warehouse
You use this function (transaction ILM_TRANS_ADMIN
) to transfer to Retention Warehouse the administrative data for archive files created in the legacy system as part of system decommissioning. This function also supports the transfer of the archived contents (of archive files) via RFC, the ILM conversion of archive files, and the storage of these files via XML DAS.
Note
You do not have to transfer archive files stored via WebDAV from an ILM-enabled legacy system (as of SAP NetWeaver 7.0 EHP1), provided the legacy system and the Retention Warehouse system use the same XML DAS.
Note
Note the procedure and the sequence of the steps for transferring and converting these files described in Transferring Data to RW System and Applying Rules.
The source system (the legacy system being decommissioned) contains archive files whose administrative data you want to transfer to Retention Warehouse. The source system also contains the following remote-enabled function modules required for communication with the Retention Warehouse system:
ARCHIVE_REMOTE_SELECT_ADMIN
ARCHIVE_REMOTE_TRANSFER_FILE
ARCHIVE_REMOTE_SELECT_OBJECTS
You implement these function modules in your legacy system using SAP Note 1411982.
The target system (the Retention Warehouse system) is available and linked to the source system via RFC. You have a user in this system, which has been assigned the following role:
SAP_BC_ILM_IRM
To be able to run an ILM conversion for the transferred archive files, use the transaction IRMPOL
to create a suitable policy and enter the corresponding rules. You must set the policy to "Live".
Call the transaction ILM_TRANS_ADMIN
in the Retention Warehouse system. The system displays a dialog box. In the Archiving Object
field, specify the archiving objects for which you want to transfer administrative data. You can save your selection as a separate variant and then store this variant as your default setting by choosing Default
in the Further Selection Criteria
group box.
You can also use the standard variant SAP&PROD_OBJS
. This variant contains all archiving objects with the exception of the test archiving objects (symbolized by a red equals sign). You can select these archiving objects from the exclusion list that is displayed when you choose Multiple Selection (Active)
.
In the Status of Archiving Sessions
field, enter which type of archiving sessions (such as complete sessions, snapshots) are relevant for transfer.
Select the Runs Without Archive Files
checkbox if you want the system to also transfer the administrative data for archiving sessions for which there are no archive files in the source system. However, it is only useful for documentation purposes to transfer sessions that are not complete or snapshots or for which there are no archive files because these sessions cannot be processed in BI.
After you have made all your entries, choose Execute
to confirm these.
The Links to Legacy Systems
section lists all the source systems to which there is a connection. You can display information about the individual systems by choosing the Details
pushbutton.
When you double-click a system, all the archiving objects that have sessions in the source system are listed under Sessions and Files
. This list also provides further information about the archived data in the legacy system. This includes information about the process status (such as “Data transfer has not started”, “Data transfer partially finished”, “Data transfer finished”), about whether this is a new archiving session or a delta archiving session and about how many data objects were transferred.
You can display detailed information about the individual archive files in the context help for an archiving object by choosing Display Details
. The system opens a new window that contains the session numbers, the archive file keys, and other status information about the archive files.
You can set up a new connection to one or more source systems by choosing the Connection to Legacy System
pushbutton. To set up this connection, choose the New Entries
pushbutton and enter the system ID, client and RFC connection for the source system.
To schedule the transfer of data, select at least one session on the Transfer Administrative Data
tab page and choose the Data Transfer
pushbutton.
Note
You can also access this function from the context menu. The standard system also supports the selection of more than one session, even across different archiving objects.
The system displays the Schedule Data Transfer
dialog box. This is where you enter the details for data transfer. If required, enter the new logical path under which the transferred data is to be stored in the target system. Select the Transfer File Contents
checkbox if you want the system to read the contents of the archive files in the source system and copy this to the target system via RFC. This is only possible if the archive files are accessible in the file system for the source system. The archive files are created in the target system with the same file names as in the source system.
Note
Note that the transfer of large amounts of data via RFC can be very time consuming and can significantly impair system performance.
If you select the Reset Repository Status
checkbox, the system resets the repository status of the transferred archive files in archive management in the target system to “Not Stored”.
Select whether you want to transfer data in test or live mode and whether you want a detailed log. Enter a start date and the spool parameters and finally schedule the data transfer job by choosing the Schedule
pushbutton.
You can follow the progress and status of the data transfer in the job overview. These jobs have the prefix ILM_TRANS
. You can restrict the jobs displayed, for example, to a specific user or date. You can also specify which type of jobs are displayed, such as data transfer jobs only.
Switch to the Convert Files
tab page and update the list of sessions and files by double-clicking the required source system under Links to Legacy Systems
. The system can convert only complete sessions and snapshots. Therefore, you should adjust your selection accordingly by choosing the Variant
pushbutton.
Select whether you want to convert the file in test or live mode and whether you want a detailed log. Enter a start date and the spool parameters and finally schedule the file conversion job by choosing the Schedule
pushbutton.
You can follow the progress and status of the file conversion in the job overview.
After a file has been converted, you can check the result in archive management. The system displays the converted sessions for complete archiving sessions and snapshots in the subcategory From File Conversion
. If the system cannot convert data because of the rules in Information Retention Manager, it sorts this data into sessions in the subcategory Delta Sessions from File Conversion
.
For more information about ILM file conversion, see File Conversion.
Switch to the Store Files
tab page and update the list of sessions and files by double-clicking the required source system under Links to Legacy Systems
. You can adjust your selection as required by choosing the Variant
pushbutton. You can select for storage only sessions with the status “File storage has not started” and “File storage partially finished”. You cannot select sessions with the status “File storage finished”.
Select the required sessions and choose the File Location
pushbutton (you can also access this function in the context menu). Enter a start date and the spool parameters and finally schedule the storage job by choosing the Schedule
pushbutton.
You can follow the progress and status of the file storage in the job overview.
In archive management, you can check in the details for the archive file under which path the archive files have been stored.