data-dictionary
data-dictionary
Breadcrumbs

FPSBASE.SCH_C_DURABLE_MNT_EVENTS

Data Dictionary

>

FPSBASE Tables

> FPSBASE.SCH_C_DURABLE_MNT_EVENTS

Table FPSBASE.SCH_C_DURABLE_MNT_EVENTS"

This table is used for the durable Maintenances configurations

  • Schema: FPSBASE

  • Tablespace: FPSDATA

  • Primary key: FACILITY, MNT_NAME

  • Foreign keys: SCH_C_DURABLE_MNT_EVENT_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)


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)

MNT_NAME

VARCHAR2(128)

N

Name identifying the scheduled maintenance event which is unique for the `logged_entity`. For example, daily qual or weekly PM. (* from FPSINPUT.EQP_MNT_FUTURE)

WAIT_SEC_TO_SCHED

NUMBER

The lot may be scheduled but must not be allowed to dispatch or start until this number of seconds has elapsed. (* from FPSINPUT.WIP_LOTS_STATIC)