data-dictionary

FPSADMIN.SCH_P_FACILITIES

Data Dictionary

>

FPSADMIN Views

> FPSADMIN.WIP_WAFER_HIST_LOOP

View FPSAPP.SCH_P_FACILITIES

Basic info on facilities.

Column

Comment

FACILITY

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

FACILITY_DISPLAY

The name of the facility displayed on all dashboards and reports. Facility is a short field since it is used in every join so we allow a longer more descriptive name here although often this will be the same as the facility. (* inherited from FPSINPUT.GEN_FACILITIES)

SORT_ORDER

This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* inherited from FPSINPUT.GEN_FACILITIES)

LOT_MIN_TRANSIT_SEC

LOT_MAX_TRANSIT_SEC

DURABLE_MIN_TRANSIT_SEC

DURABLE_MAX_TRANSIT_SEC

MIN_KIT_SEC

Minimum kit time for pod kitting (* inherited from FPSAPP.SCH_C_FACILITIES)

AVG_KIT_SEC

average kit time for pod kitting (* inherited from FPSAPP.SCH_C_FACILITIES)

DURABLE_LOAD_SEC

SCHED_GROUP_PHOTO_NAME

LABEL_LOT_RANK

is used to define the label of lot rank. it can be critical ratio or anything (* inherited from FPSAPP.SCH_C_FACILITIES)

LABEL_DURABLE

is used to define the label of durable. in most of cases it will be Reticle (* inherited from FPSAPP.SCH_C_FACILITIES)

LABEL_DURABLE_CARRIER

is used to define the label of durable carrier. in most of cases it will be Pod (* inherited from FPSAPP.SCH_C_FACILITIES)

DEFAULT_FEEDBACK_EMAIL

MAX_QTY_PER_CARR

Maximum number of wafers in a carrier - also known as maximum lot size - which is typically 25 for a wafer fab. (* inherited from FPSINPUT.GEN_FACILITIES)