Data Dictionary
>
FPSAPP Tables
> FPSAPP.ECT_SUMMARY_P1_WEEKS
Table FPSAPP.ECT_SUMMARY_P1_WEEKS"
See comments in ECT_REF_SUMMARY_P1_WEEKS view.
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Primary key: START_WEEK, FACILITY
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
START_WEEK |
DATE |
N |
Work weeks must be 7 days in duration and the start of the work week must be the start of one of the work days. (* from FPSINPUT.CAL_WORK_WEEKS) |
|
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) |
|
END_WEEK |
DATE |
It is critical that this field equal the start_week of the next work work. (* from FPSINPUT.CAL_WORK_WEEKS) |