Demantra History Collection Does Not Seem To Respect MSD_DEM Customer Attribute (Doc ID 1914041.1)

Last updated on AUGUST 08, 2014

Applies to:

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

Symptoms

Standard collection is set to bring in selective customers using MSD_DEM: Customer Attribute profile setup. Using this, ATTRIBUTE15 was set to a value of 'Yes' to only 35 customers for collecting into Demantra (Key customers).

After running Collect Shipping and Booking History Collections with EP Load set to 'No', more customers than was set in the attribute were collected into the T_SRC_LOC_TMPL table in Demantra with their associated sales transactions (more than the customers that were enabled).

Cause

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