Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSAPP.DASH_P_H_WIP_STEP_PROC_STATES
Process state level breakdown for each lot and step. This has one row per process state and only includes process states that are > 0 seconds. This will be used to display the step cycle time for each lot. We assume that this data will be grouped appropriately in the Dashboard so we do not group here. In other words, we could have multiple rows for the same process_state during the same step if a lot was in the same process_state more than once during the step.
|
Column |
Comment |
|---|---|
|
STEP_ENT_INST |
Time when the lot entered the step. (* inherited from FPSBASE.WIP_LOT_HIST) |
|
STEP_COMPLETE_INST |
|
|
LOT_SEQ_WITHIN_SEC |
For rows with identical timestamps, sequence records to get proper sequence (* inherited from FPSINPUT.WIP_EVENT_HIST) |
|
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) |
|
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) |
|
ROUTE |
Route that has threading requirements (* inherited from FPSINPUT.RTG_STEP_THREADING) |
|
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) |
|
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) |
|
IS_CURRENT_STEP |
|
|
PROCESS_STATE_SEC |
|
|
PROCESS_STATE |
Process state is the most commonly used level of our Enhanced Cycle Time hierarchy. This displays on Dashboard, Scheduler, Cycle Time Analyzer, and Finished Lot Cycle Time Reporter. Process state is the parent of ECT state, however, there is configuration for when to show the process state of Reserved in each application which is done in WIP_ECT_STATES. (* inherited from FPSADMIN.WIP_PROCESS_STATES) |
|
PROCESS_STATE_DISPLAY |
|
|
PROCESS_STATE_HTML_COLOR |
|
|
PROCESS_STATE_HTML_TEXT_COLOR |
|
|
PROCESS_STATE_SORT_ORDER |