data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.DASH_P_ROUTE_SEGMENTS

Data Dictionary

>

FPSINPUT Views

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSAPP.DASH_P_ROUTE_SEGMENTS

DROPPABLE: This view can be dropped after Dashboard queries are changed to use DASH_P_ROUTE_STEPS. That will likely be 6.14 but this could get pushed out so we must check when we think it might be safe. This view is for the WIP Segments and Line Viewer pages of the dashboard. Please note that it appears that the Line Viewer page gets route_segment_sort from DASH_P_ROUTE_STEPS so we must keep the route_segment_sort as a property of the route_family+route_segment combination. In other words, we cannot make route_segment_sort in DASH_P_ROUTE_STEPS a property of the route+route_segment and then have a route_family_segment_sort to use here with logic by route_family.

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)

ROUTE_FAMILY

Route_family indicates that all routes within the family have similar or even identical steps and have the same segments. At facilities where various prds share the same route it is likely that the route will be the route_family. This is sometimes referred to as the main process flow. It is used on Segment Summary and Line Viewer to group similar routes. (* inherited from FPSINPUT.RTG_ROUTE_FAMILIES)

ROUTE_SEGMENT

Route_segment allows for clear hierarchical segment organization for Segment Summary and Line Viewer on Dashboard. This is often referred to as stage and typically will come from the MES (as opposed to facility_segment which we will typically have to define for our purposes). We recommend that all routes in the same route family have the same route segments in the same order so that the Line Viewer by route family will be consistent but if this is not the case then we approximate the order as best we can. (* inherited from FPSINPUT.RTG_ROUTE_STEPS)

ROUTE_SEGMENT_SORT