Demantra History Is Duplicated When Location Name Is Changed In EBS
(Doc ID 2410856.1)
Last updated on FEBRUARY 15, 2019
Applies to:Oracle Demantra Demand Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
On : 18.104.22.168 version, LoadData
ACTUAL BEHAVIOR :
Demantra collects Duplicate history when a location in EBS for the Customer account is modified.
To collect Demantra data at Customer Account level, Profile setup for MSD_DEM: Collect History against customer(site) = "Customer BILL TO" is done.
Changing the location for Customer site, makes the old location as Inactive & Non-primary. It makes new location as Active & Primary.
Demantra view MSD_SH_RI_SD_730_V is only looking at the flag - ship_to_flag = 'P'
Based on research, when the location name is changed in EBS, it does not change Ship_to_flag but flips the Primary_flag.
EXPECTED BEHAVIOR :
Demantra History should not be Duplicated when Location name is changed in EBS
The issue can be reproduced at will with the following steps:
1. Customer ship to set to primary
2. Inactive location not primary
3. Run collection
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