Demantra Location Load Not Working Correctly After Demantra Upgrade From 7.3.1 To 12.2.3
(Doc ID 2151166.1)
Last updated on JUNE 26, 2017
Applies to:Oracle Demantra Demand Management - Version 12.2.3 and later
Information in this document applies to any platform.
On : 12.2.3 version, LoadData
Demantra location load not working correctly after Demantra upgrade from 7.3.1 to 12.2.3
The lowest level location dimension in Demantra is a 'Store'. This level has an attribute called 'Closed_date'. This attribute either contains a date or is null.
For any existing store in Demantra, if the staging table has a null closed date and the t_ep_store has a date value in it, the location load does not update the closed date to null. Similarly, if the staging table has a closed date and the t_ep_store has a null closed date, then the closed date is not updated.
This data load was working correctly in version 7.3.1. It is not working correctly in version 12.2.3.
On examination of the ep_model_syntax for the Store level, the following conditions have been added to the update of t_ep_store table in version 12.2.3 -
" (store_desc <> rec.store_desc OR closed_date <> rec.closed_date OR currency <> rec.currency OR open_date <> rec.open_date OR square_foot <> rec.square_foot OR total_square_foot <> rec.total_square_foot OR volume_13wk_trend1 <> rec.volume_13wk_trend1 OR volume_13wk_trend2 <> rec.volume_13wk_trend2 OR volume_13wk_trend3 <> rec.volume_13wk_trend3 OR cap_perc_13wk_trend <> rec.cap_perc_13wk_trend OR anf_yr1_fcst_volume <> rec.anf_yr1_fcst_volume OR anf_yr2_fcst_volume <> rec.anf_yr2_fcst_volume) "
These conditions did not exist in version 7.3.1. I have added the ep_model_syntax for the Store load before and after upgrade for comparison
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document