Data Dictionary
>
FPSINPUT Views
> FPSINPUT.WIP_WAFER_HIST_LOOP
View FPSADMIN.RECENT_WEH_HIST
This view is for DB ETL sites only which use ADM_LOAD_EVENT_HIST_VIA_APD. It queries the WEH+EEH_WWH record from ADM_LOAD_HIST and records basic information plus two extra calculated columns seconds behind at start and seconds behind at complete.
|
Column |
Comment |
|---|---|
|
SEC_BEH_START |
|
|
SEC_BEH_COMP |
|
|
DURATION_SEC |
Duration in seconds of the period to be used to run the APF report. Used only for CLR, CLRA, and QE. (* inherited from FPSADMIN.CFG_TABLES) |
|
LAST_START_TIME |
|
|
SYS_TIME |
This is always SYSTIMESTAMP when the record was inserted in the MSO_MES_INTERACTION_HIST table. (* inherited from FPSBASE.MSO_MES_INTERACTION_HIST) |
|
NOW |
|
|
MSG_CODE |
|
|
OBJECT_NAME |
This could be an object name (we will disable loading of that object in the scheduled jobs), a load job (we will disable loading of all objects in that scheduled job), an FPSAPP prefix (we will disable loading of all objects with that prefix), a constraint (we can explain why it is permanently disabled), or a trigger (technically an object so we can get away with omitting this from the column name and also to explain why it is permanently disabled). (* inherited from FPSADMIN.CFG_DISABLED) |
|
LOOP_MINS |
|
|
SHORT_MSG |
|
|
LONG_MSG |
|
|
MS_PER_REC |
|
|
NUM_WEH |
|
|
NUM_EEH |
|
|
NUM_WWH |
|
|
COMPONENT |
|
|
METHOD |
Method used to load data in table or execute procedure (* inherited from FPSADMIN.GEN_LOAD_METHODS) |
|
OBJ_OWNER |
|
|
OBJ_TYPE |
|
|
APPLICATION |
Application that the user is allowed or able to log events. (* inherited from FPSINPUT.GEN_USERS) |
|
OSUSER |
|
|
MACHINE |
|
|
DB_USERNAME |
For CHGLOG and automatic HIST tables, this is populated with the USER system variable. (* inherited from FPSINPUT.EQP_CHAMBERS_CHGLOG) |
|
SID |
|
|
MSG_TIME |
This column can be used for a DATE or TIMESTAMP associated with the record. If the record is from a different system like APF then this could be the timestamp from the APF repository. Or if we want to record a message about an event inserted in WIP_EVENT_HIST then this could be the INST of that event. Therefore this value could be in a different time zone from SYS_TIME. If the msg_time is not specified then we will fill in with SYSTIMESTAMP. (* inherited from FPSADMIN.ADM_LOAD_HIST) |