data-dictionary

FPSINPUT.DASH_P_FACILITIES

Data Dictionary

>

FPSINPUT Views

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSAPP.DASH_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)

HIDE_FACILITY_ON_WEB

Hide a facility from our applications. Default is N, but setting to Y hides on Dashboard and other applications will not reference hidden facility (* inherited from FPSINPUT.GEN_FACILITIES)

QTY_UNIT

Defines the unit used to measure number of quantity. The key here is that this quantity must be known throughout the entire route through the facility. For example in a sort facility where lots enter in wafers and are broken into die but the number of wafers is still known when the lot completes the facility then the qty_unit must be wafer. It cannot be die because die is not known when the lot enters so die will be the sec_qty_unit. Similarly at a final test facility where the lots enter with both wafers and die known but only die are known when the lot completes the facility then the qty_unit must be die. It cannot be wafer because wafer is not known when the lot completes so wafer will be the sec_qty_unit. Please note the entire process from only wafers to only die must be split into at least two facilities because of this requirement. (* inherited from FPSINPUT.GEN_FACILITIES)

QTY_UNIT_PLURAL

Plural form of the quantity unit. For example if qty_unit is defined as wafer then the plural form would be wafers. (* inherited from FPSINPUT.GEN_FACILITIES)

QTY_UNIT_SHORT

Short display of the quantity unit. For example if qty_unit defined is wafer then this could be wfr. (* inherited from FPSINPUT.GEN_FACILITIES)

SEC_QTY_UNIT

Secondary quantity unit. See QTY_UNIT comment for details. (* inherited from FPSINPUT.GEN_FACILITIES)

SEC_QTY_UNIT_PLURAL

Plural form of the secondary quantity unit. For example if sec_qty_unit is defined as wafer then the plural form would be wafers. (* inherited from FPSINPUT.GEN_FACILITIES)

SEC_QTY_UNIT_SHORT

Short display of the secondary quantity unit. For example if sec_qty_unit defined is wafer then this could be wfr. (* inherited from FPSINPUT.GEN_FACILITIES)

HTML_BG_COLOR

HTML_TEXT_COLOR

AVG_QTY_PER_CARR_FOR_UPH

Throughput calculations like EET, MPU, and UPH all include wafer_interval_sec which must be multiplied by wafer qty. When calculating for a specific lot, we can use its qty but when calculating generically we use this value which should be set close to the average lot size for the facility. This value can be overridden for an eqp type with exp_qty_per_job. (* inherited from FPSINPUT.GEN_FACILITIES)

TURNS_TGT_FROM_COMP_WIP_GOALS

This flag indicates to use the automatic Dashboard calculations or use the existing target entries from the dash_w_targets_xx tables (* inherited from FPSINPUT.GEN_FACILITIES)

SHIP_BEFORE_DAYS

Limits the week for due date calculation by x days. For example if the week ends on Sunday and this is specified to 2, we calculate due dates for Monday to Friday. Used in WIP_REF_FLUSH_BASE. (* inherited from FPSINPUT.GEN_FACILITIES)