DMS Consolidation Advice
I think the way to approach this problem is numerous and different people would do it in different ways.
We certainly go about a mass check out and check in of documents but let me start by sketching the scenario.
A company has several SAP Instances, each instance having their own Content Servers, totaling 9.
They want to:
a) Move all meta data of the various systems to a new single instance. For this, one would typically ALE the information over. Would the links to the documents in the various KPRO's remain intact? Also, would the object links that were created in the old systems remain intact, if those objects are recreated in the new consolidated system?
b) Let's put a different spin on this, assuming that the material masters from the different systems caused duplicates. E.g. Material 100 on system one, is also found on System 2, 3 and 4 etc, but the materials are different. As part of the consolidation, you change all materials to have a letter as part of the number, e.g. Material 100 in system 1 now becomes E100, in system 2, F100 etc.
The DIR for system 1 would have an object link to material 100. The meta data that has been transferred, will show that. Do you user a BAPI to update the DIR, and if so, would it sever the old Object link and create the new one?
Any ideas on this.
What is the best way to approach such a consolidation in a smooth as possible manner. We always end up spending days writing ABAP's and LSMW's etc et al.
Christoph Hopf replied
normally the original files should be available after the ALE transport. For further information on this kind of scenario please see the SAP notes 1027056 and 919676 which contain very useful information on the ALE transport of original data.
For editing the object link data in the new system, BAPI_DOCUMENT_CHANGE2 should be useful. Maybe also a BADI implementation of DOCUMENT_MAIN01 with method BEFORE_SAVE could help to edit the object link data before the document info record gets saved in the new system.