This appendix covers the following topics:
This profile controls where analytic workspaces are created and stored. New plans are created in the specified tablespace; existing plans remain in the tablespace specified at the time of their creation. Changing the tablespace profile has no effect on existing data.
Note: To migrate an old plan to a new tablespace, first change the profile, then recreate the plan.
MSD: Calculate Planning Percentage
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.
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 allows you to enable debugging tools and is primarily for technical use.
This profile option determines what conversion rates are collected from the General Ledger rates table. Valid values are limited to valid conversion rates.
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.
This is a source profile option used to selectively bring the customer names into Oracle Demand Planning to improve 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 field. 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 MSD profile option setup, too. 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: Enabled Organization for Item Collections
This profile option specifies how Oracle Demand Planning collects Product Family and Product Category relationships. Valid values are:
All Enabled Demand Planning Organizations: Product Family and Product Category relationships are collected from all enabled demand planning organizations.
Demand Planning Master Organization: Product Family and Product Category relationships are only collected from the master organization.
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
This profile stores the directory alias name where the files are located. It will be read during login and used during all file-based operations. This profile option can only be set at the site level.
MSD: OLAP Initial Page Pool
This profile specifies an initial minimum memory for planning and manager sessions and can be optimized for individual users. A value of 4 to 6MB is generally adequate. The default value is olap_page_pool_size.
MSD: OLAP Maximum Page Pool
This profile specifies a maximum memory footprint for planning and manager sessions requiring additional memory resources, such as forecast creation. Oracle Demand Planning reserves the amount of memory specified by this profile, and relinquishes it when the operation is complete.
MSD: OLAP Workflow Page Pool
This profile specifies the memory footprint for workflow initiated Oracle Demand Planning sessions. The default value is 64MB.
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. The default value is No.
MSD: Two-Level Planning
This profile allows you to forecast demand at 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 & Derive' and the planning method for product family and members is not set to 'Not Planned'.
This is achieved by setting the profile value to: Collect all family members and their sales histories. The default profile value, Exclude family members with forecast control 'None' enforces the existing behavior that is, only 'Consume' or 'Consume & Derive' product family members are collected.
MSD: Use Classic Even Allocation
This profile allows you to determine the allocation method used when an allocation basis does not exist. You can allocate evenly down the time dimension and use "first" allocation for other dimensions when an allocation basis is not available. Valid values are:
No, use first allocation.
This value allocates to first child at each level. This is the default value.
No, use first allocation for all dimensions except Time.
This value allocates to first child at each non-time level and allocates evenly to time.
Yes, use even allocation.
This value allocates evenly to every child. You should not use this value unless you have a genuine functional need.
Note: If you plan to use the MSD: Use Classic Even Allocation profile value feature, do the following:
Query MSD: Use Classic Even Allocation in the profiles form.
Set the value to No, use first allocation for all dimensions except Time.
For a complete list of all of the planning profile options, see: the Profile Options appendix in the Oracle Advanced Planning and Scheduling Implementation and User's Guide.