FPSBASE.DASH_P_LOT_GROUPS

LOT_GROUP

Lot_group is a grouping of lot_family and is the highest grouping in the lot type hierarchy. There should be only a few values for lot_group, i.e. Prod, Dev, TW. We group WIP and moves by lot_group on the dashboard and we group cycle time calculations by lot_group so this is an important field. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

LOT_GROUP_DISPLAY

The name of the lot_group displayed on all dashboards and reports. We allow a longer more descriptive name here although often this will be the same as the lot_group. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_INCLUDED_WIP_FLUSH

If yes, then multi-facility WIP flush should include this LOT_GROUP when calculating weighted-average cycle time for future routes. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_TW

Our standard filter to exclude test wafers is is_tw = N but what we really mean with this filter is to exclude any lots that do not add value for the facility. Lots which add value including sellable, development, and engineering and these lot groups should have is_tw set to N. Lots which do not add value are commonly grouped together and named "test wafers" which is why this flag is named is_tw. These include true test wafers like monitors and quals and dummies but also could include virtual lots used for training or testing, bare wafers, or really anything else including in the MES as a lot which does not add value. All of these lot groups should have is_tw set to Y. You could argue that the is_tw field might be more accurately named is_value or is_valuable or is_prod_eng_dev but is_tw is generally clear to most people. Plus it has the advantage that it is short which is nice given how frequently we use the is_tw = N filter. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

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)

IS_DEFAULT_UNCHECK_ON_DASH

Flag used for lot group, wafer size, and line section that indicates whether this value should be unchecked by default on the Dashboard. All TW must be unchecked. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_DEFAULT_UNCHECK_ON_DCTA

Flag used for lot group, wafer size, and line section that indicates whether this value should be unchecked by default on Dynamic Cycle Time Analyzer. All TW must be unchecked. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_DEFAULT_UNCHECK_ON_FLCT

Flag used for lot group and wafer size that indicates whether this value should be unchecked by default on Finished Lot Cycle Time. Please note that line section does not apply to FLCT. All TW must be unchecked. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_DEFAULT_UNCHECK_ON_PERF

Flag used for lot group, wafer size, and line section that indicates whether this value should be unchecked by default on Performance. All TW must be unchecked. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_DEFAULT_UNCHECK_ON_WF

Flag used for lot group, wafer size, and line section that indicates whether this value should be unchecked by default on WIP Flush. All TW must be unchecked. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

BG_COLOR

Background color assigned. BG_COLOR is in English like red or blue or light green and we look up the HTML color like #FF0000 in the GEN_COLORS table. BG_COLOR must be set manually but the FPSADMIN view BLD_POPULATE_COLORS will generate queries to randomly set bg_color for all values in a table. (* inherited from FPSINPUT.GEN_CUSTOMERS)

HTML_BG_COLOR

HTML_TEXT_COLOR

SHOULD_DISPLAY