Data Dictionary
>
FPSADMIN Tables
> FPSADMIN.RTG_COMMON_STEP_BALANCE
Table FPSADMIN.RTG_COMMON_STEP_BALANCE"
Input table for the common step balance configurations which is similar to RTG_STEP_BALANCE but for common step rather than step. This allows to control WIP at the common start step based on how much WIP is in between the start and end common steps (Balance Window), how many wafers to allow to run at the start common step per day, and tool threading calculation at the start common step.
-
Schema: FPSADMIN
-
Tablespace: FPSDATA
-
Primary key: FACILITY, COMMON_START_STEP
-
Foreign keys: RTG_COMMON_STEP_BALANCE_FK_FAC: FACILITY REFERENCES FPSINPUT.GEN_FACILITIES (FACILITY)
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
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) |
|
COMMON_START_STEP |
VARCHAR2(50) |
N |
The common step upon move out we apply the balance logic. Tied to all routes that share the common end and start steps. This is used for both the WIP window and daily input control limit to trigger WIP that is in the window limit and/or counted towards the daily limit. |
|
BAL_WINDOW_LIMIT_RANK |
VARCHAR2(1) |
Rank to assign lots needing to process at the start step when the WIP balance window limit has been exceeded. (* from FPSINPUT.RTG_STEP_BALANCE) |
|
|
COMMON_END_STEP |
VARCHAR2(50) |
The common step upon move out where the wip balance limit is no longer applied. |
|
|
DAILY_INPUT_LIMIT_RANK |
VARCHAR2(1) |
Rank to assign lots at the start step when the daily input limit for the assigned start step has been exceeded (* from FPSINPUT.RTG_STEP_BALANCE) |
|
|
START_STEP_DAILY_INPUT_LIMIT |
NUMBER(9) |
Daily maximum of wafer completes at the start step (* from FPSINPUT.RTG_STEP_BALANCE) |
|
|
TOOL_IMBALANCE_TOLERANCE_PCT |
NUMBER(3) |
Tolerance percentage for imbalance. For example if you have 47% of the WIP that started on TOOL_01 and 53% on TOOL_02 then and the imbalance tolerace set to 10% we would consider these two tools to have balanced WIP. (* from FPSINPUT.RTG_STEP_BALANCE) |
|
|
UPDATED_INST |
DATE |
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) |
|
|
USE_BALANCE_WINDOW_LIMIT |
CHAR(1) |
Flag to specify if you want to use the start to end step window limit. (* from FPSINPUT.RTG_STEP_BALANCE) |
|
|
USE_DAILY_INPUT_LIMIT |
CHAR(1) |
Maximum amount of WIP to commit to any tool in a day at the Start Step (* from FPSINPUT.RTG_STEP_BALANCE) |
|
|
USE_TOOL_BALANCE_CALC |
CHAR(1) |
Flag to specify if you want to use the start step tool balance. This will attempt to balance the start step tool WIP evenly with all tools that can run that step. (* from FPSINPUT.RTG_STEP_BALANCE) |