Sap Retail Merchandising and Assortment Planning Overview2

Merchandise and Assortment Planning (SAP MAP)
Overview – Part II
1
Agenda
1. Introduction
2. Strategic Planning
3. Store Planning
4. Merchandise Planning
5. Capacity Planning
6. eSOA services for integration SAP MAP to SOP
(Shelf Optimization Program)
7. Assortment Definition
8. Assortment Planning
9. eSOA services for integration SAP MAP to SAP ERP
10. Release Workbench
© SAP 2008 / Page 2
2
Assortment Definition
Strategic Plan
Master Data Object Assortment:
Store Merch. Creation in SAP MAP: Available in SAP ERP
Plan Plan and SAP BI
Alternatively creation in SAP ERP and

Capacity Plan
extraction to SAP MAP (depends on your
Assortment Definition business needs)
Assortment Plan
Execution
Function:
Main Objectives / Challenges:
Application for assortment definition in BI (BW-
Simplify accurate store grouping/ clustering BPS and BI-IP)
many variables are involved in accurately
clustering therefore retailer cannot manage Usage of assortments (store groups) also in
this process manually following applications: allocation, promotion
Group stores that can be considered/ planned

together in order to streamline the planning and
merchandising process
Determine which store cluster receives which

product mix for which time period
© SAP 2008 / Page 3
3
SAP Assortment
© SAP 2008 / Page 4
4
Enhancements for SAP Assortment
Assortment type
The assortment type is an assortment attribute enables the strategic
alignment of the assortment and its treatment in assortment definition,
assortment planning and procurement to be controlled
Assortment dimension
For each assortment type up to 3 dimensionens
Characteristic values per dimension
Example: Assortment type „Business type“ dimensions „Capacity
level“ (Values 1-9) and „Price level“ (Values 1-3)
Example
Clustering according to Capacity and Price level
Clustering according to climatuc zones
Clustering according to delivery regions

© SAP 2008 / Page 5
5
Assortment Definition - Example
Assortment Definition
Stores with the same price level and capacity level are assigned to the same group to ensure a
degree of standardization (common planning and use in operative processes). They are mapped
onto the SAP assortment.
Calculating
Calculating
price
price level
level 3
Price Level
What price level is a store

assigned to for a specific 2
merchandise area?
1
1 2 3 4 5 6 7 8 9
Increased
Capacity level capacity
Calculating
Calculating capacity
capacity level
level
How many fixtures does a store have for a specific merchandise area?
© SAP 2008 / Page 6
6
Assortment 3,1: Ladies’ blouses,

High level, low capacity SAP BI
Level dimension = 3
Capacity dimension = 1 Hierarchy nodes: Ladies’ blouses
Key date: Today
Store 1 11.15.03 – 02.01.05
Store 3 11.01.03 – 02.01.05 Calculate values Determine assortmt Save
...
Store Level Cap. Valid Valid Assort
old/new old/new from to ment
Assortment 3,3: Ladies’ blouses,

Store 1 2 3 2 1 11.15.03 02.01.05 2,2 3,1
High level, high capacity Store 2 2 2 1 1 11.01.03 02.01.05 2,1 2,1
Store 3 2 3 1 1 11.01.03 02.01.05 2,1 3,1
Level dimension = 3
Capacity dimension = 3 Store 4 3 3 2 3 11.01.03 02.01.05 3,2 3,3
Store 5 1 2 1 1 11.01.03 02.01.05 2,1 2,1
Store 4 11.01.03 – 02.01.05 … … … … …
...
© SAP 2008 / Page 7
7
time-dependent assignment of stores to assortments

according to their dimension values for tier and sales level
© SAP 2008 / Page 8
8
Agenda
1. Introduction
3. Store Planning
© SAP 2008 / Page 9
9
What is Assortment Planning ?
Assortment planning is a part of the bottom-up planning

process. An assortment plan is defined as a unit plan,
which defines a key mix of goods, at a point and time. It
establishes the breath and depth of the product
assortment in a set of store groups (or clusters). It is a
living, breathing plan that becomes more refined as the
decision making process of product development /
product selection is finalized.
© SAP 2008 / Page 10
10
Assortment Plan
Strategic Plan Planning level

Period month / season / rollout
Store
Plan
Merch.
Plan
Sales organization/ distribution
channel
Capacity Plan Segment / assortment
Assortment Definition Product / variants (color, size)
Assortment Plan
Execution
Key figures
Define the right product for the right
stores / assortments Sales
Offerings are tied to customer Gross margin
behavioral patterns Sales and purchase prices
Create new products, add existing
Stocks
products, remove a product, …
Æ Simulation of planned products Number of products
Assign products to assortments
Æ Planning of assortments
Markdown Planning
© SAP 2008 / Page 11
11
Assortment Planning – Fashion
Within SAP you have the following options to carry out the "creative" assortment planning
process:
OPTION 1:
You can complete assortment planning within SAP BI as soon as key figure target planning is finalized.
These targets are transferred to SAP ERP. There you can carry out the operational part of assortment
planning using the OAPC (Operational Assortment Planning and Control)
OPTION 2:
Or you carry out some or even all process steps of operational assortment planning within Integrated
Planning of SAP BI and transfer this information to SAP ERP (OAPC) for fulfillment.
The process steps are:
Determining the correct product mix for the assortment

Creating new planned articles
Selecting colors and sizes for an article
Planning quantities (this can be done down to the level of the article/color/size)
Enter packsize / quota scale
The following slides show just one possible process variant for fashion
merchandise assortment planning:
© SAP 2008 / Page 12
Due to the characteristics of fashion merchandise, the planning aspect is much more
important for assortment creation than for other types of merchandise. Where fashion
merchandise is involved, assortment planning is much more dependent on creativity, the
analysis of fashion trends, and the ability to modify existing plans as quickly as possible.
The focus with respect to materials/fabrics, colors, styles and so on must be determined
and adjusted to the target groups. It forms the basis for the article shells (planned articles)
and their attributes, which will be planned subsequently.
It is often the case that the specific articles do not even exist in the system at the time of
planning. Accordingly, assortment planning initially involves “ideas” or “shells” of articles,
which then take shape progressively through the course of the planning process. An
important task of these planned articles is to reserve capacities at a time when the actual
articles are not yet known.
12
Seasonal Assortment Planning – Overview of
one Possible Process Variant for Fashion
BI Style Creation
Assortment Planning
Color Creation
Assortment Definition Assortment Plan Style/Color Mix
Prepack/Quota-
Option Plan scale per Color
Size Creation
Relase
Workbench Size Plan
(retraction of Style/Size Mix
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
Master Data Purchase Order
ERP
Allocation
© SAP 2008 / Page 13
Assortment Definition: For each merchandise area (any article hierarchy level), you
define assortments and assign the assortments to stores that have identical dimension
values. Optionally, this assignment can occur time-dependent. You can calculate these
dimension values either in the APD (Analyze Process Designer) or using a custom-
defined algorithm that you can implement in a Business Add-In (BAdI). To make the
assortment assignments you planned in the BI system available to the operational
processes, you have to release them to SAP ECC with the Release Workbench
(message type LOCGRP), either manually or in background processing.
Target planning for your Assortment Plan: Plan the quantities and values for the initial
buy allocation and putaway quantity as the targets for Operational Assortment Planning
and Control (OAPC). You plan these targets at the level of the article hierarchy node,
assortment type, assortment, season, season year, and rollout. You transfer the targets
to OAPC in SAP ECC using the Release Workbench manually or in background
processing. There these targets can be drawn on for the further details of your planning.
Create planned article: For the correct product mix in your assortment planning, you
may require new articles. You create these planned articles (generic articles, styles)
by entering some article information. You also define the colors and sizes in which you
wish to procure the article. Normally, all planned articles are not included in the final
assortment plan. Determination of the correct product mix is usually an iterative
process. The information on the article and the actual article planning usually develops
during the process of assortment planning.
Execute quantity planning: You can plan, for example, at the article level or the
article/color level or the article/color/size level. Here you plan the quantities for fixed
allocation and reallocation of initial buy and putaway for both the planned and existing
articles.
Create prepack generation information: You can determine the prepack size and assign
a quota scale for the distribution to the sizes.
Release to merchandising system (OAPC): The release of the assortment plan can take
place at the following levels: article hierarchy node, article, rollout, season year and
season category.
Result
At the end of assortment planning, you have assigned stores to your assortments time-
dependently for each merchandise area, and released the assortments and
assignments to SAP ECC. You have also determined the articles, quantities and
prepack information and transferred them to13OAPC in SAP ECC.
Seasonal Assortment Planning – Assortment
Plan
BI
Assortment Planning
Assortment Plan
Target data for OAPC is planned

Level: Assortment, Rollout, Season, Season Year
Operational
Assortment Planning
and Control
ERP Allocation
© SAP 2008 / Page 14
The following data can be written to the inbound interface and displayed as planning
information in OAPC in the standard version:
Key performance indicators “Fixed allocation of initial buy” and “Reallocation of initial
buy” (on a quantity and value basis: purchase price, sales price) at the following levels:
Article hierarchy nodes; assortment type, assortment, season, season year, rollout
Key performance indicator “Putaway quantity” on a quantity and value basis at the
following levels:
Article hierarchy nodes; season, season year, rollout, (local distribution center)
assortment
Number of different generic articles (or single articles) per key performance indicator in
the assortments (assortment width).
The planned quantities of the key performance indicators “fixed allocation of initial buy”
and “reallocation for initial buy” for the assortments are valid for each store contained in
the assortment.
14
Assortment Planning – Assortment Plan
Example Cluster Plan
In this sample template all assortments (clusters) for a given segment, season, season year, rollout
combination are displayed
Key figures that are needed later on by the OAPC (operational assortment planning and control) are
planned
this sample also provides on overview of the number of stores and the number of options currently
assigned to an assortment thereby delivering important information as base for planning
© SAP 2008 / Page 15
15
Seasonal Assortment Planning – Option Plan
BI Style Creation
Assortment Planning
Color Creation
Prepack/Quota-
Size Creation
Relase
Workbench Size Plan
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
ERP
Allocation
© SAP 2008 / Page 16
16
Assortment planning – Option Plan
Example Option Plan per Cluster
In this sample template a given assortment can be planned in more detail

Products that are already assigned to the assortment are displayed
Planner can drill-down to colour level and verify/ change the respective key
figures that have been distributed from assortment plan down to style/ color level
Possibility to use quotascale key figure for distribution
This sample template incorporates new functionality on BI:
Create Styles, Create Colors, Style/Color Mix, Packsize/Quotascale
© SAP 2008 / Page 17
17
Seasonal Assortment Planning –
Style Creation
BI Style Creation
Assortment Planning
Color Creation
Prepack/Quota-
Size Creation
Relase
Workbench Size Plan
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
ERP
Allocation
© SAP 2008 / Page 18
18
Example Style Creation
Styles are placed in the hierarchy

Attributes are assigned, e.g.
Pack size
Size curve (quota scale)
Fashion grade
further attributes can freely be added
Possibility to copy an existing style
Release status of style (1 = planned, blank =
released)
© SAP 2008 / Page 19
19
Color Creation
BI Style Creation
Assortment Planning
Color Creation
Prepack/Quota-
Size Creation
Relase
Workbench Size Plan
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
ERP
Allocation
© SAP 2008 / Page 20
20
Example Color Creation
Colors are created and can be grouped with the

help of an attribute, e.g. colour family
New color can be released into SAP ERP via
the purchasing list release
© SAP 2008 / Page 21
21
Style / Color Mix
BI Style Creation
Assortment Planning
Color Creation
Prepack/Quota-
Size Creation
Relase
Workbench Size Plan
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
ERP
Allocation
© SAP 2008 / Page 22
22
Example Style/Color Mix
Assign new or existing color to a new or existing style

Style/ color assignment can be released into SAP
ERP via the purchasing list release
© SAP 2008 / Page 23
23
Prepack/ Quotascale per Color
BI Style Creation
Assortment Planning
Color Creation
Prepack/Quota-
Size Creation
Relase
Workbench Size Plan
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
ERP
Allocation
© SAP 2008 / Page 24
24
Example Packsize/Quotascale per Color
Add pack size per color

Add quota scale per color
this information is used to create
prepacks and variants in ERP and
distribute quantities to style/ color/
size
© SAP 2008 / Page 25
25
Size Plan
BI Style Creation
Assortment Planning
Color Creation
Prepack/Quota-
Size Creation
Relase
Workbench Size Plan
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
ERP
Allocation
© SAP 2008 / Page 26
26
Example Size Plan
In this sample template a

given assortment can be
planned in more detail
Products that are already
assigned to the assortment
are displayed
Planner can drill-down to
colour/ size level and
verify/ change the respective
key figures that have been
distributed from assortment
plan down to color/ size level
Possibility to use quotascale
key figure for distribution
This sample template
incorporates new functionality
on BI:
Create Size
Style/Size Mix
© SAP 2008 / Page 27
27
Size Creation
BI Style Creation
Assortment Planning
Color Creation
Prepack/Quota-
Size Creation
Relase
Workbench Size Plan
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
ERP
Allocation
© SAP 2008 / Page 28
28
Example Size Creation
© SAP 2008 / Page 29
29
Style/ Size Mix
BI Style Creation
Assortment Planning
Color Creation
Prepack/Quota-
Size Creation
Relase
Workbench Size Plan
transactional
or master
data)
Assortments /
Operational
Store Assignments
Assortment Planning
and Control
ERP
Allocation
© SAP 2008 / Page 30
30
Example Style/Size Mix
© SAP 2008 / Page 31
31
Assortment Planning – Process Example
Non Fashion
Within SAP you have the following options to carry out the basic assortment planning process:
OPTION 1:
You can complete assortment planning within SAP BI as soon as key figure target planning is finalized.
Transfer the assortments to the layout workbench and complete the operational assortment planning part
there.
OPTION 2:
Or you carry out some or even all process steps of operational assortment planning within Integrated
Planning of SAP BI and transfer this information to the layout workbench of SAP ERP for fulfillment.
The process steps are:
Assortment Version Creation

Product Creation
Assignment of Products to Assortments (Creation of Product Mix)
The following slide show just one possible process variant for basic
merchandise assortment planning:
© SAP 2008 / Page 32
32
Non-seasonal Assortment Planning - Overview
BI Assortment Planning
Space management
Third party
Assortment Creation
Assortment Definition Assortment Plan
Version Creation
Product Plan Product Creation
Product Mix
Relase
Workbench
(retraction of
transactional
or master
data)
Assortments /
Operational Assortment
Store Assignments Layoutworkbench
Planning and Control
Space management
Third party Master Data Purchase Order
Replenishment
ERP
© SAP 2008 / Page 33
33
Agenda
1. Introduction
3. Store Planning
© SAP 2008 / Page 34
34
ES Bundle Merchandise and Assortment
Planning Integration
Extends the integration between the Merchandise and Assortment Planning module (SAP MAP) and SAP ERP to the style/colour/size level
(SKU). This enables the style level assortment planning processes to be completed in SAP MAP and the results sent to the operational
assortment planning and control (OAPC functionality within SAP ERP) for subsequent creation of allocations and purchasing lists.
In conjunction with the development of the placeholder style, the functionality gives retail buyers and planners the ability to iteratively assort
ranges to store clusters through the planning cycle and only create approved articles in the SAP ERP at the point of approval.
Designer Buyer Planner

Buyer/Planner Planner Planner
OAPC
Creates/develops Selects Develops seasonal Assign products Releases
(aka Seasonal Purchase
product Product plans, clusters stores to clusters assortment
Management)
Backend SAP SAP

SAP MAP
MAP (BI)
SAP MAP
MAP (BI)
(BI) SAP
SAP MAP
MAP (BI)
(BI) (BI) SAP
SAP ERP
ERP
System
Business Value
Enables interactive and iterative assortment planning Use Cases
to be undertaken concurrently with product selection Assortment approval triggers the release of master and attribute data
and departmental planning.
assigned to the articles within the SAP MAP assortment process to SAP
Closes the gap between departmental planning, range
selection and execution ERP for the purpose of creating purchasing lists.
Reduces the duplication and new product data set up The released data assortment plan contains sufficient data to create
cycle time prepacks through the OAPC functionality
Purchase list creation respects the delivery dates defined in the approved
assortment plan
© SAP 2008 / Page 35
35
Overview new MAP Integration, EhP3, BI SP9:
Service Operations
ERP BI
Assortment Plan for
Basics
Assortment Plan for Basics MAP BI
Layout Layout Module Version
AssortmentProduct Foundation
Workbench Inbound Process (existing Message Version Content
AssortmentProductVersion in BI)
Create Material Basic Basic Article Data Request Material

Data
MAP Release Workbench

Basic Data
Create Sales Price

Sales Prices Data Request Sales Price
Specification Calculation
Specification Calculation
Articles
Planned
Articles
Create Product Request Product
Procurement Procurement
Arrangement as Bulk Purchasing Info records Arrangement as Bulk
Master Data
Purchasing Creation
List
Inbound Maintain Retail Purchasing plan Request Retail
Process Purchasing Plan Purchasing Plan
Including planned articles,
(in OAPC) article information, targets
on assortment level,
EhP 3
Purchases Assortment Plan for
Orders BI 7.03 SP 9 Fashion
Existing
Service
Operations
© SAP 2008 / Page 36
Service Operations:
Maintain Retail Purchasing Plan
via this service, you are enabled to maintain a Retail Purchasing Plan. Input: Retail
Purchasing Plan basic data, list of styles with their attributes, colors, sizes and planned
quantities per assortment, target sales per assortment
Inbound service in SAP ERP system, Initiated by the release workbench in MAP BI via
the service Request Retail Purchasing Plan
BO: Retail Purchasing Plan
Create Sales Price Specification Calculation (EhP2)
via this service, you are enabled to calculate a sales price.
the service Request Sales Price Specification Calculation
BO: Sales Price Specification Calculation
Create Material Basic Data
via this service, you are enabled to create a material (for retail a single article) with its
basic data. Input: material basic data such as material number, description, merchandise
category
the service Request Material Basic Data
BO: Material
36
Create Material Basic Data as Bulk (This Service will only work for standard Material,
not retail article)
via this service, you are enabled to create materials (for only a standard material) with its
basic data
Inbound service, initiated by SAP ERP system
BO: Material
Create Product Procurement Arrangement (Not used by the MAP scenario, but part
of EhP3 MAP development)
via this service, you are enabled to create a purchasing info record
Inbound service, initiated by SAP ERP system
BO: Product Procurement Arrangement
Create Product Procurement Arrangement as Bulk
via this service, you are enabled to create purchasing info records.
the service Request Product Procurement Arrangement as Bulk
BO: Product Procurement Arrangement
Request Retail Purchasing Plan
via this service, you are enabled to maintain a Retail Purchasing Plan. Input: Retail
Purchasing Plan basic data, list of styles with their attributes, colors, sizes and planned
quantities per assortment, target sales per assortment.
This is an outbound service which is called through the MAP release workbench.
BO: Assortment Plan
Request Sales Price Specification Calculation
via this service, you are enabled to calculate a sales price.
This is an outbound service which will be called through the MAP release workbench.
BO: Merchandise and Assortment Planning Material
Request Material Basic Data
via this service, you are enabled to create a material (for retail a single article) with its
basic data. Input: material basic data such as material number, description, merchandise
category
Request Product Procurement Arrangement as Bulk
via this service, you are enabled to create purchasing info records.
37
Agenda
1. Introduction
3. Store Planning
© SAP 2008 / Page 38
38
Integration Between BI & Retail System
After a plan or part of a plan containing information for subsequent

processes has been finalized, it has to be released by the planner.
The information of a plan consists of created master data and plan data.
With the release workbench XML messages are created and sent to the XI.
For some message types using an RFC or eSOA connection is optional.
Then the merchandising system (ERP or any other system) can get the
messages and use the information.
BI XI Merchandising System
Outbound proxy
Inbound proxy
Release BAPIs /
XI Function
transaction
modules
Data
Data
© SAP 2008 / Page 39
After you have drawn up the final version of a plan or sub-plan you can release it. This
triggers the creation of outbound messages with relevant data. Data can be distributed as
XML files with the SAP Exchange Infrastructure (SAP XI) and for some messages you can
choose to send it directly by RFC to the SAP ERP System. In the SAP XI environment,
MAP message types MAP are defined under application component
“http://www.sap.com/platform/netweaver/processintegration.epx”.
In the Release Workbench use appropriate selection criteria (for example, product ID,
category, sales organization and distribution channel) to specify the exact data that you
want to release. You can simultaneously release data for several message types (for
example, all message types that relate to a particular category).
To use the functions of the Release Workbench you must have the appropriate
authorization:
Authorization for specific selection criteria
Authorization for repeated release of data
39
RFC, XI or eSOA
As of BI Content release 7.0.3 SP9 and BI-IP support package 14, the
following message can be used:
Message RFC XI ESOA
Allocation / PO ●
Assortment Plan ● ●
Assortment – Product ●
Assortment version for merchandising (Original) ● ●
Assortment version for merchandising (New) ● ●
Assortment version for optimization (Original) ●
Assortment version for optimization (New) ●
Location Group / Assortment ● ●
Markdown proposals ● ●
OTB ●
Product (Original) ● ●
Product (New, including sales and purchasing prices) ** ●
Retail Purchasing plan * ● ●
Sales Reduction Budget ●
© SAP 2008 / Page 40
Following a release, XML files are created that can be distributed with the SAP Process
Integration. Alternatively, data for specific message types can be transferred directly with
Remote Function Call (RFC) to an SAP ERP Retail System. For more information on
RRCenabled message types, see OSS Note 682377.
*RetailPurchasingPlan Message type can also be used by RFC, see note 1152266
**New Product implementation sends three messages: material basic, product procurement
arrangement, sales price specification calculation
40
General Selection Screen
In the first step you select which message types you want to
release
Some message types have dependencies

E.g. markdown proposals need the corresponding product
message released first.
Use this flag to release the prior messages automatically
General selections for all

message types
© SAP 2008 / Page 41
On the initial screen in the Release Workbench you choose message types using the
relevant selection fields.
You can also choose Release Associated Messages.
In the screen area General Selection Criteria you can store general restrictions for the data
to be released.
Most message types are based on master data and can only be released once. Other
message types, such as OTB, allocations tables and purchase orders are composed of
planning data and can be released more than once. The related control is performed with a
release status that is available for master data but not for planning data.
To be able to send markdown proposals you do not need to release the proposals manually
beforehand. The system creates these at periodic intervals - usually once a week – and
transfers them to the retailing system.
41
Detailed Selection Screen
Release the messages Release messages in a job

in dialog e.g. periodically every night. Simulate the release Delete selection
process. criteria
Application log
© SAP 2008 / Page 42
After you have entered data on the initial screen a tab page is displayed for each selected
message type. You then enter additional data there that is specific to the message type.
It is not possible to release data here straight from the planning layout.
Data can be released immediately or it can be scheduled as a job for later. Alternatively
you can simulate the release. Checks are performed here without triggering a release.
42
Application Log
The history of release actions is logged in the

application log.
It helps in case of errors and answers questions like
“which products have not been released yet?”
© SAP 2008 / Page 43
Every release transaction is retained in an application log that you can call at the touch of a
button. This contains information about the selection conditions and resulting data objects
and about error messages if the release was not completed successfully.
43
Copyright 2008 SAP AG
All rights reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document
contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,
and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or
other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these
materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch
SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die
dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen
von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder
ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck
sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks
zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über
Internetseiten Dritter ab.
Alle Rechte vorbehalten.
© SAP 2008 / Page 44
44

Sap Retail Merchandising and Assortment Planning Overview2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Retail Merchandising and Assortment Planning Overview2

Uploaded by

Copyright:

Available Formats

Merchandise and Assortment Planning (SAP MAP)

© SAP 2008 / Page 2

 Alternatively creation in SAP ERP and

 Group stores that can be considered/ planned

 Determine which store cluster receives which

© SAP 2008 / Page 4

 Clustering according to climatuc zones

 Clustering according to delivery regions

What price level is a store

© SAP 2008 / Page 6

Assortment 3,1: Ladies’ blouses,

Assortment 3,3: Ladies’ blouses,

© SAP 2008 / Page 7

time-dependent assignment of stores to assortments

© SAP 2008 / Page 8

© SAP 2008 / Page 9

Assortment planning is a part of the bottom-up planning

© SAP 2008 / Page 10

Strategic Plan Planning level

 Determining the correct product mix for the assortment

© SAP 2008 / Page 12

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 13

 Target data for OAPC is planned

Master Data Purchase Order

© SAP 2008 / Page 15

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 16

 In this sample template a given assortment can be planned in more detail

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 18

 Styles are placed in the hierarchy

© SAP 2008 / Page 19

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 20

 Colors are created and can be grouped with the

© SAP 2008 / Page 21

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 22

 Assign new or existing color to a new or existing style

© SAP 2008 / Page 23

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 24

 Add pack size per color

© SAP 2008 / Page 25

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 26

 In this sample template a

© SAP 2008 / Page 27

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 28

© SAP 2008 / Page 29

Assortment Definition Assortment Plan Style/Color Mix

Master Data Purchase Order

© SAP 2008 / Page 30

Alternatively creation in SAP ERP and

Group stores that can be considered/ planned

Determine which store cluster receives which

Clustering according to climatuc zones

Clustering according to delivery regions

Determining the correct product mix for the assortment

Target data for OAPC is planned

In this sample template a given assortment can be planned in more detail

Styles are placed in the hierarchy

Colors are created and can be grouped with the

Assign new or existing color to a new or existing style

Add pack size per color

In this sample template a

Assortment Version Creation

Some message types have dependencies

General selections for all

Release the messages Release messages in a job

The history of release actions is logged in the