Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.EQP_SCHED_EVENTS_MANUAL
Table FPSINPUT.EQP_SCHED_EVENTS_MANUAL"
This table is used to store scheduled event for all tools. usually this is used by using ETL
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: FACILITY, TOOL, ENTITY, EVENT, START_INST
-
Foreign keys: EQP_SCHED_EVENTS_MANL_FK_TOOL: FACILITY, TOOL REFERENCES FPSINPUT.EQP_TOOLS (FACILITY, TOOL)
|
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) |
|
TOOL |
VARCHAR2(16) |
N |
Which tool is for this event |
|
ENTITY |
VARCHAR2(19) |
N |
This is for the chamber. if this event is applied to all of the chamber, then we should use tool as the entity on this column |
|
EVENT |
VARCHAR2(48) |
N |
Event |
|
START_INST |
DATE |
N |
The time the event is scheduled to start |
|
END_INST |
DATE |
The time the even is scheduled to end |
|
|
EVENT_DESC |
VARCHAR2(500) |
Event Description |
|
|
EVENT_TYPE |
VARCHAR2(12) |
Event Type |