data-dictionary
data-dictionary
Breadcrumbs

FPSAPP.RTG_OVR_CS_SORT_RT_FAM_SEG

Data Dictionary

>

FPSAPP Tables

> FPSAPP.RTG_OVR_CS_SORT_RT_FAM_SEG

Table FPSAPP.RTG_OVR_CS_SORT_RT_FAM_SEG"

This table allows the ETL to override this value which determines the sorting of common steps on the Line Viewer by route family. Our default logic to do this sort is in RTG_ROUTE_STEPS_PLUS and we hope that is sufficient and that this table can be empty.

  • Schema: FPSAPP

  • Tablespace: FPSDATA

  • Primary key: FACILITY, COMMON_STEP, ROUTE_FAMILY, ROUTE_SEGMENT

  • Foreign keys: RTG_OVR_CS_SORT_RT_FAM_FK_CS: FACILITY, COMMON_STEP REFERENCES FPSINPUT.RTG_COMMON_STEPS (FACILITY, COMMON_STEP)


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)

COMMON_STEP

VARCHAR2(50)

N

A display-friendly field that groups similar steps together for purposes of viewing the entire line. Typically the only duplicates within a single route will be optional ordered steps in the same segment. But we will often have steps across routes that share the same common step even though exact step definition is not identical. (* from FPSINPUT.RTG_COMMON_STEPS)

ROUTE_FAMILY

VARCHAR2(36)

N

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

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)

CS_SORT_IN_RT_FAM_SEG

NUMBER(7

The full name of this column is override to common step sort within route family and route segment.