data-dictionary
data-dictionary
Breadcrumbs

FPSINPUT.MHS_CARRIER_CLASSES

Data Dictionary

>

FPSINPUT Tables

> FPSINPUT.MHS_CARRIER_CLASSES

Table FPSINPUT.MHS_CARRIER_CLASSES"

List of FPS defined values allowed for the carrier class. Restricting carrier_class to a value defined in this table allows our applications to make specific references to these values.

  • Schema: FPSINPUT

  • Tablespace: FPSDATA

  • Primary key: CARRIER_CLASS


Column

Type

Nullable

Comment

CARRIER_CLASS

VARCHAR2(13)

N

Carrier class indicates what the carrier is able to carry. It is also an important field in EQP_PORTS but each port has a single defined carrier class and only carriers of this class should go to the port. The value must be one of those defined by FPS in FPSADMIN.MHS_CARRIER_CLASSES which include POD or CAST or BOX. This would be used as a filter on what carriers could be selected when a carrier is needed. For example, when a lot is split we need to find another carrier for the split lot and we select the best carrier in the carrier_class of CAST. But if we need to unload a reticle then we select the best carrier in the carrier_class of POD. (* from FPSINPUT.MHS_CARRIERS)

ALLOWED_TO_SCAN

CHAR(1)

In order to scan a carrier on a rack or cart in NextMove, the carrier must be in NMV_P_CARRIER_SUMMARY because this view is used for identifying carriers and displaying the info once it has been scanned. This column should always be set to Y for LOT, CAST, and BOX and always set to N for DURABLE and TOOL. POD is normally set to N but at sites where we want to allow pods to be scanned this value would be changed to Y.