data-dictionary

FPSADMIN.NMV_W_MY_LIST_TILES

Data Dictionary

>

FPSADMIN Tables

> FPSADMIN.NMV_W_MY_LIST_TILES

Table FPSADMIN.NMV_W_MY_LIST_TILES"

A table that contains the objects per LIST_ID for My lists feature within NextMove

  • Schema: FPSADMIN

  • Tablespace: FPSDATA

  • Primary key: LIST_ID, FACILITY, OBJ_ID, OBJ_TYPE


Column

Type

Nullable

Comment

LIST_ID

NUMBER

N

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)

OBJ_ID

VARCHAR2(16)

N

OBJ_TYPE

VARCHAR2(30)

N

COORD_X

NUMBER(2)

This is the x coordinate position of the location within its station, in other words horizontal position. The maximum coord_x is the width of the station. This is optional and is often used for racks and sometimes for carts so we can determine the exact position of the carrier to make it easier to find. (* from FPSINPUT.MHS_RACK_LOCATIONS)