FPSADMIN.RTG_COMMON_STEPS

Data Dictionary

FPSADMIN Tables

> FPSADMIN.RTG_COMMON_STEPS

Table FPSADMIN.RTG_COMMON_STEPS"

For the Line Viewer and anywhere else when we want to display information on steps across multiple routes (usually by route_group or facility) we need a common_step to be defined with a sort_order to be able to group steps appropriately..

Schema: FPSADMIN
Tablespace: FPSDATA
Primary key: FACILITY, COMMON_STEP
Foreign keys: RTG_COMMON_STEPS_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)
Referenced by: FPSINPUT.RTG_OVR_CS_SORT_RT_FAM_SEG (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.
COMMON_STEP_SORT	NUMBER(7,2)	N	How to sort common_step when displaying together for multiple routes in the same view. This must be unique for the entire facility so that we know how to order common_step when viewing the entire facility.
FACILITY_SEGMENT	VARCHAR2(36)	N	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.