FPSAPP.GEN_DATA_DATE

ONE_ROW

NUMBER(1)

A column whose value is 1 which is the primary key of the table ensuring only one row. (* from FPSINPUT.GEN_SITE)

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)

DATA_DATE_VALUE

DATE

N

This column is unusually named DATA_DATE_VALUE to avoid confusion with the frequently used DATA_DATE function. Normally we just use the function but occasionally we might want to get the column from the table rather than the function and this allows us to do this.

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

END_PLAN_WEEK

DATE

N

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

END_SHIFT

DATE

N

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

END_WEEK

DATE

N

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

END_WORK_DAY

DATE

N

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

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

PLAN_MONTH

VARCHAR2(9)

N

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

PLAN_QUARTER

VARCHAR2(6)

N

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

PLAN_WEEK

VARCHAR2(7)

N

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

PLAN_YEAR

VARCHAR2(6)

N

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

SHIFT

VARCHAR2(13)

N

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

START_LAST_PLAN_DAY

DATE

N

START_LAST_PLAN_WEEK

DATE

N

START_LAST_SHIFT

DATE

N

START_LAST_WEEK

DATE

N

START_LAST_WORK_DAY

DATE

N

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

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)

START_PLAN_QUARTER

DATE

N

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

START_PLAN_WEEK

DATE

N

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

START_PLAN_YEAR

DATE

N

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

START_SHIFT

DATE

N

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

START_WEEK

DATE

N

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

START_WORK_DAY

DATE

N

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

START_WORK_MONTH

DATE

N

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

START_WORK_QUARTER

DATE

N

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

START_WORK_YEAR

DATE

N

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

UPDATED_INST

DATE

Time when the record was updated according to the source data. Note this is not the time when the record was actually updated in this table - it will almost always be earlier. (* from FPSINPUT.GEN_FACILITIES)

WORK_GROUP

VARCHAR2(6)

N

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

WORK_MONTH

VARCHAR2(9)

N

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

WORK_PERIOD

VARCHAR2(6)

N

WORK_QUARTER

VARCHAR2(6)

N

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

WORK_WEEK

VARCHAR2(7)

N

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