data-dictionary

FPSAPP.CAL_SHIFTS_PLUS

Data Dictionary

>

FPSAPP Views

> FPSAPP.WIP_WAFER_HIST_LOOP

View FPSBASE.CAL_SHIFTS_PLUS

Combine our shifts/days/weeks/months/quarters/years tables into a useful view.

Column

Comment

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)

END_SHIFT

End of shift must be equal to the start of the next shift. Please note that the exact time which is both of the end of the previous shift and the start of the next shift is included in the next shift. In other words, start_shift <= inst < end_shift. (* inherited from FPSINPUT.CAL_SHIFTS)

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)

WORK_GROUP

Identifies the workforce on the shift so that we can compare performance of the different shifts. If the same people constantly work the same schedule this is the same as work_period. (* inherited from FPSINPUT.CAL_SHIFTS)

WORK_PERIOD

SHIFT_INDEX

0 represents the current shift. 1 is the next shift then 2 follows and so on. -1 is the previous shift and -2 is the shift before that and so on. This column is set automatically by trigger. (* inherited from FPSINPUT.CAL_SHIFTS)

START_WORK_DAY

Work days must be 24 hours in length and the start of the work day must be the start of one of the shifts. Contrast this to plan day which is independent of shift. (* inherited from FPSINPUT.CAL_WORK_DAYS)

END_WORK_DAY

It is critical that this field equal the start_work_day of the next work day. (* inherited from FPSINPUT.CAL_WORK_DAYS)

WORK_DAY

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)

DAY_OF_WEEK

This should be Mon, Tue, etc. (* inherited from FPSINPUT.CAL_WORK_DAYS)

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)

END_WEEK

It is critical that this field equal the start_week of the next work work. (* inherited from FPSINPUT.CAL_WORK_WEEKS)

WORK_WEEK

Name of work week must be unique and can be in any format as long as it is display friendly since this is what we show everywhere. (* inherited from FPSINPUT.CAL_WORK_WEEKS)

WW_SHORT

START_WORK_MONTH

This is the work month not the calendar month. Start of the work month must be the start of a work week and each work week must be within a single work month. (* inherited from FPSINPUT.CAL_WORK_MONTHS)

END_WORK_MONTH

It is critical that this field equal the start_work_month of the next work month. (* inherited from FPSINPUT.CAL_WORK_MONTHS)

WORK_MONTH

Name of work month 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_work_month rather than work_month in case we want to change the naming convention for the work_month. (* inherited from FPSINPUT.CAL_WORK_MONTHS)

WORK_MONTH_DISPLAY

START_WORK_QUARTER

This is the work quarter not the calendar quarter. Start of the work quarter must be the start of a work month and each work month must be within a single work quarter. (* inherited from FPSINPUT.CAL_WORK_QUARTERS)

END_WORK_QUARTER

It is critical that this field equal the start_work_quarter of the next work quarter. (* inherited from FPSINPUT.CAL_WORK_QUARTERS)

WORK_QUARTER

Name of work quarter 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_work_quarter rather than work_quarter in case we want to change the naming convention for the work_quarter. (* inherited from FPSINPUT.CAL_WORK_QUARTERS)

WORK_QUARTER_DISPLAY

START_WORK_YEAR

This is the work year not the calendar year. Start of the work year must be the start of a work quarter and each work quarter must be within a single work year. (* inherited from FPSINPUT.CAL_WORK_YEARS)

END_WORK_YEAR

It is critical that this field equal the start_work_year of the next work year. (* inherited from FPSINPUT.CAL_WORK_YEARS)

WORK_YEAR

Name of work 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_work_year rather than work_year in case we want to change the naming convention for the work_year. (* inherited from FPSINPUT.CAL_WORK_YEARS)

WORK_YEAR_DISPLAY

CORR_PLAN_DAY

CORR_START_PLAN_DAY

CORR_PLAN_WEEK

CORR_START_PLAN_WEEK

CORR_PLAN_MONTH

CORR_START_PLAN_MONTH

CORR_PLAN_MONTH_DISPLAY