Advanced Scenarios

This chapter describes advanced, real‑world scenarios where Recipe Instructions adds the most value, especially in environments where recipes change over time, multiple variants share the same manufacturing flow, and shop floor execution requires clear, controlled instructions inside Business Central.

Managing recipe changes over time

Scenario: Recipe changes (ingredients or steps) from a specific date

Food/process manufacturers frequently update instructions due to ingredient substitutions, quality improvements, allergen statements, or regulatory changes. With Recipe Versions, you can keep historical versions while controlling exactly when a new version becomes applicable.

How it works:

• A Recipe Version mirrors the original Recipe structure, but adds a Starting Date that defines when that version becomes valid.
• A version remains valid until the next version’s Starting Date takes effect.
• When a new version becomes valid, the previous one is no longer applicable.
• Last Date Modified is updated automatically when changes are made, helping you identify the latest maintenance activity.

Practical guidance (best practice):

• Create a new version instead of overwriting the existing recipe when the change must be traceable (audits/recalls).
• Use the Starting Date to coordinate go‑live with production planning (e.g., effective next week / next campaign).

Speeding up recipe creation for product variants

Scenario: Same process flow, different product presentation

You manufacture multiple variants that share the same Production BOM + Routing structure (e.g., different packaging sizes), and you want to reuse the same shop floor instructions instead of retyping them. Copy Recipe is designed for exactly this.

How it works:

• From the Recipe Card use Actions → Copy Recipe to copy instructions from an existing recipe.
• The selection list is automatically filtered to compatible recipes to protect data integrity. Compatibility is based on:
  • Same Production BOM No.
  • Same BOM Version (if applicable)
  • Same Routing No.
  • Same Routing Version (if applicable)

Why compatibility matters (and what the system prevents):

• Copying instructions between incompatible configurations (different BOMs or routings) can lead to errors when creating or executing production orders—therefore the app only shows compatible sources.

Use Copy Recipe when:

• You are creating similar products that use the same BOM/routing structure.

Avoid Copy Recipe when:

• Ingredients change (different BOM) or the process changes (different routing). In that case, create a new recipe card instead.

Controlling recipe validity and data integrity

Scenario: Prevent users from building recipes on non-approved structures

Recipe Instructions enforces critical validations to reduce execution risk:

• Only Certified Production BOMs and Routings can be selected on the recipe header.
• There can be only one combination of Item + Production BOM (+ version) + Routing (+ version), ensuring no ambiguous recipe selection for the same configuration.

Scenario: Master data deletion impact

To keep consistency:

• If a Production BOM, Routing, or Item Card is deleted, the related Recipe Card is also deleted, with a confirmation prompt warning you that the recipe will be removed.
• If a BOM or Routing version is deleted, the recipe is updated to remove the reference to that version.