Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.CM_W_SCENARIOS_DEMAND
Table FPSINPUT.CM_W_SCENARIOS_DEMAND"
This table stores demand scenarios uploaded from Excel files to the capacity model web site.
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: SCENARIO, FACILITY, PRD, WORKWEEK
-
Foreign keys: CM_W_SCENARIOS_DEMAND_FK_FACPR: FACILITY, PRD REFERENCES FPSINPUT.RTG_PRDS (FACILITY, PRD)
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
SCENARIO |
VARCHAR2(16) |
N |
|
|
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) |
|
PRD |
VARCHAR2(64) |
N |
Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* from FPSINPUT.RTG_PRDS) |
|
WORKWEEK |
VARCHAR2(7) |
N |
|
|
DEMAND_QTY |
NUMBER(9) |
N |
Number of wafers committed in the demand. (* from FPSINPUT.WIP_DEMAND) |