Resolving 'Unit Not Existing' and Invalid Master Recipes in SIMATIC BATCH After Process Cell Updates

In SIMATIC BATCH, master recipes turning invalid (highlighted in red) with validation errors reporting 'unit not existing' or 'unit recipe invalid' after compiling and downloading CFC/SFC changes occurs because the underlying Process Cell data in BATCH Control Center (BCC) has lost synchronization with the SIMATIC Manager Plant Hierarchy. Modifying SFC types or unit folders alters the internal technological identifiers (TechID). To resolve this, compile and propagate the Process Cell from SIMATIC Manager, execute 'Update Process Cell' in BATCH Control Center, open the affected master recipes in the BATCH Recipe Editor, reassign the modified unit instances in the Recipe Unit Procedure (RUP), and re-validate and release the recipes.

SIMATIC BATCH Process Cell Hierarchy and Recipe Binding Architecture

In SIMATIC PCS 7, SIMATIC BATCH models batch production facilities in strict alignment with the ANSI/ISA-88 (IEC 61512) standard:
* Plant Hierarchy (Engineering System): Configured in SIMATIC Manager under the Plant View. The physical equipment is structured hierarchically: Process Cell -> Units (Units/Teilanlagen) -> Equipment Modules (EEM) -> Control Modules (CM).
* Technological Interface (SFC Types / EPH / EOP): Technological phases and operations are engineered as SFC Types or interface blocks (IEPH / IEOP) and assigned to specific unit folders.
* Master Recipes (SIMATIC BATCH): High-level recipes define Recipe Procedures (RP), Recipe Unit Procedures (RUP), and Recipe Operations (ROP). Each RUP binds to an ISA-88 Unit Class or specific physical Unit instance via internal technological GUIDs (TechIDs).

Root Causes of 'Unit Not Existing' Recipe Invalidation

When master recipes turn red and report 'unit not existing' after AS/OS engineering changes:
1. Unsynchronized Process Cell Propagation: Adding, renaming, or modifying CFC charts, SFC Types, or Unit folders in SIMATIC Manager modifies the equipment model. If changes are compiled to AS/OS but not propagated to SIMATIC BATCH, the BATCH database references obsolete equipment structures.
2. Technological ID (TechID) Invalidation: If an SFC Type instance is deleted and re-inserted, or if a Unit folder's technological properties are reassigned, a new TechID is generated. Existing master recipes still reference the old, now non-existent TechID.
3. Unit Allocation Rule Breaches: If an SFC type interface modification adds required equipment properties or changes unit parameters, existing recipes fail validation until unit allocation requirements are updated in the recipe header.

Remediation Procedure - Propagating Process Cell and Re-Validating Recipes

Follow this standardized procedure to restore recipe validity:

[Phase 1: Compile and Propagate Process Cell in SIMATIC Manager]
   │  • In SIMATIC Manager: Right-click the Multiproject or Process Cell folder
   │  • Select: SIMATIC BATCH -> "Compile / Download..."
   │  • Check options:
   │      [x] Compile: "Entire process cell"
   │      [x] Transfer: "Process cell data"
   │  • Click "OK" to regenerate the BATCH equipment database
   │
[Phase 2: Update Process Cell Data in BATCH Control Center (BCC)]
   │  • Open BATCH Control Center on the Engineering / BATCH Server
   │  • Navigate to menu: System -> "Update Process Cell"
   │  • BCC ingests the new XML equipment schema from the ES
   │
[Phase 3: Re-Validate and Release Master Recipes]
   │  • In BCC, navigate to: Master Recipes -> Open invalid (red) recipe
   │  • The Recipe Editor highlights the affected RUP (Unit Procedure)
   │  • Double-click the RUP Header -> "Unit Allocation" tab:
   │      - Re-select the physical Unit or Unit Class from the dropdown
   │  • Select: Recipe -> "Validate"
   │      - Confirm: "Validation successful - 0 Errors, 0 Warnings"
   │  • Select: Recipe -> "Status -> Release for Testing" -> "Release for Production"

Process Cell and Recipe State Diagnostic Matrix

Evaluate recipe validation indicators and their corrective actions:

Recipe Validation ErrorUnderlying CauseBATCH Control Center IndicatorCorrective Action'Unit not existing'Unit folder modified or TechID deleted in ESRed cross on RUP HeaderRe-propagate Process Cell; reassign unit in RUP properties.'Phase not assigned to unit'SFC type moved to different hierarchy folderRed cross on Recipe Phase (ROP)Update phase allocation in BATCH Recipe Editor.'Parameter type mismatch'Setpoint data type altered in SFC TypeYellow warning on Phase ParameterOpen phase properties; enter new default parameter value.'Process Cell out of date'Engineering compilation done without BATCH updateWarning badge on Process Cell objectExecute System -> Update Process Cell in BCC.'Recipe cannot be released'Unassigned equipment phase or missing transitionStatus bar error reportComplete all required phase parameter inputs.

Verification

To confirm that all SIMATIC BATCH recipes are restored:
1. In BATCH Control Center, expand the Master Recipes tree; verify that all recipe icons show green released status without red error overlays.
2. Open each master recipe in the BATCH Recipe Editor and execute Recipe -> Validate; confirm that the validation dialog reports zero errors.
3. In BATCH Control Center, create a test control recipe; verify that the recipe transitions to 'Created' and can be scheduled on the target unit.
4. Start a dry batch run; confirm that the unit allocates successfully and SFC types transition through execution steps without allocation errors.

Limitations and Operational Precautions

Never update the Process Cell or transfer new equipment data to SIMATIC BATCH while active production batches are executing on the units. Modifying unit structures during batch execution can abort active recipes, resulting in product loss. Always wait for units to enter the 'Idle' state before executing 'Update Process Cell' in BCC. Ensure all validated recipes are backed up prior to Process Cell propagation.

Engineer FAQ

Why did modifying a CFC chart invalidate all my master recipes?

If the CFC chart contained an SFC Type instance representing a batch phase, modifying its interface altered the equipment interface database, requiring all dependent recipes to be re-validated.

Can I re-validate multiple recipes simultaneously in SIMATIC BATCH?

Yes. In BATCH Control Center, select the Master Recipes folder, right-click, and select 'Validate all recipes'. The system performs batch validation and highlights any failing recipes.

What does 'Transfer Process Cell' do during compilation?

It exports the plant hierarchy equipment model, SFC types, and unit classes into XML exchange files and transfers them across the Terminal Bus to the BATCH Server database.

How do I fix a recipe if a physical unit was permanently decommissioned?

Open the Recipe Unit Procedure (RUP), remove the decommissioned unit from the unit selection list, and assign an alternative unit from the same unit class.