FPSINPUT.EQP_WIP_METRICS_OVR

TOOL

VARCHAR2(16)

N

Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* from FPSINPUT.EQP_TOOLS)

DAY_TGT_COMPLETES_OVR

NUMBER(5)

Override for day completes WIP. When populated this will replace DAY_TGT_COMPLETES calulated in FPSBASE.EQP_WIP_COMP_TGTS

DAY_TGT_WIP_OVR

NUMBER(5)

Override for day target WIP. When populated this will replace DAY_TGT_WIP calulated in FPSBASE.EQP_WIP_COMP_TGTS

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)

SHIFT_TGT_COMPLETES_OVR

NUMBER(5)

Override for shift completes WIP. When populated this will replace SHIFT_TGT_COMPLETES calulated in FPSBASE.EQP_WIP_COMP_TGTS