Resolving Process Cell Name Mismatches During SIMATIC BATCH Generation

The error 'difference between the name of the cell in the batch and the name of the cell in the TH folder' occurs during SIMATIC BATCH generation when the Process Cell name configured in the SIMATIC Manager Technological Hierarchy (TH) differs from the existing plant model registered in the BATCH database. In PCS 7, SIMATIC BATCH enforces strict name and GUID synchronicity. Renaming a plant hierarchy folder without re-propagating and updating the BATCH configuration triggers this validation conflict. Realigning folder names, executing 'Compile / Propagate' from SIMATIC Manager, and updating the plant model resolves the error.

Synchronization Architecture: Technological Hierarchy and SIMATIC BATCH

In SIMATIC PCS 7, recipe-driven batch automation is governed by SIMATIC BATCH adhering to the ISA-88 (IEC 61512) batch standard. The foundation of any BATCH configuration is the Technological Hierarchy (TH) configured inside SIMATIC Manager:
* Plant View: The hierarchical directory tree represents physical and operational relationships:
Process Cell -> Plant Unit -> Equipment Module -> Control Module
* In folder properties, the top-level container is flagged as Process Cell (Batch Plant), child folders are flagged as Unit, and SFC types or Phase blocks are mapped as Equipment Phases.
* During batch engineering, SIMATIC Manager compiles these objects into a unified XML plant model and transfers them to the SIMATIC BATCH database via the Compile / Propagate mechanism.

During the final "Generate" phase within BATCH Configuration, the compiler checks every technological entity to verify that the plant model in the BATCH database matches the project's active TH database.

Root Cause of the Process Cell Name Discrepancy

The error message:
difference between the name of the cell in the batch and the name of the cell in the TH folder
is triggered under specific engineering conditions:

Direct Hierarchy Folder Renaming: An engineer renames the top-level plant hierarchy folder in SIMATIC Manager (e.g., from Cell_Reactor_A to Plant_Cell_1) but attempts to run "Generate" inside the BATCH Configuration application before propagating the change.
Stale BATCH Database Cache: The BATCH Configuration tool holds the original process cell descriptor in its local database repository (sb_data). Because the new TH folder name does not match the cached descriptor, the validator detects an integrity collision.
PlcSim / Offline Project Cloning: Creating a test project for S7-PLCSIM by copying and renaming projects frequently breaks internal GUID cross-references between the Step 7 project database and the BATCH database.

Step-by-Step Resolution and Model Reconciliation Procedure

Follow this structured procedure to reconcile the Technological Hierarchy with SIMATIC BATCH:

Verify Technological Hierarchy Settings:
* Open SIMATIC Manager and switch to the Plant View.
* Right-click the top-level folder representing your process cell and select Object Properties.
* Go to the Technological Hierarchy tab.
* Verify that the check box Process cell is selected. Note the exact text in the folder name.
Execute Compile and Propagate from SIMATIC Manager:
* Close the BATCH Configuration dialog and Batch Control Center (BCC) on all computers.
* In SIMATIC Manager, select the top-level Multiproject or Project folder.
* Right-click and navigate to SIMATIC BATCH -> Compile / Propagate.
* In the wizard, select Propagate (this updates internal GUID mapping tables).
* After propagation completes successfully, select Compile -> Entire system.
Reconcile within BATCH Configuration:
* Launch Configure BATCH from SIMATIC Manager.
* In the BATCH configuration tree, expand the plant model.
* If the process cell still reflects the old name, right-click the cell and select Update plant model or Synchronize with TH.
* If a conflict prompt appears, choose to accept the new name from the Technological Hierarchy.
Execute BATCH Generation and Download:
* In BATCH Configuration, click Transfer messages.
* Click Generate. The generation routine will now pass with zero mismatch errors.
* Click Download to distribute the updated recipe database to the SIMATIC BATCH Server.

Verification

In BATCH Configuration, verify that the status window reports Generation completed successfully with zero errors.
Launch Batch Control Center (BCC).
Confirm that the process cell appears in the left navigation pane displaying the updated name, and that all associated units, equipment phases, and master recipes are fully populated.
Verify communication with S7-PLCSIM or physical AS controllers by observing online status indicators on unit blocks.

Limitations and Operational Precautions

Never rename plant hierarchy folders while active production batches are executing in Batch Control Center. Always wait until batches reach the "Completed" or "Terminated" state.
Modifying process cell names invalidates existing archived batch records if database associations are severed. Perform a full BATCH backup prior to restructuring plant hierarchies.
When simulating with S7-PLCSIM, ensure that the BATCH PC communication channels (Named Connections) are correctly routed to the simulated CPU.

Engineer FAQ

Why can't I edit the cell name directly in BATCH Configuration?
SIMATIC BATCH enforces the Technological Hierarchy in SIMATIC Manager as the single source of truth. Cell names are read-only in BATCH Configuration and must be modified in SIMATIC Manager.
What is the difference between Propagate and Compile in SIMATIC BATCH?
"Propagate" synchronizes hierarchy metadata, block interfaces, and GUIDs across multiproject components. "Compile" generates the binary runtime databases and recipe interpreter files.
Does this error prevent downloading to S7-PLCSIM?
It does not prevent downloading CFC charts to S7-PLCSIM, but it completely blocks generating and starting recipes in SIMATIC BATCH.

Technical References

SIMATIC BATCH Operating Manual (A5E41356285-AA).
SIMATIC PCS 7 Engineering System - Configuring the Technological Hierarchy.
Siemens Industry Online Support Entry ID 109801081: SIMATIC BATCH Engineering and Troubleshooting Guide.