Recipes define a valid combination of workflow and Bill of Materials (BoM) or a valid workflow without a BoM. The recipe is what links a workflow and BoM to a product. Without a recipe, the workflow and BoM cannot be used.
You can only create an order for a valid workflow/BoM combination, as defined by an approved recipe.
When you create a spawned task from the shopfloor, you can only create this for a workflow and BoM combination (if one exists), as defined by an approved recipe.
The image below shows the relationships between a product and its recipes, workflows and BoMs. The red lines show the workflow and BoM versions used by the product's recipes.
The relationships are:
- A product can have many recipes.
- A recipe can link to one workflow and one BoM (if one exists).
- Each workflow and each BoM can have multiple versions – a default/constraint can be set over which versions are used.
Recipe Controls
A recipe can only be used if all of the following are true:
- There is at least one workflow version referenced that is approved.
- Either no BoM is referenced or a BoM is referenced and there is at least one BoM version that is approved.
- The recipe itself is approved.
Create a New Recipe
The New Recipe pop-up can be accessed from the Recipes page which is available as a pop-up from the Products or Workflows screens (product pre-selected) or direct (product not pre-selected). These instructions will access the Recipes pop-up from the Products screen.
- Navigate to the Products screen and search and select a product.
- Click the Recipes button. The Recipes screen is displayed with just the existing recipes that are allowed for the selected product based on the product's workflow type.
- Click the New Recipe button.
- Complete the New Recipe input screen.
New Recipe input screen
The following properties can be defined:
Blue fields in the form are required and are flagged with an asterisk (*) in this document.
- BoM: It is possible to have a recipe that has no BoM but has just a workflow. This field is optional.
- BoM Search: Type in part of the BoM to filter the BoM Search field based on your search term.
- Search*: List of BoMs filtered according to the search term provided in the BoM Search field.
- Version Control*: Use the latest approved version is the default.
- Workflow: A recipe will always have a workflow. This field is compulsory.
- Workflow Search: Type in part of the workflow to filter the workflow Search field based on your search term.
- Search*: List of workflows filtered according to the search term provided in the Workflow Search field.
- Version Control*: Use the latest approved version is the default.
- Name*: Key identifier for the recipe. This will be visible to select when you create a new works order.
- SUID: Useful where you are referencing an equivalent entity in ERP (e.g. production model in SAP).
- Change Reference: Development of new recipes is often controlled by a change management process, which is often managed within a specialist PLM system – the change reference can be stored here.
- Default Product Version: When you are using this recipe on a works order, this determines the default product version of the item that you are creating.
- Description: Can be useful additional information, especially where you have many recipes for one product.
Recipe Status
The allowed statuses for recipes are Draft, Pending Virtual Test, Pre-production, Pending Approval, Approved and Obsolete. For more information, refer to the Approval and Test Statuses documentation.
Each time you change the status of a recipe a system validation check is done on the workflow to ensure that from a system perspective there are no issues that make it functionally invalid (e.g. missing flows/invalid work centre groups).
