FPSADMIN.EQP_EVENT_ERROR_HIST

INST

DATE

N

Time when the event occurred. (* from FPSINPUT.WIP_EVENT_HIST)

FACILITY

VARCHAR2(6)

N

Facility is included in almost every join in the DWH so this represents a definitive split. A route must have all steps on tools in the same facility. A tool must process all lots in the same facility. If your site has multiple buildings where lots run on routes using tools in multiple buildings then everything should be one facility. For example, multiple Fab buildings. But if your site has independent facilities like Fab and Test and Assembly where lot may progress from one to the next but on different routes then these should be different facilities. Since this column is in virtually every table it is critical that the value here is exactly matches what is in the MES if the MES has facility. Use facility_display for the display friendly name displayed in applications. See site_name comment for client/site/facility example. (* from FPSINPUT.GEN_FACILITIES)

LOGGED_ENTITY

VARCHAR2(36)

N

Entity to which event is logged in the MES. This could be a main tool, subtool, entity, or port. In MNT tables this could be a vehicle or durable as well which is why the column width is wider. If main tool or port, we apply the event to all entities. If subtool we apply to all within the subtool. If entity we apply only to the entity. (* from FPSINPUT.EQP_EVENT_HIST)

LE_SEQ_WITHIN_SEC

NUMBER(2)

N

For rows with identical timestamps, sequence records to get proper sequence for logged entity. (* from FPSINPUT.EQP_EVENT_HIST)

CURR_SETUP

VARCHAR2(100)

The current setup of the entity. This can be set by a lot processing event from WIP_EVENT_HIST or by an event on the entity from EQP_EVENT_HIST. For example if an Implant tool processes a Boron lot then the curr_setup will be Boron. Or if an event is logged to the tool that says the setup changed to Boron then the curr_setup will be Boron. Please note that the curr_setup value populated in EQP_EVENT_HIST must match exactly with the rqd_setup value in RTG_TOOL_ASSIGNMENTS in order for the setup penalty logic to apply correctly. (* from FPSINPUT.EQP_EVENT_HIST)

DOWN_REASON

VARCHAR2(36)

A value from a reasonably short list of user-defined reasons why the entity went down. (* from FPSINPUT.EQP_EVENT_HIST)

EQP_INC_BATCH_PCT

NUMBER(3,1)

If the input data already knows the incomplete batch percent then we can input it in this value with the event and we will use it for eqp_state calculations. Normally this is blank and we calculate etp_inc_batch_pct from the lot events. (* from FPSINPUT.EQP_EVENT_HIST)

EQP_STATE

VARCHAR2(48)

Client equipment state taken directly from their MES or from their existing tool state model. For EQP_MNT_FUTURE, this is the state that we estimate the entity will be in during the maintenance which is often set to a generic PM state if we do not have detailed information. (* from FPSINPUT.EQP_L6_DETAILED_STATES)

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. (* from FPSINPUT.WIP_EVENTS)

EVENT_COMMENT

VARCHAR2(512)

Comment associated with the event. (* from FPSINPUT.WIP_HOLD_FUTURE)

INSERTED_TIME

TIMESTAMP(6)

N

Timestamp field set by trigger storing SYSTIMESTAMP when record was inserted in the table. (* from FPSINPUT.WIP_EVENT_HIST)

OPERATOR

VARCHAR2(64)

In history tables, this is the username of the person or system who logged the event. In EQP_MNT_FUTURE, this is the username of the person who input the information about the maintenance event. Usernames can be looked up in GEN_USERS to get full names, email address, etc. Please note that the existence of each username in GEN_USERS is optional, meaning that it is never required for the username logged in the operator column to be in GEN_USERS. (* from FPSINPUT.WIP_EVENT_HIST)

OPT_SORT_WITHIN_SEC

NUMBER(21,6)

This number is the order of the event within the same second for the same lot (WEH) or wafer (WWH) or entity (EEH). If the event is logged with a sequence number then this value should be that sequence number (and it is fine if this is an overall sequence number even though it only matters compared to other events in the same second). Otherwise if the event time includes milliseconds then this can be the milliseconds. Otherwise just choose the best sort order. This value does not need to be 1, 2, 3, etc. (* from FPSINPUT.WIP_EVENT_HIST)

REPAIR_REASON

VARCHAR2(36)

These are the values that can be found in EQP_EVENT_HIST REPAIR_REASON. A value from a reasonably short list of user-defined explanations of how the entity will be repaired or what caused it to go down. (* from FPSINPUT.EQP_REPAIR_REASONS)