Skip to Content
Technical Articles

Content Repository Migration in mind ? Part IV Error in Migration

Dear Colleagues,

Welcome Back¬† ūüôā I realized sometime back that there is still a missing piece in the puzzle of Repository Migration which is about error handling. With this post, I would try to answer a few more questions and also add information on how to analyze errors in case you face them and basic tricks that can help you in resolving them. I will keep it as a FAQ for simplicity.


Q:- How can I find an existing storage category that is getting used for storing the attachments


>> If you know the document class (PHIO Class) You can go to table SDOKPHCL. In this table using PHIO_CLASS as input, you can find the header table and then check the header table. This header table will hold all the PHIO Ids which will be created in this PHIO class. You can also find the storage category here.

>> If you know repository that you are using, You can go to transaction OACT and find corresponding storage category

>> If you are using Archivelink  application You can use transaction OAC2 to find the content repository and then use it in ArchiveLink report


Q:- I have performed the migration of the documents and I still find that some documents are remaining in source repository what should I do?


There can be multiple reasons why these documents can be remaining in your repository.  I can list a few possibilities so that you can weigh them and make a correct call.

>>> These documents are test /dummy documents that are created while repository testing. I need not tell you that you can ignore these documents. You can find it by checking the document contents.

>>> These are documents which are remaining as the deletion of these documents were missed out and there is no business document which is referring to them.

You can find this by trying to find these Document Ids in PHIO header table and ArchiveLink link tables and then you can be assured that these documents are most likely would not be accessed. ( Exception to this statement:- You have Archived the links and document is still there in the repository) . You should make your own call here.¬† But if there is no archiving which is involved you can consider deleting the documents.¬† ¬† You should also execute report ‘RSIR_CONTENT_UNMARK_PRELIM’¬† this report will delete marked documents.

>>> These are actual business documents from the required document class but they were not migrated and you are getting an error in migration. In this case, we need to dive deeper. You use below mentioned methods to find why failure and decide what should be next.

Please note that in case you are using Archivelink report Z_MIGRATE_ARCHIVELINK ( SAP note 1043676 Or report Z_DOC_COPY  SAP note 2774469 the source repository will be untouched and the documents would remain in the source. The above question is not relevant in that case.

] Q:- I get an error while executing report RSIRPIRL now what?


If your inputs are correct and existing documents have been saved correctly, you should not be facing any issues.¬† As you are facing the issues,¬† let’s try to find what went wrong.

As a first step, You should check application logs with transaction SLG1. You should use the object as ‘SDOK’ and ‘SCMS’. KPro will log the error against these two objects.

Here looking at the error, if you find that you have an issue in reading attachment from the original repository, You should try to access the documents from the actual business object and if you get an error, you should be certain that error is in the source repository.

If you find that error is while creating the document in the new repository, You know that error is in the target repository. To re-confirm that your target repository is working correctly, You can use test report RSCMST with input as Repository ID and then Report RSCMSTH0 and RSCMSTH1 to confirm that repository is working correctly.

In general, You will not have an error in the source repository because your business would have reached out to you by now. You will most likely have an error in the transfer of the document to the target repository or in the Target repository and steps above should help. In case this is not helping, please take necessary traces while you try to migrate the documents and contact your repository vendor.

Qs:- I have migrated the documents with report RSIRPIRL and now we are not able to access the documents.


This is the most difficult and unpleasant of all. This issue becomes more annoying if it occurs for some documents and not for all.

In my experience, there have been cases where there were some issues in the data transfer from SAP and if you are using stable software patch chances of you facing issues is fairly low.

Another case that I have seen where you may face issues is that you have saved the documents incorrectly, e.g. without file size and now you are moving your documents to the HTTP server and you find that the documents are not saved correctly.

Technically, if you were using SAP DB for the document storage, Kpro just performs the export the contents and document information to the R3 Database. 
When you try to move this data to the external server the server will get the file information along with the contents. Here if the file size zero, 
the HTTP content server ignores the contents and stores the empty file.

My recommendation to handle this would be you make sure that you take the back-up of your source server before you start the migration. This will save you in case things turn sour.

Another issue that can happen is that you have saved the documents with incorrect MIME Types and then you perform the migration where virus scanner would block the file because of the incorrect MIME type. You should correct the MIME types in this case. You can use the SAP standard report to correct the MIME type of each individual document.

This would help you with the migration of existing documents.

So That’s all that I can come up with for now. Be safe and be healthy.¬† Until next time

Bye, Ciao, Tsch√ľss.

You must be Logged on to comment or reply to a post.
  • Hi Sagar,

    thanks for all the useful information.

    is it possible to use the described reports for a system migration from SAP ECC to S/4 HANA?

    The issue is to migrate a defined list of document info records (DIR) and their originals from one system (ECC) to another (S/4 HANA). There are also GOS attachments and archivelink documents to be migrated.

    For the migration of DIR we found a migration object in the migration cockpit. But what is the best way to migrate or copy the originals?

    Thanks and best regards


    • Dear Christian

      Yes it is possible to use these reports in S/4.

      These reports are migrating DIRs / GOS attachments across systems. These reports are for copy / migrating the Documents between repositories connected to  same SAP system.

      Thus for your ECC to S/4 HANA migration i would recommend you to use Migration Object from the Migration Cockpit.

      Regards S S B

      • Dear Sagar,

        in our case, the ECC is a separately installed system than the S/4 system. So we want to copy/migrate the originals from one content repository to another.

        The target repository will later on be connected to the ohter SAP system (S/4).

        For the migration of the DIR, we can use the migration object from the migration cockpit. But this does not consider the originals.

        Therefore our idea was to copy the originals with the reports and migrate the DIR with migration cockpit.

        But in the end it will not be in the same system. And thats my question: Is that a valid way to perform the migration from one system to another. Or would you recommend another way to do this migration.

        Thanks in advance


        • Dear Christian,

          You can copy the documents with these reported. You have to connect both the repositories to the Same system (Using transaction) while Migration. and then connect new repository to the S/4 systems.

          You can perform this migration in advance before actual migration to S/4 as these programs would be slow, You can do copy as Pre-migration Activity.

          You can also just connect your existing Content Server to S/4 and then perform migration at later point.



        • Hello Christian,

          We are facing the same issue like you mentioned before - Migration DIR from ECC to S4 in migration cockpit with original documents.

          I want to get some experiences from your side that if you migration topic regarding the original files has solved by the way Sagar recommended?

          And after DIR migrated, original file copied how you perform the link between DIRs and original files in DMS* relevant tables?

          Wait for your kind reply. Thank you very much!

          With Kind regards


  • Dear Sagar,

    thank you for your clarification.

    If I may ask one more question:

    When originals are copied and DIR's are migrated, we have to create the link between the DIR and its originals. Therefore we thought about using function module "SDOK_LOIO_CREATE_WITH_PHIO" in a separate report, running after the migration. Do you think that would be a valid way or do you know a better alternative



    • Dear Christian,


      You would need to do more than that :(.  You have to copy other tables DMS_P*CD1, DMSL*CD1, and DMS specific tables like DMS_DOC2LOIO and FILE2PHIO also. There may be other tables as well and I am not fully aware of them.

      Also , if you find these Blogs useful please hit Like for the Blog ūüôā




  • Hi Sagar,

    Thanks for these blogs, these are very useful.

    We have a requirement where the content repository will be the same. The DMS documents(CV01N/02/03) in the source need to be migrated to the target system pointing to the same file in the same content repository as it is also connected to the target system. Is there any way to achieve this. Please help me here. Thanks in advance.

    • Dear Gopal,


      Then this is not a migration, you just have to create OAC0 entry in Target system. I do not recommend this because then your documents can get deleted from one system say target and source will still have the reference.


      Sagar S Bhide

  • Hi Sagar,

    we are using report Report Z_DOC_COPY for content migration.

    In our case, we are migrating from HANA to the content server ( MaxDB).

    we are not getting clarification for metadata adjustment.

    a. No changes in metadata tables are made, the customer has to adjust them manually ( How to do that ? )

    Please help us to understand this procedure.



  • Good Afternoon Sagar,


    I would like to migrate BDS documents stored in an archivelink/httpContentServer repository C5 to another archivlink/httpContentServer repository C6.

    As these documents are using BDS, there are meta information stored (eg in the table BDS_PHIO). For example, I have noticed that the column PROP09 contains the current repository C5.


    1. How can I perform a migration that would migrate the meta  information (C5->C6 in the column PROP09 of table BDS_PHIO).
    2. Could I perform a migration that would preserve the arc_doc_id?

    Have a nice day.


    Hi Sagar,


    Let me elaborate. I think most of People on your blog has same requirement as given in Diagram Below.

    Can you please elaborate details steps for this kind of Server Landscape. There are various Option for Migration

    Option 1.

    1. Create a Download program to Get List of DIR's and Their Originals on a Shared Folder.
    2. Create Upload program  and Use Data downloaded in point 1 and Upload DIR ( Meta Data, Object Links, Classification Data)

    Option 2

    Can we Use BODS Tool using BAPI_DOCUMENT_CREATE2 or DOCMAS IDOC? Can we migrate Originals using IDOCs.? What are challenges


    Option 3

    Use Program " DMS_KPRO_CONVERT2" or Bunch of Programs you have suggested.


    It would  be good and Helpful blog if you can guide on these Options.


    Also One more thing, MSDS are stored in SAP DMS as SBR Document Type and SAP has no Standard way of Extracting MSDS from Source system and Uploading on Target System.

    Every Project has to struggle on these points and SAP Has no clear cut tools which can help Consultants for various situations.

    I hope this helps you in more broader sense what issues are faced in SAP DMS Migration. If you can help us in these answers that would be appreciated.


    With Warm Regards


    Mangesh Pande



    • Dear Mangesh,


      Sorry for delay in replying. I was away and then got stuck with daily routine.

      These blogs are generic and SAP DMS is one of the use case. I have tried providing generic information and possible building blocks which can be used for migration of the documents in the content repository. I will try to write something specific to DMS if there are enough community members looking for that information.

      For Migration of DIRs (SAP DMS documents ) to S/4 You can refer to a blog,  Migration of the documents from ECC to S/4 | SAP Blogs . May be you will find that helpful.  In short, we allow customers to use same content repository in S/4 and migrate ECC data to S/4.