The following table lists and defines the MSD profile options in Oracle Advanced Planning.
| Profile Option Name | Valid Values | Default Value | Description |
|---|---|---|---|
| MSD: Calculate Planning Percentages | Planning Percentages Forecast Explosion | Forecast Explosion | This profile option controls the behavior of the planning percentage calculations. For example, it controls whether the planning percentages can be calculated from the sales history of options. This profile can prevent expensive calculations when the user does not want to calculate planning percentages and just wants to use the existing planning percentages specified in the enterprise resource planning source to explode the forecast. |
| MSD: Category Set Name | Category set names | Null | This profile option is used to select one category set during the data collection process. If the user value is left blank, then all categories will be selected for data collection. Valid values are limited to valid category set names. |
| MSD: Client Debugging | - | - | This profile option is for use by Oracle. It allows you to enable debugging tools. |
| MSD: Code Workspace | - | - | This profile option is for use by Oracle. |
| MSD: Conversion Type | Conversion rates | Null | This profile option determines what conversion rates are collected from the General Ledger rates table. Valid values are limited to valid conversion rates. |
| MSD: Currency Code | Currency codes | Null | This profile option designates the base currency used in Oracle Demand Planning. All revenues are calculated and displayed in this base currency. Valid values are limited to the currency list of values. |
| MSD: Customer Attribute | Descriptive flexfield column names | Null | This is a source profile option used to selectively bring the customer names into Oracle Demand Planning to improve the system performance. This profile holds the descriptive flexfield column name that is used to indicate if a customer in the Customers table will be used by Oracle Demand Planning. Only those customers in the Geography dimension that have this flexfield populated will be collected. This profile option value is one of the attribute columns of the RA_CUSTOMERS entity, which indicates whether or not the customer will be used for demand planning purposes. In the customers table, you need to reflect this in a descriptive flexfield. All of the source views for the geography dimension that use the RA_CUSTOMERS entity filter using this attribute column. If the profile option is not provided, then no filtering will occur. If the profile option is provided, then only the entities in the geography dimension that have the attribute in the RA_CUSTOMERS entity specified as Yes will be collected. To set up Key Customers, go to the Customer setup screen in Oracle Applications. Select the relevant customer and set an available flexfield column to Yes. For example, if you use attribute10, then you need to use this information in the MSD profile option setup also. Also, in the source instance, set up the following information for profile option value MSD_CUSTOMER_ATTRIBUTE: list of values from ATTRIBUTE1 to ATTRIBUTE15. |
| MSD: Default DP Scenario | Valid demand planning scenarios | Null | This profile option specifies a demand scenario, which appears as a demand schedule in the Plan Options window. You can select the demand scenario from the list of values. When you publish the demand scenario specified in this option, the planning engine launches the unconstrained plan specified in the profile option MSC: New Forecast Auto Plan. |
| MSD: Master Org | Master organizations | Null | This profile option is used to select a master organization, if there are multiple master organizations. The item attributes pertaining to the selected master organization are used by Oracle Demand Planning. |
| MSD: OLAP Directory Alias | - | - | Use this profile to specify the database directory alias used to store the log files created during the demand plan build process should be stored. It is primarily for the technical use of login and file-based operations. This profile option can be set at the site level. |
| MSD: One Step Collection | Yes/No | No | This profile option controls the number of steps in the data collection process. Valid values are: Yes: indicating that the collection programs should take the data directly into the Fact Tables in a single step. No: allows for the default two step collection process. In the first step, the collection programs take the data in to the Staging Tables where the data can be consolidated and cleansed by the user, if required. In the second step, the pull concurrent programs carry the data over to the Fact Tables from the Staging Tables. Both set of tables exist on the Demand Planning Server. |
| MSD: Two-Level Planning | Exclude family members with forecast control 'None'/Collect all family members and their sales histories | Exclude family members with forecast control 'None' | Use this profile option to forecast demand at product family level on the basis of sales histories of member items. You can collect the sales histories of all the product family members regardless of their forecast control; set: - Product family forecast control to Consume or Consume and derive -Planning method for the product family and its members to Not planned - This profile option to Collect all family members and their sales histories You can collect the sales histories of all the Consume and Consume and derive product family members; set this profile option to Exclude family members with forecast control 'None'. Use this profile option to forecast demand at the product family level on the basis of sales histories of member items. You can collect all the product family members and their sales histories regardless of the forecast control as long as the: - Product family forecast control is Consume or Consume and Derive - Planning method for the product family and its members is Not planned. - Set this profile option to Collect all family members and their sales histories. The default profile value is Exclude family members with forecast control 'None' specifies that only Consume or Consume and Derive product family members are subject to collection. |