Repair a Deleted SFC Setpoint Reference After a PCS 7 Batch Migration
In the reported PCS 7 V7.1-to-V9.1 SP1 migration, SIMATIC BATCH marked an SFC setpoint as deleted during Update Process Cell because the source project contained a corrupted parameter link. The reported repair was to introduce a replacement SFC variable, compile/load and update Batch so it appeared as a new parameter, relink the existing Batch reference, and then remove the broken variable through staged rename and compile/load steps. Treat this as a case-specific recovery, not a general migration rule.
Table of Contents
- Preserve project and recipe backups
- Create and register a replacement parameter
- Relink Batch and remove the broken parameter
- Why intermediate compile/load matters
- Verification
- Limitations and Operational Precautions
- Technical References
- Related Articles
- Related Tags
- Engineer FAQ
Preserve project and recipe backups
Back up the migrated PCS 7 project and SIMATIC BATCH recipe/process-cell data before changing SFC parameters or applying Update Process Cell. The reported case used matched project and recipe backups, but migration still exposed a corrupted link.
Create and register a replacement parameter
In the affected SFC, create a new setpoint variable to replace the missing one. Rename the broken parameter so the replacement can be distinguished. Compile and load the AS changes, then update the Batch process cell. The author reports that this made the new parameter appear under the phase type.
Relink Batch and remove the broken parameter
Link the new SFC parameter to the existing unlinked Batch parameter. Then delete the old SFC parameter and replace its references in the SFC with the new one. Compile and load, update the Batch process cell, and confirm that the new parameter remains mapped. Finally, restore the intended parameter name only after confirming the replacement is recognized.
Why intermediate compile/load matters
The source author states that compiling and loading between steps was important for PCS 7 and Batch to recognize the replacement as a new parameter. This is an observed repair in the specific project; follow the migration and Batch engineering procedure for the installed release.
Verification
After each stage, inspect compile/load results and Batch process-cell update output. Confirm the parameter appears under the correct phase, the existing Batch reference is linked, and recipes validate against the resulting phase interface.
Limitations and Operational Precautions
The reported project used PCS 7 V9.1 SP1, SIMATIC BATCH V9.1 SP1, and SFC V9.0 SP6 after migration from V7.1. The forum reply suggested a staged upgrade path; the author later said Siemens accepted direct migration for that project's limited feature set but reported other issues. Do not generalize that exception. A corrupted link was identified only in the specific source case.
Technical References
- Siemens, SFC for SIMATIC S7 V9.0 SP1 Programming and Operating Manual, SFC type interface and setpoint parameters: https://support.industry.siemens.com/cs/attachments/109755020/s7sfcs7b_en-US.pdf
- Siemens, SIMATIC BATCH V9.0 Getting Started, compile/load and Batch type update workflow: https://cache.industry.siemens.com/dl/files/909/109781909/att_1032032/v1/sb_gs1_b_en-US.pdf
Related Articles
Related Tags
Engineer FAQ
Why can Update Process Cell delete an SFC parameter? The reported migrated project had a corrupted parameter link; updating the Batch process cell then exposed the parameter as deleted.
What repair resolved the reported case? The author reports creating a replacement parameter, renaming the old parameter, compiling/loading, updating Batch, relinking the old Batch reference, then removing and replacing the old variable.
Why compile and load between rename steps? In the reported repair, intermediate compile/load steps allowed PCS 7 and Batch to recognize the replacement as a new parameter.
Does this repair apply to all deleted parameters? No. It is a source-reported correction for one migrated project with a corrupted link, not a general repair for every Batch migration.
What versions were reported? PCS 7 V9.1 SP1, SIMATIC BATCH V9.1 SP1, SFC V9.0 SP6, migrated from PCS 7 V7.1.
Does direct V7.1-to-V9.1 migration work? The ticket author says Siemens accepted a direct migration for their limited feature set but also experienced other problems; follow the official staged upgrade path unless Siemens confirms an exception.
What does Update Process Cell do in this workflow? It reconciles Batch process-cell objects with current engineering configuration; inspect its proposed changes and deleted-object list before applying.
Should recipes be backed up first? Yes. The case involved recipes restored from backup; preserve project and recipe backups before migration or process-cell updates.
How do I confirm the parameter is repaired? Confirm the replacement appears under the correct phase type, map the existing Batch parameter, compile/load and update again after restoring the intended name.
What if the replacement still does not appear? Stop and review SFC type links, Batch phase-type mapping, compile results, migration sequence, and logs; the reported workaround does not establish another cause.