How To Setup MSD (MSD_DEM) Customer Attribute Profile for Demand Planning and/or Demantra (Doc ID 726444.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Demand Planning - Version 11.5.9 to 12.0.4 [Release 11.5 to 12]
Oracle Demantra Demand Management - Version 7.1 to 7.2 [Release 7 to 7.2]
Information in this document applies to any platform.
***Checked for relevance on 09-Sep-2014***

Goal



Both Oracle Demand Planning (ODP) and Demantra have profiles to help control Customers collected from the ERP Source to the APS Destination tables for use in the respective products.

ODP profile: - MSD: Customer Attribute:
Demantra profile MSD_DEM: Customer Attribute:


This profile can have the same value for both profiles/applications (in case customer is transitioning from ODP to Demantra)

Product Management has the following comments about how this profile works:


This is a source profile option to selectively bring the customer names into Oracle Demand Planning or Demantra. Selective inclusion of customers helps you focus on your key customers. It also improves system performance.

The profile holds the descriptive flexfield column name that is used to indicate if a customer in the customer table will be collected. The valid profile option value is one of the attribute columns (ATTRIBUTE1 to ATTRIBUTE15) of the RA_CUSTOMERS entity. For example, if you are not using ATTRIBUTE8, then you can setup this flexfield or just populate this column in the table for your key customers - See Setups below to setup the flexfield to be able to see the values in the application.

If the data collections are run without setting up this profile, the value of the profile is set to ’None’ causing all the customers to be disabled. You can change this profile to a valid descriptive flex field column name as described above. You can also clear the value, in which case all the customers and customer sites are collected regardless of the setting in the descriptive flexfield.

To setup key customers, use the steps below to setup the flexfield, then go to the customer setup screen in Oracle e-business source and populate the descriptive flexfield.  If the flexfield is set to Yes for a customer, that customer is enabled and will be collected. Also, the fact data (booking history, shipment history, etc.) for this customer will be collected under the same customer and customer site. If the flexfield is set to any other values or left blank for a customer, that customer is disabled and the customer record will not be collected.
However, the fact data (booking history, shipment history, etc.) for this customer will be collected under a dummy customer, ’OTHER’ and customer site, ’OTHER’. Also, the fact data for all the disabled customers is grouped into the dummy customer, ’OTHER’ and customer site, ’OTHER’.

Summary of Data Collected:
1. Profile setup with ATTRIBUTE<number>  -
Only those customers with value set to Yes (1) will be collected and their fact data will be associated with their customer/customer site. All other booking/shipment data will be under dummy customer OTHER / customer site OTHER
2. Profile = NONE - All customers disabled and all shipment and booking data is collected under dummy customer OTHER / dummy customer site OTHER
3. Profile = NULL - All customer/customer sites collected and all data is associated with customer/customer sites - largest data load

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