FPSBASE.CHK_OPER_MOVE_CFG

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)

USE_COUNT_AS_OPER_MOVE_FLAG

Normally we count an oper move when the lot moves from one operation to another (along with plenty of other configuration options). If we use this flag instead then we count any move from a step where count_as_oper_move is Y and ignore the operation. (* inherited from FPSINPUT.GEN_FACILITIES)

IS_COMP_RQD_FOR_OPER_MOVE

This indicates whether a move must have move_type of COMP in order to count as an oper move. (* inherited from FPSINPUT.GEN_FACILITIES)

COUNT_SHIP_AS_OPER_MOVE

When is_ship_event is set to Y then the normal oper moves logic is ignored and we only use these two COUNT_SHIP flags. If the ship results in a qty greater than zero then we use this flag. Ships that also set qty to 0 and therefore terminate the lot are subject to COUNT_SHIP_TO_ZERO_AS_OPER_MV (* inherited from FPSINPUT.GEN_FACILITIES)

COUNT_SHIP_TO_ZERO_AS_OPER_MV

Normally we do not count any move that results in terminating the lot as an oper move. However ships can be the exception to this rule. If this flag is Y then moves where is_ship_event is Y and qty is 0 are counted as an oper move. (* inherited from FPSINPUT.GEN_FACILITIES)

COUNT_MV_TO_BANK_AS_OPER_MOVE

Some facilities count moves to bank as oper moves and some do not. The default when this flag is N is to not count these so set to Y if you wish to count them. (* inherited from FPSINPUT.GEN_FACILITIES)

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)

IS_OPER_MOVE_IF_REWORK_START

See comments on IS_OPER_MOVE_IF_REWORK_MOVE. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

IS_OPER_MOVE_IF_REWORK_MOVE

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

IS_OPER_MOVE_IF_REWORK_END

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

DO_NOT_COUNT_OP_MV_FROM_LIST

DO_NOT_COUNT_OP_MV_TO_LIST

IS_IGNORE_MOVES_OPFAM_LIST

IS_IGNORE_MOVES_PRCS_LIST

GEN_FAC_TEMPLATE_QUERY