| 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 |
The Item Planning @ Store task is used to create location level exception plans. These plans can be inherited from the approved Item Planning cluster level plan, or the planner can use other seeding methods, discussed below. The output of this task is a location/item level sales and inventory plan. It is also used to address any store-level real time alerts, through the exception management process.
The typical business user who completes this task will be an Assortment Planner. The Planner usually will have completed the Item Planning process at the cluster level and needs to create exception plans at the individual location level.
Local Currency
Local Currency refers to the ability to plan in more than one currency if your business operates in multiple countries with different currencies. Multiple currencies and their exchange rates can be managed within Item Planning, allowing the planner to choose which currency they would like to plan in. Data will be stored in the one global currency, and within a segment, users can switch between currencies as business needs dictate.
Location hierarchy
Product hierarchy
Calendar hierarchy
Sales Retail, Sales Unit, and Cost actuals
Customer Returns actuals
Direct/ecommerce actuals
Size profiles
Item attributes and attribute values
The high-level steps to complete this process:
Determine which stores require an exception plan.
Replan Sales and Margin by item/location.
Replan receipt and inventory by item/location.
Apply size profiles and round receipts to packs
Approve the item plan to the Current Plan.
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 @ Store segment:
Click Assortment Services in the Task menu. Then, click the Planning Services activity and then the Item Planning @ Store task.
The dialog to create 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 subcategories, or a subset of items, and click Next.
In Select Calendar, select the assortment period and click Next.
In Select Location, select the individual locations that will receive this assortment. Use the Levels & Positions drop-down menu to view the stores that belong to each location cluster.
Click Finish. The Item Planning @ Store segment is built.
The first step in the Item Planning @ Store process is Sales & Margin. This step is used to define parameters such as whether the item will be assorted in a particular store and to make adjustments of regular, promotional, and clearance sales at the item/location level.
The steps to complete this process:
Seed sales.
Seed like items, if necessary.
Set VAT rate.
Plan regular, promotional, and clearance sales and margin.
Prior to Starting this Step:
Cluster level item plans should be approved.
After Completing this Step:
Plan receipts and inventory based on the sales plan.
Tabs and Views in this Step:
Application Actions
Seed Plan
The Seed Plan Application Action populates an item's weekly sales based on the Sales Source selected.
Refresh Product Rollup
The Refresh Product Rollup Application Action dynamically creates alternate hierarchies based on user defined attribute selections. After running the Application Action, the user may select the dynamically created product hierarchy to see rollups based on the attribute selections. If the Process Extension CDT is being used, the planner can choose a CDT version and the Application Action will populate the selected CDT.
Local Currency Process Extension
If your business is using the local currency function, follow this process:
Go to the Local Currency tab and Setup view and select the currency you wish to plan in from the Use Local Currency measure picklist.
Run the Convert Local Currency Application Action.
Go to the Plan Local Currency view to plan item level sales in the local currency.
Note that local currency is denoted by an L in the measure name to indicate Local Currency, for example, WP Sales LR.
This tab is used to define which items will be assorted by location, seed like items, and plan Sales & Margin.
The Define Parameters view is used by the planner to define which items will be assorted by location, select a sales seed source, and seed like items, if necessary.
The steps to complete this process:
Review the WP Assorted Item Boolean flag measure and ensure it is checked for each valid item location.
Only item/location combinations with the WP Assorted Item measure set to true will receive a seeded sales plan.
Review the CP Assorted Item measure to understand if there are differences between the Item Planning @ Cluster plan and the exception plan that you are creating.
If Assortment Planning & Optimization Cloud Service is in use, review the AP CP Assort Core measure to understand which items are assorted in the Assortment Plan.
In the WP Seed Source picklist, select a seeding source.
Assort Plan - The Assortment Planning Current Plan (CP) units will be spread based on the Item Planning @ Cluster sales curve.
The units will be seeded, then multiplied by the Item Price to calculate the Sales Retail.
Only Sales Retail, Units, and AUR are seeded with this option:
Last Year - Sales, Returns, Receipts, Transactions, and Traffic are seeded with this option.
Forecast - Units will be seeded, then multiplied by the Item Price to calculate the Sales Retail.
Current Plan - Sales, Returns, Receipts, Transactions, and Traffic are seeded with this option.
Like Item Seeding - If you want to assign a like item, in the WP Like Item measure, select the existing item to assign to the new item.
Note that you can use the Search feature to quickly find items with the Add designation so that it is easier to locate new items.
Select a Like Item Seed Source:
Like Item CP and Like Item LY - Sales, Returns, Receipts, Transactions, and Traffic are seeded with this option.
In the Like Item Adjustment measure, assign an adjustment ratio for the existing item sales to be copied to the new item.
Run the Seed Plan Application Action.
Note that only unelapsed periods will be updated with seeded data.
Measure Table
Table 16-1 1. Define Parameters View Measures
| Label | Definition |
|---|---|
|
AP CP Assort Core |
A Boolean flag measure used to indicate that an item is carried as core in the approved Assortment Plan. |
|
AP Tgt Assort Core Count |
The number of items carried in the approved Assortment Plan. |
|
WP Assorted Item |
An editable Boolean measure indicating whether an item is a core item in the Item Plan @ Store assortment. Only WP Assorted Items will receive a seeded sales plan. |
|
WP Assorted Item Count |
The number of items carried in the Item Plan @ Store Working Plan. |
|
CP Assorted Item |
A Boolean measure indicating whether an item is an active item in the Item Planning Current Plan. |
|
CP Assorted Item Count |
The number of active items in the Item Planning Current Plan. |
|
WP Seed Source |
A picklist used to select the seed source for an item's sales. |
|
WP Seed Plan |
A Boolean flag measure which is required to be checked to create a weekly sales plan for assorted items. |
|
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. |
|
Like Item Adjustment Ratio % |
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. |
Measure Profile
Default Profile
The Default profile is used to assign item parameters before seeding sales.
Application Action
Seed Plan
The Seed Plan Application Action populates an item's weekly sales based on the Sales Source selected.
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 16-2 2. 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 Plan Sales and Margin view is used by the planner to replan regular, promotional, and clearance sales by item and location.
The steps to complete this process:
Review and adjust each item/week/store 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.
Review AUC and Gross Margin 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.
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 Calculations
The calculations for the Sell Thru Gap and Markdown Optimization measures are shown in the following table.
Table 16-3 3. Plan Sales & Margin View Measure Calculations
| Label | Calculation |
|---|---|
|
WP Sell Thru % diff CP |
WP Sell Thru % - CP Sell Thru % |
|
Needed Sales Lift % |
WP Sell Thru U var CP / WP Sales U |
|
Recommended Markdown Price |
The maximum value of either Unconstrained Price or Inventory Constrained Price. Note that if the calculated Recommended Markdown Price is greater than the item unit price, then it will be zero. Unconstrained Price: ((Item Unit Cost * elasticity) / (elasticity - 1)) Inventory Constrained Price: ((BOP U + Remaining Receipts U) / Seasonal Effects, -1/elasticity) Seasonal Effects (Sales Plan): WP Sales U * (WP Sales AUR, elasticity) The Item Unit Price is the current price fed from the source system. |
|
Recommended Markdown % |
(Item Unit Price - Recommended Markdown Price) / Item Unit Price Note that if the Recommended Markdown Price rounded down is zero, then the recommended markdown % will be 0%. |
Measure Table
Table 16-4 3. Plan Sales & Margin View Measures
| Label | Definition |
|---|---|
|
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 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 Sales Promo R, U, AUR |
Promotional Sales Retail, Units, and Average Unit Retail. |
|
WP Planned Promo % |
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 R, U, AUR |
The aggregation of WP Sales Reg, WP Sales Promo and WP Clr. WP Sales do not include customer returns. |
|
WP ROS |
The weekly rate of sales for the item/cluster/calendar periods that were selected in the wizard process. |
|
WP Sell Thru % |
The percent of inventory that will be sold during a period, calculated as Net Sales Units / (BOP U + Receipts U). |
|
CP Sell Thru % |
The percent of inventory that will be sold during a period, calculated as Net Sales Units / (BOP U + Receipts U) in Current Plan. |
|
WP Sell Thru U var CP |
The BOP unit variance between your WP Sell Thru and CP Sell Thru. |
|
WP Sell Thru % diff CP |
WP Sell Thru % - CP Sell Thru %. |
|
Needed Sales Lift % |
The unit sales lift percent necessary to bridge the gap between your WP Sell Thru and CP Sell Thru. |
|
Recommended Markdown Price |
The recommended optimal markdown price that maximizes margin, subject to inventory constraints. The calculation is based on elasticity, current inventory and the sales plan. |
|
Recommended Markdown % |
The recommended markdown percent to maximize margin, subject to inventory constraints. |
Measure Profiles
Default Profile
The Default profile is used to plan regular, promotion, and clearance sales by item and location.
Return/Net Sales Profile
The Return/Net Sales profile is used to plan customer returns and view net sales.
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 16-5 3. Plan Sales & Margin View with Returns/Net Sales Measures
| Label | Definition |
|---|---|
|
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, Ex VAT R, U, AUR, C, AUC, GM R, GM R %, Net GM Ex VAT R |
Net Sales = Sales - Customer Returns Net Sales Retail, excluding VAT Rate, Units, Average Unit Retail, Cost, Average Unit Cost, Gross Margin value, Gross Margin percent and Gross Margin excluding the Vat Rate. |
Last Year Profile
The Last Year profile is used to review last year 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 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.
Direct WP/CP Profile
The Direct WP/CP profile is used to review and plan measures related to the Direct, or ecommerce business and compare to the Item Plan CP.
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.
Direct WP/CP Profile
The Direct WP/CP profile is used to review and plan measures related to the Direct, or ecommerce business and compare to the Item Plan CP.
Measure Table
Table 16-6 3. Plan Sales & Margin View with WP/CP 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 U |
Average Transaction Size is calculated as Sales U / Transaction Count. |
|
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. |
Process Extension
If your business is using the local currency function, follow this process:
Go to the Local Currency tab and Setup view and select the currency you wish to plan in from the Use Local Currency measure picklist.
Run the Convert Local Currency Application Action.
Go to the Plan Local Currency view to plan item level sales in the local currency.
Note that local currency is denoted by an L in the measure name to indicate Local Currency, for example WP Sales LR.
This view is used to elect the currency you wish to plan in from the Use Local Currency measure picklist.
Local Currency refers to the ability to plan in more than one currency if your business operates in multiple countries with different currencies. Multiple currencies and their exchange rates can be managed within Assortment Planning, allowing the planner to choose which currency they would like to plan in. Data will be stored in the one global currency, and within a workbook, users can switch between currencies as business needs dictate.
This tab is used to select item attributes to view in an alternate hierarchy.
The Define Filter/Rollup view is used to select Product/Location attributes to view in an alternate hierarchy. This is available in views that display the item/store level. For example, if you select Color as a product attribute, in the Create and Review Assortment steps, you can click the Product Hierarchy tile to select the attribute as an alternate hierarchy, and view the proposed assortment by Black, Red, Navy, and so on. This allows you to roll up your items by different attributes to analyze and review the proposed assortment based on important attributes. You may select one attribute at a time from the alternate hierarchy. Similarly, planners can select Store attributes such as Climate and roll up the locations.
The Filter Items By picklist allows you to select one of the Real-Time Alerts and use it to filter the items on each view. One filter may be used at a time in the segment.
The Filter Markdown % Max and Min measures can be used to enter maximum and/or minimum markdown percents used to filter items within the segment.
The steps to complete this process:
Select up to three dynamic product attributes from the picklist.
Select up to three dynamic location attributes from the picklist.
Run the Refresh Attributes Rollup Application Action.
To view the product attribute:
In a view that displays item level, click the Product Hierarchy tile.
Select the attribute that you want to view in the alternate hierarchy.
Click OK.
To view the location attribute rollup:
In a view that displays location level, click the Location Hierarchy tile.
Select the attribute that you want to view in the alternate hierarchy.
Click OK.
To set a filter:
In the Filter Items By measure picklist, select the real-time alert to filter by.
Click Calculate.
In the Filter Markdown % Max or Min % measures, enter markdown percents to filter by; the Recommended Markdown % is used to compare against the Min/Max filter.
Go to the Edit View window, select the products and view by choosing the filter.
Measure Table
Table 16-7 Define Filter/Rollup View Measures
| Label | Definition |
|---|---|
|
Product Attribute 1, 2, 3 |
Picklist to present product attributes for a dynamic product hierarchy rollup. |
|
Location Attribute 1, 2, 3 |
Picklist to present location attributes for a dynamic location hierarchy rollup. |
|
Filter Items By: |
Picklist used to select a real-time alert to filter items. |
|
Filter Markdown Max and Min % |
Measures used to enter markdown percentages to filter items. |
Measure Profile
Default Profile
The Default profile is used to select dynamic product/location attributes and filter items.
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/Location hierarchy to see rollups based on the attribute selections.
The second step in the Item Planning @ Store process is Receipts & Inventory. This step is used to define parameters such as presentation minimums, safety stock, and real time alert parameters.
The steps to complete this process:
Review and update inventory parameters.
Adjust receipts and inventory based on the sales plan.
Prior to Starting this Step:
Item/location sales plans should be completed.
After Completing this Step:
Approve the Item Planning @ Store plan.
Tabs and Views in this Step:
Application Actions
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 satisfy supplier-driven pack sizes and minimum order quantities.
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.
This tab is used for receipts and inventory.
The Inventory 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. Parameters that were set in the Item Planning @ Cluster segment are inherited in this segment.
The steps to complete this process:
Review the inventory parameters; if changes need to be made, follow the steps below.
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.
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 Select Size Range picklist, select the size range associated with for that product. This will define the sizes that are used when applying the size profile
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.
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 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 TGT Sell Thru % measure, enter the targeted Sell Thru %.
This measure is used to generate the Sell Thru Warning Real Time Alert, letting you know that your Sell Thru is higher or lower than your targeted Sell Thru.
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 16-8 1. Inventory Parameters View Measures
| Label | Definition |
|---|---|
|
WP Presentation Min U |
The minimum amount of inventory on the sales floor per store, used in the Inventory Threshold Real Time Alert. |
|
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, as well as used in the Inventory Threshold, Immediate Need, and Lead Time Future Need Real Time Alerts. |
|
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 as well as used in the Inventory Threshold, Immediate Need, and Lead Time Future Need Real Time Alerts. |
|
WP Pack Size U |
The number of units that come in a pack, used to round up receipts. |
|
Select Size Range |
Used to select the size range, which defines the group of sizes associated with the product being planned. |
|
WP Min Order Quantity |
The minimum order quantity, used to round up receipts. |
|
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. |
|
Tgt WOS |
The planner entered targeted WOS by item/cluster, used in the Overage Real Time Alert. |
|
Tgt Sell Thru % |
The planner entered targeted Sell Thru % by item/cluster, used in the Sell Thru Warning Real Time Alert. |
Measure Profile
Default Profile
The Default profile is used to assign receipt parameters before flowing receipts.
Application Action
Round Receipts
The Round Receipts Application Action uses the inputs of WP Pack Size U and WP Min Order Quantity to satisfy supplier-driven pack sizes and minimum order quantities.
The Plan Receipts & Inventory view is used by the planner to readjust the receipt plan to meet sales trends based on business knowledge or constraints.
The steps to complete this process:
Review the WP Receipts U and make adjustments to quantities or delivery weeks based on business knowledge and the updated sales plan.
Review the On Order measure to understand when ordered receipts are scheduled to arrive.
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 you that action is needed.
The What-If Cover Weeks measure can be used to enter a number of weeks that receipts must cover sales, based on the sales plan and current week BOP.
For example, if you enter 3, the system will look at 3 future weeks of sales and subtract this week's planned sales, this week's BOP and any planned Safety Stock U.
The resulting receipt unit need will populate the What-if Receipts U measure.
The Needed Inventory U measure compares the WP EOP with Safety Stock U. If WP EOP is less than Safety Stock U, the measure will populate with the unit amount needed to be above the Safety Stock threshold.
Review the WP WOS to view the calculated Weeks of Supply based on the sales and receipt plan.
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 location.
Once all /locations have been planned, utilize the measure profiles to compare to LY and CP.
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 16-9 2. Plan Receipts & Inventory View Measures
| Label | Definition |
|---|---|
|
WP Event |
Populated after a What-if promotion or markdown event is applied in the IP @ Cluster segment, or the planner can manually enter a value |
|
WP BOP U, C, AUC |
The calculated Beginning of Period Units, Cost, and Average Unit Cost. |
|
WP Net Sales U, C, AUC |
Net Sales = Sales - Customer Returns Working Plan Net Sales Units, Cost, and Average Unit Cost. |
|
WP Receipts U, C, AUC |
Working Plan Receipts Units, Cost, and Average Unit Cost. |
|
On Order U, C, AUC |
On Order Units, Cost, and Average Unit Cost. |
|
WP EOP U, C, AUC |
Working Plan calculated End of Period Units, Cost and Average Unit. |
|
What-If Cover Weeks |
The what-if number of weeks that receipts must cover based on the sales plan and current week BOP, used to populate the What-If Receipts U measure. |
|
What-If Receipts U |
The receipt units needed to cover the planner entered What-If Cover Weeks, based on the future sales, current BOP and Safety Stock U. |
|
Needed Inventory U |
Compares the WP EOP with Safety Stock U; if WP EOP is less than Safety Stock U, then the measure will populate with the unit amount needed to be above the Safety Stock threshold. |
|
WP WOS |
The number of future weeks of sales that will be covered by the current week's EOP U. |
|
WP Sell Thru % |
The Working Plan percent of inventory that will be sold during a period, calculated as Net Sales Units / (BOP U + Receipts U). |
Real Time Alerts
Inventory Threshold
The alert will activate when current week EOP units fall below Pres Min, Safety Stock U, and Safety Stock (Weeks) measures. This alert is used in the Item Planning and In-Season Planning segments.
Immediate Need
The alert will activate when current week EOP units fall below Safety Stock U + Lead Time Days for an item/cluster/week. Note that lead time days are converted to week. This alert is used in the In-Season Planning segment.
Lead Time Future Need
The alert will activate when current week EOP units fall below Safety Stock U + Lead Time Days + Lead Time Future Days for an item/cluster/week. Note that lead time days are converted to week. This alert is used in the In-Season Planning segment.
Overage
The alert will activate when WP WOS between current week and current week + WP Lead Time Days is greater than the TGT WOS, and there are non-zero values in Receipt U or On Order U from current week + WP Lead Time Days for an item/cluster/week. This alert is used in the In-Season Planning segment.
On Order Reconciliation
The alert will activate when WP On Order U is greater than zero and does not match WP Receipt U for an item/cluster/week. This alert is used in the In-Season Planning segment.
Sell Thru Warning
The alert will activate green when WP Sell Thru % is higher than the planner entered TGT Sell Thru % and activate yellow when the WP Sell Thru % is lower than the TGT Sell Thru % for an item/cluster/week. This alert is used in the In-Season Planning segment.
Measure Profiles
Default Profile
The Default profile is used to plan weekly receipts to cover the sales plan based on the updated sales plan 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.
Current Plan Profile
The Current Plan profile is used to compare the WP weekly receipts and inventory levels to an approved Current Plan.
This tab is used to select item attributes to view in an alternate hierarchy.
The Define Filter/Rollup view is used to select Product/Location attributes to view in an alternate hierarchy. This is available in views that display the item/store level. For example, if you select Color as a product attribute, in the Create and Review Assortment steps, you can click the Product Hierarchy tile to select the attribute as an alternate hierarchy, and view the proposed assortment by Black, Red, Navy, and so on. This allows you to roll up your items by different attributes to analyze and review the proposed assortment based on important attributes. You may select one attribute at a time from the alternate hierarchy. Similarly, planners can select Store attributes such as Climate and roll up the locations.
The Filter Items By picklist allows you to select one of the Real-Time Alerts and use it to filter the items on each view. One filter may be used at a time in the segment.
The Filter Markdown % Max and Min measures can be used to enter maximum and/or minimum markdown percents used to filter items within the segment.
The steps to complete this process:
Select up to three dynamic product attributes from the picklist.
Select up to three dynamic location attributes from the picklist.
Run the Refresh Attributes Rollup Application Action.
To view the product attribute:
In a view that displays item level, click the Product Hierarchy tile.
Select the attribute that you want to view in the alternate hierarchy.
Click OK.
To view the location attribute rollup:
In a view that displays location level, click the Location Hierarchy tile.
Select the attribute that you want to view in the alternate hierarchy.
Click OK.
To set a filter:
In the Filter Items By measure picklist, select the real-time alert to filter by.
Click Calculate.
Go to a view that shows item level and has the Filter function available. Click Filter.
Measure Table
Table 16-10 Define Filter/Rollup View Measures
| Label | Definition |
|---|---|
|
Product Attribute 1, 2, 3 |
Picklist to present product attributes for a dynamic product hierarchy rollup. |
|
Location Attribute 1, 2, 3 |
Picklist to present location attributes for a dynamic location hierarchy rollup. |
|
Filter Items By: |
Picklist used to select a real-time alert to filter items. |
|
Filter Markdown Max and Min % |
Measures used to enter markdown percentages to filter items. |
Measure Profile
Default Profile
The Default profile is used to select dynamic product/location attributes and filter items.
Application Action
Refresh Attribute Rollup
The Refresh Attribute 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/Location hierarchy to see rollups based on the attribute selections.
The third step in the Item Planning @ Store process is Receipts by Size. It is used to review the size profiles set for each location, review the sales broken out by size and to plan out the store-level receipts by size according to the size profiles.
The steps to complete this process:
Review Size Profiles, adjust as needed. Review Sales by broken out by size.
Plan receipts by size according to the store's size profile.
Prior to Starting this Step:
Receipts and Inventory plans should be completed.
After Completing this Step:
Approve the Item Planning @ Store plan.
Tab and Views in this Step:
Application Action
Apply Size Profile
The Apply Size Profile Application Action is used to apply the size profiles to the receipts of products for each location.
The tab is used to review by size.
The Review Size Profile view is used by the planner to review the size profile percentage of the working plan. The size profiles are fed to Item Planning Cloud Service through a data feed or set up in the Administrative steps. They can be overridden here if needed.
The step to complete this process:
Review the size profile percentage associated with each location for a working plan. Update if needed.
Measure Table
Table 16-11 1. Review Size Profile View Measure
| Label | Definition |
|---|---|
|
WP Size Profile % |
Working Plan Size Profile %. |
Measure Profile
Default Profile
The Default profile is used to review working plan's size profile percentage.
The Review Sales by Size view is used by the planner to review the sales that happened for each size profile of a product for a location for every calendar time.
The step to complete this process:
Review the sales for each size profile.
Measure Table
Table 16-12 2. Review Sales by Size View Measures
| Label | Definition |
|---|---|
|
Sales by Size U |
Sales by Size Units. |
|
Sales U % by Size Range |
Sales Unit % by the size range. |
Measure Profile
Default Profile
The Default profile is used to review sales by size.
The Receipts by Size view is used by the planner to break out the planned receipts by size.
The step to complete this process:
Set the WP Receipts by Size U by running the Apply Size Profile Application Action. Review and adjust if needed.
Application Action
Apply Size Profile
The Apply Size Profile Application Action is used to apply the size profiles to the receipts of products for each location.
Measure Table
Table 16-13 3. Receipts by Size View Measures
| Label | Definition |
|---|---|
|
WP Receipts by Size U |
After running the Application Action, this measure will populate with the size-level receipts. |
|
WP Receipts U diff to Size |
Variance used to compare the receipts against the size profiles. |
Measure Profile
Default Profile
The Default profile is used to set WP Receipts by Size U values for each size profile.
The fourth and final step in the Item Planning @ Store process is Approve Plan. This step approves the item/location plans that you have created, analyzed and reviewed for accuracy.
The output of this step is an approved store level Item Plan Current Plan.
|
Note: When approving to CP at the store level, the store level plan is copied to the CP@Cluster plan, allowing for the export of the CP@Cluster plan to cover both the approved cluster and store level plans. A copy of the CP@Store plan is available for the planner to use during the seeding process in this segment. |
The step to complete this process:
Approve the item plan.
Prior to Starting this Step:
Thoroughly analyze and review the item plans by store to ensure they meet the goals of the category.
After Completing this Step:
Continue with Item Planning activities as necessary
Tab and View in this Step:
Application Action
Approve Plan
The Approve Application Action copies data from the Working Plan (WP) to the Current Plan (CP).
This tab is used to approve the plan.
The steps to complete this process:
In the WP Approve to CP measure, check the Boolean flag for the subcategories and stores that should be approved.
If all subcategories and stores should be approved at once, roll up to All Product and All Location and check the Approve to CP 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.
Measure Table
Table 16-14 1. Approve Plan View Measures
| Label | Definition |
|---|---|
|
WP Approve to CP |
Boolean flag measure required to be checked in order to approve the Working Plan Item Plan to the Current Plan. |
|
WP Comments |
Comments entered here will be copied to the CP Approval Comments and concatenated with the approver's ID, for future reference in this view. |
|
CP Comments |
Current Plan comments used as a reference. |
Measure Profile
Default Profile
The Default profile is used to approve the Item Plan to the CP version.
Application Action
Approve Plan
The Approve Application Action copies data from the Working Plan (WP) to the Current Plan (CP).
