Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 126.96.36.199 and later
Information in this document applies to any platform.
Customer has upgraded from 7.2.1 to 188.8.131.52. They now mention that whenever there is a change in the hierarchy (like product family name, or product line or Status etc) for a given item in the source (11.5.10), the data is not getting updated for all item-locations combinations in demantra. The new value is being updated correctly only for the one record in the items table, which is causing having duplicate prod families etc for a given item.
Below is the example on this issue:
Say currently for item ABC1 the product family is PF1 in the source and also in Demantra.
in t_ep_item table the t_ep_pf_ep_id is for PF1.
in items table for this item and demand class, the data is as below.
ABC1 - DC1 - PF1
ABC1 - DC2 - PF1
Now when the prod family value for this item is changed to PF2 from PF1 in the source, we run demantra collections and ebs full download. Then we see data in t_ep_item table properly as ABC1 - t_ep_pf_ep_id is of PF2.
but in the items table, the data is like below:
ABC1 - DC1 - PF2
ABC1 - DC2 - PF1
This is causing this item ABC1 to be displayed under 2 PFs which is wrong.
Before upgrading to 184.108.40.206 this sync is happening properly by updating all the recs in items table to PF2. after upgrade, they are facing this sync issue with items and mdp_matrix table with these ids.
When they look at ep_load_items proc, in the older (7.2) version, they see a block which updates all the combinations by taking value from t_ep_item table. But the same process is not in place in ep_load_items in 220.127.116.11. DO they need to do anything else to sync the values in items, mdp_matrix tables from t_ep_item table in the upgraded version?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms