Data Dictionary
>
FPSBASE Tables
> FPSBASE.MHS_CARRIER_FUTURE_SCHED
Table FPSBASE.MHS_CARRIER_FUTURE_SCHED"
Future schedule information for the carrier
-
Schema: FPSBASE
-
Tablespace: FPSDATA
-
Primary key: CARRIER, FACILITY
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
CARRIER |
VARCHAR2(32) |
N |
RFID of the cassette or FOUP the lot is currently in. (* from FPSINPUT.MHS_CARRIERS) |
|
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) |
|
SCHED_COMMENT |
VARCHAR2(4000) |
||
|
SCHED_IS_RESERVED |
CHAR(1) |
||
|
SCHED_START |
DATE |
The first start time for the reticle to be used |
|
|
SCHED_TOOL |
VARCHAR2(16) |
the tool from the first lot that scheduled (* from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT) |