data-dictionary

FPSINPUT.CAL_PLAN_MONTHS_PLUS

Data Dictionary

>

FPSINPUT Views

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSBASE.CAL_PLAN_MONTHS_PLUS

Combine our months/quarters/years table into a useful view.

Column

Comment

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

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)

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)

CORRESPONDING_START_WORK_MONTH

This is the start of the work month which most closely corresponds with this plan month. We prefer that plan and work calendars are identical so this would be equal to start_plan_month but if they are off we need to be able to match them as close as possible using this field. (* inherited from FPSINPUT.CAL_PLAN_MONTHS)

START_PLAN_QUARTER

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

END_PLAN_QUARTER

It is critical that this field equal the start_plan_quarter of the next plan quarter. (* inherited from FPSINPUT.CAL_PLAN_QUARTERS)

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_QUARTER_DISPLAY

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

START_PLAN_YEAR

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

END_PLAN_YEAR

It is critical that this field equal the start_plan_year of the next plan year. (* inherited from FPSINPUT.CAL_PLAN_YEARS)

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)

PLAN_YEAR_DISPLAY