Data Dictionary
>
FPSBASE Views
> FPSBASE.WIP_WAFER_HIST_LOOP
View FPSBASE.CHK_REF_WSF_LOTS_TO_FIX
This stores lots where WIP_SMP_FUTURE or RTG_ROUTE_STEPS or RTG_TOOL_ASSIGNMENTS_LOT has been updated after WIP_STEP_FUTURE in a way that requires an update to WSF. This query can be slow so we refresh this table outside of the RealTime job and then use the results in two sections of the ADM_FIX_WIP_STEP_FUTURE procedure which must run in the RealTime job since it updates WIP_STEP_FUTURE. The ALL section call UPDATE_WIP_STEP_FUTURE procedure to fully refresh all records for the lot. The SINGLE section goes in a merge statement to update individual records.
|
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) |
|
SINGLE_OR_ALL |
|
|
PROBLEM |
|
|
WSF_INST |
|
|
NUM_SEQ_AWAY |
Number of steps away including all steps which will or might be skipped. We name this column seq because it is just the delta in seq_num between the current step and the future step. (* inherited from FPSBASE.WIP_STEP_FUTURE) |
|
STEP |
A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* inherited from FPSINPUT.RTG_ROUTE_STEPS) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
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) |
|
OLD_PROCESS |
|
|
OLD_PROCESS_GROUP |
|
|
OLD_SCHED_GROUP |
|
|
NEW_PROCESS |
|
|
NEW_PROCESS_GROUP |
|
|
NEW_SCHED_GROUP |