Reversing and Deleting Propagated Recipe Header Parameters in SIMATIC BATCH

In SIMATIC BATCH Recipe Editor, attempting to delete a Master Recipe Header parameter that was previously created by upward propagation from a Recipe Phase (RPH) will fail because the header parameter maintains active parent-child database references. The Recipe Header properties dialog intentionally omits a 'Delete' button for referenced parameters. To reverse and delete a propagated parameter (such as SP_Temp), you must traverse down to the originating Recipe Phase, open its parameter properties, break the reference by setting the Source/Destination link to 'None' (unlinked), repeat this disconnection in intermediate Recipe Operations (ROP) and Recipe Unit Procedures (RUP), and finally return to the Master Recipe Header to delete the now-unreferenced parameter.

Executive Summary

During recipe engineering in SIMATIC BATCH, engineers frequently propagate setpoints from lower-level equipment phases upward to the master recipe header to test automated parameter distribution. When operational requirements change or a parameter is mistakenly linked, reversing the operation becomes a common frustration: opening the Master Recipe Header properties reveals that the parameter has no 'Delete' button or right-click removal option. Even after deleting the parameter in intermediate recipe operations, the header retains the variable. This technical guide explains the relational data binding model in SIMATIC BATCH and provides the precise step-by-step sequence required to unlink and delete propagated parameters.

Architecture and Fundamental Mechanics

The relational database integrity rules of SIMATIC BATCH govern recipe parameter dependencies:
1. The Propagation Reference Chain:
- When a parameter (e.g., SP_Temp) is propagated from a Recipe Phase (RPH) to the Recipe Header, SIMATIC BATCH establishes an unbroken relational binding chain:
RPH (Destination) <--- ROP (Intermediate) <--- RUP (Intermediate) <--- Header (Source)
- The parameter in the Header exists as a dependent master entity. The database schema enforces referential integrity: a master entity cannot be deleted while any child entity references it.
2. Why Deleting in ROP/RUP Fails:
- Deleting a parameter in an intermediate Recipe Operation (ROP) or Recipe Unit Procedure (RUP) often fails to break the underlying database link if the lowermost Recipe Phase (RPH) still marks the parameter as a 'Destination' seeking that header variable.
- SIMATIC BATCH retains the header record to prevent orphaned destination references that would cause recipe compilation crashes.
3. The Bottom-Up Disconnection Rule:
- To remove a propagated parameter cleanly, the dependency chain must be deconstructed from the bottom up:
a. First, sever the reference at the physical consumer (RPH).
b. Second, clear the intermediate conduits (ROP and RUP).
c. Third, delete the isolated parameter from the top-level Master Recipe Header.

Step-by-Step Implementation Procedure

Open the Master Recipe in BATCH Recipe Editor:
a. Open Batch Control Center (BatchCC).
b. Navigate to Master Recipes and open the affected master recipe.
c. Expand the recipe diagram to view all Unit Procedures, Operations, and Phases.
Sever the Parameter Reference at the Originating Recipe Phase (RPH):
a. Double-click the Recipe Phase (RPH) where SP_Temp was originally linked.
b. Switch to the Parameters tab.
c. Select the setpoint parameter (e.g., SP_Temp).
d. Under the 'Reference' / 'Interconnection' section:
- If configured as 'Destination', click the Source dropdown and select None (or clear the linked parameter name).
- Change the reference type back to Local / Direct Input.
  e. Click Apply and OK.
Clear Parameter Interconnections in Recipe Operations (ROP):
a. Double-click the parent Recipe Operation (ROP) containing the phase.
b. Switch to the Parameters tab.
c. Select SP_Temp: confirm the reference is now marked unlinked or orphaned.
d. Click the Delete button to remove SP_Temp from the ROP level.
e. Click OK.
Clear Parameter Interconnections in Recipe Unit Procedures (RUP):
a. Double-click the parent Recipe Unit Procedure (RUP).
b. Switch to the Parameters tab.
c. Select SP_Temp and click Delete.
d. Click OK.
Delete the Parameter from the Master Recipe Header:
a. In the Recipe Editor main menu, select Recipe -> Properties.
b. Navigate to the Parameters tab.
c. Select the target parameter SP_Temp.
d. Verify that the Delete button is now enabled (no longer grayed out).
e. Click Delete and confirm removal.
f. Click Apply and OK.
Validate and Save the Recipe:
a. Select Recipe -> Check Recipe Consistency.
b. Confirm that the consistency check returns 0 Errors and 0 Warnings.
c. Save the recipe.

Verification

In Recipe Editor, open Recipe -> Properties -> Parameters: verify that SP_Temp no longer appears in the header parameter list.
Open the originating Recipe Phase: verify that its setpoint now accepts local numeric entry without reference indicators.
Execute Recipe -> Release for Production: confirm the recipe releases cleanly without orphaned parameter warnings.

Limitations and Operational Precautions

If the same header parameter is referenced by multiple distinct Recipe Phases across different operations, ALL child references must be disconnected before the header parameter can be deleted.

Engineer FAQ

Why is the 'Delete' button grayed out for header parameters in SIMATIC BATCH?

Because the parameter is actively referenced by one or more lower-level Recipe Phases or Operations; referential integrity prevents deleting active sources.

What order must be followed to delete a propagated recipe parameter?

Always follow a bottom-up order: disconnect the Recipe Phase first, delete intermediate ROP/RUP references next, and delete the header parameter last.