My Oracle Support Banner

26267317 Demantra History Is Duplicated When Location Name Is Changed In EBS (Doc ID 2410856.1)

Last updated on AUGUST 09, 2018

Applies to:

Oracle Demantra Demand Management - Version 12.2.4.1 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4.1 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

STEPS :

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

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.