BB Configuration Guide
EHP5 for SAP ERP 6.0June 2011EnglishEnglish
Assortment Operations (713)
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyBuilding Block
Configuration Guide
Copyright
2011 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. Microsoft, Windows,
Excel, Outlook, and PowerPoint are registered trademarks of
Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i,
System i5, System p, System p5, System x, System z, System z10,
System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel
Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6,
POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect,
RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent
Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or
registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S.
and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are
either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the
Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or
registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology. Java is a registered
trademark of Sun Microsystems, Inc. JavaScript is a registered
trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape. SAP, R/3, SAP
NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects
Explorer, StreamWork, 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 other countries.
Business Objects and the Business Objects logo, BusinessObjects,
Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and
other Business Objects products and services mentioned herein as
well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. Business Objects is an
SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere,
and other Sybase products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of
Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks
of their respective companies. Data contained in this document
serves informational purposes only. National product specifications
may vary.
These materials are subject to change without notice. These
materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or
warranty of any kind, and SAP Group shall not be liable for errors
or omissions with respect to the materials. The only warranties for
SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as
constituting an additional warranty.Icons
IconMeaning
Caution
Example
Note or Tip
Recommendation
Syntax
Typographic Conventions
Type StyleDescription
Example textWords or characters that appear on the screen. These
include field names, screen titles, pushbuttons as well as menu
names, paths and options.
Cross-references to other documentation.
Example textEmphasized words or phrases in body text, titles of
graphics and tables.
EXAMPLE TEXTNames of elements in the system. These include
report names, program names, transaction codes, table names, and
individual key words of a programming language, when surrounded by
body text, for example, SELECT and INCLUDE.
Example textScreen output. This includes file and directory
names and their paths, messages, source code, names of variables
and parameters as well as names of installation, upgrade and
database tools.
EXAMPLE TEXTKeys on the keyboard, for example, function keys
(such as F2) or the ENTER key.
Example textExact user entry. These are words or characters that
you enter in the system exactly as they appear in the
documentation.
Variable user entry. Pointed brackets indicate that you replace
these words and characters with appropriate entries.
Contents
5Assortment Management: Configuration Guide
51Purpose
52Preparation
53Configuration
53.1Assortment
53.1.1Maintain General Control for Assortments
73.1.2Maintain Assortment Dimensions
83.1.3Maintain Assortment Types
93.2Layout
93.2.1Maintain Fixture Categories
103.2.2Maintain Settings for Layout Workbench Connection
113.2.3Setting System Messages
113.2.4Creation Status for Core Articles
123.2.5Maintain a Maintenance Group for Core Articles
143.2.6Maintain Space Management Profiles
153.2.7Assign Space Management Profile to Site
153.2.8Maintain annual seasons
Assortment Management: Configuration Guide
1 Purpose
This configuration guide provides the information you need to
set up the configuration of this building block manually.
If you do not want to configure manually and prefer an automated
installation process using BC Sets and other tools, refer to the
installation guide of this building block.2 Preparation
Before you start installing this building block, you must
install prerequisite building blocks. For more information, see the
building block prerequisite matrix located on the Documentation DVD
on the Content Library page under Technical Information (on the
left navigation pane).
3 Configuration
3.1 Assortment3.1.1 Maintain General Control for
AssortmentsUse
In the transaction WSS1 (General Control, Retail Master Data)
you define some basic master data related parameters that affect
several application areas in SAP Retail. Relevant for this building
block are the settings that are related to assortments, which are
grouped in subscreen Control, Assortments. Here you define: Which
interface module you want to use between Assortment and Integrated
Article Maintenance (Using a module other than the available
standard module is a massive deviation from the standard and should
not be done lightly.) If you want to work with without listing
conditions (As listing conditions are a prerequisite for POS
download and assortment list generation this indicator should not
be set). The function module which performs subsequent
listing/master data creation in cases where the article master data
is missing in a transaction involving stock for a target site and
subsequent listing is allowed for it. Whether you want an entry to
be made in the system log if during the creation of article master
segments in assortment maintenance functions no reference can be
found and thus the article segments can not be created fully. If
when processing the errors reported in the system log for missing
article master segments, the system determines that some errors
still cannot be solved, another entry is made in the log. Number of
days that the log records for missing segments would remain in the
system (if you have chosen to create such log entries). The
function module with which you can carry out any further checks to
see whether an article is allowed in a sales order or delivery
(User-Exit). If multiple assignment of sites and assortments is
active. When multiple assignment is active, a site can be assigned
several assortment of type 'C' besides its own local site-specific
assortment. If it is not active, there is a 1:1 assignment ratio
between site and assortment, meaning every site has its own local
assortment and cannot be assigned any other assortments. If the
local (site-specific) assortments are taken into account in listing
when using the mass listing processes (WSM4, WSM8). If you want to
use time-dependent assignment of sites to assortments
Procedure
1. Access the activity using one of the following navigation
options:
Transaction CodeWSS1
IMG MenuIMG( Logistics - General ( Basic Data Retail ( General
Control, Retail Master Data
2. On the Retail Master Data General Control screen, check that
the following entries exist:Field nameDescriptionUser action and
valuesNote
FM AssortmentInt.art.maint.ASSORTMENT_VERSION_ALL
Work Without Listing Conditionsnot set
FMod Subs. listingUSER_EXIT_NACHLISTUNG
Log missing article segmentsSet flag
Error log, multipleSet flag
Log records retention (days)10
FMod Any listing checkASSORTMENT_VERSION_GHC
Multiple Assignment Is ActiveSet flag
Local Assort-ments ListingSet flag
Time-Dep. Assignm.Set flag
3.1.2 Maintain Assortment Dimensions
Use
Assortment dimensions are used to group plants with similar
characteristics together to use one assortment. The assortment
dimensions to be used are defined by the assortment type. An
assortment can use up to three assortment dimensions.
In this step, you define all assortment dimensions and their
possible characteristic values that you want to use in assortment
planning.Procedure
1. Access the activity using the following navigation
option:
Transaction CodeSPRO
IMG MenuIMG( Logistics - General ( Assortment ( Assortment (
Maintain Assortment Dimensions
2. Check if the entries described below already exist and if not
add them via New Entries.3. On the New Entries: Details of Added
Entries screen, make the following entries:
Field nameField 1
(Dimension)Field 2
(Description)
Entry 1PRSpace Profitability
Entry 2SPSpace
4. Select the first entry (PR) and choose Dimension Values.5. On
the New Entries: Overview of Added Entries screen, make the
following entries:
Field nameField 1
(Val.)Field 2
(Description)
Entry 1P1high
Entry 2P2mid
Entry 3P3low
6. Choose Back.7. Select the second entry (SP) and choose
Dimension Values.8. On the New Entries: Overview of Added Entries
screen, make the following entries:
Field nameField 1
(Val.)Field 2
(Description)
Entry 1S150 sqm
Entry 2S230 sqm
9. Choose Save.3.1.3 Maintain Assortment TypesUse
The assortment type defines assortment attributes and the system
response during assortment maintenance. Among other things, the
assortment type controls:
The assortment dimensions
The option to assign a layout or layout module to the
assortment
Automatic creation of a layout module when creating an
assortment
PrerequisitesThe assortment dimensions you want to use must
already be defined in the system.
Procedure1. Access the activity using the following navigation
option:
Transaction CodeSPRO
IMG MenuIMG -Logistics - General ( Assortment ( Assortment (
Maintain Assortment Types
2. Check if the entries described below already exist and if not
add them via New entries.3. On the New Entries: Details of Added
Entries screen, make the following entries:Entry 1:
Field nameDescriptionUser action and valuesNote
Assortment typeBASI
DescriptionBasic assortment
Dimension 1SP
Dimension 2PR
Assign Layout ModuleSet flag
Create Layout moduleSet flag
LayoutModule Not InpRdySet flag
Entry 2: Field nameDescriptionUser action and valuesNote
Assortment typeFASH
DescriptionFashion assortment
Dimension 1SP
Dimension 2PR
Assign Layout ModuleNo flag
Create Layout moduleNo flag
LayoutModule Not InpRdyNo flag
4. If you want to add a description in another language choose
GoTo and then Translation, select the desired language (for
example, DE for German) and maintain the description (for example,
Fashion Sortment).5. Choose Save.3.2 Layout3.2.1 Maintain Fixture
CategoriesUse
A fixture type describes the general appearance for a group of
fixtures for example, shelves, rounders or magazine racks. These
are then defined in more detail in the definition of the actual
fixture (for example, shelf 2 m wide).Procedure
1. Access the activity using the following navigation
option:
Transaction CodeSPRO
IMG MenuIMG ( Logistics - General ( Assortment ( Assortment (
Layout ( Space Management ( Maintain Fixture Categories
2. Check if the entries described below already exist and if not
add them via New Entries.3. On the New Entries: Overview of Added
Entries screen, make the following entries:
Field nameField 1
(Fixture Categ.)Field 2
(Description)
Entry 1BPBSBasket
Entry 2BPFRFreezer Case
Entry 3BPRORounder
Entry 4BPSHShelf
Entry 5BPTATable
4. Choose Save.3.2.2 Maintain Settings for Layout Workbench
Connection
Use
If you want to transfer certain articles from the Layout
workbench to the Operational Assortment Planning and Control (OAPC)
for further processing you have to make a couple of settings to
enable such a transfer to take place successfully.First of all, an
indicator has to be set to allow the transfer. A default value for
the season category needs to be maintained in the general settings
for OAPC. The reason for that is that season category, season year
and rollout are required for the header data when a purchasing list
is created in OAPC. Both the season year and the rollout can be
determined based on dates maintained for the layout module version
but the season category is determined from this default setting in
Customizing. The procedure for allowing the transfer is outlined
below - for all settings that are required to work with the OAPC.
Refer to R20 Seasonal Procurement.
Procedure
1. Access the activity using the following navigation
option:
IMG MenuLogistics - General ( Assortment ( Operational
Assortment Planning and Control ( Maintain General Settings
2. On the Change View Maintain General Settings: Details screen,
check that the following entries exist in the subscreen Settings
for Layout Workbench Connection:Field nameDescriptionUser action
and valuesNote
Default Season Category0000
Allow LWB OAPC TransferIndicator is set
3. Choose Save.3.2.3 Setting System Messages
Use
Change the message that controls whether the season data
assigned to the article needs to match the season data of the
purchasing list from an error message to a warning message.That way
basic articles that do not have any season assigned to them can be
transferred to OAPC without an error message.Procedure
1. Access the activity using the following navigation
option:
Transaction CodeSPRO
IMG MenuIMG ( Logistics - General ( Assortment ( Operational
Assortment Planning and Control ( Settings for System Messages
2. Select message number 254 (Article &1 is assigned to a
different season than this purchasing list).
3. On the Change View Settings for System Messages: Overview
screen, check that the following entry exists or change it if
required:
Field nameDescriptionUser action and valuesNote
Message TypeW Warning Message
4. Choose Save.3.2.4 Creation Status for Core Articles
Use
The creation status is an informational field in the basic data
of the material master that indicates the application in which you
created the material. For the creation of a core article from the
layout workbench a specific status should be maintained
here.Procedure
1. Access the activity using the following navigation
option:
Transaction CodeSPRO
IMG MenuIMG( Logistics - General ( Material Master (
Retail-Specific Settings ( Settings for Key Fields ( Maintain
Creation Status
2. On the Change View Maintain Creation Status: Overview screen,
check that the following entry exists:Field nameDescriptionUser
action and valuesNote
Creation status03
DescriptionLayout Workbench
(If it does not exist add it via New Entries).3.2.5 Maintain a
Maintenance Group for Core Articles
Use
Maintenance groups determine which fields of the article master
the system displays for processing in the applications that use
maintenance groups, for example, core master data processing,
integrated mass change or the article list.You can create one or
more templates for a maintenance group where you enter default data
for example for the initial screen for core article master data
processing. A maintenance group can be defined as cross-application
or application-specific. Below an application-specific maintenance
group is created for the creation of core articles from the layout
workbench. A core article master record contains the article
segments and article data that you need for the function in which
you are creating the core master record. You can enhance a core
article master record later on with the missing master data so that
you can use it operationally as a complete article in every
application.Procedure
1. Access the activity using one of the following navigation
options:
Transaction codeWRFMGROUP
SAP system menuLogistics ( Retailing ( Master Data ( Article
Data ( Article ( Manage Maintenance Groups
2. If there is no hierarchy tree structure displayed on the left
side of the screen, use the Show/Hide Tree button to display it.3.
Choose Change Mode.4. Select the Layoutworkbench folder in the
hierarchy tree.5. Choose Create Node .6. The message: Select a node
type, displays. Choose Maint.Group.7. Maintain the following
values:Field nameDescriptionUser action and valuesNote
Node ID(not maintained by user)The node ID is assigned by the
system
Node name
(field right of the ID)Layout workbenchField name is not
displayed on the screen
DescriptionLayout workbenchCan be used to describe the node in
more detail. Via button maintenance of language-speci-fic text
possible.
8. Choose the Select field groups button to add the following
field groups to the maintenance group. Once they are transferred
from the selection screen to subscreen Field Group Assignment, set
the indicators in the Propose (field cont.) column, as indicated
below:FGDescriptionProposeAttributes
32: Classification
71: Assortment Assignment
80: Variant Dataset indicator
93: Purch. Price Maint.set indicator
104: Sales Price Maint:set indicator
110: Basic Data Textset indicator
500: Art. Hierarchy Nodes
920: Seasonset indicator
950: Tax Classificationset indicator
980: RTF Creation Statusset indicator
1180: Purchasing Groupset indicator
1230: Short Textset indicator
1400: Alternate UoMset indicator
1410: HEAN/UPC Codeset indicator
1420: Measurements of a UoMset indicator
1430: Volumes of a UoMset indicator
1440: Weight of a UoMset indicator
1654: Item Category Groupset indicator
2023: Vendor Article Numberset indicator
The indicator Propose (field cont.) specifies that the field
content is proposed from the reference material when creating an
article master record using a reference article.9. Maintain a
template for the maintenance group. Select maintenance group and
choose the Show/Hide button.
10. On the subscreen Maintain templates, make the following
entries:
Field nameDescriptionUser action and valuesComment
Short textT1
CS03
MTypHAWA
Ct00
POrg1000
Cat0(Info record category)
SOrg1000
DChl10
11. Choose Save.
12. Choose Change Mode.13. Choose the Show/Hide button.
14. Choose the Maintain Default Data button in the Maintain
Templates subscreen.15. On the Maintain template screen, make the
following entries under Basic Data:Field nameDescriptionUser action
and valuesComment
Season year2011
Season0000
Tax class.1
16. Make the following entries under Sales Data:Field
nameDescriptionUser action and valuesComment
Item category groupNORM
17. Choose Back.18. Choose Save.3.2.6 Maintain Space Management
ProfilesUse
The space management profile groups various control parameters
for connection with external space management programs.
Procedure
1. Access the activity using the following navigation
option:
Transaction CodeSPRO
IMG MenuIMG ( Logistics - General ( Assortment ( Assortment (
Layout ( Space Management ( Maintain Space Management Profile
(Basis LIS or BW)
2. Check if the entry described below exists, and if not, add it
via New Entries.3. On the New entries: Details of Added Entries
screen, make the following entries:
Field nameDescriptionUser action and valuesNote
Space Mgtm ProfileZ001
DescriptionShelf Optim. Profile
Read pur. priceSet flag
Read sales pr.Set flag
4. Choose Save.3.2.7 Assign Space Management Profile to Site
Use
The space management profile, groups various control parameters,
for connection with external space management programs.
Procedure
1. Access the activity using the following navigation
option:
Transaction codeWB02
SAP system menuLogistics ( Retailing ( Master Data ( Site Data (
Site ( Change
2. On the Site Change Initial Screen screen, make the following
entry:
Field nameDescriptionUser action and valuesNote
SiteM014
3. Choose Enter.4. Choose the Layout/Blocks tab and make the
following entry:
Field nameDescriptionUser action and valuesNote
Space Mgmt ProfileZ001
5. Choose Save.3.2.8 Maintain annual seasons1. Access the
activity using one of the following navigation options:
Transaction CodeSPRO
IMG MenuLogistics General ( Season ( Maintain annual seasons
SAP Role Menu
2. This settings should be in Season "0001/0002". If a setting
is missing, then choose the button to add a new method step and add
the missing entries.Field nameField 1
Season.Field 2
Season yearField 3
Rollout
Entry 100012008 to 2010
Entry 200022008 to 2010
The entries for 2009 and 2010 are similar
3. Choose the button or select ENTER on the keyboard.
4. Choose the button to save the entries.
_1118216528.bin