FPSAPP.CAL_PLAN_DAYS

START_PLAN_DAY

DATE

N

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.

CALENDAR_DAY

DATE

N

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. (* from FPSINPUT.CAL_WORK_DAYS)

DAY_OF_WEEK

VARCHAR2(3)

N

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

END_PLAN_DAY

DATE

N

It is critical that this field equal the start_plan_day of the next plan day.

PLAN_DAY

VARCHAR2(13)

N

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.

START_PLAN_MONTH

DATE

N

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. (* from FPSINPUT.CAL_PLAN_MONTHS)