data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.SCH_C_CARRIER_SLOT_STATE

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.SCH_C_CARRIER_SLOT_STATE

Table FPSINPUT.SCH_C_CARRIER_SLOT_STATE"

This table is used to store the pod/carrier slot state. it can be either UP or DOWN; if it set to DOWN, then the scheduler will try not to use this slot

  • Schema: FPSINPUT

  • Tablespace: FPSDATA

  • Primary key: FACILITY, CARRIER, SLOT_NUM

  • Foreign keys: SCH_C_CARRIER_SLOT_STAT_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)

CARRIER

VARCHAR2(32)

N

RFID of the cassette or FOUP the lot is currently in. (* from FPSINPUT.MHS_CARRIERS)

SLOT_NUM

NUMBER(2)

N

The slot number the durable is occupying in its pod. This applies when a durable is stored in a pod that can hold multiple durables. (* from FPSINPUT.RTG_DURABLES)