FPSINPUT.WIP_LOTS_COLS_NO_DD_PRTN

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)

ACTIVE_ABORT_INST

DATE

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)

BEG_PROC_INST_NOT_ABORTED

DATE

BLOCK_OR_DOWN_REASON

VARCHAR2(600)

CARRIERS_IN_JOB_WCJ

NUMBER(2)

CARRIER_DISPLAY

VARCHAR2(32)

CARRIER_FOR_MHS_TRG

VARCHAR2(32)

N

CURR_BAY

VARCHAR2(12)

Current bay of carrier. See column comment on BAY in FPSINPUT.MHS_BAYS for more information. (* from FPSINPUT.MHS_DELIVERY_NEXT)

CURR_BUILDING

VARCHAR2(12)

Current building of carrier. See column comment on BUILDING in FPSINPUT.MHS_BUILDINGS for more information. (* from FPSINPUT.MHS_DELIVERY_NEXT)

CURR_PORT

VARCHAR2(5)

CURR_PORT_MODE

VARCHAR2(24)

CURR_PRIORITY_BG_COLOR

VARCHAR2(24)

CURR_PRIORITY_DISPLAY

VARCHAR2(20)

N

CURR_PRIORITY_SORT

NUMBER(3)

CURR_STATION

VARCHAR2(32)

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

CURR_STATION_TYPE

VARCHAR2(32)

Current station type of carrier. See view MHS_LOCATIONS for more information. (* from FPSINPUT.MHS_DELIVERY_NEXT)

CUSTOMER

VARCHAR2(64)

Customer who will accept shipment of the lot. Currently this only used for grouping and filtering but in the future we might want to allow a customer to view a Dashboard only including their products. (* from FPSINPUT.GEN_CUSTOMERS)

DEMAND_INST

DATE

Start of period when this qty of this planprd needs to finish. We automatically spread demand across each plan week in WIP_DEMAND_BY_WEEK which feeds WIP_FLUSH therefore this column can be the start of any time period less than or equal to plan week. It could be the demand for each shift or for each day or for each plan week but if the site has no preference then the easiest way to set this up is to write one row per plan week and let us spread across that week. It is important to note that we always spread across the plan week with our custom logic so even if this table is by day we might adjust it to another day within the same plan week. (* from FPSINPUT.WIP_DEMAND)

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)

DIRECT_DELIVERY_BAY

VARCHAR2(12)

DISP_PROC_ENDED_SEC

NUMBER(8)

DURABLE_CARRIER

VARCHAR2(32)

The durable carrier ID of the durable required for this carrier to process. (* from FPSINPUT.MHS_DELIVERY_NEXT)

DURABLE_LOCATION

VARCHAR2(32)

The location of the durable. (* from FPSINPUT.MHS_DELIVERY_NEXT)

EET_SEC_BATCH_FOR_TTS

NUMBER(7)

N

EET_SEC_LOT_FOR_TTS

NUMBER(7)

N

EET_SEC_WCJ

NUMBER(7)

EST_BEG_INST_TOOL

DATE

EST_DISP_INST_TOOL

DATE

EST_END_INST_FROM_BEG

DATE

EST_NEXT_BEG_INST_FROM_BEG

DATE

EST_SEC_TO_COMP_SLOW

NUMBER(8)

EXTL_DISP_INST

DATE

Time by when the external system recommends that the job must be dispatched. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

EXTL_DO_NOT_MOVE

CHAR(1)

This column will decided whether NextMove will highlight to move or override it (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

EXTL_NEXT_STATION

VARCHAR2(32)

EXTL_REQ_EXACT_DEST

CHAR(1)

This column will decided whether NextMove use alternates and station assignments or ignore them. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

EXTL_RESERVE_INST

DATE

EXTL_SHOW_EXACT_DEST

CHAR(1)

This column will decided whether NextMove will show the destination Bay or the exact destination. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

EXTL_START

DATE

Time by when the external system recommends that the job will begin processing. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

EXTL_STATION_FOR_NEXT_STEP

VARCHAR2(32)

EXTL_TIME_TO_NEXT_MOVE

DATE

Time provided by an external system to override the carrier time to move for racks. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

EXTL_TRANSPORT_MODE

VARCHAR2(16)

Name of the site transport mode which represents how material is moved from one location to another. (* from FPSINPUT.MHS_EXTERNAL_TRANSPORT_MODES)

EXTL_TRANS_MODE_FOR_NEXT_STEP

VARCHAR2(16)

EXTL_VEHICLE_SUB_ROUTE

VARCHAR2(36)

EXTL_VEH_SUB_RT_FOR_NEXT_STEP

VARCHAR2(36)

FACILITY_FOR_MHS_TRG

VARCHAR2(6)

N

FACILITY_OF_BANK

VARCHAR2(6)

FIRST_LOT_IN_JOB_WCJ

VARCHAR2(32)

FUT_HOLD_SEC_ADD_TO_EST_COMP

NUMBER(7)

FUT_HOLD_TYPE

VARCHAR2(24)

GBL_SORT

NUMBER(38)

Sorting used for dispatching or allocation systems to sort future start lots based on priority, critical ratio, etc. (* from FPSINPUT.WIP_STARTS)

HIDE_LOTS_IN_DASH

CHAR(1)

This flag is similar to CONSIDER_IN_BANK but even more extreme. This flag will completely hide all lots and moves on this route from the Dashboard. Honestly we discourage anyone from using this flag (and strongly discourage it for anything but test wafers) but it is here at least for Dashboard only if a particular site really wants it. (* from FPSINPUT.RTG_ROUTES)

HOLD_FOR_DISPLAY

VARCHAR2(64)

HOLD_MODULE

VARCHAR2(12)

HOLD_PRTY_GROUP

VARCHAR2(20)

This field determines the grouping of hold lots displayed on the Dashboard hold page. Typically the highlighted priorities will each be in their own group and all others will be in a group named OTHERS. We might want to separate low priority lots too. (* from FPSINPUT.WIP_PRIORITIES)

HOLD_TYPE_DISPLAY

VARCHAR2(36)

IGNORE_BANK_TW_ON_DASH

CHAR(1)

The Dashboard spotlight shows a number of Test Wafers in the facility. Usually we want this to include test wafers in a bank so we would set this to N. To ignore test wafers in a bank then set this to Y. (* from FPSINPUT.GEN_FACILITIES)

IS_ALLOWED_FOR_SCHED

CHAR(1)

Lots on hold are only scheduled if this flag for the hold type is set to Y. By default this is N which means that lots on hold are not scheduled. (* from FPSINPUT.WIP_HOLD_TYPES)

IS_COMPLETE_FROM_OVR

CHAR(1)

IS_COUNT_PRIORITY_PCT

CHAR(1)

This flag determines which priorities to include in our overall percentage of priority lots in the Dashboard spotlight. This is similar to is_highlighted_prty but it is possible that we might want to highlight a priority but not include it in the percentage. (* from FPSINPUT.WIP_PRIORITIES)

IS_CURR_PRTY_HIGHLIGHTED

CHAR(1)

IS_DURABLE_AT_DESTINATION

CHAR(1)

NextMove flag indicating if the durable location is the same as the tool the carrier needs to process on. (* from FPSINPUT.MHS_DELIVERY_NEXT)

IS_DURABLE_REQUIRED

CHAR(1)

NextMove flag indicating if the carrier requires a durable to process. (* from FPSINPUT.MHS_DELIVERY_NEXT)

IS_HOLD_DISPLAY

VARCHAR2(4)

IS_N2

CHAR(1)

Flag to display N2 icon in NextMove if lot requires N2 (nitrogen purged) storage. In a future version we will allow more generic AMHS-related flags but this is specific to N2 for now. (* from FPSINPUT.MHS_DELIVERY_NEXT)

IS_NEXT_MOVE_NEXT_STEP

CHAR(1)

IS_NMV_PRIORITY

CHAR(1)

This flag indicates if this priority should be emphasized in NextMove (* from FPSINPUT.WIP_PRIORITIES)

IS_PLAN_PRTY_HIGHLIGHTED

CHAR(1)

IS_QUEUE_TIMER

CHAR(1)

Flag to display queue timer icon in NextMove if lot is in queue time loop. (* from FPSINPUT.MHS_DELIVERY_NEXT)

IS_RESERVED

CHAR(1)

This flag indicates if the carrier has been reserved to a tool. (* from FPSINPUT.MHS_DELIVERY_NEXT)

IS_SCHED

CHAR(1)

This flag indicates that lots in this group should be scheduled. This flag additionally causes TW groups to be included in WIP_STEP_FUTURE which they are normally not. (* from FPSINPUT.WIP_LOT_GROUPS)

IS_TW

CHAR(1)

Our standard filter to exclude test wafers is is_tw = N but what we really mean with this filter is to exclude any lots that do not add value for the facility. Lots which add value including sellable, development, and engineering and these lot groups should have is_tw set to N. Lots which do not add value are commonly grouped together and named "test wafers" which is why this flag is named is_tw. These include true test wafers like monitors and quals and dummies but also could include virtual lots used for training or testing, bare wafers, or really anything else including in the MES as a lot which does not add value. All of these lot groups should have is_tw set to Y. You could argue that the is_tw field might be more accurately named is_value or is_valuable or is_prod_eng_dev but is_tw is generally clear to most people. Plus it has the advantage that it is short which is nice given how frequently we use the is_tw = N filter. (* from FPSINPUT.WIP_LOT_GROUPS)

LAST_KNOWN_BAY

VARCHAR2(12)

LAST_KNOWN_BUILDING

VARCHAR2(12)

LAST_KNOWN_DURABLE_LOC

VARCHAR2(32)

The previous location of the durable. (* from FPSINPUT.MHS_DELIVERY_NEXT)

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)

LINE_SECTION_NOT_NULL

VARCHAR2(32)

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

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

LOCATION_TYPE

VARCHAR2(32)

LOTS_IN_JOB_WCJ

NUMBER(2)

LOT_FAMILY

VARCHAR2(24)

Lot_family is a grouping of lot_type which is mainly use for goal planning. We set goals by family and are allowed to switch goals for different lots of different types within the family. We also report goal performance by family. (* from FPSINPUT.WIP_LOT_FAMILIES)

LOT_GROUP

VARCHAR2(8)

Lot_group is a grouping of lot_family and is the highest grouping in the lot type hierarchy. There should be only a few values for lot_group, i.e. Prod, Dev, TW. We group WIP and moves by lot_group on the dashboard and we group cycle time calculations by lot_group so this is an important field. (* from FPSINPUT.WIP_LOT_GROUPS)

LOT_TYPE_SORT_ORDER

NUMBER(6)

MAIN_RT_PROC_STATE

VARCHAR2(5)

MANL_RESERVE_INST

DATE

The actual time the lot was manually reserved by NextMove will be helpful especially for compliance and debugging to have these columns. In the absence of the Scheduler this will also determine the order to run the reserved lots. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

NEXT_STATION

VARCHAR2(32)

NMV_USE_DISP_INST

CHAR(1)

A flag that will help decided whether to use the start time or dispatch time. (* from FPSINPUT.EQP_TYPES)

OVR_BANK_FROM_CONSIDER_FLAG

VARCHAR2(36)

OVR_CARRIER_DISPLAY

VARCHAR2(32)

The ID of the carrier for application display purposes. For example, the internal/referential carrier ID might be a zero-padded hexidecimal number, while the human-readable labels on the carriers might be an unpadded decimal equivalent (e.g. CARRIER=A1B2, OVR_CARRIER_DISPLAY=41394). (* from FPSINPUT.MHS_CARRIERS)

OVR_EST_END_INST

DATE

Estimated time when the lot will end processing on the tool. (* from FPSINPUT.WIP_LOTS_OVR_EST_END_INST)

OVR_EST_NEXT_BEG_INST

DATE

Estimated time when the next job must start processing on the tool in order to maintain full cascading and not lose productivity. (* from FPSINPUT.WIP_LOTS_OVR_EST_END_INST)

PLAN_PRIORITY_BG_COLOR

VARCHAR2(24)

PLAN_PRIORITY_DISPLAY

VARCHAR2(20)

PLAN_PRIORITY_SORT

NUMBER(3)

PREP_SEC

NUMBER(4)

The time in seconds required to prepare the lot before track in. (* from FPSINPUT.EQP_TYPES)

PROCESS_MODULE_DISPLAY

VARCHAR2(20)

PROC_STATE_DASH

VARCHAR2(5)

PROC_STATE_DASH_DETAILS

VARCHAR2(600)

PROC_STATE_DASH_DISPLAY

VARCHAR2(24)

PROC_STATE_DASH_SORT_ORDER

NUMBER(4)

PROC_STATE_SCH

VARCHAR2(5)

PROC_STATE_SCH_DETAILS

VARCHAR2(600)

PROC_STATE_SCH_DISPLAY

VARCHAR2(24)

PROC_STATE_SCH_SORT_ORDER

NUMBER(4)

PRTY_CTM_FACTOR

NUMBER(3,2)

Factor to multiply cycle time for this priority group compared to other groups if not known. For example, if this factor is 1.5 and we know the CTM is 6 hours for another priority group whose factor is 1.0 then we would estimate it to be 9 hours for this group. (* from FPSINPUT.WIP_PRTY_CTM_GROUPS)

PRTY_CTM_GROUP

VARCHAR2(7)

This is one of the primary keys of our CTM tables. We use this group rather than the priority because we often have several different priorities which are close and are expected to have the same cycle time. (* from FPSINPUT.WIP_PRIORITIES)

PULL_POINT_DETAILS

VARCHAR2(256)

PULL_POINT_INST

DATE

PULL_POINT_START_WEEK

DATE

PULL_POINT_WEEK

VARCHAR2(7)

QTY_IN_JOB_WCJ

NUMBER(7)

RECIPE_DISPLAY

VARCHAR2(100)

REMAINING_HOLD_SEC

NUMBER(7)

ROUTE_DISPLAY

VARCHAR2(516)

ROUTE_FAMILY_OF_PRD

VARCHAR2(36)

ROUTE_GROUP_OF_MAIN_RT

VARCHAR2(36)

ROUTE_GROUP_OF_PRD

VARCHAR2(36)

ROUTE_OF_PRD

VARCHAR2(256)

RQD_SETUP_DISPLAY

VARCHAR2(100)

RT_STEP_BANK_ENT_INST

DATE

If the lot is at a step then this is the time when it entered the current route-step. If the lot is at a bank then this is the time it entered the current bank. (* from FPSBASE.WIP_LOTS_REALTIME)

SCHEDULE_STATUS_OFFSET_DAYS

NUMBER(1)

N

If the expected out inst is more than this many days after the pull point (a.k.a. due or demand) inst then we consider the lot to be late. We also consider it late if it is in the next plan week even if less than this number of days behind. (* from FPSINPUT.GEN_FACILITIES)

SCHED_CARRIER

VARCHAR2(32)

SCHED_CARRIERS_IN_JOB

NUMBER(2)

SCHED_CH_TO_USE

VARCHAR2(24)

Please note that the Scheduler often populates this with M which indicates the main tool therefore we often should filter out a value of M when using this value since that it not a valid chamber combination. When this is populated with any value other than M then we use this as est_ch_used rather than calculating with GET_CH_ALLOWED_STATUS or GET_CH_PATH_STATUS. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

SCHED_DISP_INST

DATE

SCHED_DURABLE

VARCHAR2(129)

SCHED_END

DATE

SCHED_QTY_IN_JOB

NUMBER(7)

SCHED_START

DATE

The first start time for the durable to be used (* from FPSBASE.RTG_DURABLE_FUTURE_SCHED)

SCHED_WAIT_ETP_STATE

VARCHAR2(48)

The only way for ETP to know that the Scheduler is asking to wait is for the Scheduler to populate this column indicating that the lot is scheduled but waiting for a particular reason. This column must be an exact etp_state value starting with SBY-IW so it has a check constraint and a foreign key on ETP_STATE_DIAGRAM. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

SHOULD_AUTO_HIDE

CHAR(1)

If the flag is set to Y then the module will be hidden on the Dashboard even if it has active WIP or moves. (* from FPSINPUT.GEN_MODULES)

STEP_SEC_FOR_WSF_TO_EOL

NUMBER(11)

TCT_SEC_FOR_TTS

NUMBER(7)

N

TCT_SEC_WCJ

NUMBER(7)

TIME_TO_NEXT_MOVE_OVR

DATE

This column allows for sites to control the NextMove countdown timers. Normally we do not populate this but for certain use cases clients may want to change this value based on certain criteria. (* from FPSINPUT.MHS_DELIVERY_NEXT)

TOOL_FOR_NEXT_STEP

VARCHAR2(16)

TOOL_FOR_OVR_EST_END

VARCHAR2(16)

TOOL_FOR_TTS

VARCHAR2(16)

TTS for tool is greatest(last start plus EET of last start, data_date). TTS for first lot not started is the same as the TTS for tool but we need to store TTS for tool because tool might not have any reserved lots. TTS for subsequent lots cums the EET of each lot after the first lot. (* from FPSBASE.WIP_STEP_FUTURE_SCHED)

TRANSPORT_MODE

VARCHAR2(10)

Name of the standard FPS transport mode which represents how material is moved from one location to another. (* from FPSINPUT.MHS_EXTERNAL_TRANSPORT_MODES)

TRANSPORT_MODE_FOR_NEXT_STEP

VARCHAR2(4000)

TTS_BAY

VARCHAR2(12)

Bay of the tool where this carrier is reserved or scheduled. (* from FPSINPUT.MHS_DELIVERY_NEXT)

TTS_INST_FOR_NEXT_STEP

DATE

TTS_PROCESS_FAMILY

VARCHAR2(50)

TTS_SOURCE

VARCHAR2(5)

USE_LOT_COMP_OVR

CHAR(1)

Flag to indicate whether lot process completion requires is_complete to be set to Y in fpsinput.wip_lots_ovr_est_end_inst for a specific tool. (* from FPSINPUT.EQP_TOOLS)

VEHICLE_SUB_ROUTE

VARCHAR2(36)

Sub route associated to a cart or carts within a vehicle route. (* from FPSINPUT.MHS_VEHICLE_SUB_ROUTES)

VEHICLE_TYPE

VARCHAR2(36)

WAFER_SIZE

VARCHAR2(8)

If the facility only has one wafer size then this column should be null in both RTG_PRDS and EQP_TYPES. If the facility has more than one wafer size then a value of null in EQP_TYPES means that those tools can run all wafer sizes. See column IS_ANY_WAFER_SIZE for details. (* from FPSINPUT.GEN_WAFER_SIZES)

WAFER_SIZE_DISPLAY

VARCHAR2(16)

The name of the wafer_size displayed on all dashboards and reports. We allow a longer more descriptive name here although often this will be the same as the wafer_size. (* from FPSINPUT.GEN_WAFER_SIZES)

WAIT_SEC_TO_SCHED_CARRIER

NUMBER(7)

If the carrier is not ready to reserve, we set this value and Scheduler will not reserve lots in this carrier. It will schedule them but no earlier than the wait_sec_to_sched value from the current time. (* from FPSINPUT.MHS_CARRIERS)

WAIT_SEC_TO_SCHED_STATIC

NUMBER(7)

WAIT_TO_SCHED_REASON_ABORT

VARCHAR2(256)

WAIT_TO_SCHED_REASON_CARRIER

VARCHAR2(256)

If the carrier is not ready to reserve, this is an explanation of why. This might be because of location or state or whatever reason. (* from FPSINPUT.MHS_CARRIERS)

WAIT_TO_SCHED_REASON_STATIC

VARCHAR2(256)