Demand Signal Repository-Demantra Integration Issue (Doc ID 1203844.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Demantra Demand Management - Version: 7.3.0 and later   [Release: 7.3.0 and later ]
Information in this document applies to any platform.

Goal

  Users wish to use standard out-of-the-box integration between Demand Signal Repository (DSR) and Demantra.
  The SITE level values in Demantra are encrypted, (concatenation of customer site, customer etc.), while from DSR the site code comes as name of Business Unit code, which is not concatenated.

Does this mean DSR should be loaded with same naming convention for Business Unit codes as Demantra, so that the data load will not error out due to mismatched data values?


Solution

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 hundreds of Community platforms