Data Dictionary
>
FPSAPP Views
> FPSAPP.WIP_WAFER_HIST_LOOP
View FPSAPP.MSOUI_P_DISASSOCIATED_TAG_COND
View provides a list of the rules that have been disassociated from a tag conditions
|
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) |
|
TAG_CONDITION_ID |
Unique tag condition identification number. (* inherited from FPSBASE.MSO_TAG_CONDITIONS) |
|
SMP_RULE_ID |
The tag condition that corresponds with the specified sample rule. This must already be defined in MSO_EXTL_TAG_CONDITIONS. (* inherited from FPSINPUT.MSO_EXTL_RULE_TAG_COND) |
|
UPDATED_INST |
Time when the record was updated according to the source data. Note this is not the time when the record was actually updated in this table - it will almost always be earlier. (* inherited from FPSINPUT.GEN_FACILITIES) |
|
USER_ID |
The user Id that initiated the last move of this carrier (* inherited from FPSINPUT.MHS_CARRIERS) |