FPSAPP.DASH_P_CUSTOM_RPT_SECTIONS

Data Dictionary

FPSAPP Views

> FPSAPP.WIP_WAFER_HIST_LOOP

View FPSAPP.DASH_P_CUSTOM_RPT_SECTIONS

This P view shows the contents of the DASH_P_CUSTOM_RPT_SECTIONS table plus any sections assigned to any global FPS reports which are not included in the DASH_C_CUSTOM_REPORTS table. Since this view only shows section with reports assigned, it will not show records in DASH_P_CUSTOM_RPT_SECTIONS which have no reports assigned in DASH_C_CUSTOM_REPORTS.

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)
SECTION	The section the report link belongs under, such as Operations or Maintenance (* inherited from FPSAPP.DASH_C_CUSTOM_REPORTS)
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)