---
alias: user-guide-create-recipe
description: "Create a new recipe object, defining details for resource service execution and material usage"
---

# Create Recipe

:lock: Recipe.**Create**

## Overview

This operation is used to create a Recipe, that is, to define the necessary information that a specific Resource requires in order to perform a Service on a given Material.

## Setup

No special setup is required other than to meet the preconditions of the transaction.

## Preconditions

* The Recipe name must be provided and must be unique.

## Sequence of Steps

There are several ways to create a new versioned object. Depending on the level, follow these steps to get started:

* Entity - In the landing page of this entity type in the Business Data menu or in the details page of an existing entity of the same type, select **New** on the top ribbon. For more information see [Creating Entity Objects](../../general/creating_entity_objects.md).
* Revision - If you want to create a new revision, go to the **New** dropdown button on the top ribbon and select **Revision**. For more information, see [Revisions](../../general/revisions/index.md).
* Version - If you want to create a version associated to an existing revision, go to the **New** dropdown button on the top ribbon and select **Version**. For more information, see [Versions](../../general/versions/index.md).

### Step 1: Change Set

1. Select an existing *Change Set* or click **Create New** to create a new *Change Set* to be used for this purpose. If the support of *Implicit Change Sets* has been configured beforehand, it is also possible to check the option *Use Automatic Change Set*.
2. Optionally, select an *Approver Role*.

### Step 2: General Data

1. Provide a name for the **Recipe**.
2. If you are creating a new version, the revision that was selected when you started the process will be the revision to which this version will be associated. If you are creating a new entity or revision (with a new version associated to it), provide a name for the revision or it will be automatically generated for you. For more information on revision naming, see [Revision Naming](../../../general/revisions#Naming/).
3. Provide a description for the **Recipe**.
4. Select the **Recipe** type. The list of possible values is taken from the lookup table *RecipeType*.
5. Select whether the **Recipe** is enabled - note that the enable property applies to the global portion of the **Recipe**.

    !!! warning
        A disabled **Recipe** cannot be used to create a **Recipe** instance.

6. Select whether the **Recipe** is executable - an executable **Recipe** can be used as the **Recipe** for a Material, whereas a non-executable **Recipe** can only be used as a Sub-Recipe.
7. Enter the `Resource Recipe Name` - this information is mandatory and should match the local recipe name in the equipment. This will help differentiate the recipe in the MES from the one in the equipment.  
8. Optionally, enter additional information on the **Recipe**.
9. Optionally, enter additional supplier information.
10. Select **Create** to finish the operation.

![create_recipe][create_recipe]

[create_recipe]: images/create_recipe.png