FPSADMIN.ETP_TOOL_E10_PD_HIST

Data Dictionary

FPSADMIN Tables

> FPSADMIN.ETP_TOOL_E10_PD_HIST

Table FPSADMIN.ETP_TOOL_E10_PD_HIST"

See comments in ETP_APD_TOOL_E10_PD_HIST view.

Schema: FPSADMIN
Tablespace: FPSDATAHIST
Primary key: FACILITY, TOOL, START_PLAN_DAY
Foreign keys: ETP_TOOL_E10_PD_H_FK_STDAY: START_PLAN_DAY REFERENCES FPSINPUT.CAL_PLAN_DAYS (START_PLAN_DAY)

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	Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* from FPSINPUT.EQP_TOOLS)
START_PLAN_DAY	DATE	N	Plan days must be 24 hours in length and the start of the plan day must be the start of one of the shifts. Contrast this to plan day which is independent of shift. (* from FPSINPUT.CAL_PLAN_DAYS)
AMU	NUMBER(9,3)
AOU	NUMBER(9,3)
ATU	NUMBER(9,3)
E10_ENG	NUMBER(10,1)
E10_EQP_DOWN	NUMBER(10,1)
E10_EQP_UP	NUMBER(10,1)
E10_E_OPER	NUMBER(10,1)
E10_E_SDT	NUMBER(10,1)
E10_E_SDT_ENTITIES	NUMBER(10,1)
E10_E_UDT	NUMBER(10,1)
E10_E_UDT_ENTITIES	NUMBER(10,1)
E10_MFG	NUMBER(10,1)
E10_NST	NUMBER(10,1)
E10_OPER	NUMBER(10,1)
E10_PRD	NUMBER(10,1)
E10_SBY	NUMBER(10,1)
E10_SDT	NUMBER(10,1)
E10_SDT_ENTITIES	NUMBER(10,1)
E10_SDT_PM_ENTITIES	NUMBER(10,1)
E10_SDT_QUAL_ENTITIES	NUMBER(10,1)
E10_SDT_WO_WAITS	NUMBER(10,1)
E10_TOTAL	NUMBER(10,1)
E10_TOTAL_ENTITIES	NUMBER(10,1)
E10_UDT	NUMBER(10,1)
E10_UDT_ENTITIES	NUMBER(10,1)
E10_UDT_QUAL_ENTITIES	NUMBER(10,1)
E10_UDT_WO_WAITS	NUMBER(10,1)
E10_UDT_WO_WAITS_ENTITIES	NUMBER(10,1)
END_PLAN_DAY	DATE		It is critical that this field equal the start_plan_day of the next plan day. (* from FPSINPUT.CAL_PLAN_DAYS)
E_AOSDT	NUMBER(9,3)
E_AOU	NUMBER(9,3)
E_AOUDT	NUMBER(9,3)
E_MTBF_P	NUMBER(9,3)
E_MTBF_U	NUMBER(9,3)
E_MTTR	NUMBER(9,3)
E_MUBF	NUMBER(12,3)
IT	NUMBER(9,3)
MFD_P	NUMBER(9,3)
MFD_U	NUMBER(9,3)
MTBF_P	NUMBER(9,3)
MTBF_U	NUMBER(9,3)
MTOL	NUMBER(9,3)
MTTI	NUMBER(9,3)
MTTPM	NUMBER(9,3)
MTTQ	NUMBER(9,3)
MTTR	NUMBER(9,3)
MUBF	NUMBER(12,3)
N_CDT_EPISODES	NUMBER(6,1)
N_CDT_EPISODES_ENTITIES	NUMBER(6,1)
N_E_SDT_EPISODES	NUMBER(6,1)
N_E_SDT_EPISODES_ENTITIES	NUMBER(6,1)
N_E_UDT_EPISODES	NUMBER(6,1)
N_E_UDT_EPISODES_ENTITIES	NUMBER(6,1)
N_E_UDT_P_EPISODES	NUMBER(6,1)
N_ONLY_ALARMS	NUMBER(6,1)
N_ONLY_QUALS	NUMBER(6,1)
N_PM_EPISODES_ENTITIES	NUMBER(6,1)
N_QUALS	NUMBER(6,1)
N_SDT_EPISODES	NUMBER(6,1)
N_SDT_EPISODES_ENTITIES	NUMBER(6,1)
N_SDT_P_EPISODES	NUMBER(6,1)
N_SDT_P_EPISODES_ENTITIES	NUMBER(6,1)
N_UDT_EPISODES	NUMBER(6,1)
N_UDT_EPISODES_ENTITIES	NUMBER(6,1)
N_UDT_P_EPISODES	NUMBER(6,1)
N_UDT_P_EPISODES_ENTITIES	NUMBER(6,1)
PLAN_DAY	VARCHAR2(13)		Name of plan day must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. We prefer that other tables should reference start_plan_day rather than plan_day in case we want to change the naming convention for the plan_day. (* from FPSINPUT.CAL_PLAN_DAYS)
TFR	NUMBER(10,3)
UNITS	NUMBER(10,1)
UOU	NUMBER(9,3)
UTU	NUMBER(9