data-dictionary
data-dictionary
Breadcrumbs

FPSADMIN.RTG_ROUTE_SEGMENT_SORTS

Data Dictionary

>

FPSADMIN Tables

> FPSADMIN.RTG_ROUTE_SEGMENT_SORTS

Table FPSADMIN.RTG_ROUTE_SEGMENT_SORTS"

Route_segment_sort is provided to the Dashboard by route_family+route_segment in the questionably named view DASH_P_ROUTE_SEGMENTS. This table allows us to set the segment_sort for all route segments across the overall facility. If this table is empty (which is common and acceptable) then logic in RTG_REF_ROUTE_STEPS_PLUS will calculate the segment sort for each route family by ordering based on the seq_num of the various routes in the family. But if this table is populated, we will always see the segment chart sorted based on the order in this table at all levels (family, group, facility). It is critical that if you populate this table that you include all route segments on production routes. If it is populated for some segments but not all (which should not happen but could especially for new routes) then the segments with a defined sort will be first in that order followed by the undefined segments. This logic is not perfect is when the same segments are in clearly different order in different families. So in family Eugenia segment A comes before segment B but in family Audelia segment B comes before segment A. In the table, we set the segment_sort for the overall facility as best we can but we have to choose. We choose to sort like Eugenia so when we look at the Line Viewer for any family, we see A before B which meets our customer requirement that all segments are shown in the order defined in the table. But this is out of order for the Audelia family.

  • Schema: FPSADMIN

  • Tablespace: FPSDATA

  • Primary key: FACILITY, ROUTE_SEGMENT

  • Foreign keys: RTG_ROUTE_SEGMENT_SORTS_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)


Column

Type

Nullable

Comment

FACILITY

VARCHAR2(6)

N

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. (* from FPSINPUT.GEN_FACILITIES)

ROUTE_SEGMENT

VARCHAR2(36)

N

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. (* from FPSINPUT.RTG_ROUTE_STEPS)