Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSADMIN.RECENT_INACTIVE_HIST
This is a quick shortcut to view the recent activity regarding the RTG_ROUTE_STEPS_INACTIVE table. These records are always logged to ADM_SPEED_HIST regardless of the setting of any CC flag.
|
Column |
Comment |
|---|---|
|
TS |
|
|
ACTION |
For CHGLOG and automatic HIST tables, this is I for insert or U for updated or D for delete. (* inherited from FPSINPUT.EQP_PORT_HIST) |
|
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) |
|
REASON |
Reason why the action was triggered. This is used to provide a comment to MES. (* inherited from FPSBASE.MSO_TRIGGERED_MES_ACTIONS_HIST) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
STEP |
A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* inherited from FPSINPUT.RTG_ROUTE_STEPS) |
|
STEP_OR_PROCESS_TO_MATCH |
|
|
FACILITY |
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. (* inherited from FPSINPUT.GEN_FACILITIES) |
|
NUM_ROWS |
|
|
SECONDS |
|
|
VALUE_DEFINITIONS |