You set up activity hooks at the site level in Site Maintenance
(see Setting Up Activity Hooks).
The following table describes the site level hook points:
Hook Point |
When a Hooked Activity Executes |
---|---|
|
After the system releases a shop order to the shop floor |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After a user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the user chooses |
|
After the system closes a shop order and the status of the shop order changes to |
|
After an SFC number is removed from a process lot in the |
|
After an SFC number is added to a process lot in the |
|
Resides in Allows an operator to scan a barcode that contains multiple data values for a component in assembly point
When you associate your custom hook point activity with the For the
Example Suppose you purchase a component with a bar-coded label indicating the part number. The part number contains a component name code followed by a vendor code. In that case, your custom activity could separate the two values embedded in the part number and pass the information back to End of the example. |
|
Resides in Allows an operator to scan a barcode that contains multiple data values for a slot
For the
|
The following figure shows the site level hook points that relate to serialization and split in the POD:
For more information about split and serialization, see SFC Split and Serialize.