oper_step_grp
- Last UpdatedNov 20, 2024
- 2 minute read
The oper_step_grp able provides the ability to define any number of step groups per process operation. Every step must be assigned to one step group.
The step_grp_seq field specifies the sequence in which the step groups must be performed relative to other step groups, the same sequence number meaning that those step groups may be performed concurrently.
Together the step_seq and step_grp_seq fields allow any combination of serialized or concurrent steps to be defined for each operation.
The ‘repeatability’ field is used to specify the repeatability of all steps in this group. This field is set = 0 for setup and teardown steps that are only performed once during the execution of the job, = 1 if the steps should be repeated for each lot that is produced. Future settings could be used to specify steps that need to be performed at shift start only etc.
|
Field |
Datatype |
PK |
Nulls? |
Description |
|---|---|---|---|---|
|
process_id |
string40 |
Y |
N |
Identify process |
|
oper_id |
string40 |
Y |
N |
Identify operation |
|
step_grp_id |
int32 |
Y |
N |
Identify step group |
|
step_grp_desc |
string80 |
N |
N |
Description for this step group |
|
step_grp_seq |
int32 |
N |
N |
Sequence to perform step groups. Same seq means groups can be done concurrently. |
|
repeatability |
int32 |
N |
N |
Enumeration of ways in which steps in this group are to be repeated: 0 = only performed once during the execution of the job, as for setup and teardown steps 1 = steps should be repeated for each lot that is produced (default) |
|
last_edit_comment |
string254 |
N |
Y |
Reserved for internal use to indicate why this record was changed |
|
last_edit_by |
string40 |
N |
Y |
Who last changed this record |
|
last_edit_at |
tdatetime |
N |
N |
When this record was last changed |
|
row_id |
ID 1 |
N |
N |
Unique row identifier, for audit trail |
FK from process_id, oper_id to oper. (Cascade delete)