Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSAPP.SCH_P_GROUP_HOSTS
the list web/service hosts for each sched group
|
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) |
|
HOST_ID |
|
|
PREFER_RANK |
|
|
IS_ACTIVE |
Flag to enable or disable the tag condition. (* inherited from FPSBASE.MSO_TAG_CONDITIONS) |
|
HOST_TYPE |
is used to tell if this is for WEB or SERVICE (* inherited from FPSAPP.SCH_C_GROUP_HOSTS) |
|
HOST_URL |
|
|
HOST_DESC |
|
|
HOST_CONTROLLER |
Indicate the default controller of host (* inherited from FPSAPP.SCH_C_HOSTS) |
|
HOST_ACTION |
Indicate the default action of host (* inherited from FPSAPP.SCH_C_HOSTS) |
|
PRELOAD_REFRESH_CONTROLLER |
Indicate the controller for the data refresh (* inherited from FPSAPP.SCH_C_HOSTS) |
|
PRELOAD_REFRESH_ACTION |
Indicate the action for the data refresh (* inherited from FPSAPP.SCH_C_HOSTS) |
|
RESULT_REFRESH_CONTROLLER |
Indicate the controller when it needs to send the signal that the new result is ready (* inherited from FPSAPP.SCH_C_HOSTS) |
|
RESULT_REFRESH_ACTION |
Indicate the action when it needs to send the signal that the new result is ready (* inherited from FPSAPP.SCH_C_HOSTS) |
|
APP_POOL |
This is the application pool that the application should be run under (* inherited from FPSAPP.SCH_C_HOSTS) |
|
RECYCLE_URL |
the web servie where to run the recycle application (* inherited from FPSAPP.SCH_W_RECYCLE_REQUESTS) |
|
INT_SEC_TO_RUN_SCHEDULER |
This column is used to determine how often to run the scheduler for this SCHED-GROUP. For example, if it sets 60 seconds in this column, it means it will wait for at least 60 seconds before initializing a new scheduler run from the end time of previous run. (* inherited from FPSINPUT.RTG_SCHED_GROUPS) |
|
WAIT_SEC_TO_TIME_OUT |
|
|
WALLET_PATH |
Path to the Oracle wallet for https calls, for example file:/ORACLE/wallet (* inherited from FPSAPP.SCH_C_HOSTS) |
|
WALLET_PW |