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,

Moving forward with migrations , We are supporting our customers on their way to SAP S/4HANA to take advantage of best in class innovations and get ready for the new world of challenges and opportunities.

You all must be aware of the SAP S/4HANA Migration Cockpit, which allows you to move your ERP data to SAP S/4HANA.

For our customers the attached documents are an important part of a successful data migration. With the SAP S/4HANA Migration Cockpit we are now able to support the migration of Document info record (DMS). Please find the object documentation here.

The optimal way was always a question for us and here is what we decided

The boundary condition is that the storage location of the documents remains as it is - physical migration of the documents is not in scope of the migration. In case you would like to use a new storage, e.g. new content server from a new vendor, you should change it in your ERP source system (best case). The second option is to do it as a post migration activity in your SAP S/4HANA system (next best). The business documents will be migrated with the SAP S/4HANA Migration Cockpit and in addition the related attachments will be RELINKED with same attachment ID to the NEW Business Document number of your SAP S/4HANA system.

This migration also does not allow or covers changing the documents from one document type to another. e.g. changing the GOS attachments in DMS and vice versa.

This migration currently ONLY covers DMS attachments, but we are working to support also GOS attachments in the future.

Why we decided to keep the actual migration of the documents outside the scope of the Migration cockpit ?

Covering the document migration within the migration scope, the process would have become very slow. Further the migration complexity incl. issue handling would increase the migration process considerably. With this proposed approach we are going to minimize the impact on your business processes after migration.

What you should do ?

Before performing the migration you should  create all the content repositories (OAC0) and storage categories (OACT) in S/4 System. You use the same repository as in your ERP source system.

Afterwards use the SAP S/4HANA Migration Cockpit and migrate your DIRs (DMS).

Results :-

Your DIR details would change but actual documents (Attachment) would remain in the same Content Repository / Storage category.


FAQ :- 

1.What if you want to like to migrate the attachments ?

Ideally you should do it as a separate project before / after performing S/4 migration. This will make sure that you are sure that this will not cause issues in the migration and will execution time for your actual migration.

2.What should you do if you are using Repository of type SAPDB ?

You can

  1. Copy the content table directly from your source system to target system.

  2. You can follow SAP Note 685521. Then use your Pre-migration SAP system as a source for your document.



Vote-of-Thanks before I finish.

This post wouldn’t have been possible without inputs from devyan and claudia.gemm . So Thank you for your inputs.