Data Dictionary
>
FPSINPUT Tables
> FPSINPUT.GEN_FACILITY_BUILDINGS
Table FPSINPUT.GEN_FACILITY_BUILDINGS"
List of buildings associated with each facility. This is an important table because the NextMove application is separate for each facility. For the facility selected, only bays, vehicles, racks, and locations in these buildings will be visible. This is a many-to-many relationship so it requires a separate table. in each site.
-
Schema: FPSINPUT
-
Tablespace: FPSDATA
-
Primary key: FACILITY, BUILDING
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
FACILITY |
VARCHAR2(6) |
N |
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. (* from FPSINPUT.GEN_FACILITIES) |
|
BUILDING |
VARCHAR2(12) |
N |
Building is the top of our MHS hierarchy at each site. It is independent of facility which is at the top of our EQP/RTG hierarchy. It is possible for a building to include multiple facilities and for a facility to include multiple buildings but we do not even need to define these relationships because EQP_TOOLS determines this by the combination of the facility and bay columns (since bay points to building). (* from FPSINPUT.MHS_BUILDINGS) |