Ansicht
Dokumentation

BDM_TRANSACTION_POSTPROCESS - BDoc type post-processing (more than one active/inactive version)

Vendor Master (General Section)   General Material Data  
This documentation is copyright by SAP AG.

Title

Purpose

During a customer system upgrade, some BDoc and Replication Repository objects with new active versions are imported into the system. If no modification has been made to an SAP object in the system, the repository data remains consistent after the upgrade. However, if SAP delivers a new version of an SAP object that has been modified and activated by the customer. Both objects are active in the Repository after the system upgrade.

You can use this program when you encounter such problems. It helps you to deal with inconsistencies.

For each inconsistent object, you see the differences of the two versions, and then perform one of the following activities:

• Select an active version
  Mark the object version you want to keep as the active version and click on the Select button. The other object version is then deactivated.

• Merge two active versions to create a new version with edit status
  Mark the two object versions from which you want to get a merged version and click on the Merge button. The active version on the left side of the display remains active while the other version is deactivated.

During these steps, transport requests are created for the processed objects.

If there are more than two active versions in the system, the above activity should be repeated until the object data is consistent.

For an object selected as an active version, you have to start the generation process in BDoc Modeler to generate runtime objects. The generation is only possible if the data is in a consistent state.

For merged objects, you have to start the activation process in BDoc Modeler to activate the created edit version. The activation is only possible if the data is in a consistent state.

In a productive system, you must make sure that the generation or activation step is only started after all inbound queues have been locked and all messages in the flow processed. Otherwise, a short-dump will be created or messages in the flow can no longer be processed.

This program is called by BDoc Modeler. It is not online executable.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example

ROGBILLS - Synchronize billing plans   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 2709 Date: 20240520 Time: 091328     sap01-206 ( 55 ms )