Data Dictionary
>
FPSAPP Tables
> FPSAPP.WIP_STEP_FUT_DURABLE_ASGN
Table FPSAPP.WIP_STEP_FUT_DURABLE_ASGN"
See comments in WIP_REF_STEP_FUT_DURABLE_ASGN view.
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Primary key: LOT, TOOL, FACILITY, STEP, ROUTE, DURABLE_FAMILY
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
LOT |
VARCHAR2(128) |
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) |
|
TOOL |
VARCHAR2(16) |
N |
Tool is generally just the main tool. The exception is when different entities on the tool run completely independently and it is physically impossible to run wafers of the same lot across multiple entities. In this exception case, we may want to assign the entities to different eqp_types and therefore we should define each entity as a tool. Please note that when we do this there is no indication whatsoever that these different entities are on the same tool. (* from FPSINPUT.EQP_TOOLS) |
|
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) |
|
STEP |
VARCHAR2(256) |
N |
A single processing step within a route representing a single tool visit. Step is often a very complex string and should rarely be displayed. Instead we should use process_display. (* from FPSINPUT.RTG_ROUTE_STEPS) |
|
ROUTE |
VARCHAR2(256) |
N |
Route that has threading requirements (* from FPSINPUT.RTG_STEP_THREADING) |
|
DURABLE_FAMILY |
VARCHAR2(64) |
N |
Durable_family indicates what durable is required by the process. When multiple durables are in a family any of them can be used. Typically there is only one reticle per family and therefore the durable and durable_family are the same. The exception would be a high running product with backup reticles. However for probe cards it is common to have several cards for each product so we have several durables with the same family. (* from FPSINPUT.RTG_DURABLE_FAMILIES) |
|
DRBL_RANK |
VARCHAR2(1) |
||
|
DRBL_RANK_DISPLAY |
VARCHAR2(24) |
||
|
IS_BLOCK_BY_DRBL_RANK |
CHAR(1) |
||
|
IS_IN_NMV_PICK_LIST |
CHAR(1) |
Set to Y if lot-step is within range to be displayed in NextMove Pick List according to hours/steps_to_schedule fields in GEN_FACILITIES (* from FPSBASE.WIP_STEP_FUTURE) |
|
|
IS_MULTIPLE_REQUIRED |
CHAR(1) |
When more than one durable family of the same durable class is assigned to the same criteria, we use this field to determine whether to choose one or whether we need all. Our default indicated by N is that any of them can be used. Occasionally certain processes require multiple durables of the same group (i.e. double reticles) and you indicate this by setting this column to Y. (* from FPSINPUT.RTG_DURABLE_ASSIGNMENTS) |
|
|
NUM_STEPS_AWAY |
NUMBER(4) |
Number of steps away not including steps which we know will be skipped nor those which we estimate will be skipped at least x pct of the time. This x value is configurable in GEN_FACILITIES using the smp_pct_for_num_steps_away column. (* from FPSBASE.WIP_STEP_FUTURE) |
|
|
PROCESS_GROUP |
VARCHAR2(36) |
Process group is the critical field where tools and processes come together for the purposes of Scheduler. Process group is in both EQP_TOOLS for the tools and in RTG_PROCESSES for processes. Ideally all tools that run the same set of processes with no crossover including back-up and emergency tools would be in the same process group but it is important to note that this is not technically required for Scheduler as long as all process groups are in the same sched group. (* from FPSINPUT.RTG_PROCESS_GROUPS) |