FPSADMIN.DOC_HOW_TO_POPULATE_MANUAL

>

> FPSADMIN.WIP_WAFER_HIST_LOOP

View FPSADMIN.DOC_HOW_TO_POPULATE_MANUAL

The topic of how to populate data which is not stored in the MES is one of the most tricky topics of our DWH. Many of the columns in EQP_TYPES are excellent examples of this but we will use exp_cascade_qty which is an important column because it is a huge factor in calculating UPH on cascading tools. EQP_TYPES is definitely an automatically populated table but exp_cascade_qty is probably not stored in the MES. So how do we set the value of exp_cascade_qty manually? We have three options: 1) Hardcode the logic in the ETL (either APF report or REF view). In other words, just specify that exp_cascade_qty is "if eqp_type like 'IMP%' then 6 else if eqp_type like 'LITHO%' then 4" or something like this. The advantage of this method is that the value will be sure to update when we copy the ETL logic between development and production. The disadvantage is that it is rather awkward to update the value because you have to modify the ETL. 2) Configure the column to be set to manual within an automatically populated table using ADM_LOAD_CFG_MANUAL_COLS. This means the ETL will not update this column for existing records even when other columns change. The advantage is that it is easy to modify directly in the database. The disadvantage is that production and development can have different values since it is set manually. 3) Add a column or populate a user-defined column in the MES. This is the best way to store necessary information if possible. The disadvantages are that it might be impossible to do this and that it might require more change control that desired to modify the value in the future.