Master Recipes with Several Change Statuses 

If you change master recipes or recipe objects with a change number, the recipe has several change statuses. If you never make changes with a change number, the master recipe and its objects have only one change status.

For more information on the change status of a master recipe or recipe object, see the administrative data of the corresponding object.

Deleting Master Recipes Online

If you delete a change status online in a master recipe with several change statuses, only this one change status along with its subordinate objects is deleted. You can still access any other change statuses

The master recipe and its subordinate objects are locked:

The change statuses of your master recipe are distributed as in the graphic. You delete the recipe online on the key date shown in the graphic. The system automatically deletes the change statuses of all subordinate objects within the header change status, such as operations, phases, or component assignments. In this example, the change status for operation 10 is only partially deleted because it starts before the change status of the recipe header. After the start of the deleted header change status, you can no longer access the change status of operation 10.

Setting a Deletion Flag

When you set a deletion flag for a change status in a master recipe with several change statuses, the deletion flag is also set for all change statuses of the master recipe. If you enter deletion flags as a selection criterion for an archiving run, the entire master recipe with all recipe objects and change statuses is archived. If you remove a deletion flag, this affects all change statuses of the recipe.

How to Delete a Master Recipe with Several Change Statuses Completely from the Database:

Or