FPSBASE.RTG_STEP_WINDOW_WIP

FACILITY

VARCHAR2(6)

N

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

ROUTE

VARCHAR2(256)

N

Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)

LOT

VARCHAR2(32)

N

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

COMMON_END_STEP

VARCHAR2(50)

The common step upon move out where the wip balance limit is no longer applied. (* from FPSINPUT.RTG_COMMON_STEP_BALANCE)

COMMON_START_STEP

VARCHAR2(50)

The common step upon move out we apply the balance logic. Tied to all routes that share the common end and start steps. This is used for both the WIP window and daily input control limit to trigger WIP that is in the window limit and/or counted towards the daily limit. (* from FPSINPUT.RTG_COMMON_STEP_BALANCE)

END_STEP

VARCHAR2(256)

The step upon move out where the WIP balance limit is no longer applied (* from FPSINPUT.RTG_STEP_BALANCE)

RTG_BALANCE_TABLE

VARCHAR2(30)