FPSBASE.RTG_PRDS

FACILITY

VARCHAR2(6)

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)

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.

ACTIVE_VERSION

VARCHAR2(12)

This field is optional and is not used by any other FPS DWH objects but it is frequently used in ETL so if the MES uses versioning for prd then it is useful to put here.

COMMIT_CT_DAYS

NUMBER(5,1)

Number of days of cycle time committed to the customer for the prd or bank. This commit is published externally. This should be greater than or equal to the target. (* from FPSINPUT.RTG_BANKS)

DEFAULT_PLANPRD

VARCHAR2(64)

The normal or most frequently used planprd for this prd. At most sites each prd will only use one planprd which is this default_planprd but multiple planprds is allowed. For detailed information, see table comments in RTG_PLANPRDS.

DESCRIPTION

VARCHAR2(256)

Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS)

GROSS_DIE_PER_WFR

NUMBER(6)

Expected gross die per wafer for the product. This is a critical field for planning die shipments. Note this is gross so we multiply by line yield and by sort yield for remaining steps of remaining products.

KEEP_ACTIVE

CHAR(1)

Manual flag to keep record active even if no activity for the prd-route

LINE_SECTION_IF_NO_MAIN_RT

VARCHAR2(32)

Line section is in RTG_ROUTE_STEPS but the Dashboard uses this filter for the bank spotlight too so this allows us to put lots of this prd which are in a bank and not on a main route into a specific line section.

OUTSIDE_SOURCE

VARCHAR2(50)

For all PRDs that are externally sourced (e.g. purchased or produced at an external site), this field describes their source.

OVR_BG_COLOR

VARCHAR2(24)

This column defines the override color used in Dashboard reports for displaying WIP qtys by Prd

OVR_PROC_CT_DAYS_FOR_FLCT_XF

NUMBER(5,1)

Some sites prefer to use a fixed number for the processing time of each prd in the denominator of their X-Factor calculation. The FLCT app will use this value if populated in the X-Factor calculation instead of the calculation processing time. For sites which combine prd in the same facility to report a sequence of prds in FLCT, this value must be populated for the last prd in the same sequence but it should have the value of the total processing time for all prds in the sequence.

OVR_RORP

VARCHAR2(256)

The Capacity Model does its calculations by rorp, step. In FPSBASE.RTG_PRDS_PLUS, rorp is set to prd by default if ovr_rorp is null. Populating ovr_rorp in the ETL (with route, for example) will override the default and set rorp = ovr_rorp.

PRD_MSO_GROUP

VARCHAR2(64)

Product group to be used for the Metrology Sampling Optimizer, generally based on similarity of technology or volume.

PRD_TO_USE_FOR_CT

VARCHAR2(64)

We often have many prds and routes which are similar and we want to report CT as a group and we can use this field for this. You either enter the target_ct_days and commit_ct_days or you enter prd_to_use_for_ct to use the target and commit for another prd. For example we have prds A and B which are similar. You enter 80 days as target and commit for A then enter A as the prd_to_use_for_ct for B. Then all lots of A and B will be reported with the CT for A and we will not report CT for B.

PRD_TO_USE_FOR_PROBE_CARD

VARCHAR2(64)

Use value from another product for the probe card required

PRODUCT_SCORE

NUMBER(2)

Scheduler Evaluation slider value for product priority slider

RETICLE_SET

VARCHAR2(64)

Reticle set used for the product.

ROUTE

VARCHAR2(256)

Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)

SMP_GROUP

VARCHAR2(64)

Product group to be used for sampling, generally something like high/medium/low based on volume of the product.

TARGET_CT_DAYS

NUMBER(5,1)

Number of days of cycle time targeted for the prd or bank. This target is only published internally which often means it is not even published to corporate planning. This should be less than or equal to the commit. (* from FPSINPUT.RTG_BANKS)

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)