| Oracle® Retail Price Management User Guide Release 13.2.9 E71079-01 |
|
 Previous |
 Next |
The system options workspace allows you to configure RPM to maximize the system. System options allow you to customize various parameters, defaults, and constants that are used throughout the system. Normally, these elements are set when RPM is installed by the system or database administrator. They tend to remain fixed unless a business practice is changed which necessitates a change in RPM. System options are the values used in your system that define the overall configuration of the system.
The System Defaults Edit workspace allows you to configure RPM to maximize the system. Select the values that should be should be initially displayed when a user enters the workspace. This helps the user save time as they do not have to select the appropriate value each time they complete a task. The values entered will appear in other areas of the application.
System options are organized on the following tabs:
General
Conflict Checking
Price Events
Location Moves
Table 3-1 System Options Fields and Descriptions
| System Options | Definition |
|---|---|
|
General |
|
|
Sales Calculation Method |
The method used by the merchandise extract program to populate the Projected Sales column in the worksheet. |
|
Update Item Attributes |
When selected, the merchandise extract program updates certain item attributes during each extract that occurs during a worksheet review period. |
|
Recognize WHs as Locations |
When selected, indicates that warehouses can be assigned to regular and clearance price zones. They cannot be assigned to promotion price zones. |
|
Open Zone Use |
When selected, indicates a zone can be used across different types of pricing, regardless of zone type. |
|
Exact Deal/Funded Promotion Dates |
For promotions, start and end dates are specified at two places: 1) promotion header, and 2) promotion component detail. No date is associated at the promotion component level. Deals are associated with promotion components and not component details. |
|
Default Out of Stock Days |
The number of days that should be added to an items clearance effective date in order to calculate the Out of Stock date. The default is applied to generate the out of stock date when the clearance is first created. |
|
# of Days Reject Held |
The number of days after the effective date of a rejected price change or clearance that it is purged from the system. |
|
Ends in Digits for Zero Decimal Currencies |
The number of digit fields set in system options that are available in the Ends In definition area. This field is used for currencies that do not contain a place after the decimal point. For currencies that contain places after the decimal point, the digit fields that are available. |
|
External Prices Allowed |
When selected, RPM accepts pricing events created in other systems. |
|
Zone/Parent Ranging |
When selected, RPM performs ranging checks for price changes, promotions, and clearances that are created at a higher level than transaction/location. If the indicator is set to yes, the system will not let you create a price change at the parent or zone level if none of the transaction item/location combinations are ranged. If the indicator is set to no, the system will let you create a price change at the parent or zone level even if none of the transaction item/location combinations are ranged. |
|
Apply Promo Change Type 1st |
Indicates which type of promotion change should be applied first, however, the processing uses this option only after fixed price and non-secondary promotions are processed. The ranking is applied to the Promotion Header first, before looking at the Promotion Components. The promotions are applied to an item/location based on the ranking order shown below. These rules apply to all promotions, including those created using the Injector Price Event Batch. Ranking order:
Example scenario:
Both promotions are NON secondary and the system option: Apply Promo Change Type 1st is set to Amount Off. The system will first rank at the Promotion Level. Since Promo 2 has the Fixed Price Component in it, it will be ranked higher than Promo 1. All components under Promo 2 will be applied first, and then component under Promo 1 will be applied. When applying Promo 2, component P2C2 will be applied first, since it is a Fixed Price and then P2C1. After applying all components under Promo 2, then component under Promo 1 will be applied. For this example, the order of application is:
|
|
Pricing Strategy Default Effective Day |
When selected, the user can choose which day of the week price changes will be effective. |
|
Dynamic Area Differentials |
When selected, allows the worksheet to dynamically update secondary locations based on changes to the primary location. |
|
Minimize Worksheet Data |
When checked, the user is given an optional workflow which includes worksheet data filtering. When unchecked, the worksheet filter screen will not be accessible. |
|
Maximum Worksheet Search Result |
Indicates the maximum number of rows that are displayed based on the respective search criteria. |
|
Allow Item List Explosion |
Allows you to select whether the item list should be exploded to the item level or left at itemlist level. Valid values are: Y – Yes/Checked. Two options are provided in the Item Level field: Item List and Item (when Item Type = Item List). N – No/Unchecked. Item Level could only be Item List (when Item Type = Item List). The default value is N/Unchecked. |
|
Hierarchy, Item List, Price Event List, Zone Level # of Item Conflicts Allowed |
The percent value of items on the price event that can fail conflict check and continue with price event approval. If more than the defined percent of items fail, the price event will be set to Worksheet status with errors. |
|
Conflict Check |
|
|
# Days Event Displayed Before Vdate |
The number of days before the VDATE that a pricing event is displayed in the Conflict Review Check window. |
|
# Days Event Displayed After Vdate |
The number of days after the VDATE that a pricing event is displayed in the Conflict Review Check window. |
|
Display Conflicts Only |
When selected, only the record that caused the conflict will be displayed in the lower portion of the Conflict Review List window. When unchecked and the days before/after are provided, the system will search for all records using the price event's effective date as the point to search forward and back. This will bring back all records within the window of time calculated. Multiple records are displayed in the conflict review list window so that if one rule returns conflicts for multiple item/locs in a price event, all those conflicts are displayed. This is limited to a maximum of 100 records. |
|
Unique UOM is used for all items |
(DBA maintained) When selected, you have to specify which UOM should be used when fixed price events are created and the system will skip the UOM validation. |
|
Unique UOM to be used for all items |
(DBA maintained) Specifies which unique UOM needs to be used. This is a required field if "Unique UOM is used for all items" option is checked. |
|
Do not run Conflict Check for Submit |
When checked, the system will skip conflict checking process when the user clicks the Submit button. |
|
Do not run Conflict Check for Complex Promotion Approval |
When checked, the system will skip conflict checking process when the user approves a Complex Promotion. |
|
Price Events |
|
|
Price Change/Promotion Overlaps |
When selected, indicates an item/location can have a price change occur during the middle of an active promotion. |
|
Cost Calculation Method |
The way cost is determined for the zone. Choose Highest Location Cost or Average Location Cost. |
|
Clearance/Promotion Overlaps |
When selected, indicates an item/location can be on clearance and promotion at the same time. |
|
Multiple Item/Loc Promotions |
When selected, an item/location can exist on more than one promotion detail at any given time. |
|
Maximum Number of Overlapping Promotion Component Details |
The number of overlapping promotion components allowed for any single item/location. The default value is 4. |
|
Allow Complex Promotions |
When selected, all promotion types are available. |
|
Purge Reset Clearance Months |
The number of months RPM will retain clearance price events that have reset before purging them. |
|
Default Reset Date |
When selected, indicates a reset date should be defaulted when a clearance is created. The reset date is defaulted to one day greater than the out of stock date. |
|
Promotion End Date Required |
When selected, a promotion end date is required for the promotion header. |
|
Promotion # Days Rejects Held |
The number of days, set in system options, after the end date (or start date for promotions with no end date) of a rejected promotion that it is purged from the system. |
|
Price Change Processing Days |
The number of days, set in system options, between the creation date of a price change and the first date it can become effective. It allows the retailer to insure that price changes are created with enough advance timing that stores and other process areas can react. |
|
Promotion History Months |
The number of months, set in system options, after a promotion is completed that is purged. This parameter is also used to purge cancelled promotions. |
|
Filter Price Change/Clearance Results |
When selected, the user is taken to a filter window that displays the search results for price changes and clearances. |
|
Display Full Promotion Column Detail |
When selected, all columns in the table are displayed. If this option is not selected, not all columns are displayed. If the user wants to review the details for the remaining columns, the user can do so by selecting rows and requesting the additional data. |
|
Display Full Price Change/Clearance Column Detail |
When selected, all columns in the table are displayed. If this option is not selected, not all columns are displayed. If the user wants to review the details for the remaining columns, the user can do so by selecting row(s) and requesting the additional data. |
|
Event ID Required |
When selected, a promotion event must be assigned to the promotion. |
|
Display And/Or Condition |
When selected, this option allows OR conditions to be used when a multi-buy promotion component contains multiple buy lists or reward lists. If this option is not selected, only AND conditions can be used. |
|
Maximum Number of Buy Lists |
This option specifies the maximum number of buy lists allowed for a multi-buy promotion component. |
|
Maximum Number of Reward Lists |
This option specifies the maximum number of reward lists allowed for a multi-buy promotion component. |
|
Number of Past Markup Impact Events Displayed |
The maximum number of past dates that have a cost or retail change to be displayed in the Markup Change Date column, used to review cost/retail change history. The value of this option can be an integer from 1 to 10 (default 1). |
|
Maximum Number of Promotion Component Details per Promotion Component |
Specifies the maximum number of promotion component details for a promotion component. |
|
Maximum Search Results |
|
|
Price Changes |
The maximum number of search rows returned for price changes. If the search limit is reached, a message is displayed informing users that they will not see all of their search results. |
|
Clearances |
The maximum number of search rows returned for clearances. If the search limit is reached, a message is displayed informing users that they will not see all of their search results. |
|
Promotions |
The maximum number of search rows returned for promotions. If the search limit is reached, a message is displayed informing users that they will not see all of their search results. |
|
Price Inquiry |
The maximum number of search rows returned for price inquiry. If the search limit is reached, a message is displayed informing users that they will not see all of their search results. |
|
Location Moves |
|
|
Location Move Lead Time |
The number of days, set in system options, required before a location can be moved between zones in RPM. |
|
Location Move Purge Days |
The number of days RPM will retain location moves that have either successfully completed or are the same number of days past the scheduled effective date but have had no action taken on them. |
|
Promotion Overlap |
When selected, promotions are allowed to overlap a scheduled location move. If Promotion Overlap is selected, a Promotion Overlap Behavior option must be selected. If Promotion Overlap is not selected (default), promotions cannot overlap a scheduled location move. |
|
Promotion Overlap Behavior |
When Promotion Overlap is selected, one of these behavior options must also be selected:
|
|
Inherit New Zones Regular Retail |
When selected, the location inherits the retails of the new zone. If not selected (default), the zone keeps the existing retail. |
|
Pricing Strategy Review Period Overlap |
When selected, pricing strategies with review periods are allowed to overlap a move date. The validation of a worksheet review period is bypassed, and a location move can be scheduled. When unchecked (default), validation is not bypassed. |
Navigate:From the Task Pad, select System Options > System Options Edit. The System Options workspace opens.
Update any enabled fields as necessary.
See "System Options Definitions" for more information.
Click Save to commit any changes and close the workspace.
Navigate: From the Task Pad, select System Options > System Options View. The System Options View workspace opens.
See "System Options Definitions" for more information.
Click Close to exit the workspace.
The following table lists the system defaults.
Table 3-2 System Defaults Definitions
| System Default | Definition | Options |
|---|---|---|
|
Item Level |
The level of an item in an item group. |
|
|
Pricing Strategy |
The pricing strategy is the default strategy type displayed for the user when entering the Pricing Strategy workspace. |
|
|
Diff Type |
The category that a diff belongs. |
Valid diff types from the Merchandising System. |
|
Type |
The type is the default price change type displayed when creating a price change. |
|
|
Currency |
The primary currency used in RPM. |
See LOV button on System Default screen for code and description. |
|
Maintain Margin Strategy Method |
Defines the default method used when creating a maintain margin pricing strategy. |
|
|
Ignore Constraints |
Defines whether or not promotion constraints are taken into account when conflict checking is performed in the worksheet. |
Select/Clear check box |
The Aggregation Level Settings workspace allows you to define system parameters that vary for price strategies and price worksheet. When a department is created in the merchandising system, Oracle Retail Price Management assigns the default value for each parameter to the default or default level defined in the system. You may choose to define the aggregation level at a different parameter than the default. When a price strategy exists for a department, parameters are disabled and cannot be changed.
Navigate: From the Task Pad, select Aggregation Level > Maintain Aggregation Levels. The Aggregation Level Settings workspace opens.
Select the record you want to update.
Click in the field that you want to change.
Lowest Definable Level: Select the lowest level of the merchandise hierarchy for which a price strategy can be defined.
Worksheet Level: Select the level of the merchandise hierarchy at which worksheets are generated.
Historical Sales: Select the sales period RPM should represent as historical on the worksheet.
Regular: Select the check box to indicate that regular sales should be included as part of historical sales in the price worksheet.
Clearance: Select the check box to indicate that clearance sales should be included as part of historical sales in on the price worksheet.
Promotion: Select the check box to indicate that promotional sales should be included as part of historical sales in on the price worksheet.
Include WH Inventory: Select the check box to indicate that warehouse inventory should be included in the calculations for sell through and price change impact in the price worksheet.
Include On Order In Sell Thru: Select the check box to indicate that inventory ordered is included in the sell through calculations on the price worksheet.
Price Change Amount Calc: Select the method of calculating the price change amount on the price worksheet.
New-Current: The current price is subtracted from the new price.
Current-New: The new price is subtracted from the current price.
Past Retail Change Highlight Days: Enter the number of days previous retail changes will cause the Last Price Change column of the pricing worksheet to be highlighted.
Past Cost Change Highlight Days: Enter the number of days previous cost changes will cause the Last Cost Change column on the pricing worksheet.
Pending Cost Change Window Days: Enter the number of days into the future the system should look for pending cost changes.
Pending Cost Change Highlight Days: Enter the number of days into the near future the system should look for pending cost changes. The Pending Cost Change column on the worksheet is highlighted if a cost change falls within the Pending Cost Change Highlight Days.
|
Note: Pending Cost Change Highlight Days must be less than or equal to Pending Cost Change Window Days. |
Click Done to save any changes and close the workspace.
