data-dictionary

FPSADMIN.CTR_B_RRS_FOR_SAME_FAC_SEQ

Data Dictionary

>

FPSADMIN Tables

> FPSADMIN.CTR_B_RRS_FOR_SAME_FAC_SEQ

Table FPSADMIN.CTR_B_RRS_FOR_SAME_FAC_SEQ"

See comments in CTR_REF_B_RRS_FOR_SAME_FAC_SEQ view.

  • Schema: FPSADMIN

  • Tablespace: FPSDATA

  • Primary key: FACILITY, COMBINED_ROUTE, ROUTE_SEGMENT, 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)

COMBINED_ROUTE

VARCHAR2(256)

N

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)

STEP

VARCHAR2(256)

N

A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* from FPSINPUT.RTG_ROUTE_STEPS)

COMBINED_SEQ_NUM

NUMBER(7,2)

COMMIT_STEP_SEC

NUMBER(7)

COMMIT_STEP_SEC_TO_EOL

NUMBER(11)

ORIG_ROUTE

VARCHAR2(256)

ORIG_SEQ_NUM

NUMBER(7,2)

ROUTE_USED_FOR_FILLIN

VARCHAR2(256)

TARGET_STEP_SEC

NUMBER(7)

TARGET_STEP_SEC_TO_EOL

NUMBER(11)

TOTAL_COMMIT_CT_DAYS

NUMBER(7,3)

TOTAL_TARGET_CT_DAYS

NUMBER(7