Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSAPP.SCH_P_CFG_SCHED_GROUPS_KPI
the list of KPI items that will be used in calculation
|
Column |
Comment |
|---|---|
|
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) |
|
SCHED_GROUP |
This is the grouping of tools and processes which the FPS Scheduler schedules together. Since this is a parent of tool via tool->process_group and a parent of process via process->process_group, by definition each tool and each process can only be in one sched group. We need all related tools and processes to be in the same sched group for efficient scheduling. One example is sinks and furnaces because of queue times and batching. Another example is for smaller facilities like Assembly or Test where we might schedule the entire facility together. (* inherited from FPSINPUT.RTG_PROCESS_GROUPS) |
|
CONFIG_ID |
This is used to tell which configuration the current sched-group is using (* inherited from FPSINPUT.RTG_SCHED_GROUPS) |
|
KPI_ID |
|
|
KPI_DISPLAY |
|
|
KPI_DESC |
|
|
SORT_ORDER |
This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* inherited from FPSINPUT.GEN_FACILITIES) |
|
IS_CURR |
Boolean flag where Y indicates this row is for the current main route or product. Same as flush_seq_num = 1. (* inherited from FPSBASE.WIP_FLUSH) |
|
SCHED_GROUP_STATE |
State is constrained to one of three values. ON: Running for production. DEV: Schedule is visible for authorized users only (Q-Mgr and Scheduler run as if ON). OFF: Rarely used except when setting up a new sched_group. (* inherited from FPSINPUT.RTG_SCHED_GROUPS) |
|
DIRECTION_OF_INCREASE |
This column determines if an increase in the KPI Result value after a scenario run indicates a positive outcome. Value can be POSITIVE, NEGATIVE, or IGNORE. If set to IGNORE, Scheduler will ignore the change in result and not use a visual indicator. (* inherited from FPSAPP.SCH_G_KPIS) |