You can use this function to define conditions that automatically trigger the execution of functions such as Deactivate process instruction or Lock process step in the context menu.
Example
You want to specify, for example, that the quantity recording for a certain material depends on the current pH value of the mixture in the vessel. This means that the material quantity may not be recorded until the process operator has measured a pH value of less than seven (< 7).
Using this function, you define this condition in the process order or master recipe. When the PI sheet is opened, the input field for material quantity recording would first be locked. The lock for the input field for material quantities would only be removed after a pH value of less than seven was entered in the preceding input field. The material quantity field would become ready for input.
OPC Events
To use events of the service OAE (OPC Alarms/Events), you must first have created a subscription in Customizing.
To do so, go to Customizing for Process Management and choose SAP ODA (OPC Data Access).
For more information about SAP ODA, see SAP OPC Data Access .
You can define conditions to automatically execute the following functions:
- Save document- Document report data
- Activate process step- Deactivate process step- Lock process step- Unlock process step- Complete process step
- Activate process instruction- Deactivate process instruction- Lock process instruction- Unlock process instruction- Complete process instruction
- Activate table- Deactivate table- Lock table- Unlock table- Complete table
- Add table line- Activate table line- Deactivate table line- Lock table line- Unlock table line- Complete table line
You can define conditions for the automatic execution of functions as follows:
In a Formula
In the calculation formula, you specify when this command should be executed.Refer to Syntax of Calculation Formulas
In a Function Module
You enter a function module, in which the conditions for triggering the command are stored. You assign values to the parameters of the function module.
See also: XStep: Function Module Parameters
As a Manufacturing Event (PPPI_EVENT)
You specify an event, which the PI sheet is to subscribe to.
For more information on events, see:
You create an XStep process instruction of type Control Data -> Command.
In the process instruction on the Command tab page, you specify the following:
The command that is automatically executed, displayed or hidden once the conditions have been met.
An action, which specifies whether the command should be executed, displayed or hidden once the conditions have been met.
On the Trigger tab page, you specify a trigger type.
Enter a calculation formula for trigger type Formula
Specify a function module for trigger type Function
Specify a manufacturing event for trigger type Event
The following example shows, how it is possible to define the example described above:
You create a standard XStep in the SXS repository.
You create an XStep for the XStep tree.
You create the following XStep parameters for the XStep:
( )
You assign values to the XStep in the following way:
( )
Assign a Control Recipe Destination to the XStep .
You create a process instruction.
You create an XStep process instruction of type Input -> Parameter Value for parameter P1 for the XStep node ( ) .
You create additional process instructions.
You create the following XStep process instructions for this XStep node ( ) :
Enter parameter value for parameter P2
Control Command
Command: Process instruction locked
Action: Execute
Trigger: Formula
Formula: P2>7
Control Command
Command: Remove process instruction lock
Action: Execute
Trigger: Formula
Formula: P2<7
Your standard XStep should now have the following structure:
( )
You check and simulate the XSteps.
You release the SXS version.