Undoing of Changes 

Use

You can use this function to undo object changes that were made with reference to a specific change number.

Prerequisites

Users must have the necessary authorization (authorization object C_AENR_BGR, activity 85).

Integration

In the standard system, undo is implemented for changes to important master data:

·        Scheduled material changes

·        Bill of material

·        Characteristic

·        Characteristic assignment to classes

·        Variant table contents

·        Individual dependency

·        Dependency net

·        Classification

In the BAdI ECM_UNDO Undo Changes, SAP provides separate classes as BAdI implementations for each of these objects. If you want to implement undo changes for more SAP master data and for customer-specific master data, you can use these classes as templates for your own implementations.

Features

Data That Is Undone

Before each undo, the system checks each changed object to see whether the changes can be undone. The following overview shows which data is undone by this function.

Activity	Result of Function
Creating objects	When you create an object with reference to a change number and execute the Undo function, the system removes the object from the database. In contrast to deleting with reference to a change number, the object is not only marked as deleted. You can also create an object with the same name again after this undo.
Deleting objects	When you delete an object with reference to a change number and execute the Undo function, the system only removes the deletion indicator.
Changing objects	When you change an object with reference to a change number and execute the Undo function, all changes are always undone for each object that were made with the selected change number. This also applies for cases where the changes were made at different times or with different transactions. If, for example, you create an object, change it several times, and then delete it with the same change number, it will be removed completely by the undo.

Constraints

If at least one change with a different change number builds on the selected change, dependent changes exist. In this case, an undo is not possible.

The validity of the time is not always decisive for this check. It is always possible, therefore, to undo the last change made, even if this is not the change with the newest validity date.

Two versions of a characteristic exist:

Version 1 with date valid from          01/01/2005

Version 2 with date valid from          01/01/2006

If you make a change with the date valid from 07/01/2005, this third version can be undone although a version exists that lies behind it in time.

Effects on Change Master Record and Change Order

The following effects can be observed in these master records:

·        The change master record or change order is not changed in an undo.

·        Object management records are not deleted automatically.

After you have executed the Undo function, the object can be edited again without a new object management record being created or the change being approved if necessary.

Result of Undo

After undo, the original data that was saved before the change with the selected change number becomes valid again.

You edit a BOM with reference to a change number. For example, you add an item. When you undo the change, the new item is removed from the BOM.

The undo is considered to be a change to the object. Therefore, after the undo, the person who executed the Undo function appears as the person who last changed the object. If change documents are written, they contain the changes to table contents that were made as a result of the Undo function having been executed.

Activities

To start undo, choose Cross-Application Components → Engineering Change Management → Change Number → Undo.

·        A list of all objects appears that were changed with reference to the change number. You can undo changes either for individual objects or for all objects.

Only those objects are displayed for which an undo is possible. For example, scheduled changes to materials are displayed.
Immediate material changes or changes to routings are not displayed.

·        Before you undo the changes, you can simulate the undo in order to check the affected objects. A status and a message text tell you whether an undo is possible, or which error prevents undo. For example, if the change order has already been released, undo is no longer possible.

The system does not check undo authorization for the simulation. This means any user with authorization for change management can check whether an undo is possible.

·        Each undone change is logged.

Even when you have undone all changes and the system does not display any more changes in its overview, you can display the log.

You can see whether changes were undone and which ones. The log also informs you which users executed the Undo function and when.