data-dictionary

FPSBASE.SCH_W_DURABLE_SCHED_EVENTS

Data Dictionary

>

FPSBASE Tables

> FPSBASE.SCH_W_DURABLE_SCHED_EVENTS

Table FPSBASE.SCH_W_DURABLE_SCHED_EVENTS"

This table is for storing sched events for each durable.

  • Schema: FPSBASE

  • Tablespace: FPSDATA

  • Primary key: FACILITY, DURABLE, EVENT, START_INST


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)

DURABLE

VARCHAR2(64)

N

Durables are either reticles for Litho or probe cards for Wet or Sort. A durable can either be in a carrier or at a location without a carrier. (* from FPSINPUT.RTG_DURABLES)

EVENT

VARCHAR2(48)

N

This is the event registered in the MES. This is for the historical record and display only. Each event is mapped to an FPS event_type and the event_type is what is used by FPS applications. (* from FPSINPUT.WIP_EVENTS)

START_INST

DATE

N

Time when the lot started. (* from FPSINPUT.WIP_STARTS)

DURABLE_FAMILY

VARCHAR2(64)

Durable_family indicates what durable is required by the process. When multiple durables are in a family any of them can be used. Typically there is only one reticle per family and therefore the durable and durable_family are the same. The exception would be a high running product with backup reticles. However for probe cards it is common to have several cards for each product so we have several durables with the same family. (* from FPSINPUT.RTG_DURABLE_FAMILIES)

END_INST

DATE

The time the even is scheduled to end (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL)

EVENT_DESC

VARCHAR2(500)

Event Description (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL)

EVENT_TYPE

VARCHAR2(12)

Event Type (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL)