FPSADMIN.WIP_STAGE_CONFORMANCE_HIST

Data Dictionary

FPSADMIN Tables

> FPSADMIN.WIP_STAGE_CONFORMANCE_HIST

Table FPSADMIN.WIP_STAGE_CONFORMANCE_HIST"

When a lot is placed on a staging location, records the scheduled tool at the time of relocation. Staging location status is defined by MHS_STATION_ASSIGNMENTS. If one location is a staging location for multiple tools, one row per each tool will be inserted

Schema: FPSADMIN
Tablespace: FPSDATAHIST
Primary key: LOCATION_INST, LOT, CARRIER, STAGE_TOOL

Column	Type	Nullable	Comment
LOCATION_INST	DATE	N	Time when the carrier arrived at the location. (* from FPSINPUT.MHS_CARRIERS)
LOT	VARCHAR2(32)	N	A lot is a group of units that process together. Usually lot_id or lot_number in MES. All units in a lot are in the same carrier but there may be multiple lots in a carrier. (* from FPSINPUT.WIP_LOTS_STATIC)
CARRIER	VARCHAR2(32)	N	RFID of the cassette or FOUP the lot is currently in. (* from FPSINPUT.MHS_CARRIERS)
STAGE_TOOL	VARCHAR2(16)	N
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)
ROUTE	VARCHAR2(256)	N	Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING)
SCHED_TOOL	VARCHAR2(16)		the tool from the first lot that scheduled (* from FPSAPP.SCH_W_SCHED_DURABLE_INSPECT)