FPSAPP.SCH_P_DISPATCH_DURABLES

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)

DURABLE

VARCHAR2(64)

N

Durables are either reticles for Litho or probe cards for Wet or Sort. A durable can either be in a carrier or at a location without a carrier. (* from FPSINPUT.RTG_DURABLES)

SCHED_SORT

NUMBER(3)

N

The sorting used by the scheduler to prioritize lots. This is more generic than priority_sort as different priorities may have the same sched_sort. (* from FPSINPUT.WIP_PRIORITIES)

ACTION_TIME

DATE

ACTION_TOOL

VARCHAR2(16)

CARRIER

VARCHAR2(32)

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

CARRIER_ASGN_TOOL

VARCHAR2(16)

CARRIER_CLASS

VARCHAR2(13)

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)

CURR_PROCESS_STATE

VARCHAR2(5)

CURR_PROCESS_STATE_SORT

NUMBER(2)

DURABLE_STATE

VARCHAR2(36)

Durable state indicates the current state of the durable The value must be one of those defined by FPS in FPSADMIN.MHS_CARRIER_STATES. This is a 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 durables could be used for scheduling. For example, if there are two durables in the durable_family and one is OK and the other is DOWN then we schedule using the OK durable. But if there is only one durable in the family then we cannot schedule any lots which require this family if that lone durable is DOWN. (* from FPSINPUT.RTG_DURABLES)

DURABLE_STATE_DISPLAY

VARCHAR2(128)

The name of the durable state displayed on all dashboards and reports. Durable_state must match the FPS list defined in MHS_DURABLE_STATES but this display field might be formatted in a more familiar way to the users in the facility. (* from FPSINPUT.RTG_DURABLES)

FIRST_SCHED_START

DATE

LOCATION

VARCHAR2(32)

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)

MOVE_ACTION

VARCHAR2(8)

MOVE_DESTINATION

VARCHAR2(16)

MOVE_SCHEDULE

DATE

NEW_MOVE_ACTION

VARCHAR2(8)

NEW_MOVE_SCHEDULE

DATE

NUM_DRBL_CURR_ON_TOOL

NUMBER(3)

NUM_LOTS

NUMBER(3)

NUM_LOTS_RESV

NUMBER(3)

RETICLE_LIBRARY_CAPACITY

NUMBER(3)

SCHED_LOTS

VARCHAR2(2000)

STATION

VARCHAR2(32)

The rack, bay, building, tool, cart, or stocker which has alternately acceptable stations (* from FPSINPUT.MHS_STATION_ALTERNATES)