data-dictionary
data-dictionary
Breadcrumbs

FPSAPP.CM_C_SCENARIO_INFO_COLS

Data Dictionary

>

FPSAPP Tables

> FPSAPP.CM_C_SCENARIO_INFO_COLS

Table FPSAPP.CM_C_SCENARIO_INFO_COLS"

This table stores a list of columns, configurable by site, that customers would like to see for informational purposes only when downloading a scenario template in the capacity model application. As an example, in a calculation scenario, THP data is shown by (RORP,SETP). It is often the case that this information is not easily human-readable, and that by adding a column like PROCESS, the template makes more sense to the end user.

  • Schema: FPSAPP

  • Tablespace: FPSDATA

  • Primary key: FACILITY, CM_SCENARIO, COLUMN_NAME

  • Foreign keys: CM_C_SCENARIO_INFO_COLS_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)

CM_SCENARIO

VARCHAR2(6)

N

This is the scenario to which the column should be added. Currently, the options are: STARTS, EQUIP, CALC for starts, equipment, and calculation scenarios respectively.