data-dictionary

FPSAPP.WIP_HOLD_ESTIMATES

Data Dictionary

>

FPSAPP Tables

> FPSAPP.WIP_HOLD_ESTIMATES

Table FPSAPP.WIP_HOLD_ESTIMATES"

See comments in WIP_REF_HOLD_ESTIMATES view.

  • Schema: FPSAPP

  • Tablespace: FPSDATA

  • Primary key: FACILITY, HOLD_TYPE, PROCESS_FAMILY, LOT_GROUP


Column

Type

Nullable

Comment

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)

HOLD_TYPE

VARCHAR2(24)

N

Generally hold_type will come directly from the MES. (* from FPSINPUT.WIP_HOLD_TYPES)

PROCESS_FAMILY

VARCHAR2(50)

N

See https://help.inficonims.com/display/DW/Guide+to+Process+Families. (* from FPSINPUT.RTG_PROCESS_FAMILIES)

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

CALCULATED_NUM_HOLDS

NUMBER(6)