Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSBASE.CTM_REF_FINISHED_PERIODS
This view generates time periods and their sorting order for the graph. If the entire database is less than 10 weeks old then we use weekly buckets. Once we have more than 10 weeks of data then we switch to our normal logic of last few months then last few quarters then years. Note that the trigger CTM_FINISHED_PERIODS_DELETE takes care of the switch automatically if the periods get larger which they normally do as time goes on. However if you ever want to manually change the logic then this simple merge query will update all rows with the new periods: merge into ctm_finished_lot_hist h using ctm_finished_periods p on (h.inst >= p.start_period and h.inst < p.end_period) when matched then update set h.finished_period = p.finished_period;.
|
Column |
Comment |
|---|---|
|
FINISHED_PERIOD |
|
|
START_PERIOD |
|
|
END_PERIOD |
|
|
PLAN_YEAR |
Name of plan year must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. We prefer that other tables should reference start_plan_year rather than plan_year in case we want to change the naming convention for the plan_year. (* inherited from FPSINPUT.CAL_PLAN_YEARS) |
|
PERIOD_TYPE |
|
|
SORT_ORDER |
This is used to sort within the grouping. SORT_ORDER always has a deferrable unique key to ensure uniqueness while allowing the user to make changes without erroring until the commit is attempted. Because of this you must be careful to not violate the unique key otherwise you will lose all of your edits. (* inherited from FPSINPUT.GEN_FACILITIES) |