FPSBASE.DASH_P_CAL_PLAN_DAYS

PLAN_DAY

Name of plan day 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_day rather than plan_day in case we want to change the naming convention for the plan_day. (* inherited from FPSINPUT.CAL_PLAN_DAYS)

START_PLAN_DAY

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

END_PLAN_DAY

It is critical that this field equal the start_plan_day of the next plan day. (* inherited from FPSINPUT.CAL_PLAN_DAYS)

DAY_OF_WEEK

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

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_INDEX

IS_PREVIOUS_DAY

IS_CURRENT_DAY

PLAN_WEEK

Name of plan 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_PLAN_WEEKS)

START_PLAN_WEEK

Plan weeks must be 7 days in duration and the start of the plan week must be the start of one of the plan days. (* inherited from FPSINPUT.CAL_PLAN_WEEKS)

END_PLAN_WEEK

It is critical that this field equal the start_plan_week of the next plan week. (* inherited from FPSINPUT.CAL_PLAN_WEEKS)

PLAN_MONTH

Name of plan 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_plan_month rather than plan_month in case we want to change the naming convention for the plan_month. (* inherited from FPSINPUT.CAL_PLAN_MONTHS)

START_PLAN_MONTH

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

END_PLAN_MONTH

It is critical that this field equal the start_plan_month of the next plan month. (* inherited from FPSINPUT.CAL_PLAN_MONTHS)

PLAN_MONTH_DISPLAY

Particularly at sites which use a fiscal year starting in July we might want to show a longer month in certain places that includes the fiscal month and calendar month for clarity. (* inherited from FPSINPUT.CAL_PLAN_MONTHS)

PLAN_QUARTER

Name of plan 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_plan_quarter rather than plan_quarter in case we want to change the naming convention for the plan_quarter. (* inherited from FPSINPUT.CAL_PLAN_QUARTERS)

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)

WEEK_INDEX