Data Dictionary
>
FPSAPP Tables
> FPSAPP.RTG_DURABLE_FUTURE_SCHED
Table FPSAPP.RTG_DURABLE_FUTURE_SCHED"
Future schedule information for the durable
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Primary key: DURABLE, FACILITY
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
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) |
|
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) |
|
CLAIMED_BY |
VARCHAR2(64) |
||
|
CLAIMED_CARRIER |
VARCHAR2(32) |
||
|
CLAIMED_END |
DATE |
||
|
CLAIMED_SLOT_NUM |
NUMBER(2) |
||
|
CLAIMED_START |
DATE |
||
|
CLAIMED_STATE |
VARCHAR2(12) |
||
|
CLAIMED_TOOL |
VARCHAR2(16) |
||
|
EXTENDED_BY |
VARCHAR2(64) |
||
|
IS_CLAIMED |
CHAR(1) |
||
|
RELEASED_BY |
VARCHAR2(64) |
||
|
SCHED_CARRIER |
VARCHAR2(32) |
||
|
SCHED_COMMENT |
VARCHAR2(4000) |
||
|
SCHED_INSPECTION_INST |
DATE |
the time scheduled to do the inspection |
|
|
SCHED_IS_RESERVED |
CHAR(1) |
||
|
SCHED_RESERVE_INST |
DATE |
The actual time the lot was reserved by the scheduler will be helpful for compliance and debugging. (* from FPSBASE.WIP_STEP_FUTURE_SCHED) |
|
|
SCHED_START |
DATE |
The first start time for the durable to be used |
|
|
SCHED_TOOL |
VARCHAR2(16) |
the tool from the first lot that scheduled (* from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT) |
|
|
TRANSIT_FROM |
VARCHAR2(24) |
to indicate where the durable is now/transit from |
|
|
TRANSIT_START |
DATE |
to indicate when the transit should start |
|
|
TRANSIT_TO |
VARCHAR2(24) |
to indicate where the durable is going to/transit to |