Up to now, you have made your changes using a change number in the SAP system. You have defined the validity, assigned the objects and made the object changes.
In the following process, not all objects are known from the start, or the date of the change has not yet been defined. In addition, several groups are involved in the process.
Basic process
Watch the following video, which shows a possible process.
In engineering change management, the central object is the change master. You can use the change master to make changes with history to all related objects and document these changes.
Why should I use a Change Record?
If, however, you want to map a change process including status administration in engineering change management, you can use a Change Record.
You compile and check the objects to be changed and see if the object changes appear worthwhile. You change the status of a Change Record when the changes are approved. Then you can perform the changes.
When creating a Change Record, you must define the change type. You can use the change type to define different business processes for requesting, checking, and releasing a change.
A workflow management system coordinates the flow of all types of information through the different activities. A workflow ensures that the correct task is given in the right sequence, to the right person, at the right point in time.
Unlike the change master, the Change Record needs a change type upon which workflow management, or other settings, depend.
Inside the Change Record, you must use a status network, defined inside customizing.
Note
However, when working with a Change Record, a Changer Master always does the object changes. The Change Record is only an object and information folder.