|
IADD |
|
|
IADX |
|
|
IAUN |
|
|
IAUX |
|
|
IDEL |
|
|
IDRF |
|
|
IINS (Destination) |
|
|
IINS (Via API) |
|
|
IMOD |
|
|
IMRA |
|
|
IMRM |
|
|
IMVN |
|
|
IMVX |
|
|
ISCR |
|
|
ISTP |
|
|
ISTT |
When item is added via API (or user interface). If item is not production start and is added (not inserted).
region_1_id and region_1_loc contain the location of the event
When item is being deleted in source region due to being advanced via API (or user interface).
region_1_id and region_1_loc contain the location of item being deleted.
When item is being added to destination region due to a point transition.
region_1_id and region_1_loc contain the destination of the added item.
When serialized item is added to region and XREF table indicates that the item was already somewhere within the view of that service, the item already there is deleted.
region_1_id and region_1_loc contain the location of the item being deleted
When item is being deleted in source region due to a point transition.
region_1_id and region_1_loc contain the location of the item being deleted.
When item deleted via API (or user interface) and item is being deleted (not scrapped and not production-stopped).
region_1_id and region_1_loc contain the location of the item being deleted.
This item has been deleted because room was needed in the region.
region_1_id and region_1_loc contain the location of the item being deleted.
IINS (Destination Due)
When item is being added to destination region due to being advanced via API (or user interface).
region_1_id and region_1_loc contain the destination of added item.
IINS (Via API)
When item is added via API (or user interface). If item is not production start and is inserted (not added).
region_1_id and region_1_loc contain the location of the event.
Automatic item association when adding an item:
PARENT_ITEM_BIT set in modify_bitmask
region_1_id contains the region id where the modify occurred
When modifying item:
modify_bitmask passed from API call
region_1_id contains the region id where the modify occurred
When item moves and transition_type_indicator is ASSOCIATE_REF_TO_ITEM or ASSOCIATE_TYPE_TO_ITEM:
modify_bitmask set to REFERENCE_ID_MOD_BIT or ITEM_TYPE_BIT respectively
region_1_id and region_1_loc contain the destination location.
When a combine or disperse region has a serialized item in it and another serialized item is moved into the region, the item is automatically moved to a detainment region and two messages generated, one for the item being deleted and one for the item being added.
region_1_id and region_1_loc contain the region from which the item is being deleted
region_1_id and region_1_loc contain the destination of detainment region to which the item is being added
When an item becomes delayed and the region is configured to detain (rather than scrap) delayed items, two messages are generated for the item being detained, one for the item being deleted from the combine/disperse region and one for the item being added to the detainment region.
region_1_id and region_1_loc contain the location of item being deleted
region_1_id and region_1_loc contain the destination of detainment region to which the item is being added.
When an item is moved via an API call (or user interface) to its detainment region, two messages are generated, one for the item being deleted from the source region and one for the item being added to the detainment region.
region_1_id and region_1_loc contain the location of the item being deleted
region_1_id and region_1_loc contain the destination of detainment region to which the item is being added.
When item is being added to destination region due to being moved via API (or user interface).
region_1_id and region_1_loc contain the destination of the added item.
When item is being deleted in source region due to being moved via API (or user interface).
region_1_id and region_1_loc contain the location of the item being deleted.
When item deleted via API (or user interface) and item is being scrapped (not deleted and not production-stopped).
region_1_id and region_1_loc contain the location of the scrapped item
When an item becomes delayed and the region is configured to scrap (rather than detain) delayed items, a message is generated for the item being scrapped.
region_1_id and region_1_loc contain the location of the scrapped item.
Production stop generated via API call.
region_1_id and region_1_loc contain the location of the item being stopped.
When adding item via API and prod_start_flag is set:
region_1_id and region_1_loc contain the location of the event
When moving and SRC region is NULL:
region_1_id and region_1_loc contain the destination location.
|
|
Event codes. |
