Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSINPUT.STD_RTG_REF_COMMON_STEPS
This view is a template for a standard way to build RTG_COMMON_STEPS. It sorts common steps based on weighted cycle time across routes and then divides them into 10 facility segments based on cycle time. This view may be used as is or slightly modified for the site or not used at all if the site has its own logic. If you use this logic as is then just make a wrapper view so that any future changes to the STD logic will be automatically used: CREATE VIEW FPSINPUT.RTG_REF_COMMON_STEPS AS select (slash)* We use the standard logic for RTG_COMMON_STEPS so we do not include any history comment here. *(slash) facility, common_step, common_step_sort, facility_segment from fpsinput.std_rtg_ref_common_steps; In addition, if you use this view, you must disable RTG_ROUTE_STEPS_FK_COMMON_STEP like this: insert into fpsadmin.cfg_disabled (object_name, why_disabled, is_permanent) values ('RTG_ROUTE_STEPS_FK_COMMON_STEP', 'Since we build RTG_COMMON_STEPS based on RTG_ROUTE_STEPS here we must disable this foreign key since we will have the new common_step in RTG_ROUTE_STEPS before it will be in RTG_COMMON_STEPS.', 'Y'); alter table fpsinput.rtg_route_steps disable constraint RTG_ROUTE_STEPS_FK_COMMON_STEP;
|
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) |
|
COMMON_STEP |
A display-friendly field that groups similar steps together for purposes of viewing the entire line. Typically the only duplicates within a single route will be optional ordered steps in the same segment. But we will often have steps across routes that share the same common step even though exact step definition is not identical. (* inherited from FPSINPUT.RTG_COMMON_STEPS) |
|
COMMON_STEP_SORT |
How to sort common_step when displaying together for multiple routes in the same view. This must be unique for the entire facility so that we know how to order common_step when viewing the entire facility. (* inherited from FPSINPUT.RTG_COMMON_STEPS) |
|
FACILITY_SEGMENT |
Facility segment is the parent of common step and is used as the highest level grouping when we show WIP for a route group or the entire facility where we cannot use route segment. We would prefer somewhere between 8 and 20 facility segments. Typically we will have to define these (as opposed to route_segment which we will typically come from the MES). There is no RTG_FACILITY_SEGMENTS table because sorting of facility segments is determined by common_step_sort. A trigger on RTG_COMMON_STEPS ensures that facility segments are contiguous when the entire facility is sorted by common step. (* inherited from FPSINPUT.RTG_COMMON_STEPS) |