Data Dictionary
>
FPSAPP Tables
> FPSAPP.SCH_W_SCHED_DURABLE_INSPECT
Table FPSAPP.SCH_W_SCHED_DURABLE_INSPECT"
This table is to store the schedule of durable inspections.
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Primary key: FACILITY, DURABLE
|
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) |
|
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) |
|
COUNTER_LEFT |
NUMBER(5) |
the counter left on the durable |
|
|
COUNTER_MSG |
VARCHAR2(512) |
the counter message on the durable |
|
|
CURR_PRIORITY |
VARCHAR2(7) |
the priority from the first lot scheduled |
|
|
DURABLE_REQUESTED_INST |
DATE |
will be the time that the durable needed by the lot to process |
|
|
DURABLE_UNAVAILABLE_INST |
DATE |
will be the time when the durable becomes unavailable |
|
|
EARLIEST_DISP_INST |
DATE |
the earliest scheduled dispatch time that lots request to use this durable to process |
|
|
EARLIEST_REQUESTED_INST |
DATE |
the earliest step enter time that lots request to use this durable to process |
|
|
EARLIEST_SCHED_START |
DATE |
the earliest scheduled process start time that lots request to use this durable to process |
|
|
END_INST |
DATE |
The time the even is scheduled to end (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL) |
|
|
EVENT_DESC |
VARCHAR2(500) |
Event Description (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL) |
|
|
EVENT_LIST |
VARCHAR2(500) |
||
|
EVENT_TYPE |
VARCHAR2(12) |
Event Type (* from FPSINPUT.EQP_SCHED_EVENTS_MANUAL) |
|
|
LOT |
VARCHAR2(32) |
the lot id from the first lot that scheduled |
|
|
NUM_REQUESTS |
NUMBER(4) |
# of lots request to use this durable to process in the next 12 hours, based on step enter time |
|
|
NUM_REQUESTS_AT_OPER |
NUMBER(4) |
the number of requests that the lots are now at the operation |
|
|
NUM_REQUESTS_PRTY |
NUMBER(4) |
# of priority lots request to use this durable to process in the next 12 hours, based on step enter time |
|
|
NUM_STEPS_AWAY |
NUMBER(4) |
the # steps away from the first lot that scheduled |
|
|
OTHER_COUNTER_MSG |
VARCHAR2(500) |
to store other counter message, like 2nd counter msg or 3rd counter msg |
|
|
OTHER_NOTE |
VARCHAR2(500) |
Some description for this scheduler (* from FPSINPUT.RTG_SCHED_GROUPS) |
|
|
SCHED_START |
DATE |
the sched start time from the first lot that scheduled |
|
|
SCHED_TOOL |
VARCHAR2(16) |
the tool from the first lot that scheduled |
|
|
START_INST |
DATE |
Time when the lot started. (* from FPSINPUT.WIP_STARTS) |
|
|
TOOL_TYPE |
VARCHAR2(50) |
the tool type from the first lot that scheduled |