FPSADMIN.DASH_P_FACILITY_SEGMENTS

Data Dictionary

FPSADMIN Views

> FPSADMIN.WIP_WAFER_HIST_LOOP

View FPSAPP.DASH_P_FACILITY_SEGMENTS

This view provides facility segments to the dashboard. Sort is based on common step sort and the FPSBASE.CHK_FACILITY_SEGMENTS view ensures this sort is consistent. NOTE: In previous versions of this view using RRSP we had to cast sort_order as number(4) which made no sense because fss is a number(4) in RRSP but without it the segment chart failed at some sites. Now we find the same problem using row_number. Something strange is going on in the Dashboard code but this cast seems to fix it so it stays.

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)
FACILITY_SEGMENT	Facility segment is the parent of common step and is used as the highest level grouping when we show WIP for a route group or the entire facility where we cannot use route segment. We would prefer somewhere between 8 and 20 facility segments. Typically we will have to define these (as opposed to route_segment which we will typically come from the MES). There is no RTG_FACILITY_SEGMENTS table because sorting of facility segments is determined by common_step_sort. A trigger on RTG_COMMON_STEPS ensures that facility segments are contiguous when the entire facility is sorted by common step. (* inherited from FPSINPUT.RTG_COMMON_STEPS)
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)