FPSBASE.WIP_REF_FLUSH_CURR_FAC

LOT

A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

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)

PRD

Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PRDS)

PLANPRD

Planning product used for all planning purposes. All lots with the same planprd are interchangeable to ship to the customer regardless of their prd, route, technology, wafer size, etc. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PLANPRDS)

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)

DUE_INST

To indicate the due date for this futuer start lot (* inherited from FPSINPUT.WIP_STARTS)

DEMAND_INST

Start of period when this qty of this planprd needs to finish. We automatically spread demand across each plan week in WIP_DEMAND_BY_WEEK which feeds WIP_FLUSH therefore this column can be the start of any time period less than or equal to plan week. It could be the demand for each shift or for each day or for each plan week but if the site has no preference then the easiest way to set this up is to write one row per plan week and let us spread across that week. It is important to note that we always spread across the plan week with our custom logic so even if this table is by day we might adjust it to another day within the same plan week. (* inherited from FPSINPUT.WIP_DEMAND)

DEMAND_WW_QTY

CUM_DEMAND_BY_WW

SHIP_QTY_THIS_WEEK

EOL_INST_TARGET

Date/time when the lot is estimated to finish the specified route/bank using Target cycle time. (* inherited from FPSBASE.WIP_FLUSH)

EOL_INST_COMMIT

Date/time when the lot is estimated to finish the specified route/bank using Commit cycle time. (* inherited from FPSBASE.WIP_FLUSH)

PLAN_WEEK_DEMAND

PLAN_WEEK_TARGET

PLAN_WEEK_COMMIT

PLAN_WEEK_DUE

START_PLAN_WK_DEMAND

START_PLAN_WK_TARGET

Work week when the lot is estimated to finish the specified route/bank using Target cycle time according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_COMMIT

Work week when the lot is estimated to finish the specified route/bank using Commit cycle time according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)

START_PLAN_WK_DUE

Work week of due date according to CAL_WEEKS. (* inherited from FPSBASE.WIP_FLUSH)