FPSINPUT.RTG_PRD_END_BANKS

Data Dictionary

FPSINPUT Tables

> FPSINPUT.RTG_PRD_END_BANKS

Table FPSINPUT.RTG_PRD_END_BANKS"

Stores bank(s) where lots will go after finishing main route of facility-prd. This table has two important uses. First it is used together with RTG_PRD_FACILITY_NEXT. If the facility-prd has no records here then lots go directly to the main_route of the next prd. If it has one record then it will go to that bank until started on the next prd. It is possible to have multiple records which would mean the lots would go to multiple banks in sequence but that is unusual. Second it is used in the WLRT trigger to log jumps to WIP_JUMP_HIST. When a lot moves from any step to an end bank, we jump all non-bank steps on the route which are after that step including any steps which occur after the move_to_bank on the route. Recording the jump for all following steps is necessary to calculate est_smp_pct correctly. One example is a packaging route with multiple choices for the end bank. An example route ends with the following five seq_num: process X, process A1, move to end bank B1, process A2, move to end bank B2. All lots go to process X but A1 and A2 are optional! So lots will either go to X->A1->B1 or X->B1 or X->A2->B2 or X->B2. Of course when the lot moves X->B2 we will log jumps over A1 and A2 since those steps are in between X and B2 on the route. And when the lot moves X->A2 (and then to B2) we will jump over A1. But the important logic is that when we move X->B1 or A1->B1 we actually need to log a jump over A2! Even though A1->B1 is a move between sequential steps on the route! This is so that the est_smp_pct for A2 correctly shows this lot "skipping" this step! If we did not have this logic and the split was 50-50 we would calculate est_smp_pct of 50% for A1 and 100% for A2! With this special "move to end bank" logic we correctly calculate 50% for both steps. An important corollary of this logic is that if a bank in the middle of the route is actually an intermediate bank (meaning that lots leave that bank and continue with the following steps) then it is critical to not include that bank in RTG_PRD_END_BANKS.

Schema: FPSINPUT
Tablespace: FPSDATA
Primary key: FACILITY, PRD, BANK
Foreign keys: RTG_PRD_END_BANKS_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)
PRD	VARCHAR2(64)	N	Prd determines the route which is used to process the lot in the facility and what tools, recipes, durables, etc. can be used at each step. Prd also determines the next facility for the lot when it finishes its route. For detailed information on prd vs. planprd see table comments in RTG_PLANPRDS. (* from FPSINPUT.RTG_PRDS)
BANK	VARCHAR2(36)	N	Lots which are not on a route are considered in a bank and the bank name indicates why the lot is off route. Bank must be NA for lots which are on a route. Our standard filter for active lots is bank = NA. (* from FPSINPUT.RTG_BANKS)
END_BANK_SEQ_NUM	NUMBER(2)		Most products only have one end bank so this should almost always be set to 1. But we have seen prds that have multiple end banks and here is where we indicate the order of the banks.
END_BANK_STRUCTURE	VARCHAR2(11)		Indicates the ordering and structure of end-banks for a given PRD: if SEQUENTIAL, then WIP moves from the PRD route through the N end-banks in sequence (END_BANK_SEQ_NUM=1..N); if PARALLEL, then WIP moves from the PRD route to only of of the N end-banks (END_BANK_SEQ_NUM=1).
OVR_COMMIT_CT_DAYS	NUMBER(5,1)		Commit_ct_days is set for each bank in RTG_BANKS but occasionally we want to override for a specific product and we do that with this field.
OVR_TARGET_CT_DAYS	NUMBER(5,1)		Target_ct_days is set for each bank in RTG_BANKS but occasionally we want to override for a specific product and we do that with this field.