My Oracle Support Banner

Demantra Location Load Not Working Correctly After Demantra Upgrade From 7.3.1 To 12.2.3 (Doc ID 2151166.1)

Last updated on OCTOBER 16, 2020

Applies to:

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

Symptoms

On : 12.2.3 version, LoadData

ACTUAL BEHAVIOR
---------------
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 table 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 tables 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 tables in version 12.2.3 -
 


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!


In this Document
Symptoms
Changes
Cause
Solution
References


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