SetAllLot
The
SETALLLOT
execute sets the same lot name on all material phase steps within a recipe. In material addition phases, the lot name helps identify specific material sublots for use. In material distribution phases, the lot name is applied to the material lot distributed.The
SETALLLOT
execute applies only to material-enabled phases. The execute results in no changes with non-material phases.The format and return for this execute includes:
Execute Format | A FactoryTalk Batch Server supports an execute with this format:[SETALLLOT( Item,UserID,ProcedureID,LotString )] | ||
where: | Item | Item name as specified by the client. | |
UserID | User Identification entered into the event journal associated with this event. | ||
ProcedureID | Unique hierarchical path name to the procedure, unit procedure, operation or phase:
| ||
LotString | Lot name to be assigned. | ||
where: | <FullPath> | is | <CreateID> | <CreateID> /t <Path> |
<Path> | is | <StepIdentifier> | <StepIdentifier> /t <Path> | |
where: | |||
Field | Format | Description | |
<CreateID> | ASCII - Integer | Unique batch ID assigned by the FactoryTalk Batch Server. | |
<StepIdentifier> | ASCII – String | Step identifier (for example, Mix:1) | |
Action | A successful SETALLLOT execute changes the lot name values in the specified step(s). | ||
Return Format | The item populates with this data: SUCCESS: | SUCCESS: <ActionID> | FAIL: <message> | ||
where: | |||
Field | Format | Description | |
<ActionID> | ASCII – Integer | Action identifier associated with signature(s) generated as a result of the potential parameter value change. The parameter value will not actually change unless all signatures are successfully signed. | |
<message> | ASCII - String | Error message appropriately formatted for operator display. | |
The following table shows an example of the return on this execute.
Example: | An execute string consisting of: SETALLLOT(Item,Station2/View, 99, 53) Could return: SUCCESS:997 |
Provide Feedback