FPSAPP.WIP_LOTS_OVR_EST_END_INST

LOT

VARCHAR2(32)

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)

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)

IS_COMPLETE

CHAR(1)

Boolean indicating whether the lot has completed processing.

IS_UNLOADED

CHAR(1)

Boolean indicating whether the lot has been unloaded.

OVR_ACTUAL_CH_USED

VARCHAR2(24)

Allows our external source to populate ACTUAL_CH_USED column overriding WIP_EVENT_HIST.

OVR_ACTUAL_MACHINE_RECIPE

VARCHAR2(100)

Allows our external source to populate ACTUAL_MACHINE_RECIPE column overriding WIP_EVENT_HIST.

OVR_EST_END_INST

DATE

Estimated time when the lot will end processing on the tool.

OVR_EST_NEXT_BEG_INST

DATE

Estimated time when the next job must start processing on the tool in order to maintain full cascading and not lose productivity.

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)