Documentation and Evaluation of Recipe Changes 
Use
To meet internal requirements or ensure regulatory compliance, many companies must be able to give an account of the status of their master recipes for any particular point in time. You can do so by documenting the relevant changes in the R/3 System. The data can then be used for evaluation purposes.
Prerequisites
There are several ways to document master recipe changes:
To do so, you must first create a change master record for the recipe or - for master recipes requiring approval - an engineering change order, in engineering change management.
To do so, you must activate the creation of change documents at the following locations in the system:
Note, however, that activating the creation of change documents for too many fields may decrease system performance.

You can activate the creation of change documents for all recipe fields, including the material list. However, you cannot create change documents for the BOM that is assigned to the recipe.
Features
Change Documentation with Change Statuses
When you change a recipe with reference to a change master record or engineering change order, the system creates a new change status for all changed
recipe objects. This change status is valid from the valid-from date of the change number. The status before the change is saved as a separate change status. 
To make sure that all recipe changes are fully documented as change statuses, note the following:
See also:
Working with Change StatusesEvaluating Change Statuses
There is a special function that you can use to compare the change statuses of selected recipes or recipe objects. The system displays:
Change Documentation Using Change Documents
Using change documents, you can document all master recipe changes, irrespective of whether you use a change number or not. The system creates change documents for all editing activities, provided that you have activated the creation of change documents in your system (see Prerequisites).
Evaluating Change Documents
There is a special evaluation function that you can use to find change documents for selected recipe groups,
recipe objects, and persons who made the change. You can choose between the following ways of presenting the results:The system displays the change documents in the order in which they were created. Administrative data is displayed for each change document (for example, person who last changed the recipe, change date, and validity).
You can also display the changes recorded in each change document. Information is displayed on the edited recipe objects, the activity carried out (created, changed, or deleted), as well as the changed field contents.
The system displays all recipe objects that have change documents within the evaluation period. Information is provided on the object, the activity that was performed (created, changed, or deleted), and changed field contents. The objects are sorted according to type, that is, the system first displays all recipe headers, then the material assignments, etc.