Despite the ideal design of having custom path tables to avoid problems with upgrades, for load tables, if the source of the data for the new custom column is coming from a source that is already being accessed by a load table in the data warehouse, it would be redundant to repeat the action of loading a second custom table from the same source for just one new column. So in an example as provided earlier where idh_prodline is added to the fact_om_invoice table, it should be added as a custom column xx_idh_prodline to the existing load_idh_hist table. In cases where the required new columns from source tables that are not being utilized by the existing warehouse, a whole new loadx_ table should be created and should contain all relevant columns for linking that data to the existing data warehouse if that is the intent.