FPSADMIN.WIP_WAFER_EVENTS_CURR_STEP

INST

DATE

N

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

LOT

VARCHAR2(32)

N

A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* from FPSINPUT.WIP_LOTS_STATIC)

WAFER

VARCHAR2(32)

N

Field that uniquely identifies a wafer. (* from FPSINPUT.WIP_WAFER_HIST)

LOT_SEQ_WITHIN_SEC

NUMBER(6,2)

N

For rows with identical timestamps, sequence records to get proper sequence (* from FPSINPUT.WIP_EVENT_HIST)

ACTUAL_DURABLE_USED

VARCHAR2(129)

Actual durable used as logged by the tool during processing of the lot. This can be a comma delimited string if multiple durables are used. (* from FPSINPUT.WIP_EVENT_HIST)

ACTUAL_MACHINE_RECIPE

VARCHAR2(100)

Machine recipe used to process the lot as logged during processing by the tool. (* from FPSINPUT.WIP_EVENT_HIST)

EVENT

VARCHAR2(48)

N

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)

EVENT_INST1

DATE

User-defined field which can store any instant relevant to the event. Description of use should be noted in WIP_EVENTS table. (* from FPSINPUT.WIP_EVENT_HIST)

EVENT_INST2

DATE

User-defined field which can store any instant relevant to the event. Description of use should be noted in WIP_EVENTS table. (* from FPSINPUT.WIP_EVENT_HIST)

EVENT_INST3

DATE

User-defined field which can store any instant relevant to the event. Description of use should be noted in WIP_EVENTS table. (* from FPSINPUT.WIP_EVENT_HIST)

EVENT_PARM1

VARCHAR2(128)

User-defined parameter which can store any value relevant to the event. Description of use should be noted in WIP_EVENTS table. (* from FPSINPUT.WIP_EVENT_HIST)

EVENT_PARM2

VARCHAR2(128)

User-defined parameter which can store any value relevant to the event. Description of use should be noted in WIP_EVENTS table. (* from FPSINPUT.WIP_EVENT_HIST)

EVENT_PARM3

VARCHAR2(128)

User-defined parameter which can store any value relevant to the event. Description of use should be noted in WIP_EVENTS table. (* from FPSINPUT.WIP_EVENT_HIST)

EVENT_TYPE

VARCHAR2(12)

Event Type (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL)

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)

IS_CURR_EVENT

CHAR(1)

LOGGED_ENTITY

VARCHAR2(36)

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)

OPERATOR

VARCHAR2(64)

N

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)