FPSBASE.WIP_LOT_GROUPS

LOT_GROUP

VARCHAR2(8)

N

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.

BG_COLOR

VARCHAR2(24)

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

CTM_FACTOR

NUMBER(3,2)

N

Factor to multiply cycle time for this lot group compared to other groups if not known. For example, if this factor is 1.5 and we know the CTM is 6 hours for another lot group whose factor is 1.0 then we would estimate it to be 9 hours for this lot group.

DESCRIPTION

VARCHAR2(256)

Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS)

IGNORE_PROC_LONGER

CHAR(1)

This flag tells ETP that we should never set state to Missed Cascade when processing a lot of this lot group because the throughput estimates are unreliable. This must always be N for production lot groups.

IS_DEFAULT_UNCHECK_ON_DASH

CHAR(1)

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.

IS_DEFAULT_UNCHECK_ON_DCTA

CHAR(1)

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.

IS_DEFAULT_UNCHECK_ON_FLCT

CHAR(1)

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.

IS_DEFAULT_UNCHECK_ON_PERF

CHAR(1)

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.

IS_DEFAULT_UNCHECK_ON_WF

CHAR(1)

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.

IS_INCLUDED_WIP_FLUSH

CHAR(1)

If yes, then multi-facility WIP flush should include this LOT_GROUP when calculating weighted-average cycle time for future routes.

IS_OPER_MOVE_IF_REWORK_END

CHAR(1)

So far the decision to count the move which ends the rework and returns the lot back to normal production is only by facility but we have it by lot group to be consistent with the decision for rework moves.

IS_OPER_MOVE_IF_REWORK_MOVE

CHAR(1)

This is usually set to Y for Development so that we count an oper move even if reworked. This flag does not affect moves which start rework, even though those are strictly speaking a subset; the separate IS_OPER_MOVE_IF_REWORK_START flag covers those.

IS_OPER_MOVE_IF_REWORK_START

CHAR(1)

See comments on IS_OPER_MOVE_IF_REWORK_MOVE.

IS_SCHED

CHAR(1)

This flag indicates that lots in this group should be scheduled. This flag additionally causes TW groups to be included in WIP_STEP_FUTURE which they are normally not.

IS_TW

CHAR(1)

N

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.

IS_USED_FOR_GOALS

CHAR(1)

If yes, lot group will be included in goal calculations. Filter is applied in FPSBASE.WIP_REF_GOAL_EST_SHIFT view: IS_USED_FOR_GOALS = Y.

LOT_GROUP_DISPLAY

VARCHAR2(24)

N

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.

OVR_CTM_VALID_LOTS_2D

NUMBER(4)

This column allows users to specify the minimum lot count for cycle time to be considered valid for the 2 day period and not apply fill in logic on the lot group level. If this is null then the gen_facilities ctm_valid_lots_2d will be used

OVR_CTM_VALID_LOTS_7D

NUMBER(4)

This column allows users to specify the minimum lot count for cycle time to be considered valid for the 7 day period and not apply fill in logic on the lot group level. If this is null then the gen_facilities ctm_valid_lots_7d will be used

OVR_CTM_VALID_LOTS_FULL

NUMBER(4)

This column allows users to specify the minimum lot count for cycle time to be considered valid for the full period and not apply fill in logic on the lot group level. If this is null then the gen_facilities ctm_valid_lots_full will be used

OVR_CTM_VALID_LOTS_LONG

NUMBER(4)

This column allows users to specify the minimum lot count for cycle time to be considered valid for the long period and not apply fill in logic on the lot group level. If this is null then the gen_facilities ctm_valid_lots_long will be used