How to Disable Cannibalization in Demantra TPO
(Doc ID 2441029.1)
Last updated on DECEMBER 04, 2019
Applies to:
Oracle Demantra Predictive Trade Planning - Version 7.3.1.5 and laterOracle Demantra Demand Management - Version 7.3.1.5 and later
Information in this document applies to any platform.
Goal
Customer is on 12.2.4.1 and mention that Cannibalization is enabled by creating indirect promotional causals in m3 causal factors table. Engine inserts rows with is self = 0 in promotion matrix and data tables if it finds indirect effects between products.
Customer now wants to disable cannibalization effect from application. Engine should not calculate Cannibalization while generating forecast in TPO.
They have run below update to disable the two indirect for both short and long models.:
UPDATE m3_causal_factors SET short_val = 0, long_val = 0 WHERE factor_id IN (1320, 2320);
COMMIT;
After update they ran the cycle and found that cannibalization numbers are still existing in system.
They can still see cannibalization uplift.
Solution
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
| Goal |
| Solution |