Purpose
During a customer system upgrade, some BDoc and Replication Repositoryobjects with new active versions are imported into the system. If nomodification has been made to an SAP object in the system, therepository data remains consistent after the upgrade. However, if SAPdelivers a new version of an SAP object that has been modified andactivated by the customer. Both objects are active in the Repositoryafter the system upgrade.
You can use this program when you encounter such problems. It helps youto deal with inconsistencies.
For each inconsistent object, you see the differences of the twoversions, and then perform one of the following activities:

• Select an active version

Mark the object version you want to keep as the active version andclick on the Select button. The other object version is thendeactivated.

• Merge two active versions to create a new version with edit status

Mark the two object versions from which you want to get a mergedversion and click on the Merge button. The active version on theleft side of the display remains active while the other version isdeactivated.
During these steps, transport requests are created for the processedobjects.
If there are more than two active versions in the system, the aboveactivity should be repeated until the object data is consistent.
For an object selected as an active version, you have to start thegeneration process in BDoc Modeler to generate runtime objects. Thegeneration is only possible if the data is in a consistent state.
For merged objects, you have to start the activation process in BDocModeler to activate the created edit version. The activation is onlypossible if the data is in a consistent state.
In a productive system, you must make sure that the generation oractivation step is only started after all inbound queues have beenlocked and all messages in the flow processed. Otherwise, a short-dumpwill be created or messages in the flow can no longer be processed.
This program is called by BDoc Modeler. It is not online executable.

Features