FPSBASE.SCH_P_DATA_REFRESH

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)

HOST_ID

HOST_TYPE

is used to tell if this is for WEB or SERVICE (* inherited from FPSAPP.SCH_C_GROUP_HOSTS)

URL

The URL of the report link (* inherited from FPSAPP.DASH_C_CUSTOM_REPORTS)

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)