| Oracle® Retail Assortment & Item Planning for Fashion/Softlines Cloud Service User Guide Release 19.0 F24864-08 |
|
 Previous |
 Next |
| Oracle® Retail Assortment & Item Planning for Fashion/Softlines Cloud Service User Guide Release 19.0 F24864-08 |
|
Previous |
Next |
Prior to the beginning of an item's lifecycle, item planning takes place. The planner has the option of planning regular, promotional, and clearance sales by item, as well as the weekly receipt plan to support sales. The Item Plan can use the approved Assortment Plan as the starting point for the plan which can either come from an external Assortment Planning tool or from the Assortment Strategy described in the prior chapter.
Item-Planning Basics handles the life cycle of Basic/Continuous items. In this workflow, the user has the capability of planning for basics across multiple seasons in one workspace rather than having to plan and replan the same set of items in different workspaces, one for each season. Every fashion retailer has a mix of both basics and seasonal items. Basics are long lifecycle items that include white t-shirts, denims, socks, and so on, and are active lines throughout the year. Seasonal items are short lifecycle items such as specific winter wear or summer wear, active only during a particular season. The planner will have to log in to a different workspace for each season for short life cycle items. But, for long life cycle/basic items, Item-Planning Basics provides a single workspace to work across seasons for the chosen product hierarchy. If a subclass has a mix of both basics and seasonal items, the user can review the aggregated plans of both basics and seasonal style colors in the Item-Planning workbook and make the required edits to meet Targets.
The typical business user who completes this task will be an Assortment Planner and Item Planner. The Planner will usually have completed the Assortment Planning process, and is now ready to plan the execution of that assortment plan for basic/continuous items in the Item Planning - Basics process.
Approved location clusters
Location hierarchy
Product hierarchy
Calendar hierarchy
Sales Retail, Sales Unit, and Cost actuals
Curve Library
Customer Returns actuals
Direct/ecommerce actuals
Item attributes and attribute values
Price elasticity entered by the Administrator
Promotional lifts entered by the Administrator
Markdown lifts entered by the Administrator
Item images loaded by the Administrator (optional)
When working in a segment, it is a common practice to keep the wizard selections for the segment size limited to what will be worked on, to facilitate navigation and increase UI responsiveness.
To create the Item Planning Basics segment:
Click Assortment Services task in the Tasks menu. Then, click the Planning Services activity and then the Item Planning Basics task.
The dialog to create the new plan opens. Click Create New Plan.
Enter a descriptive Plan Label in the text field. Click Ok.
In Select Product, select one or multiple subclasses and click Next. Items having the attribute product type as basics alone will be visible in the wizard as this workbook is exclusively for basics.
In Select Calendar, select the time period for this assortment. Weeks belonging to Multiple Assortment Periods may be brought into the segment. The time period between the first week and the last week serves are the lifecycle of the item.
In Select Cluster Version, select the cluster you want to plan the basics in. If the cluster selected for planning basics is same as the cluster assigned to thr assortment period for the parent department, plans from IP-Basics will match the plans in IP- pre season and In-Season workbooks.
If the cluster selected for planning basics is different than the cluster assigned to the assortment period of the parent department, plans created in IP-Basics stored at the granular level of store will get regrouped to the new cluster definitions of the IP Pre Season and In Season workbooks.
|
Note: Assortment Details can vary by Sub-class. If multiple subcategories are selected, the details shown will be based on the first order Sub-class. When final plans are being reviewed in the IP seasonal workbook, if the cluster versions selected IP-Basics and IP Seasonal workbooks are different, the plans from the Basics workbook will reaggregate based on the cluster definitions of the seasonal workbook. |
Click Finish. The Item Planning Basics segment is built.
The high-level steps to complete this process:
Review targets from Assortment Strategy and MFP.
Plan Sales and Margin by item for basics.
Create a receipt and inventory plan by item for basics.
Reconcile to the targets.
Approve the Op and Cp version item plan for basics.
The planner can review these plans and aggregate basics and seasonal lines against department level targets in the item planning pre-season workbook.
If a user overrides the approved plans for basics in the item-planning pre-season workbook, that will take priority over the approved basics plan. Whichever is the last committed and approved plan, that will have the precedence.
The first step in the Item Planning Basics process is Sales & Margin. The planner can create a unit target from the CP from Assortment Strategy, import it from an external Assortment Plan, or create a unit target using MFP, LY, or a user-entered number. The purpose of this step is to create unit targets for each item, to be used in the creation of the sales plan. This can be performed at the cluster level or higher. This step is also used to define parameters such as whether the item will be assorted in a particular cluster, start and end selling date overrides, markdown events and dates, and adjustments of regular, promotional, and clearance sales.
The steps to complete this process:
Set item parameters.
Define markdowns and promotions.
Seed sales.
Plan regular, promotional, and clearance sales and margin.
Prior to Starting this Step:
An approved Assortment Plan should be completed if the planner wants to use it as a seeding source.
An approved plan from MFP Cloud Service for use in spreading the cluster level plan down to the location level during the Item Plan approval process.
Sub-class/Category targets should be set and reviewed
After Completing this Step:
Plan receipts and inventory based on the sales plan.
Tabs and Views in this Step:
Application Actions
Seed Sales
The Seed Sales Application Action populates an item's weekly sales based on the Sales Source selected.
Calculate What-If
The Calculate What-If Application Action is used to calculate the effect of potential markdowns or promotions on the selected products. The Calculate What-If Application Action will calculate the new unit and retail sales and margin, after considering the discount applied and the elasticity (sales lift) that correlates to the selected discount. After running the Application Action, What-if measure data will be populated with the calculated effect.
Apply What-If Plan
The Apply What-If Plan Application Action is used to copy what-if promotion measure data into the working plan measures. After running the Application Action, what-if promotion measure data will be cleared.
Refresh Product Rollup
The Refresh Product Rollup Application Action creates dynamically nested three groups of alternate hierarchies based on three user-defined attribute selections for each selection. After running the Application Action, the user may select the alternate product hierarchy to see rollups based on the selections.
The Plan Parameters tab is used to plan Target Sales U, override start and end sell dates, seed sales based on a selected data source, and select markdown events and dates. Using the Linked Items measure profile, plan Markdown events, and the markdown timeframes, the planner may copy sales from a discontinued item to its replacement item for items that were linked in the Assortment.
The Plan Parameters view is used by the planner to assign a curve, seed sales, and set markdown events and dates for each item and location cluster. If all items within a Sub-class and all clusters will receive the same data, the planner can roll up to Sub-class and All Location in the product and location hierarchies, respectively.
The steps to complete this process:
Review the assorted items in the AP Tgt Assorted Item Boolean measure. Item Plans will be created for all assorted items. AP Tgt Assorted Item will be true if any weeks within this basic planning workbook contain weeks where the item is assorted in AP.
AP Tgt Sales U is the sum of all sales planned and approved from assortment periods. You can use the variance measure to populate the Tgt Sales U which is used to create the weekly sales using the selected curve. For item Planning Basics, this can be manually planned by the planner based on the number of seasons an item is being carried in. If AP Tgt Sales U gives N number of units per assortment period. If the planner is planning to carry this item in three assortment periods, planner can populate the Tgt Sales U as 3*N, thereby planning enough quantity required to last the life. Planners can also plan units by editing the Target ROS measure which recalculates the Target Sales U.
Review the start and end selling weeks. The start and end selling week dates are based on the start and end week selected in the calendar wizard.
Optionally, override the start and end selling week dates. If the override start date is outside the workbook weeks, it will default the start week to the first week of the workbook. Similarly, if the override end date is outside the workbooks weeks, it will be defaulted to the end of workbook period.
In the WP Seed Sales measure, check the Boolean.
In the WP Seed Sales Source measure, select a data source to seed sales from:
Target Using Selected Curve: Sales TGT defined in the Target Review step.
If this is the source selected, the WP Curve Source must also be defined.
Last Year: last year.
Like Item LY: like item last year.
Forecast: forecast.
IP CP: Item Plan Current Plan.
Like Item CP: Like Item Current Plan.
If this is the source selected, then WP Like Item and WP Like Item % must also be defined.
In the WP Curve Source measure, select the curve from which to seed sales.
Curves were set in the Assortment Maintenance segment and can be referenced in the Review Curve Library view.
If you want to assign a like item, in the WP Like Item measure, select the existing item to assign to the new item.
In the Like Item % measure, assign an adjustment ratio for the existing item sales to be copied to the new item.
In the Markdown Event measure, select the appropriate markdown event for the item.
A real time alert has been provided to alert the user if the target is selected, but curve source and type is not set.
Additionally there is a real time alert if you select Seed Sales source of Like Item, but WP Like Item is not set.
In the WP Start Markdown, select the date that the markdown will begin for the item.
Once a Markdown Event and Date have been assigned to an item, the sales plan for that item will be allocated to Clearance sales for the remainder of the Assortment Period.
Markdowns and their associated discounts and lifts were set in the Assortment Maintenance segment and can be referenced in the Review Markdowns Library view.
Note that if markdowns will occur by item attribute, the Define Product Rollup view can be used to assign a dynamic attribute rollup to assign markdowns based on attribute values. For example, if you know that all items of a particular brand will be marked down on the same date, you can set the attribute of Brand as a Dynamic Product Attribute and set markdowns for all items under the brand. For information about how to set the attributes, see "Define Product Rollup View."
Measure Table
Table 13-1 1. Define Parameters View Measures
| Label | Definition |
|---|---|
|
AP Tgt Assorted Item |
A Boolean flag measure used to indicate that an item is carried in the approved Assortment Plan. AP Tgt Assorted Item will be true if any weeks within this basic planning workbook contain weeks where the item is assorted in AP. |
|
AP Tgt Assorted Item Count |
An integer measure used to indicate the total number of items carried. |
|
Tgt Sales U |
The Target Sales U planned by the planner. AP Tgt Sales U is the sum of all sales planned and approved cycle of the item. |
|
Tgt ROS |
The Target Rate Of Sale Planned by the planner. Planners can edit the Target ROS to change the Target Sales U. |
|
AP Start Week |
Read-only week based on the start week of the assortment period where the item is first assorted. |
|
Tgt Sales U Var AP Tgt % |
Variant measure that can be used to set Tgt Sales U in comparison with AG Tgt Sales U. |
|
Start Week |
The beginning of the item life cycle per the calendar wizard selection. If AP Start Week is populated, then it equals the AP Start Week. If not, it will default to the first week of the workbook built unless Selling Start Override is entered. |
|
End Week |
The ending of the item life cycle per the calendar wizard selection. It will default to the last week of the workbook built unless Selling End Override is entered. |
|
Wp Selling Start(Override) |
Overridden value of beginning of item lifecycle. |
|
Wp Selling End(Override) |
Overridden value of end of item lifecycle. |
|
WP Seed Sales |
A Boolean flag measure which is required to be checked to create a weekly sales plan for assorted items. |
|
WP Seed Sales Source |
A picklist used to select the flow source for an item's sales. |
|
WP Curve Source |
A picklist used to select the curve source for an item's sales. |
|
WP Like Item |
An item used to populate the Sales R, U, and GM R of a new item being added to the assortment using an adjustment ratio. |
|
WP Like Item % |
Provides a facility to adjust a new item's Sales R, U, and GM R by using a percentage ratio to the sales of the like item. |
|
WP Markdown Event |
A picklist measure used to display markdown events that correspond to a markdown percentage, viewable in the Review Markdowns Library view. |
|
WP Start Markdown |
The start date that the markdown percentage will occur. |
Measure Profile
Default Profile
The Default profile is used to assign item parameters before planning sales.
AP Targets Profile
The Profile having aggregated approved plans. Target Sales U can be planned here based on the aggregated Approved AP Target Sales U. Target Sales U can now be planned to be copied as the Approved AP Target FP Sales or the AP Target Buy Quantity. During Assortment planning of basic items, planner can create high buy quantity to cater to sales across multiple assortment periods in one go and copy that buy quantity as the AP Target Sales U to start creating item plans for basic items across multiple assortment periods. Else, user can also consider the planned Target Sales to copy as AP Target Sales U.
The Define Promotions view is used to assign promotions to items or a Sub-class. If all items within a Sub-class and all clusters will receive the same data, the planner can roll up to Sub-class and All Location in the product and location hierarchies, respectively.
The steps to complete this process:
In the WP Promo Week measure, check the Boolean for the item/week that a promotion will occur.
In the WP Promo Event measure, select the promotion event associated with the item/week.
Once a Promotion Event and Week have been assigned to an item, the sales plan for that item will be allocated to Promotional sales for the duration of the Promotion Events and Weeks selected.
If you select a Promotion Week, but not a Promotion Event, the Regular sales plan for the item will be allocated to the Promotional sales for the duration of the Promotion Weeks selected with no promotional lift.
Promotion Events and their associated discounts and lifts were set in the Assortment Maintenance segment and can be referenced in the Review Promotions Library view.
If you previously assigned an item to have a markdown, it will be visible in this view as a reference.
Note that if promotions will occur by item attribute, the Define Product Rollup view can be used to assign a dynamic attribute rollup to assign promotions based on attribute values. For example, if you know that all items of a particular size will have a promotion on the same date, you can set the attribute of Size as a Dynamic Product Attribute and set promotions for all items that have that size attribute. For information about how to set the attributes, see "Define Product Rollup View."
Run the Seed Sales Application Action to populate the weekly sales plan based on the selected parameters.
Measure Table
Table 13-2 2. Define Promotions View Measures
| Label | Definition |
|---|---|
|
IP Selling Weeks |
A Boolean flag measure used to indicate the weeks the item is active in the assortment. |
|
WP Promo Week |
A Boolean flag measure used to indicate that an item is on promotion that week. |
|
WP Promo Event |
A picklist measure used to display promotional events that correspond to a promotion percentage, viewable in the Review Promotions Library view. |
|
Markdown Week |
A read-only measure which indicates which products/ weeks have planned markdowns. |
Measure Profile
Default Profile
The Default profile is used to assign promotion events and weeks to items.
The Define VAT Rate view is used by the planner to choose the VAT Rate used for the category.
The step to complete this process:
In the Use VAT Rate picklist measure, select the appropriate VAT rate for the category.
Measure Table
Table 13-3 3. Define VAT Rate View Measure
| Label | Definition |
|---|---|
|
Use VAT Rate |
User-selected VAT rate for the category/store being planned. |
Measure Profile
Default Profile
The Default profile is used to select the appropriate VAT Rate.
The Review Markdowns Library view is a reference-only view used to review the planned markdown discounts and the associated sales lifts that are expected with each markdown amount that was set up in Promotion and Markdown Maintenance.
The step to complete this process:
Review the markdown discounts and their associated sales lifts by markdown amount and Sub-class, as necessary.
Measure Table
Table 13-4 4. Review Markdowns Library View Measures
| Label | Definition |
|---|---|
|
Markdown Discount % |
The planned markdown elasticity percentage. |
|
Markdown Sales Lift % |
The markdown sales lift based on the planned markdown elasticity for the amount and Sub-class. If an override is used, it will take the place of the system-calculated value in the Item Planning segments. |
Measure Profile
Default Profile
The Default profile is used to view each markdown amount and its related discount and sales lift percent.
The Review Promotions Library view is a reference-only view used to review the planned promotional discounts and the associated sales lifts that are expected with each promotion event that was set up in Promotion and Markdown Maintenance.
The step to complete this process:
Review the promotional discounts and their associated sales lifts by promotion event and Sub-class, as necessary.
Measure Table
Table 13-5 5. Review Promotions Library View Measures
| Label | Definition |
|---|---|
|
Promo Discount % |
The planned discount percentage of the promotion. |
|
Promo Sales Lift % |
The percent of increased sales that must occur to overcome the decrease in price to sell the same dollar amount. The lift in this measure is automatically calculated from the Planned Promo Discount % measure after calculating. If an override is used, it will take the place of the system-calculated value in the Item Planning segments. |
Measure Profile
Default Profile
The Default profile is used to view each promotion event and its related discount and sales lift percent.
This tab is used to review the curve.
The Review Curve Source view shows the normalized Forecast, Last Year, and MFP sales curve % for the calendar duration of the workbook at Subclass/Cluster. The seed sales custom menu is executed with the curve source selecting either the absolute or relative curve. If the planner selects Absolute as the curve type, Absolute will take the courve source's respective selling weeks of the item and normalize it. If the user selects the curve type Relative, it will take the curve of the entire workbook duration and shrink it to fit the item's selling periods.
The Review Curve Source view is a reference-only view used to review curves that were set up in Curve Maintenance. The curves can be applied to the sales, to intelligently spread sales over time, which is later used for planning receipt flows. For more information about the different types of curves and their functionality, see Chapter 10, "Curve Maintenance.".
The step to complete this process:
Review the sales percent to totals for each curve, as necessary.
Measure Table
Table 13-6 3. Review Curve Source View Measure
| Label | Definition |
|---|---|
|
Fcst Sales Curve U % |
Used to display the weekly sales percent to total of Forecast Sales curve. |
|
Ly Sales Curve U % |
Used to display the weekly sales percent to total of Last year Sales curve. |
|
MFP Sales Curve U% |
Used to display the weekly sales percent to total of MFP Sales curve. |
Measure Profile
Default Profile
The Default profile is used to view each curve.
The Review Normalized Curve view is a read-only curve showing the applied sales percent to total of the selected curve at the style-color level. This view allows the planner to analyze weekly sales percentage at the item level for a chosen cluster.
Measure Table
Table 13-7 2. Review Normalized Curve View Measure
| Label | Definition |
|---|---|
|
Wp Normalized Curve U % |
Used to display the weekly sales percent to total of the applied sales curve. |
Measure Profile
Default Profile
The Default profile is used to view the curve for each style-color.
The Sales and Margin tab is used to plan regular, promotional, and clearance sales by item and cluster. What-if promotional plans and markdown plans may be created to help the planner understand the financial impacts of different promotional and markdown scenarios. The what-if scenarios can be applied to the working plan for approval, if deemed appropriate by the planner.
The Plan Sales and Margin view is used by the planner to plan regular, promotional, and clearance sales by item, week, and location cluster. What-if analysis can be used to simulate and evaluate the impact of different promotional and markdown activities on sales and markdowns.
Running the Seed Sales Application Action creates the following logic for each Assorted Basic Item:
Source Sales Units are spread to week based on the source selected.
Units are multiplied by the Base Unit Price and Base Unit Cost to get Retail and Cost.
Base Unit Price and Cost are interfaced from a source system for existing items and entered by the planner for placeholder items in the Item Administration segment.
The steps to complete this process:
Review and adjust each item/week/cluster Regular, Promotional, and Clearance Sales:
It is a best practice to seed sales before planning the sales buckets so that there is a demand curve in Reg, Promo, and Clr Sales from which to begin your plan.
If there is no seeding and no prior data entered, then planning WP Sales will spread proportionally (since there is no demand curve the data will spread evenly) to Reg, Promo, and Clr Sales.
If that is not the desired behavior, plan Reg Sales, Promo Sales, and Clr Sales before planning Sales, so that a demand curve is in place before planning WP Sales.
Review and adjust Sales after having planned Regular, Promotional, and Clearance Sales, if necessary.
User-Defined Exceptions are a helpful way to identify exceptions which would need to be manually adjusted. For detailed information on these capabilities, see the Oracle Retail Predictive Application Server Cloud Edition User Guide.
Review AUC and GM measures to ensure financial viability of the plan.
Measure Interactions
The following logic is used when planning different types of sales:
WP Sales are the aggregation of WP Sales Reg, WP Sales Promo, and WP Clr.
Updates to WP Sales will update WP Reg Sales, WP Promo, and WP Clr Sales proportionally.
Updates to WP Sales Reg R will hold AUR and recalculate Units.
The following logic is used when planning promotions and markdowns:
If a Promotion or Markdown event is applied to a week, the predefined discount percent is applied to the WP Reg Sales and the pre-defined Sales Lift % is applied to WP Reg Units, which are then multiplied to calculate the WP Promo/Clr Sales Retail and Units.
Updates to WP Sales Promo Disc % or the WP Markdown % will apply the entered discount to the WP Promo/Clr Sales AUR, hold the units and recalculate WP Promo/Clr Sales Retail.
Updates to WP Sales Promo/Clr R will hold the AUR and recalculate units.
Measure Table
Table 13-8 1. Plan Sales & Margin View Measures
| Label | Definition |
|---|---|
|
Selling Weeks |
A Boolean flag measure used to indicate the week the item begins selling in the assortment. |
|
WP Event |
Populated after a What-if promotion or markdown event is applied after running the Apply WI Application Actions, or the planner can manually enter a value. |
|
WP Sales Reg R, U, AUR |
Regular Sales Retail, Units, and Average Unit Retail. |
|
WP ROS |
Working Plan Rate of Sales. |
|
WP Sales Promo R, U, AUR |
Promotional Sales Retail, Units, and Average Unit Retail. |
|
WP Sales Promo Disc % |
The Promotional discount percent applied to the promotional week. |
|
WP Sales Clr R, U, AUR |
Markdown Sales Retail, Units, and Average Unit Retail. |
|
WP Markdown % |
The Markdown discount percent applied to the markdown week. |
|
WP Sales GM R, GM R % |
Sales Gross Margin value and Gross Margin percent for an item. |
|
Fcst Sales U |
Forecasted Sales Units from RDF or RDF Lite. |
|
Base Unit Price R |
An item's retail value, which can be different by location. |
|
WP Sales R, U, C, AUR, AUC |
Working Plan Sales Retail, Units, Cost, Average Unit Retail, and Average Unit Cost. |
Measure Profiles
Default Profile
The Default profile is used to plan regular, promotion, and clearance sales by item and cluster.
Return/Net Sales Profile
The Return/Net Sales profile is used to plan customer returns and view net sales, as well as compare the returns and net sales to last year (LY) and the Item Plan Original Plan (OP).
The steps to complete this process:
Review the seeded Customer Returns data and make adjustments by item and cluster as necessary.
Review the Net Sales data.
Net Sales = Sales - Customer Returns
Measure Table
Table 13-9 1. Plan Sales & Margin View with Returns/Net Sales Measures
| Label | Definition |
|---|---|
|
Fcst Sales U |
Forecasted Sales Units from RDF or RDF Lite. |
|
Customer Returns R, R %, U, U%, AUR, C, AUC |
Customer Returns Retail, Retail percent of WP Sales R, Units, Units percent of WP Sales U, Average Unit Retail, Cost and Average Unit Cost |
|
Net Sales R, U, AUR, C, AUC, GM R, GM % |
Net Sales = Sales - Customer Returns Net Sales Retail, Units, Average Unit Retail, Cost, Average Unit Cost, Gross Margin value and Gross Margin percent. |
|
WP Sales C, AUC |
Working Plan Sales Cost and Average Unit Cost for an item. |
Last Year Profile
The Last Year profile is used to review last year regular, promotional, and clearance data compared to the working plan.
Original Plan Profile
The Original Plan profile is used to review the most recently approved Item Plan Original Plan (OP) regular, promotional and clearance data compared to the working plan.
Current Plan Profile
The Current Plan profile is used to review the most recently approved Item Plan Current Plan (CP) regular, promotional, and clearance data compared to the working plan.
Direct WP/LY Plan Profile
The Direct WP/LY profile is used to review and plan measures related to the Direct, or ecommerce business, and compare to last year.
Measure Table
Table 13-10 1. Plan Sales & Margin View with Direct WP/LY Measures
| Label | Definition |
|---|---|
|
Traffic Count |
Measures the hits an item receives. |
|
Conversion Rate |
Conversion rate is calculated as Transaction Count/ Traffic Count. |
|
Transaction Count |
Measures the number of transactions for an item. |
|
Avg Transaction Size |
Average Transaction Size is calculated as Sales U/ Transaction Count. |
|
Avg Transaction Size U var LY % |
Average transaction variance to Last Year, when the data is available. |
|
Customer Returns U, U %, R, R%, AUR |
Customer Returns Units, Units percent of WP Sales U, Retail, Retail percent of WP Sales R, Average Unit Retail. |
Direct WP/OP Plan Profile
The Direct WP/OP profile is used to review and plan measures related to the Direct, or ecommerce business, and compare to the Item Plan Original Plan (OP). The measures for the Direct WP/LY Plan and Direct WP/OP Plan profile look similar, replacing the LY measures by the OP measures.
The What-If Price Point Setup View is used to define What-If price points, which will drive the what-if discount not associated to predefined events. The promotional what-if and markdown what-if capabilities are both driven by percent off; this capability is the setup view for another choice to promote or mark down by price points. Examples of price point promotions would be to promote a product from 80.00 to 49.99, or 2 for 29.99 (14.99 each). Setup entails defining the new price points and the sales lift associated with that price point.
The steps to complete this process:
For products planned to have a price point promotion, enter the What-if Promo Price R and Sales Lift % that will be used in the item plan.
For products planned to have a clearance price point, enter the What-if Clr Price R and Sales Lift % that will be used in the item plan.
Measure Table
Table 13-11 2. What-If Price Point Setup View Measures
| Label | Definition |
|---|---|
|
Retail Price |
Price upon which price point discount is based. |
|
What-if Promo Price R |
User-entered promotional price point. |
|
What-if Promo Disc % |
((Base Unit Price R - What-if Markdown Price R)/Base Unit Price R). |
|
What-if Promo Sales Lift % |
User-entered lift associated with the promotional price point. This defines how much more the product will sell than the currently planned WP sales, once the promo price is in effect. |
|
What-if Clr Price R |
User-entered clearance price point. |
|
What-if Clr Disc % |
((Base Unit Price R - What-if Markdown Price R)/Base Unit Price R). |
|
What-if /Clr Sales Lift % |
User-entered lift associated with the clearance price point. This defines how much more the product will sell than the currently planned WP sales, once the clearance price is in effect. |
The What-If Plan view is used to perform what-if analysis with different promotions or markdowns. It allows the planner to view the sales, units and gross margin impacts if a larger or smaller promotion or markdown is taken, without changing the working plan measures. The What-if capability provides an intelligent tool for analysis; it automatically incorporates different sales lifts for different types of discounts, using either an entered lift percent or the products' elasticity (responsiveness to a discounted price). If the planner wants to apply the what-if plan to override the working plan, the Apply What-If Plans Application Action can be run to automatically copy the data to the working plan. Promotions and markdowns can be planned by item/week/location cluster or at higher levels in the hierarchy, as desired.
Item Planning provides four options to perform a what-if analysis:
By promotion event
By markdown amount
By price point
By directly entering what-if sales AUR, discount %, and/or lift %
The steps to complete this process:
Select the measure profile consistent with the type of what-if that will be performed: 1. Promotion or 2. Markdowns.
Calculate the what-if:
To what-if using an event: In the What-if Promo or Markdown Event measure, select the what-if promotion event associated with the item/week/cluster and click Calculate What-if.
The What-If Promotion or Markdown lift is calculated from Reg Sales.
To what-if using a price point: Check the What-If Apply Price Point measure for the item/week(s)/cluster and click Calculate What-if.
The What-If Promotion or Markdown lift is calculated from Reg Sales.
|
Note: When performing a What-if for Markdowns, check the What-if Apply Calc Onwards measure for the week when applying the markdown, which will apply the markdown from the current week's change to the remaining future weeks. |
Review the What-if Promo or Markdown sales measures to view the sales, unit and gross margin impact of the what-if event.
Promotion events and Markdown amounts and their associated discounts and lifts were set in the Assortment Maintenance segment and can be referenced in the Review Promotions Library or Review Markdowns Library view.
If you previously assigned an item to have a markdown, it will be visible in this view as a reference.
Review the What-if Gross Margin R, Gross Margin R%, and variance measure.
Continue making adjustments to the what-if plan until satisfied with the financial results.
Once satisfied with the what-if plan in WP, copy it into the WP Apply What-if Promo (or Markdown) Plan measure, and check the Boolean for the item/week/cluster that a what-if markdown will occur.
Run the Apply What-If Plan Application Action to copy the what-if measure data to the WP measure data.
After running the Application Action, the what-if measure data will be cleared.
Note that if there is a business need to override the markdown discounts and lifts, use the appropriate measures in the Promotions or Markdown measure profile.
Additional platform capabilities exist which further enhance the What-If capabilities. The scenario feature of RPAS can be used to create a completely different second scenario, and compared against the planned scenario, by creating a scenario and then measure profile What-if Override and following the same process as above using the (Override) measures. Details on this feature can be found in the Oracle Retail Predictive Application Server Cloud Edition User Guide.
Measure Profile
Promotions Profile
The Promotions profile is used to plan what-if promotions to assess the financial impact of different scenarios. This view offers the ability to what-if for a promotional event or promotional price point. It also provides the ability to override the promotional discount, lift, or AUR.
Measure Table
Table 13-12 3. What-If Plan with Promotions Measure Profile View Measures
| Label | Definition |
|---|---|
|
WP Event |
Populated after a What-if promotion or markdown event is applied after running the Apply WI Application Actions, or the planner can manually enter a value. |
|
Base Unit Price R |
An item's retail value, which can be different by location. |
|
WP Apply What-if Promo Plan |
Boolean measure that when flagged and used in conjunction with the Apply WI Markdown Application Action, copies the what-if promotion plan into the working plan. |
|
What-if Promo Event |
Picklist used to select a what-if promotion event. |
|
What-if Sales U, R, AUR, C, GM R, GM % |
The aggregation of What-if Reg, What-if Promo, and What-if Clr Sales Units, Retail, Average Unit Retail, Cost, Gross Margin value and Gross Margin percent. |
|
WP Sales Reg U, R, AUR |
Working Plan Sales Regular Units, Retail, and Average Unit Retail. |
|
Fcst Sales U |
Forecasted Sales Units from RDF or RDF Lite. |
|
Selling Weeks |
A Boolean flag measure used to indicate the week the item begins selling in the assortment. |
|
What-if Sales Reg U, R, AUR |
What-if Regular Sales Units, Retail, and Average Unit Retail. If a What-if Promotion event is planned, the Regular sales will be cleared. |
|
What-if Promo Lift % |
The Promotional lift percent associated with the selected What-if Promo Event. This comes from the administration views and can be overridden if needed. |
|
What-if Promo Sales Lift U |
The unit lift associated with the selected What-if Promo Event. This comes from the administration views and can be overridden if needed. |
|
What-if Promo Sales R, U, AUR |
What-if Promotional Sales Retail, Units and Average Unit Retail. |
|
What-if Sales Promo Disc % |
The Promotional discount percent applied to the promotional week. |
Markdowns Profile
The Markdowns profile is used to plan what-if markdowns to assess the financial impact of different scenarios. This view offers the ability to what-if for a markdown event or price point. It also provides the ability to override the markdown discount, lift or AUR. As markdowns are permanent (do not end), the planner should check the What-if Apply Calc Onwards measure for the week when applying the markdown, which will apply the markdown from the current week's change to the remaining future weeks.
Measure Table
Table 13-13 3. What-If Plan with Markdowns Measure Profile Measures
| Label | Definition |
|---|---|
|
WP Event |
Populated after a What-if promotion or markdown event is applied after running the Apply WI Application Actions, or the planner can manually enter a value. |
|
Base Unit Price R |
An item's retail value, which can be different by location. |
|
WP Sales Reg U, R, AUR |
Working Plan Sales Regular Units, Retail, and Average Unit Retail. |
|
Fcst Sales U |
Forecasted Sales Units from RDF or RDF Lite. |
|
Selling Weeks |
A Boolean flag measure used to indicate the week the item begins selling in the assortment. |
|
WP Apply What-if Markdown Plan |
Boolean measure that when flagged and used in conjunction with the Apply WI Markdown Application Action, copies the what-if promotion plan into the working plan. |
|
What-if Markdown Event |
Picklist used to select a what-if promotion event. |
|
What-if Apply Price Point |
Boolean measure that when flagged will apply the price point associated with the product. This price point is established by the planner in the 2. What-if Price Point Setup view. |
|
What-if Sales U, R, AUR, C, GM R, GM % |
The aggregation of What-if Reg, What-if Promo, and What-if Clr Sales Units, Retail, Average Unit Retail, Cost, Gross Margin value and Gross Margin percent. |
|
What-if Sales Reg U, R, AUR |
What-if Regular Sales Units, Retail, and Average Unit Retail. If a What-if Clearance event is planned, the Regular sales will be cleared. |
|
What-if Clr Lift % |
The clearance lift percent associated with the selected What-if Promo Event. This comes from the administration views, and can be overridden if needed. |
|
What-if Clr Sales Lift U |
The unit lift associated with the selected What-if Markdown Event. This comes from the administration views, and can be overridden if needed. |
|
What-if Clr Sales U, R, AUR |
What-if Clearance Sales Retail, Units, and Average Unit Retail. |
|
What-if Apply Calc Onwards |
If this is checked, the markdown change will apply from the current week's change to the remaining future weeks. This is provided so that the planner has the option to apply markdown clearance across multiple weeks without having to manually edit each week. |
Application Actions
Calculate What-If
The Calculate What-If Application Action is used to calculate the effect of potential markdowns or promotions on the selected products. The Calculate What-If Application Action will calculate the new unit and retail sales and margin, after considering the discount applied and the elasticity (sales lift) that correlates to the selected discount. This also allows the What-if Promo Sales AUR, Promo Disc %, and Promo Lift % to be editable. After running the Application Action, What-if measure data will be populated with the calculated effect.
Apply What-If Plan
The Apply What-If Plan Application Action is used to copy what-if promotion measure data into the working plan measures. After running the Application Action, what-if promotion measure data will be cleared.
This tab is used to reconcile the working plan with MFP Targets to approve the item plan for basics.
The Reconcile to MFP view in Item planning Basics is used by the planner to compare the working plan of the item plan to the approved MFP Current Plan (MFP Tgt) for each Sub-class and cluster.
The steps to complete this process:
Review WP Sales var MFP Tgt % measures to identify variances that are outside of acceptable parameters.
Review Sales R, Sales U, Sales C, and GM variances to ensure that all of the financials meet targets or are within the targets.
Make adjustments to the sales and the receipt plans to be within an acceptable variance.
If a Sub-class has a mix of both Basic and Seasonal lines, Basics are planned here. MFP Targets serve as a reminder of the Target. Final Reconciliation happens in the Item Planning Pre-season workbook after aggregating item plans for both Basics and Seasonal lines
Repeat this process for each Sub-class and cluster in the assortment.
Note that if a Location Plan is not available, the MFP CP view displays the MFP Current Plan by Sub-class spread to Location using last year's location sales' proportionality. If a Location Plan is available, the MFP CP view displays the MFP Current Plan by Sub-class spread to Location using the Location Plan CP sales' proportionality.
Measure Table
Table 13-14 Reconcile to MFP View Measures
| Label | Definition |
|---|---|
|
MFP Sales R, U, AUR, C, AUC, GM R, GMR% |
MFP Sales Retail, Units, Average Unit Retail, Cost, Average Unit Cost, Gross Margin value, Gross Margin percent. |
|
MFP Sales Reg + Promo R, U, AUR |
MFP Full price Sales Retail, Units, Average Unit Retail. |
|
MFP Sales Clr R, U, AUR |
MFP Clearance Retail, Units, Average Unit Retail. |
|
WP Sales R, U, AUR, C,AUC, GM R, GM R% |
IP Working Plan Retail, Units, Average Unit Retail, Cost, Average Unit Cost, Gross Margin value, Gross Margin percent. |
|
WP Sales Reg+Promo R, U, AUR |
IP Working Plan Full Price Retail, Units, Average Unit Retail. |
|
WP Sales Clr R, U, AUR |
IP Working Plan clearance Retail, Units, Average Unit Retail. |
This tab is used to select item attributes to view in an alternate hierarchy.
The Define Product Rollup view is used to select product attributes to view in an alternate hierarchy. This is available in the tab to display the item level. Nested product attribute roll up has been provided with three levels. A planner can set up to three different combinations for nested rollup with a maximum of three levels in each combination.
For example: as a first combination, you select Brand as a Level1, Color as Level2, and Fabric as Level3 by clicking the list of attributes available at that category. This allows you to roll up your items by brand, then color inside each brand, and then by fabric inside each color.
This feature allows the planner to analyze and review the proposed assortment based on important attributes. You may select up to three attributes at a time for the dynamic rollup.
The steps to complete this process:
Select up to three dynamic product attributes from the picklist.
Run the Refresh Product Rollup Application Action.
To view the product attribute:
In a view that displays item level, click the Product Hierarchy tile.
Select the attribute (Attribute 1 or 2 or 3) that you would like to view in the nested dynamic rollup.
Click OK.
Measure Table
Table 13-15 Define Product Rollup View Measure
| Label | Definition |
|---|---|
|
Product Attribute 1, 2, 3 |
Picklist to present product attributes for a dynamic product hierarchy rollup. |
Measure Profile
Default Profile
The Default profile is used to select dynamic product attributes. The planner can view up to three Levels to review and work on Plans rolled up to multiple attributes. Using the nested dynamic product rollup feature, the planner can group plans for three different attributes. If a planner is working on a class, level 1 is brand, level 2 is color, and level 3 is fabric, the planner can review and analyze plans for all brands of a class, then across all colors inside each brand, and then across every fabric for each color.
Application Action
Refresh Product Rollup
The Refresh Product Rollup Application Action creates dynamically updated alternate hierarchies based on user-defined attribute selections. After running the Application Action, the user may select the alternate product hierarchy to see rollups based on the attribute selections.
Integration with Assortment Planning
The Basic Sales Reg+Promo U is available in the Build Wedge and Plan Buy Quantity worksheets in Wedge as a read-only measure to show the approved CP Sales Reg and Promo units from the Item Planning - Basics template. This will allow the user to see basics planned sales in case these basic items already have sales planned farther out in the future; so it serves as s reference for the AP planner to select the basic iteme with the sales plan and use for planning the buy quantity.
Integration with Item Planning
The WP and approved version of data from the Item Planning - Basics workbook should reflect in the pre-season and in-season templates. It will load/refresh the corresponding week's Sales plan from the Basics workbook to the Item Planning templates. It also works vice versa if a user plans in the Item Planning templates for the basic items and commit/approve should reflect the change in the Basics workbook.
If the basic items are planned farther out in the planning horizon than the assortment periods, there will be a real-time alert in pre-season and in-season workbooks to notify the user that they should assort/add the basic item with the approved plan. In the pre-season workbook, this real-time alert will be reflected in the WP Assorted Item flag. In the in-season workbook, this real-time alert is reflected in Keep/Add/Drop. This will allow the user to make sure they include the basic items already planned ahead in the planning horizon using the new basic planning template.
The third step in the Item Planning Basic process is Receipts & Inventory for basic lines. This step is used to define parameters such as BOS inventory, initial buys, lead time, presentation minimums, and safety stock, among other parameters.
The steps to complete this process:
Set inventory parameters.
Seed receipts.
Adjust receipts and inventory based on the sales plan.
Prior to Starting this Step:
Category target should be set.
Item sales plans should be completed.
After Completing this Step:
Reconcile the sales and inventory plan to AP and/or MFP.
Tabs and Views in this Step:
Application Actions
Flow Receipts
The Flow Receipts Application Action populates a weekly receipt plan based on the parameters Order Frequency, Pres Mins, Safety Stock U, and Safety Stock Weeks.
Round Receipts
The Round Receipts Application Action uses the inputs of WP Pack Size U and WP Min Order Quantity to round receipts up to match these parameters.
The Receipts & Inventory tab is used to set inventory parameters to flow receipts and to adjust weekly sales and receipts to create an inventory plan for reconciliation and approval.
The Define Parameters view is used by the planner to assign inventory and receipt parameters in order to flow receipts. Based on the parameters, the system will calculate the optimal receipt flow to support the sales plan.
The steps to complete this process:
In the WP Flow Receipts measure, check the Boolean.
If an item is a carryover item, it will inherit its projected EOP for the Start Sell week and populate the BOP.
For the new item, plan the BOP for the first week Item Lifecycle, visible in the Receipts and Inventory tab.
Entering a BOS would not be necessary in this scenario.
Planning the BOS will populate the first week BOP of the Assortment Period, visible in the Receipts and Inventory tab.
Plan two out of the three measures to calculate the third value.
In the WP Initial Buy U, C, and AUC measures, enter the initial buy quantities for each item.
Plan two out of the three measures to calculate the third value.
In the WP Initial Receipt Lead Time measure, enter the number of weeks before the Start Sell week that receipts should be received.
In the WP Lead Time (Days) measure, enter the number of days it takes for product to arrive from your vendor/supplier to the warehouse or store.
This measure is used to generate the Immediate Need real time alert in the In-Season Planning segment, letting you know that your EOP is below your Safety Stock.
In the WP Lead Time Future (Days) measure, enter the number of buffer days it takes for product to arrive from your vendor/supplier to the warehouse or store.
This measure is used to generate the Lead Time Future Need real-time alert in the In-Season Planning segment, letting you know that your future EOP is below your Safety Stock.
In the WP Order Frequency (Weeks) measure, enter how often receipts will arrive.
For example, entering 1 means that receipts arrive every week, 2 means that receipts arrive every other week.
In the WP Presentation Min U measure, enter the minimum amount of inventory on the sales floor per store.
This is used only in calculating the initial buy and can be thought of as a fixture fill.
In the WP Safety Stock U measure, enter the quantity of units that should be maintained to mitigate the risk of stock-outs.
Use this measure if you know that a certain unit quantity should be kept on hand for safety stock.
It is recommended to use Safety Stock U or Safety Stock (Weeks), not both, as they are both used to generate a recommended initial buy.
In the Safety Stock (Weeks) measure, enter the number of weeks of sales that the safety stock should cover.
Use this measure to use future weeks of sales to generate a dynamic safety stock recommendation.
It is recommended to use Safety Stock U or Safety Stock (Weeks), not both, as they are both used to generate a recommended initial buy.
Click Calculate.
Review the WP Initial Buy U var Recommended % to compare the user set initial buy to the system calculated initial buy that is based on the entered parameters.
The WP Recommended Initial Buy is based on BOS, Order Frequency, Presentation Minimums, Safety Stock Weeks, Safety Stock U, and the Sales plan.
Make adjustments to the initial buy quantities to ensure that items are not over or under inventoried.
In the Tgt WOS measure, enter a target Weeks of Supply.
This is used in the In-Season segment to compare the Tgt WOS with the WP WOS.
In the WP Pack Size U measure, enter how many items come in a pack.
This measure is used in conjunction with the Round Receipt Application Action to round receipts up to the pack size entered.
For example, if your pack size is 10 and your receipts are 88, it will round up to 90 to meet the pack size.
In the WP Min Order Quantity measure, enter a minimum order quantity.
This measure is used in conjunction with the Round Receipt Application Action to round receipts up to the minimum order quantity entered.
For example, if your minimum order quantity is 100 and your receipts are 88, it will round up to 100.
Run the Flow Receipts Application Action to create a weekly receipt flow based on the parameters and the Sales plan.
Run the Round Receipts Application Action to round receipts using the Pack Size and/or Min Order Quantity measure inputs.
Review your WP EOP, WP WOS and WP Sell Thru % after running the Round Receipts Application Action to ensure that you are not over-inventoried due to rounding up.
Measure Table
Table 13-16 1. Define Parameters View Measures
| Label | Definition |
|---|---|
|
WP Flow Receipts |
A Boolean flag measure which is required to be checked to calculate receipt quantity and flow based on set parameters and the sales plan. |
|
WP Initial Buy U, C, AUC |
The planned initial buy Units, Cost, and Average Unit Retail. |
|
WP Initial Buy U var Recommended % |
The variance between the planner input Initial Buy and the system-recommended Initial Buy. |
|
WP Recommended Initial Buy U, AUC |
The system calculated recommend initial buy Units and Average Unit Cost based on Order Frequency, Presentation Minimums, Safety Stock Weeks, Safety Stock U, and the Sales plan. |
|
WP Initial Receipt Lead Time |
The number of weeks before the start sell week that the receipts should arrive. The planner has the ability to select the number of weeks from a picklist, with the maximum value being set in the Assortment Period Maintenance segment. |
|
WP Lead Time (Days) |
The number of days it takes for product to arrive from your vendor/supplier to the warehouse or store. This measure is used to generate the Immediate Need real time alert in the In-Season Planning segment, letting you know that your EOP is below your Safety Stock. |
|
WP Lead Time Future (Days) |
The number of buffer days it takes for product to arrive from your vendor/supplier to the warehouse or store. This measure is used to generate the Lead Time Future Need real time alert in the In-Season Planning segment, letting you know that your future EOP is below your Safety Stock. |
|
WP Order Frequency (Weeks) |
How often, in weeks, receipts arrive. |
|
WP Presentation Min U |
The minimum amount of inventory on the sales floor per store. This is used only in calculating the initial buy and can be thought of as a fixture fill. |
|
WP Safety Stock U |
Unit quantity maintained to mitigate the risk of stockouts. It is used for the initial buy as well as for subsequent receipt drops. |
|
WP Safety Stock (Weeks) |
The number of future weeks of sales that additional units should be maintained to mitigate the risk of stockouts, based on future sales weeks. It is used for the initial buy as well as for subsequent receipt drops. |
|
Tgt WOS |
The planner entered targeted WOS by item/cluster, used in the Overage Real Time Alert. |
|
WP Pack Size U |
The number of units that come in a pack, used to round up receipts. |
|
WP Min Order Quantity |
The minimum order quantity, used to round up receipts. |
Measure Profile
Default Profile
The Default profile is used to assign receipt parameters before flowing receipts.
Application Actions
Flow Receipts
The Flow Receipts Application Action populates a weekly receipt plan based on the parameters Order Frequency, Pres Mins, Safety Stock U, and Safety Stock Weeks.
Round Receipts
The Round Receipts Application Action uses the inputs of WP Pack Size U and WP Min Order Quantity to round receipts up to match these parameters.
The Plan Receipts & Inventory view is used by the planner to adjust net sales if necessary and adjust the receipt plan to meet sales needs based on business knowledge or constraints.
The steps to complete this process:
Review the WP Net Sales U and make adjustments if necessary.
Review the WP Receipts U and make adjustments to quantities or delivery weeks based on business knowledge.
Review the WP EOP U to ensure there are not over or under stock issues.
If the receipt plan does not support the sales plan, a Real Time Alert will be activated to alert action is needed.
Adjust the sales or the receipt plan to resolve the Real Time Alert.
Review the WP WOS to view the calculated Weeks of Supply based on the sales and receipt plan.
The WP WOS metric represents the number of future calendar positions that the current stock will cover. For example, If your calendar is aggregated to month, then WP WOS represents the future number of months that the stock will cover, if the calendar is aggregated to quarter, then it represents the number of quarters that the stock will cover.
The WP WOS Weeks metric represents the inventory available to cover the future weeks at week level irrespective of the calendar level selected.
For each week, WOS is calculated as the number of future weeks of sales covered by the current period's EOP U.
Review the WP Sell Thru % as a reference value to see how fast inventory is projected to sell through.
For each week, Sell Thru % is calculated as Net Sales Units / (BOP U + Receipts U).
Review the Cost measures.
Repeat this process for each item and cluster in the assortment.
Note that you can use Product Attributes to roll up your items by attributes. For example, this can be used to view inventory levels by attributes that are important to the category, to make sure that receipts are invested for important attributes.
Measure Table
Table 13-17 2. Plan Receipts & Inventory View Measures
| Label | Definition |
|---|---|
|
WP Event |
Populated after a What-if promotion or markdown event is applied after running the Apply WI Application Actions, or the planner can manually enter a value. |
|
Selling Weeks |
A Boolean flag measure used to indicate the week the item begins selling in the assortment. |
|
WP BOP U, C, AUC |
The calculated Beginning of Period Units, Cost, and Average Unit Cost. |
|
Net Sales U, C, AUC |
Net Sales Units, Cost, and Average Unit Cost. |
|
Receipts U, C, AUC |
Receipts Units, Cost, and Average Unit Cost. |
|
EOP C, AUC |
The calculated End of Period Cost and Average Unit. |
|
WP WOS |
The number of future weeks of sales that will be covered by the current week's EOP U for the calendar level selected. |
|
WP WOS Weeks |
The number of future weeks of sales that will be covered by the current week's EOP U at the week level |
|
Sell Thru % |
The percent of inventory that will be sold during a period, calculated as Net Sales Units / (BOP U + Receipts U). |
Real Time Alerts
Inventory Stock Thresholds
Alerts the user that EOP Units is negative. Adjust the sales or the receipt plan to resolve the alert. The alert is activated when EOP falls below the pres min, safety stock U, and safety stock weeks measures.
Measure Profiles
Default Profile
The Default profile is used to plan weekly receipts to cover the sales plan based on EOP inventory objectives.
Last Year Profile
The Last Year profile is used to compare the WP weekly receipts and inventory levels to last year values.
Initial Buy Profile
The Initial Buy profile is used to plan initial buy quantities for the first drop.
Original Plan Profile
The Original Plan profile is used to compare the WP weekly receipts and inventory levels to an approved Original Plan.
The third and final step in the Item Planning process is Approve Plan. This step approves the item plans that you have created, analyzed, and reviewed for accuracy.
The output of this step is an approved Item Plan Original Plan and Current Plan.
The step to complete this process:
Approve the item plan.
Prior to Starting this Step:
Thoroughly analyze and review the item plans by cluster to ensure they meet the financial goals of the category.
After Completing this Step:
Begin Item Planning pre-season for seasonal items.
Tab and View in this Step:
Application Action
Approve Plan
The Approve Plan Application Action copies data from the Working Plan (WP) to the Original Plan (OP) and to the Current Plan (CP).
This tab is used to approve the plan.
The steps to complete this process:
In the WP Approve to OP/CP measure, check the Boolean flag for the subcategories and clusters that should be approved.
If all subcategories and clusters should be approved at once, roll up to All Product and All Location and check the Approve to OP measure at that level.
In the WP Comment measure, enter approval comments.
The WP Approval Comments will be copied to the OP Approval Comments and concatenated with the approver's ID, for future reference in this view.
Run the Approve Plan Application Action.
Note that the Approve Plan Application Action creates the OP and CP versions of the plan.
Measure Table
Table 13-18 Approve Plan View Measures
| Label | Definition |
|---|---|
|
WP Approve to OP/CP |
Boolean flag measure required to be checked in order to approve the Working Plan Item Plan to the Original Plan and the Current Plan. |
|
WP Comments |
Comments entered here will be copied to the OP Approval Comments and concatenated with the approver's ID, for future reference in this view. |
|
OP Comments |
Original Plan comments used as a reference. |
Measure Profile
Default Profile
The Default profile is used to approve the Item Plan to the OP and CP versions.
Application Action
Approve Plan
The Approve Plan Application Action copies data from the Working Plan (WP) to the Original Plan (OP) and Current Plan (CP).
