FPSBASE.WIP_CTM_FORECAST

FACILITY

VARCHAR2(6)

N

Facility is included in almost every join in the DWH so this represents a definitive split. A route must have all steps on tools in the same facility. A tool must process all lots in the same facility. If your site has multiple buildings where lots run on routes using tools in multiple buildings then everything should be one facility. For example, multiple Fab buildings. But if your site has independent facilities like Fab and Test and Assembly where lot may progress from one to the next but on different routes then these should be different facilities. Since this column is in virtually every table it is critical that the value here is exactly matches what is in the MES if the MES has facility. Use facility_display for the display friendly name displayed in applications. See site_name comment for client/site/facility example. (* from FPSINPUT.GEN_FACILITIES)

PRD

VARCHAR2(64)

N

Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* from FPSINPUT.RTG_PRDS)

PERIOD_LABEL

VARCHAR2(64)

N

Label of the week, month, quarter, or year to display on FLCT application. Note this is also part of the primary key of this table.

CTM_FORECAST_COMMIT_DAYS

NUMBER(5,1)

This column has the same meaning as COMMIT_CT_DAYS but it is a forecasted value starting at a specified time in the future.

CTM_FORECAST_TARGET_DAYS

NUMBER(5,1)

This column has the same meaning as TARGET_CT_DAYS but it is a forecasted value starting at a specified time in the future.

IS_CONTIGUOUS

CHAR(1)

Since this table accepts different period types to display on FLCT we might need to choose only certain values to represent the forecasted cycle time for this prd over time. For example, we might have weekly values and then a value for the entire upcoming year and in this case all of the weekly values would be Y and the year value would be N so we would ignore the year value for all uses other than displaying it.

PERIOD_SORT_ORDER

NUMBER(4)

This column is only to sort the periods in the FLCT application. Normally this will match the period_start_inst but when sites has multiple period types like months and years then it is nice to be able to control the sort order.

PERIOD_START_INST

DATE

N

Start of period when this forecasted total cycle time applies. We assume it applies from this period until the next period_start_inst for the same prd and period type.