Show TOC

Background documentationSite Level Hook Points

 

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

POST_ORDER_RELEASE

After the system releases a shop order to the shop floor

POST_PROD_CHANGE

After the user chooses Save in Change Production. Use with a custom hook point activity. The hook point passes old and new values for the material, routing, BOM and/or shop order to the activity.

PRE_MERGE

After the user chooses Merge in SFC Merge, before the system merges SFC numbers

POST_MERGE

After the user chooses Merge in SFC Merge, after the system merges SFC numbers

POST_SERIALIZE

After the user chooses OK in Serialize, after the SFC number is serialized

POST_SPLIT

After the user chooses OK in SFC Split, after the SFC number is split

PRE_RMA_SFC_RECEIPT

After the user chooses Done in RMA SFC Receipt, before the system adds the SFC numbers to the RMA shop order

PRE_SERIALIZE

After the user chooses OK in Serialize, before the SFC number is serialized

PRE_SPLIT

After the user chooses OK in SFC Split, before the SFC number is split

POST_RMA_SFC_RECEIPT

After a user chooses Done in RMA SFC Receipt, after the system adds the SFC numbers to the RMA shop order

POST_CONTAINER_SAVE

After the user chooses Save in Pack/Unpack

POST_CONTAINER_CLOSE

After the user chooses Done and Close in Pack/Unpack

PRE_PACKING_SFC

After the user chooses Add in Pack/Unpack, before the system adds the SFC number to the container

PACKING_VALIDATION

After the user chooses Add in Pack/Unpack, before the system adds the SFC number to the container

REOPEN_CONTAINER

After the user chooses Unpack in Pack/Unpack

CALC_DIMENSIONS

After the user chooses Close Container in Pack/Unpack

ADD_COMPONENT

After the user chooses Add on the Add Component screen of As-Built Configuration or Assembly Point

REMOVE_COMPONENT

After the user chooses Scrap, Return, or Send to Routing on the Remove Component screen of As-Built Configuration

POST_ORDER_CLOSE

After the system closes a shop order and the status of the shop order changes to Done

POST_PL_REMOVE

After an SFC number is removed from a process lot in the Process Lot (PR560) activity

POST_PL_ADD

After an SFC number is added to a process lot in the Process Lot activity (PR560)

PARSE_COMPONENT

Resides in Assembly Point (CT500), and relates to manual/discrete component traceability

Allows an operator to scan a barcode that contains multiple data values for a component in assembly point

PARSE_COMPONENT executes the hook point activity when Assembly Point (CT500) is in the CHOOSE mode and the operator scans a barcode in the Choose field.

When you associate your custom hook point activity with the PARSE_COMPONENT hook point, the hook point passes the entered value to your activity. Your activity then looks up the value associated with the entered value and returns a value that Assembly Point (CT500) can recognize.

For the PARSE_COMPONENT hook point, the custom activity you create needs to do the following:

  1. Read the value that Assembly Point passes to PARSE_COMPONENT

  2. Parse the value or perform a lookup so it can create a string that contains the component identifier, and other assembly data, in the required format

  3. Return that string to PARSE_COMPONENT

Example 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 Assembly Point's PARSE_COMPONENT. Assembly Point then takes the identifier the custom activity, passes back – in this case, the component name – finds the component in the BOM, and enters the information in Assemble Components. The activity replaces the value the operator entered initially with the component name passed back from the custom activity, and displays data fields associated to the component in the assembly data fields of Assemble Components.

End of the example.

PARSE_SLOT_COMPONENT

Resides in Resource Slot Config Setup (EN530) and Load or Replenish (EN531), and relates to time-based component traceability.

Allows an operator to scan a barcode that contains multiple data values for a slot

PARSE_SLOT_COMPONENT executes the hook point activity when Resource Slot Config Setup (EN530) or Load or Replenish (EN531) is in CHOOSE mode, and the operator enters a value in the Choose field.

For the PARSE_SLOT_COMPONENT hook point, the custom activity you create needs to do the following:

  1. Read the value that Resource Slot Config Setup or Load or Replenish passes to PARSE_SLOT_COMPONENT

  2. Parse the value or perform a lookup so it can create a string that contains the slot, component identifier, and other assembly data fields, in the required format

  3. Return that string to PARSE_SLOT_COMPONENT

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.