Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
Showing results for 
Search instead for 
Did you mean: 
Dear Reader,

I am a Product Expert for the area of Knowledge Provider (KPro). KPro is a framework that is used in Document Manage Systems.

I receive queries on performing the migration of the content repositories. In this post, I would like to introduce to possible ways in which you can perform the migration of the content repositories.


Approach 1) SAP report RSIRPIRL SAP Note  389366 and 1536325

This report works with attachments that are stored with applications like DMS (Transaction CV0*N / Attachment Service), CRM (CRM attachments), GOS (Generic object services / Services for object), SRM (SAP Records and Case Management), SOLMAN attachments and so on.

The report would use the PHIO class header table to get the list of attachments; and thus if the attachments are stored via Archivelink, the attachments would remain untouched in the repository.There may be some orphan/corrupt/dummy attachments which would remain untouched in the original repository.

The report copies the attachments from the source repository to the destination repository and then deletes them from the source repository. Therefore, you must take a backup of the repositories before performing the migration with this report.

This report has the following inputs:-

Document Area:- In case, you would like to perform the migration for all PHIO Classes within a document area.                                    (I have not seen anyone using this actively.)

PHIO Class         :-  PHIO Class which is used for storing the attachments.

Target Category :-  Destination category where you would like to move the documents(Transaction OACT).

Source Category:- Current storage category which is used for storing the attachments(Transaction OACT).

DATUM                :- Creation date of the documents.

Test Run             :- The documents would not be moved (if the test run is checked) but (and) customer would get a list of the documents what would be moved.

You should make sure that the storage category should point to different content repositories ( content repositories are created with transaction OAC0).

Approach 2 ) SAP Development provided report Z_DOC_COPY  SAP note 2774469 

This report works with documents that are stored with the SAP repository (Database / SAP HTTP repository). Report requests content server for document list to the content server ( Command  'adminContRep' & operation 'docIdList').  This command would provide the list of attachments from the content server.

The report would use a list of attachments received from the content server and copy the attachments from the source repository to the destination repository one by one. This report also compares the list of attachments from between source and destination before actual copy and thus even if the report gets terminated for any reason, restart is possible.

Destination Repository  < P_REPDST > Repository from Transaction OAC0

Source Repository  < P_REPSRC > Repository from Transaction OAC0

Document List  < SEL_LIST > This should be used in case you want to copy the specific documents and do not want to copy all the documents.

Approach 3 ) Z_MIGRATE_ARCHIVELINK  SAP note 1043676 - Migration of ArchiveLink Documents.

This report is specifically for Archivelink attachments where the attachment selection is done based on the link tables of Archivelink. The report will get the link entries from all the link tables (TOA01, TOA02, TOA03, TOAHR...) for a given repository and then perform a copy of the attachments from the source repository to destination repository.

The report would also adjust the link table entries. The documents are not deleted from the source repository. Link tables are updated with newly generated document ID and destination repository. Old documents remain orphans in the source repository. 

Approach  4 ) RSGOS_RELOCATE_ATTA  2293171 For GOS attachments. 

You need to relocate the contents of SAPoffice documents relevant to the GOS attachments that are managed by KPro from one category to another.

This report works similar to RSIRPIRL and it has the GOS context attached. Selection screens have GOS related options.

This should be used when the customer wants to move the attachments created from certain applications only e.g. Mail attachments.


Not much documentation available but again similar to RSIRPIRL and adds DMS context to it. In other words, it works for DIR (Document Info Record).

This should be used when the customer wants to move the attachments created with specific document types (e.g. DRW / FOL / SRF and so on) and Document status.


This should be used when the customer wants to move the attachments created with SAP Records and Case Management.

Approach 7) Migration of the documents via Transport Layer.

There are also other reports RSCMSEXT / RSCMSEXA /  RSCMSIM / RSCMSCPY using SAPKPROTP. I have seen some issues. Also, it uses transport files. Troubleshooting is very difficult in the case of SAPKPROTP.  This is not usually recommended for large migration. You can use this report if you have a small list of documents that you want to migrate.



In cases where you are aware of the application that is used to store the attachment. Please use the program from the corresponding application That will give users more control over what is being migrated. In case you just want to copy the documents irrespective of the application you can use report Z_DOC_COPY.

In the next blog post I am planning to explain the difference in Report RSIRPIRL, Z_DOC_COPY, Z_MIGRATE_ARCHIVELINK