FPSINPUT.WIP_EVENTS

EVENT

VARCHAR2(48)

This is the event registered in the MES. This is for the historical record and display only. Each event is mapped to an FPS event_type and the event_type is what is used by FPS applications.

COUNT_AS_COMP_IF_PROCESSED

CHAR(1)

By default we count a move of any event as a COMP if the lot processed on a tool during the step so the default value of this field is Y. But some facilities prefer to only count certain events so setting this to N means that a move of this event is never counted as COMP.

EVENT_SOURCE

VARCHAR2(36)

The source where the event happened for the lot. For example MES, EI, Dispatching, etc.

EVENT_TYPE

VARCHAR2(12)

Event Type (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL)

HIDE_EVENT_IN_DASH_HIST

CHAR(1)

Occasionally we have certain events which are logged frequently in the MES but are unimportant. We do not want to show these events in the Dashboard lot event history table as they clutter up the list. Set this column to Y to hide an event from this list.

IS_REPEAT_IF_SET_BY_EVENT

CHAR(1)

This column is only relevant if GEN_SITE.SET_REPEAT_BY_EVENT is set to Y. If so, then any move for this event is counted as a repeat and effectively not counted as a move. Typically the MES event name does not indicate repeat so we will have to add a Repeat suffix onto the event name in our ETL if the move is recorded as a repeat in the MES.

IS_WARN_WHEN_LOGGED_AFTER_COMP

CHAR(1)

We normally log an error in WIP_EVENT_HIST if an event is logged for a lot before its current step_ent_inst. This means that the events were logged out of order. Specifically it means COMP event was logged to WIP_EVENT_HIST and then another event with an inst before the inst of the COMP event was logged subsequently. For certain events, usually END events logged by a separate automation system outside of the MES, this behavior is acceptable and we can just ignore this and this flag allows us to configure this by event.

MES_EVENT_NUMBER

NUMBER(3)

This optional field is used to simplify the ETL for MES such as PROMIS where the event is stored as a number.

MVIN_MULTIPLIER

NUMBER(1)

This is specifically for our movein counting logic. Moveins are counted similar to completes so we can also have the (mvins + completes) / 2 logic, however, a complete always changes the step while a movein never changes the step. So the most flexible way to count moveins is to set this to 1 for the event(s) that each site wishes to count as a movein and to set this to -1 for the event(s) to subtract from the count. Typically BEGIN_M and/or DISP events will be 1 and ABORT and/or CANCEL events will be -1.