Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSAPP.CTR_B_ORIG_PRD
This view is used to pick a *single* start/original PRD to display for each finished PRD in CTR. It replaces the ORIG_FACILITY, ORIG_PRD columns that used to be in FPSINPUT.RTG_PRDS. It picks the alphabetically highest START_PRD from the facility with the lowest SORT_ORDER. (The rationale is that, when a PRD is replaced by a newer version, its suffix is typically incremented, as in XYZ_01 to XYZ_02.) This is only an approximation, because a PRD in a multi-facility flow can clearly have multiple starting PRDs.
|
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) |
|
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) |
|
ORIG_PRD |
|
|
ORIG_FACILITY |
See comments in OTHER_FACILITY column (* inherited from FPSINPUT.RTG_ROUTE_STEPS) |