data-dictionary
data-dictionary
Breadcrumbs

FPSBASE.SCH_C_CARRIER_SLOT_NUM

Data Dictionary

>

FPSBASE Tables

> FPSBASE.SCH_C_CARRIER_SLOT_NUM

Table FPSBASE.SCH_C_CARRIER_SLOT_NUM"

This table is used to store the pod/carrier slot num configuration. currently it needs to be set by facility level, but in the future if it needs to be set by different way, then we can do it too

  • Schema: FPSBASE

  • Tablespace: FPSDATA

  • Primary key: FACILITY, SLOT_NUM

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