FPSINPUT.STD_WIP_LOTS_FAST_FROM_ETL

Data Dictionary

FPSINPUT Views

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSINPUT.STD_WIP_LOTS_FAST_FROM_ETL

The WIP_LOTS_FAST_FROM_ETL view must return the six basic fields of lot_type, plan_priority, facility, prd, planprd, and qty which may be left blank in the actual event but are required to be populated in WIP_EVENT_HIST by the trigger. This STD version is a template for how to write this view. It should exist at all sites where our ETL is by database link because it prevents incorrect information in events for new lots. It is neither necessary nor possible to create this at sites where ETL uses APF. This view must be fast when filtered for a single lot as that is how it is used in the trigger. It is extremely likely that WIP_LOTS_FAST_FROM_ETL should also be your base for both WIP_REF_LOTS_STATIC and WIP_REF_LOTS_VERIFY. At most sites you might have another view like LOAD_LOT_BASE which uses WIP_LOTS_FAST_FROM_ETL and then add some information which takes longer to obtain but is required for the WIP_REF_LOTS view. Again it is important to emphasize that WIP_LOTS_FAST_FROM_ETL must be lightning fast when filtered for one lot.

Column	Comment
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)
LOT_TYPE	Lot_type is the base of the hierarchy that determines lot_family then lot_group. Ideally lot_type will come straight from the MES with little modification. (* inherited from FPSINPUT.WIP_LOT_TYPES)
PLAN_PRIORITY	Permanent priority of the lot set in the MES generally by planning. (* inherited from FPSINPUT.WIP_EVENT_HIST)
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)
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)
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)
QTY	Quantity of units in the lot according the qty_unit defined for the facility. It is required for all lots in each facility to have their qty defined in the same units therefore the change in the unit is critical to defining the facility. For example, a pretest facility might have a sort step in the middle where we learn the qty of die. Prior to this step we know only the wafer qty but after this step we know both wafer and die. Since wafer is the only qty we know throughput the flow then wafer must be defined as the qty unit for this facility. Die can then be populated as sec_qty when it is known. Similarly the wafer saw facility might have a step in the middle where we cut the wafers into die. After this step we no longer know the number of wafers which means that die must be the qty unit for this facility and wafers can be the sec_qty prior to the saw step. Please note that a lot with qty of 0 is allowed but only if the sec_qty is greater than 0. This is unusual but one case is where we know the wafers will be scrapped but cannot be scrapped quite yet. (* inherited from FPSINPUT.WIP_EVENT_HIST)