data-dictionary

FPSADMIN.RM_P_CARRIERS

Data Dictionary

>

FPSADMIN Views

> FPSADMIN.WIP_WAFER_HIST_LOOP

View FPSAPP.RM_P_CARRIERS

the carriers, here it only binds the carriers with the carrier assignments, for those not dedicated the carriers, it is fine not to bring to the scheduler.

Column

Comment

FACILITY

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

CARRIER

RFID of the cassette or FOUP the lot is currently in. (* inherited from FPSINPUT.MHS_CARRIERS)

CARRIER_CLASS

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

CARRIER_FAMILY

DURABLE_CAPACITY

CURR_LOCATION

store the curr location of the lot (* inherited from FPSAPP.SCH_W_H_S_LOTS)

CURR_LOCATION_DISPLAY

CURR_STATION

See column comment on STATION in FPSINPUT.MHS_STATION_ALTERNATES for more information. (* inherited from FPSINPUT.MHS_DELIVERY_NEXT)

CARRIER_STATE

Carrier state indicates the current state of the carrier. The value must be one of those defined by FPS in FPSADMIN.MHS_CARRIER_STATES. This is a very short list of simple states like OK or WARN or DOWN in contrast to the complex options available for equipment states. This would be used as a filter/sort 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 would prefer one with state of OK then WARN but we could not choose one which was DOWN. (* inherited from FPSINPUT.MHS_CARRIERS)

CARRIER_STATE_DISPLAY

The name of the carrier_state displayed on all dashboards and reports. Carrier_state must match the FPS list defined in MHS_CARRIER_STATES but this display field might be formatted in a more familiar way to the users in the facility. (* inherited from FPSINPUT.MHS_CARRIERS)

IS_CLAIMED

CLAIMED_TOOL

CLAIMED_START

CLAIMED_END

CLAIMED_BY

SHOULD_DISPLAY

ASSIGNED_TOOL