data-dictionary

FPSAPP.MHS_VEHICLE_LOCATIONS

Data Dictionary

>

FPSAPP Tables

> FPSAPP.MHS_VEHICLE_LOCATIONS

Table FPSAPP.MHS_VEHICLE_LOCATIONS"

This table is optional and should only be populated if we want to specify multiple locations on a vehicle, usually a cart. If this table is blank then we just consider the vehicle to be the location and the station.

  • Schema: FPSAPP

  • Tablespace: FPSDATA

  • Primary key: LOCATION

  • Foreign keys: MHS_VEHICLE_LOCATIONS_FK: VEHICLE REFERENCES FPSINPUT.MHS_VEHICLES (VEHICLE)


Column

Type

Nullable

Comment

LOCATION

VARCHAR2(32)

N

Location of a carrier or lot or durable which comes directly from the tracking system used at the site. This could be a port or internal tool location or tool or rack or stocker or zero footprint storage or room or really anywhere. Many non-automated sites allow users to manually enter locations into their system. Therefore unless we know for sure that the source data implements a size limitation, it is recommended to always trim the value in the ETL to 32 characters to fit into the column size and avoid load errors. For ports, location is the full name of the port which is unique across the entire site and usually includes the tool name. Please see the comment in the port column which explains the difference between location and port. Rack locations are similar. (* from FPSINPUT.MHS_RACK_LOCATIONS)

CAST_CAPACITY

NUMBER(3)

Maximum number of cassettes that can be stored. We define cassette as a carrier for a lot. (* from FPSINPUT.MHS_RACK_LOCATIONS)

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)

COORD_Y

NUMBER(2)

This is the y coordinate position of the location within its station, in other words vertical position or shelf number. The maximum coord_y is the height 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)

COORD_Z

NUMBER(1)

This is the z coordinate position of the location within its station, in other words front-to-back position. This is usually 1. The maximum coord_z is the depth 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)

IS_EXTRA_SCAN_BUFFER

CHAR(1)

This column allows you to bifurcate locations into 2 types. 1st is a real location that represents a physical spot, this is the default N value. The 2nd is if this location is not actually real and just being used to give extra space for whatever reason you may need it. If this is set to Y then it will not add to the cast_capacity displayed in the Dashboard.

LOC_ON_VEHICLE

VARCHAR2(5)

This is the short name of the location on the vehicle, probably named something simple like S1, S2, etc. but perhaps if the vehicle has two levels perhaps A1, A2, B1, B2, etc. This field is unique within the given vehicle and is used to save space when we already know the vehicle, for example on the vehicle NextMove tablet. This column is in contrast to the location field which is the full name of the location. Location is unique within the entire site and almost always includes the vehicle name. Location is what is in MHS_CARRIERS and gets set when a carrier is placed on the vehicle.

POD_CAPACITY

NUMBER(3)

Maximum number of pods that can be stored. We define pod as a carrier for a durable. (* from FPSINPUT.MHS_RACK_LOCATIONS)

UPDATED_INST

DATE

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. (* from FPSINPUT.GEN_FACILITIES)