Data Dictionary
>
FPSBASE Tables
> FPSBASE.SCH_C_DURABLE_MANUAL
Table FPSBASE.SCH_C_DURABLE_MANUAL"
This table is used to store other durable families.
-
Schema: FPSBASE
-
Tablespace: FPSDATA
-
Foreign keys: SCH_C_DURABLE_MANUAL_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
DURABLE |
VARCHAR2(64) |
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) |
|
|
DURABLE_FAMILY |
VARCHAR2(64) |
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) |
|
|
DURABLE_GROUP |
VARCHAR2(64) |
Durable group is the parent of family and the child of class and its only use is to track the time to change durables. In many cases, group will be the same as class. An example where group would be different than class is where we have different reticles for different stepper manufacturers so the durable_group would be Nikon or Canon or ASML while the durable_class would be DURABLE. (* from FPSINPUT.RTG_DURABLE_GROUPS) |
|
|
DURABLE_CLASS |
VARCHAR2(36) |
The class of the durable becomes important when we have multiple durables assigned in RTG_DURABLE_ASSIGNMENTS. If these durables are in different classes then we know that both of them are required. For example, a tester might require both a probe card and an electrical board. If these durables are in the same class then we use the is_multiple_required field to determine whether we will choose either or need both. (* from FPSINPUT.RTG_DURABLE_CLASSES) |
|
|
FACILITY |
VARCHAR2(6) |
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) |
|
|
CURR_USAGE |
NUMBER |
||
|
DURABLE_TYPE |
VARCHAR2(72) |
||
|
MAX_USAGE |
NUMBER |
the max usage for change_from before it change to the new value (* from FPSINPUT.EQP_PROCESS_USAGES) |
|
|
SETUP_COST_EXPENSE |
NUMBER |
||
|
SETUP_COST_SEC |
NUMBER |