data-dictionary
data-dictionary
Breadcrumbs

FPSAPP.WFM_B_DEMAND_BY_PLANPRD

Data Dictionary

>

FPSAPP Views

> FPSAPP.WIP_WAFER_HIST_LOOP

View FPSAPP.WFM_B_DEMAND_BY_PLANPRD

This is a query to the WIP_FLUSH table which demonstrates its demand planning capability for planprds where demand is populated in the WIP_DEMAND table. Currently we only use this as a reference for clients to use in their own custom reports but we might add something to our WIP Flush application in the future. It filters for a particular facility+planprd+lot_group+bank because this is how we group the lots for demand planning. Lot_group is usually something like Prod or PROD and bank should nearly always be NA for this query. It selects the appropriate columns use for demand planning and sorts appropriately by cum_planprd_qty_eol.

Column

Comment

FACILITY

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

PLANPRD

Planning product used for all planning purposes. All lots with the same planprd are interchangeable to ship to the customer regardless of their prd, route, technology, wafer size, etc. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* inherited from FPSINPUT.RTG_PLANPRDS)

PRD

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

BANK

Lots which are not on a route are considered in a bank and the bank name indicates why the lot is off route. Bank must be NA for lots which are on a route. Our standard filter for active lots is bank = NA. (* inherited from FPSINPUT.RTG_BANKS)

LOT_GROUP

Lot_group is a grouping of lot_family and is the highest grouping in the lot type hierarchy. There should be only a few values for lot_group, i.e. Prod, Dev, TW. We group WIP and moves by lot_group on the dashboard and we group cycle time calculations by lot_group so this is an important field. (* inherited from FPSINPUT.WIP_LOT_GROUPS)

LOT

A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* inherited from FPSINPUT.WIP_LOTS_STATIC)

FLUSH_SEQ_NUM

Flush sequence number is the order of main routes and banks for the lot from current to the final flushed product. 1 is always the current main route or bank. (* inherited from FPSBASE.WIP_FLUSH)

EST_QTY_AT_EOL

The estimated quantity when the lot finishes the route/bank listed in units of the facility listed. The calculation is based on line yield from the current step to the end of the route/bank listed. So if the route/bank is in the future then the upcoming routes/banks starting with the current one are included since we expect those wafers to be lost between now and the end of the future route/bank listed. This does not include sort yield. (* inherited from FPSBASE.WIP_FLUSH)

CUM_PLANPRD_QTY_EOL

Cumulative qty for the specified planprd of the specified main route or bank. This counts from the finish so if we have a several lots with 25 units then the closest to the finish would be 25 and the next closest would be 50 then 75 and so on. We match this with the demand for the prd to determine when each lot is needed to meet demand. (* inherited from FPSBASE.WIP_FLUSH)

CUM_DEMAND

DEMAND_WW_QTY

START_PLAN_WK_DEMAND

DEMAND_INST

Start of period when this qty of this planprd needs to finish. We automatically spread demand across each plan week in WIP_DEMAND_BY_WEEK which feeds WIP_FLUSH therefore this column can be the start of any time period less than or equal to plan week. It could be the demand for each shift or for each day or for each plan week but if the site has no preference then the easiest way to set this up is to write one row per plan week and let us spread across that week. It is important to note that we always spread across the plan week with our custom logic so even if this table is by day we might adjust it to another day within the same plan week. (* inherited from FPSINPUT.WIP_DEMAND)

REORDER_MESSAGE

FLUSH_SEQ_DESC

Flush sequence descending is the order of main routes and banks for the lot from final flushed product back to the current. 1 is always the last main route or bank for the final flushed product. (* inherited from FPSBASE.WIP_FLUSH)

CURR_FACILITY

Current facility of the lot. (* inherited from FPSBASE.WIP_FLUSH)

CURR_FAC_PRD

Current product of the lot. (* inherited from FPSBASE.WIP_FLUSH)

CURR_FAC_BANK

Current bank of the lot (NA if lot is currently on a route). (* inherited from FPSBASE.WIP_FLUSH)

CURR_FAC_STEP

Current step of the lot on its current main route (NA if lot is currently in a bank). (* inherited from FPSBASE.WIP_FLUSH)

IS_START

Boolean flag where Y indicates the lot is an upcoming start and not an existing lot. (* inherited from FPSBASE.WIP_FLUSH)

START_INST_ORIG_FAC

EOL_INST_FULL_WAVG

Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the Full period. (* inherited from FPSBASE.WIP_FLUSH)

EOL_INST_7D_WAVG

Date/time when the lot is estimated to finish the specified route/bank using weighted average cycle time from the last 7 days. (* inherited from FPSBASE.WIP_FLUSH)

EOL_INST_7D_MED

Date/time when the lot is estimated to finish the specified route/bank using median cycle time from the last 7 days. (* inherited from FPSBASE.WIP_FLUSH)

CURR_QTY

Current qty of the lot using quantity unit of the current facility. (* inherited from FPSBASE.WIP_FLUSH)

CURR_SEC_QTY

Current secondary qty of the lot using secondary quantity unit of the current facility. (* inherited from FPSBASE.WIP_FLUSH)

GROSS_DIE_PER_WFR

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

LINE_YIELD_PCT

Sort yield percentage from the current step to the finish of the specified route/bank. If the route/bank is not the current one then this included all steps. (* inherited from FPSBASE.WIP_FLUSH)

SORT_YIELD_PCT

Line yield percentage from the current step to the finish of the specified route/bank. If the route/bank is not the current one then this included all steps. (* inherited from FPSBASE.WIP_FLUSH)