FPSINPUT.MHS_CARRIER_LOCATION_HIST

CHG_TIMESTAMP

TIMESTAMP(4)

N

For CHGLOG and automatic HIST tables, this is populated with SYSTIMESTAMP. This means that this record existed in the original table from this time until NEXT_CHG_TS. (* from FPSINPUT.EQP_PORT_HIST)

CARRIER

VARCHAR2(32)

N

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

ACTION

VARCHAR2(1)

For CHGLOG and automatic HIST tables, this is I for insert or U for updated or D for delete. (* from FPSINPUT.EQP_PORT_HIST)

AMHS_DESTINATION

VARCHAR2(24)

The destination of a carrier when in transit or when a move is requested. This is an optional input value that comes from the AMHS. It is not where the carrier needs to go which we decide in MHS_DELIVERY_NEXT but rather where it is already going in the AMHS. If this value is blank then we know the carrier has no move requested. (* from FPSINPUT.MHS_CARRIERS)

AMHS_VEHICLE

VARCHAR2(24)

The vehicle used to move a carrier when in transit or when a move is requested. This is an optional input value that comes from the AMHS. It is not the cart which should be used which we decide in MHS_DELIVERY_NEXT. (* from FPSINPUT.MHS_CARRIERS)

DB_MACHINE

VARCHAR2(64)

For CHGLOG and automatic HIST tables, this is populated with the HOST system variable from USERENV. (* from FPSINPUT.EQP_CHAMBERS_CHGLOG)

DB_OSUSER

VARCHAR2(30)

For CHGLOG and automatic HIST tables, this is populated with the OS_USER system variable from USERENV. (* from FPSINPUT.EQP_CHAMBERS_CHGLOG)

DB_USERNAME

VARCHAR2(30)

For CHGLOG and automatic HIST tables, this is populated with the USER system variable. (* from FPSINPUT.EQP_CHAMBERS_CHGLOG)

DEST_STATION

VARCHAR2(32)

The final destination the lot is required to move. Typically the reserved tool but also can be the scheduled tool if the client wants too, but this should be with caution as the scheduled tool can change (* from FPSINPUT.MHS_DELIVERY_NEXT)

DO_NOT_MOVE

CHAR(1)

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)

IS_LOCATION_ASSUMED

CHAR(1)

This column flags whether or not the location value is an assumed value or not. An assumed value is when the location is set, usually within the ETL, based on certain conditions rather than actually coming from a source system directly. (* from FPSINPUT.MHS_CARRIERS)

LAST_KNOWN_LOCATION

VARCHAR2(32)

Often when a carrier is in transit we do not know exactly where it is but we only know where it came from. In this case we might set the location to something generic like TRANSIT and the last known location to where it came from. (* from FPSINPUT.MHS_CARRIERS)

LAST_KNOWN_LOCATION_INST

DATE

Time when the last_known_location was originally updated as the location of this carrier. This column and last_known_location are both updated by trigger. (* from FPSINPUT.MHS_CARRIERS)

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)

LOCATION_INST

DATE

N

Time when the carrier arrived at the location. (* from FPSINPUT.MHS_CARRIERS)

NEXT_CHG_TS

TIMESTAMP(4)

For CHGLOG and automatic HIST tables, this is null when inserted and then updated with SYSTIMESTAMP of the next change. This means that this record existed in the original table from CHG_TIMESTAMP until this time. (* from FPSINPUT.EQP_PORT_HIST)

NEXT_LOCATION

VARCHAR2(32)

NEXT_LOCATION_INST

DATE

NEXT_STATION

VARCHAR2(32)

RESERVED_TOOL

VARCHAR2(16)

TIME_TO_NEXT_MOVE

DATE

TIME_TO_START

DATE

TRANSPORT_METHOD

VARCHAR2(10)

UPDATED_INST

DATE

N

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)