Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSAPP.PERF_P_H_LINEBAL_SHIFT_FROMCFG
This view filters PERF_P_H_LINEBAL_SHIFT to provide per row per line balance grouping level based on how line balance is configured to be calculated. This allows Performance to show a calculation of line balance KPI's the way they are configured in the system as opposed to doing the calculation for each route/step which is how the data is stored. For example, PERF_P_H_LINEBAL_SHIFT may have 3 rows for 3 different route/steps all assigned to the same common_step. If line balance is configured to be calculated by common_step, then one row should be returned per common_step with the data aggregated accordingly.
|
Column |
Comment |
|---|---|
|
SHIFT |
Name of shift 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_shift rather than shift in case we want to change the naming convention for the shift. (* inherited from FPSINPUT.CAL_SHIFTS) |
|
START_SHIFT |
Shifts can be of any length and it is important that all queries get the shift length based on start_shift and end_shift rather than assuming a set number of hours. (* inherited from FPSINPUT.CAL_SHIFTS) |
|
CALENDAR_DAY |
When we choose this day on a website calendar we will associate with work_days of this day. Typically this is the day of the start_day but not always. For example, start_day might be 17:00 and represent the following calendar_day. (* inherited from FPSINPUT.CAL_WORK_DAYS) |
|
CALENDAR_DAY_TXT |
|
|
START_WEEK |
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. (* inherited from FPSINPUT.CAL_WORK_WEEKS) |
|
WEEK |
|
|
START_MONTH |
|
|
MONTH |
|
|
FACILITY |
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. (* inherited from FPSINPUT.GEN_FACILITIES) |
|
LINE_BALANCE_GROUP_CFG |
|
|
LINE_BALANCE_GROUP |
|
|
TARGET_WIP_QTY_FROM_CFG |