data-dictionary
data-dictionary
Breadcrumbs

FPSADMIN.MHS_RACKS

Data Dictionary

>

FPSADMIN Tables

> FPSADMIN.MHS_RACKS

Table FPSADMIN.MHS_RACKS"

This table includes racks, rooms, or any location where a carrier, lot, or durable could be located which are not tools nor ports nor stockers nor vehicles. This is because tools, ports, stockers (including zero footprint storage), and vehicles (including carts and AMHS vehicles) each have their own table.

  • Schema: FPSADMIN

  • Tablespace: FPSDATA

  • Foreign keys: MHS_RACKS_FK_BAY: BAY REFERENCES FPSINPUT.MHS_BAYS (BAY)

  • Referenced by: FPSINPUT.MHS_RACK_LOCATIONS (RACK)


Column

Type

Nullable

Comment

RACK

VARCHAR2(32)

Rack is the parent of location and is where we ask to send the carrier.

BAY

VARCHAR2(12)

N

A bay is a physical area within the building. The bay is important for estimating travel time for a carrier to reach its destination as we usually store these estimates as a matrix of bay-to-bay and assume that the estimated time from any location within one bay to any location within another bay is approximately the same. (* from FPSINPUT.MHS_BAYS)

CLEANUP_IF_FREE_LESS_THAN

NUMBER(3)

If the free space at the rack (measured by total capacity of all locations minus carriers at all locations) is less than this number then we will move carriers away from this station to another storage location with more free space. If this value is 0 then we will never do this.

DESCRIPTION

VARCHAR2(256)

Tool desciption. This value is only used to display in the Dashboard. (* from FPSINPUT.EQP_TOOLS)

IS_OUTPUT_FOR_BAY

CHAR(1)

This flag indicates if this rack qualifies as an output rack for the bay for NextMove.

RACK_DISPLAY

VARCHAR2(32)

N

Optional column to show a user friendly station name on the NextMove GUI which is different that the station name on the barcode.

REQUIRE_LOCATION_SCAN

CHAR(1)

This flag indicates if the rack requires a location scan

UNBLOCK_AFTER_ABORT

CHAR(1)

After a lot aborts processing it has the process state BLOCK and cannot be scheduled. This allows the operator to put on hold or send to rework or otherwise take the appropriate action. Normally this lasts for the period specified in wait_sec_to_sch_after_abort in GEN_FACILITIES. But at many sites if a lot arrives back in a stocker or on certain storage racks then it should no longer be blocked. This flag enables this behavior. It is set for each stocker or rack but most likely will be set to Y for all stockers and/or all input racks if this behavior is desired at the site. Any lot at a location with this flag set to Y will no longer be blocked after abort. Instead it will have process state of WAIT and will be available to schedule on any tool. (* from FPSINPUT.MHS_STOCKERS)