Telechargé par Brahim Kaddafi

SAP Item Management 711

publicité
EHP7 for SAP ERP
6.0
July 2014
English
Item Management (711)
Business Process Documentation
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
Item Management (711): BPD
Copyright
© 2014 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company
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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality mentioned
therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and
possible future developments, products, and/or platform directions and functionality are all subject to
change and may be changed by SAP SE or its affiliated companies at any time for any reason without
notice. The information in this document is not a commitment, promise, or legal obligation to deliver any
material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties
that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should
not be relied upon in making purchasing decisions.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style
Description
Example text
Words 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 text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names 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 text
Screen 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 TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Contents
1
Purpose ................................................................................................................................... 6
2
Prerequisites............................................................................................................................ 6
2.1
Master Data and Organizational Data .............................................................................. 6
2.2
Checking User Parameters .............................................................................................. 7
2.3
Roles ................................................................................................................................ 7
3
Process Overview Table ......................................................................................................... 8
4
Article Maintenance ............................................................................................................... 11
4.1
Process Flow .................................................................................................................. 12
4.2
Single Article .................................................................................................................. 13
4.2.1
Creating a Single Article (Manually) ....................................................................... 13
4.2.2
Process the Single Article ....................................................................................... 16
4.3
Reference Handling In the Article Master ...................................................................... 20
4.3.1
Reference Article as Copy Template ...................................................................... 21
4.3.2
Article Data with Client-Wide Validity...................................................................... 21
4.3.3
Determining Organizational Levels for an Article ................................................... 22
4.3.4
Comment on Mass Maintenance of Article Data for Same Org. Levels ................. 23
4.3.5
Work with Maintenance Groups .............................................................................. 27
4.3.6
Store Characteristic Values .................................................................................... 45
4.4
Generic Article ................................................................................................................ 52
4.4.1
Creating a Generic Article with Variants ................................................................. 52
4.4.2
Process the Generic Article .................................................................................... 55
4.4.3
Reference Handling For Generic Article Variants ................................................... 56
4.4.4
Matrix Maintenance for Generic Articles ................................................................. 58
4.5
Prepack .......................................................................................................................... 62
4.5.1
Creating A Prepack ................................................................................................. 62
4.5.2
Processing the Prepack .......................................................................................... 65
4.5.3
Determining Valuation Prices for Prepack Components ........................................ 67
4.5.4
Goods Receipt without References ........................................................................ 68
4.6
Sales Set ........................................................................................................................ 70
4.6.1
Creating a Sales Set ............................................................................................... 70
4.6.2
Processing a Sales Set ........................................................................................... 71
4.6.3
Goods Receipt without References ........................................................................ 75
4.6.4
Setting up Structured Article ................................................................................... 76
4.7
Display............................................................................................................................ 78
4.7.1
Creating Display...................................................................................................... 78
4.7.2
Process Display ...................................................................................................... 80
4.7.3
Goods Receipt without References ........................................................................ 84
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
4.8
Department Store/ Shop Concept .................................................................................. 86
4.9
Price Level Groups ......................................................................................................... 87
4.10
Direct Store Delivery (DSD) ....................................................................................... 88
4.10.1
Creating Supply Relationship ................................................................................. 88
4.10.2
Copying Supply Relationship .................................................................................. 90
4.10.3
Changing Purchase/Sales Price ............................................................................. 91
4.10.4
Creating Purchase Order ........................................................................................ 93
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Item Management
1
Purpose
Within the scope item, Item Management, Article creation of single, generic and structured
articles are displayed in the process for article maintenance. We will look at the principal features
of creating listing conditions using integrated article maintenance and also at reference handling
in the article master.
2
Prerequisites
Note the settings for this scope item in the customizing guide.
Master data needed in the processes has already been created using the eCatt tool.
Master data needed for the business cases is displayed in the master data overview for the
individual article types (fashion, food, and hardgoods) and can be referenced in the
corresponding processes.
2.1 Master Data and Organizational Data
To execute the scope item, use the master data listed for your installation of the preconfigured
system. For the relevant identifiers, see the following tables:
FASHION
HARDGOODS
FOOD
ARTICLE 1
PCS-01-ART111
PCS-02-LKP111
PCS-01-ART201
ARTICLE 2
PCS-01-ART146
PCS-06-ART432
PCS-06-ART321
ARTICLE 3
PCS-01ART111001
PCS-01-ART204
PCS-01-ART201001
ARTICLE 4
PCS-01-ART146
PCS-06-ART431
PCS-01-ART331
ARTICLE 5
PCS-01-ART147
PCS-06-ART433
PCS-01-ART322
ARTICLE 6
PCS-01-ART148
PCS-06-ART434
PCS-01-ART323
VENDOR1
PCS-V111
PCS-V201
PCS-V201
VENDOR2
PCS-V112
PCS-V202
PCS-V202
VENDOR3
PCS-V141
PCS-V431
PCS-V321
MC SINGLEART[MC-SA]
MC11451
MC14201
MC13202
MC GENERICART[MC-GA]
MC11141
MC14402
MC12003
MC SALES SET
MC11152
MC14203
MC12003
MC DISPLAY
MC11152
MC14402
MC12003
Required Master Data for Direct Store Delivery (DSD) Scope item:
Data Type
Data Value
COMPANY CODE
1000
SALES ORGANIZATION
1000
DISTRIBUTION CHANNEL
10
Store Sales
PURCHASE ORGANIZATION 1000
ARTICLE (HARDGOODS)
© SAP SE
PCS-01-ART204
Within the article master data
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Data Type
Data Value
the source of supply key is to
be set to external procurement
(1) at logistic view store
PCS-06-ART431
PCS-06-ART433
PCS-06-ART434
Article (Food)
PCS-06-ART321
PCS-01-ART331
PCS-01-ART322
PCS-01-ART323
VENDORS
PCS-V201
PCS-V202
STORES
M001
M002
2.2 Checking User Parameters
Use
In this step, check the user parameters and the default settings.
Procedure
1. On the SAP Easy Access screen, choose Customize Local Layout (Alt+F12), and select
Options….
2. In the Options dialog box, select Interaction Design  Visualization1 Make sure the field of
Show keys within Dropdown Lists is selected.
3. Choose OK.
4. Access the activity using one of the following navigation options:
Toolbar menu
System  User Profile  Own Data
Transaction code
SU3
5. On the Defaults tab, make the following entries:
Field name
Description
User actions and values
Note
Decimal Notation
1.234.567,89
Fixed Values
Date Format
1 DD.MM.YYYY
Fixed Values
Start menu
W10T
Fixed Values
6. Choose Save.
7. Choose Back.
2.3 Roles
Use
The roles listed below must have been installed to test this scope item in the SAP NetWeaver
Business Client (NWBC). They must be assigned to the users testing this scope item. You only
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
need the roles if you use the NWBC interface. You do not need them if you use the standard
SAP GUI.
Prerequisites
The business roles have been assigned to the user who is testing this scope item. Roles are not
limited to the transactions mentioned below. This is just a Cross-Channel Customer Order
Management related and process step oriented view.
Business Role
Technical Name
Process Step
Transaction
Retail Masterdata
Specialist
SAP_NBPR_MAST All the master data related steps
ERDATA_RT_S
Retail Assortment
ECC Planner
SAP_NBPR_ASSO Display a generate assortment
RTMENT_RT_S
module
WSL11
WSO7
Display the profile module for store
3
Warehouse
Specialist
SAP_NBPR_WAR Initial stock
EHOUSECLERK_S
MIGO
IT Administrator
(Professional User)
SAP_NBPR_IT_AD ABAP workbench
MIN_S
SE16
Retail Non-Seasonal
Buyer
SAP_NBPR_NONS Assortment
EASBUYER_RT_S
WSL1
Retail Pricing
Manager
SAP_NBPR_PRICI
NG_RT_S
Change price
MR21
Retail Warehouse
Manager
SAP_NBPR_WAR
EHOUSE_RT_S
Display material document
MB03
Retail Warehouse
Manager
SAP_NBPR_WAR
EHOUSE_RT_S
Transfer posting
MB1B
Process Overview Table
Process Step
Business Role
Transactio
n code
Create Single
Article
(Manually)
Retail
Masterdata
Specialist
MM41
Implement
Listing
Retail
Masterdata
Specialist
MM42
Display a
Generated
Assortment
Module
Retail
Assortment
ECC Planner
WSL11
Display the
Profile Module
for Store M001
Using
Assortment
Menu
Retail
Assortment
ECC Planner
WSO7
Maintain
Logistics Data
Retail
Masterdata
MM42
© SAP SE
External
Process
Reference
Business
Condition
Expected
Results
Page 6 of 8
SAP Best Practices
Process Step
Item Management (711): BPD
External
Process
Reference
Business
Condition
Business Role
Transactio
n code
for All
DCs/Stores
Specialist
Create a
maintenance
group
Retail
Masterdata
Specialist
WRFMGRO
UP
Extension of a
maintenance
group by a
template
Retail
Masterdata
Specialist
WRFMGRO
UP
Create Core
Master Article
with Template
Retail
Masterdata
Specialist
WRFMATB
ODY
Check the
Article Creation
Retail
Masterdata
Specialist
MM43
Mass
Maintenance
Using Reference
Sites
Retail
Masterdata
Specialist
MM41
Mass
Maintenance
Using Mass
Maintenance
Tool
Retail
Masterdata
Specialist
REFSITE
Alternative Data
Maintenance
(Alternative
Organizational
Levels)
Retail
Masterdata
Specialist
MM42
Mass
Maintenance
using the Article
Monitor
Retail
Masterdata
Specialist
WRFMATM
ON
Article Copy to
Create a New
Article
Retail
Masterdata
Specialist
WRFMATC
OPY
Check Article
Creation for the
Copied Article
Retail
Masterdata
Specialist
MM42
Article
Discontinuation
Retail
Masterdata
Specialist
WRF_DIS_
SEL
© SAP SE
Expected
Results
The
selected
articles are
checked,
follow-up
actions are
carried out
and the
articles are
marked for
deletion.
Page 6 of 8
SAP Best Practices
Process Step
Item Management (711): BPD
External
Process
Reference
Business
Condition
Business Role
Transactio
n code
Expected
Results
The results
are
checked in
the
discontinua
tion
monitor
Create Article
List
Retail
Masterdata
Specialist
WRF_AL
Follow up and
Replacement
Articles
Retail
Masterdata
Specialist
WRFFUAR
T
Store
Characteristic
Values
Retail
Masterdata
Specialist
CT04
Characteristic
Value Grouping
Retail
Masterdata
Specialist
WRFCHVA
LGRP
Create a
Characteristic
Profile with the
New
Characteristics
Retail
Masterdata
Specialist
CLWE
Assign the
Characteristic
Profile to a
Merchandise
Category
Retail
Masterdata
Specialist
WG22
Create a
Generic Article
with Variants
Retail
Masterdata
Specialist
MM41
Process Generic
Article
Retail
Masterdata
Specialist
MM42
Reference
Handling For
Generic Article
Variants
Retail
Masterdata
Specialist
MM43
Price Matrix for
Variants of
Generic Articles
Retail
Masterdata
Specialist
MM42
Matrix Handling
For Master Data
Fields For The
Generic Article
Retail
Masterdata
Specialist
MM42
Create a
Prepack
Retail
Masterdata
Specialist
MM41
© SAP SE
Page 6 of 8
SAP Best Practices
Process Step
Item Management (711): BPD
External
Process
Reference
Business
Condition
Business Role
Transactio
n code
Process
Prepack
Retail
Masterdata
Specialist
MM42
Determining
Valuation Prices
for Prepack
Components
Purchaser
MR21
Goods Receipt
without
References
Retail Pricing
Specialist
RWBE
Create a Sales
Set
Retail
Masterdata
Specialist
MM41
Process Sales
Set
Retail
Masterdata
Specialist
MM42
Goods Receipt
Without
References
Warehouse
Specialist
MIGO
Set Up
Structured
Article
Warehouse
Specialist
MB1B
Create a Display
Retail
Masterdata
Specialist
MM41
Process Display
Retail
Masterdata
Specialist
MM42
Goods Receipt
without
References
Warehouse
Specialist
MIGO
Department
Store/Shop
Concept
Retail
Masterdata
Specialist
WRFDEP01
Price Level
Groups
Retail
Masterdata
Specialist
WRF_PRG
RP01
Business
Role
Transaction
code
Retail
Masterdata
Specialist
WDSD_WB
Expected
Results
Additional scenario:
Process Step
External
Process
Reference
Business
Condition
Direct Store
Delivery
4
Expected
Results
Article Maintenance
© SAP SE
Page 6 of 8
SAP Best Practices
4.1
Item Management (711): BPD
Process Flow
Master data is the foundation for mapping processes in SAP retail.
All the basic information regarding customers, sites, vendors, articles, and so on, is contained in
the master data.
The information from the following screens can be created and maintained in the article master:

Basic data
global article data such as purchase order units, division assignment, valuation class and
characteristic values.

Listing
data on assortment layout, listing procedure, distribution chains, listing and sales periods.

Purchasing
vendor-specific data such as purchasing price, order units, purchasing group, conditions,
delivery times for each vendor.

Sales
sales-specific data for each distribution chain or site, such as sales units, purchasing dates
and sales prices.

Logistics distribution center
site-specific data for distribution centers such as planning parameters, forecast parameters,
storage data and general control parameters.

Logistics store
site-specific data for stores, such as planning parameters, replenishment parameters,
forecast parameters, general control data, storage data and accounting data.

POS
article data needed to communicate with a POS system, such as control for each distribution
chain or site, POS sales period and sales receipt text.
In the article master data, the user can map both single and structured articles (prepacks, sales
sets, generic articles with variants, displays, and so on).
By entering additional information such as article type, merchandise category, vendor or
reference article, the user already supplies the article being created with important control
information and reference values.
The article type MODE contains fashion specific information, once the screen sequence 33 is
assigned to the article type. The following sub screens (with respective fields) are new or
changed on the Basic Data screen:

Assignment to article hierarchy

Color/Size of Variant

Fashion Attributes

Textile Indicator

Care Code

Groupings

General Data

Validities

Successor/Substitute Article
For detailed information refer to the various help options (for example, SAP Help Portal, Field
help F1).
An article master record contains all the data that is required to manage an article. This data is
divided up as follows:
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD

Descriptive data such as size and weight.

Data with control functions such as article type.
Besides this data, which can be directly maintained by the user, an article master record also
contains data that the system updates automatically (for example, warehouse stocks).
However, an article master record does not only contain data that concerns the article itself, but
also contains data from other areas that are relevant to the article.
Listing is one of the most important of the other areas for article master records. In listing,
articles are assigned to a number of assortment owners. The listing process determines how the
articles are assigned and which assortment owners are defaulted by the system. The user can
define how the assignment is done.
4.2
Single Article
The single article is the standard article that is sold to the customer; it is the classic SAP article.
This article cannot be changed into a generic article and a generic article cannot be changed into
a single article.
Apart from being able to create the article manually in this Business Process Documentation,
there is also the option of creating the article automatically using the eCATT tool. For more
information on article creation and for detailed documentation on the eCATT tool, go to the
component BC-eCATT-tool in the SAP library (help  SAP library or http://help.sap.com) under
basis components.
4.2.1 Creating a Single Article (Manually)
Use
Two-level pricing is used for this article.
In supply source determination, normal purchase ordering (1) is used for the DC, and stock
transfer before normal purchase ordering (4) for the stores.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Create
Transaction code
MM41
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Create Article
2. On the Create Article( Initial Screen), make the following entries:
Field name
Description
User action and values
Article
SINGLEART1xx
Article Type
MODE (Apparel
seasonal)
HAWA(Trading Goods)
HAWA or FRIP
(Perishables)
© SAP SE
Comment
Fashion
Hardgoods
Food
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
MC11451 (Fashion)
Merchandise
Category
MC14201 (Hardgoods)
MC13202 (Food)
Article
Category
If the system
message You have
entered a different
article type…
displays, choose a
view as requested
Single article
3. On the Areas of validity section, make the following entries:
Field name
Description
User action and values
Purchasing
Org.
1000
Vendor
PCS-V111 (Fashion)
Comment
PCS-V201 (Hardgoods)
PCS-V201 (Food)
4. Choose Enter.
5. Choose the Basic Data view.
6. If Characteristic Profiles and Char. For Merchandise Category dialog box pop up, choose
one profile.
7. Choose Enter.
8. On the Create Article: Basic data screen, make the following entries:
Field name
Description
Comment
Article Description
Article
Description
Ct
User action and values
GTIN category
IE
1st Line /Column Ct
9. Choose Enter.
The system message: The GTIN will be determined internally on the basis of the
GTIN category, displays.
10. Choose Enter.
The system message: You are about to exit, displays.
11. Choose Cancel.
12. Choose the Purchasing tab.
13. On the Create Article( Purchasing) screen, make the following entries:
Field name
Description
User action and values
Purchasing
Group
100
Net Price
<Value>
Comment
14. Choose the Sales tab.
15. Choose Validity Area.
16. On the Areas of validity screen, make the following entries:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Sales Org.
1000
Distr. Chl
30
Comment
17. Choose Enter.
18. On the Create Article: Sales screen, make the following entries:
Field name
Description
User action and values
PP det. Seq.
01
SP determ.
Seq.
01
Final Price
<Value>
Save Calc.
Price
X
Comment
If you change the Final Price, the system message Sales pricing has been
performed or changed displays.
19. Choose the Logistics DC tab.
20. On the Create Article(Logistics: DC) screen, make the following entries:
Field name
Description
User action and values
RP Type
ND
Supply
source
1
Avail. Check
KP
Comment
21. Choose the Logistic: Store tab.
22. On the Create Article(Logistics: Store ) screen, make the following entries:
Field name
Description
User action and values
Rp Type
ND
Supply
source
4
Avail. Check
KP
GR Proc.
Time (In
Days)
5
Comment
23. Choose Save.
24. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
The System Message Article … Created, displays.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
4.2.2 Process the Single Article
4.2.2.1 Assortment Listing
The assortment determines whether a store, a distribution center or a customer is allowed to
receive a delivery of a certain article at a certain point in time. The assortment is used, for
example, to check purchase orders and sales orders.
An assortment is an object in SAP retail to which articles are assigned or listed.
There are three different assortment categories (key that describes possible uses of an
assortment).
 Store assortment category
 Distribution center assortment category
 Customer assignment category
An assortment module is a collection of articles that should be used together in assortments. The
assortment module is valid for a particular period. The range of the assortment is determined by
the assignment of assortment modules to it.
Assortment users (retail sites, distribution centers or customers) can be assigned to the
assortment. The total of all the articles assigned to assortments counts for the assortment owner
as being listed.
A local assortment is valid for one retail site. One or more assortments can be assigned to a
customer in each distribution chain. Each of these assignments can be given an order of rank
that can be evaluated, for example, during order processing or when assortment lists are being
created, as additional information.
The checks that are run by the listing procedure determine whether an article is to be listed in an
assortment.
Only articles that are listed in a site fulfill the prerequisites for purchasing, inventory management
and posting sales.
The main aim of listing is to create or determine the listing conditions for an article:
Assortments and distribution chains that carry the article.
Period during which the article can be delivered to the assortment user (listing period).
In addition to this function of assigning articles to sites, entries for the relevant assortments are
generated in listing for different tables (MVKE, MARC, MBEW...) – if none have already been
made this form of handling uses mass maintenance to copy data relating to the reference sites to
the newly listed sites.
Assortment modules define how articles are assigned to sites. These can be created manually
using

Standard module
A standard module is an assortment module that is used to list articles that are carried
over a long period of time and are similar (for example, branded products).

Local assortment module
A local assortment module is a special kind of standard module that is used for one store
or distribution center only and cannot be assigned to any other store or distribution
center.

Exclusion module
An exclusion module is an assortment module that cancels every listing for the article it
contains.
If an article is added to an exclusion module item, the article is not listed in any of the
assortments assigned to the exclusion module for its validity period.

Rack jobber modules
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Rack jobber modules are modules for vendors who take on the responsibility of delivering
and displaying articles in the stores themselves. A rack jobber module can only be
assigned to one vendor. A vendor can, however, access several rack jobber modules. An
article that is listed in a rack jobber module cannot be listed in any other module. As
articles that are listed in rack jobber modules are carried separately in the POS system,
you can analyze sales and revenue information specific to articles maintained in rack
jobber modules.
Or automatically using

Profile modules
Profile modules are created by automatic processes when listing is carried out. There is
exactly one profile module for each assortment and merchandise category. Profile
modules carry the assortment listings that are found automatically using rules. Profile
modules do not contain any items themselves – their items are the listing conditions.

Promotion modules
Articles to be used in a promotion can be combined in a promotion module. Several
modules can be assigned to a promotion, but these can also be assigned individually to
assortments. This way the promotion can be mapped on different time scales for different
regions.
A listing procedure determines which checks are to be run in concrete assortment
management processes.
By performing the listing you determine which sites are assigned to an article (listed). In
many situations, this is a required entry (for example, integrated material maintenance,
assortment maintenance).
SAP ships the following listing procedures:

01 standard procedure completeness check
- assignment to site merchandise categories/assortment grades
- site classification < article
- matching layout rules
- availability of sales prices

02 listing without condition

03 manual module selection

04 standard for promotions (without conditions)

05 standard for allocation table (without conditions)

06 completeness check without sales price check

07 completeness check without sales price and layout check

08 completeness check without layout check

10 automatic conversion of wrf6 changes

B1 basic procedure: merchandise category/assortment grade

B2 basic procedure: check classification

B3 basic procedure: layout check

K1 never any listing
There are three basic procedures for automatic listing:
© SAP SE
Page 6 of 8
SAP Best Practices

Item Management (711): BPD

Selection using site
and merchandise category master and assortment grade (B1)
Selection using classifying match (B2)

Layout comparison (B3)
In this documentation, only the basic procedure, B1, is used to create articles for
automatic listing in integrated article maintenance as this is the most commonly used
listing procedure? For more detailed information on this topic see the online
documentation and the scope item assortment management. This also deals in
depth with the option of multiple assignments of general assortments to sites (n:massignment) and how to configure these.
4.2.2.2 Implement Listing
Use
The following table describes how to assign the single article created in section 4.2 to all sites
using the automatic listing procedure (B1).
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change Article
2. On the Change Article ( Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
SINGLEART1xx
Article
3. Choose Listing view.
4. Choose Enter.
5. On the Change Article ( Listing ) screen, make the following entries:
Field name
Description
User action and values
Assortment
Grade
Blank
List.
Procedures
B1
Comment
Pay Attention To The
Listing Periods Of
The Different Listing
Procedures
Listing for Store
List.
Procedures
B1
Local
Assortments
Set Flag
© SAP SE
Listing for Distribution
Center
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Comment
Also
List
Supplying
Sites
Set Flag
6. Choose Execute Listing.
7. Choose Sales tab.
8. Choose Validity Area.
9. In the Areas of Validity dialog box, make the following entries:
Field name
Description
User action and values
Sales Org.
1000
Distr. Chl
10
Comment
10. Choose Enter.
11. On the Change Article: SINGLEART1XX (Sales) screen, make the following entries:
Field name
Description
User action and values
Final Price
Value
Save
Calculated
Price
X
Comment
12. Choose Save.
13. The System Message Article ... Changed, displays.
14. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.2.2.3 Displaying a Generated Assortment Module
Use
The assortment module from a site (for example, M001) is first determined from the hierarchy
display.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Assortment/Listing
 Evaluations  For Article  Tree Display of Listing
Conditions
Transaction code
WSL11
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Assortment ECC Planner
(SAP_NBPR_ASSORTMENT_RT_S)
Business role menu
© SAP SE
Master Data  Assortment Master Data  Listing
condition  Evaluation of Listing conditions
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
2. On the Evaluation of Listing Conditions screen, make the following entries:
Field name
Description
Article
User action and values
Comment
SINGLEART1xx
Article Number See
4.2.1’
3. Choose Execute.
4. Expand The Controlling Tree For M001. Note down the module number for the local
assortment M001.
5. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.2.2.4 Displaying the Profile Module for Store M001 using
Assortment Menu
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Assortment/Listing 
Assortment  Module  Assortment Assignment  Display
Transaction code
WSO7
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Assortment ECC Planner
(SAP_NBPR_ASSORTMENT_RT_S)
Business role menu
Master Data  Assortment Master Data  Assortment Module 
IS-R Astmts, Display module  store
2. On the Assortment Module assignment to Assortment: Display: Initial Screen, make the
following entries:
Field name
Description
User action and values
Module
Module number see
4.2.2.3
Select Date
'Current Date'
Comment
3. Choose Items or confirm your entry.
4. On the Assortment Module assignment to Assortment: Display: Items screen, you may check
the item details assigned in the module. You can see the number of articles assigned to this
module and by choosing from menu: (NWBC: More…) Extras  Article in module, in the
popup dialog box, you will see the articles that have been assigned to this module.
5. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3
Reference Handling In the Article Master
Due to the large volume of data in article maintenance, when creating article master records
there are templates available for reference purposes. This reduces the amount of work involved
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
in entering data, and changes to templates can immediately be transferred to the related data
records.
The functions that are used to enter reference data and to copy data in article maintenance are
described in the following as reference handling. There are numerous specific requirements from
reference handling for articles that have to be taken into consideration. The current version of
reference handling does not cover all these requirements.
4.3.1
Reference Article as Copy Template
Reference articles are used to determine default values when creating and extending article
data. All data is proposed for the reference article apart from GTINs, consumption and forecast
values and prices and conditions (for purchasing and sales).
Changes to reference articles do not affect an article that is created using a reference article. No
record is made of the reference article that was used to create an article. When extending an
article, it is also possible to use a different article as a template than the one you used when you
created the article. For example when you create purchasing info records for an existing article,
you can use another article of the vendor as a template, even if the article was created with the
merchandise category reference article.
There are two different types of reference articles:

Reference articles in the initial screen
Here you enter the reference article in the field with the same name in the initial screen.

Merchandise category reference articles
Merchandise category reference articles are used to simplify maintenance of article
master data. These are not physically available in retailing (for example, you cannot buy
them). Merchandise category reference articles only contain information that the system
proposes when you create an article master record.
You can create a merchandise category reference article for each merchandise
category.
You should assign the merchandise category reference article to the article category that
appears most frequently in the merchandise category.
If you do not specify a reference article when create an article master record, the
merchandise category reference article is always used (if available).
You cannot use both types of reference articles at the same time. A reference article
entered in the initial screen takes precedence over the merchandise category reference
article. If you have created an article master record on the basis of a reference article,
you can supplement it on the basis of the merchandise category reference article - the
reverse is also true.
4.3.2 Article Data with Client-Wide Validity
Use
In production companies, there are comparatively fewer articles and in comparison there are
also fewer sites (production sites) than in retail companies. As there is often individualized
control of industry sites, much of the article data in ERP is stored at site level. In retail, some
data is not supposed to be maintained differently for each site, or only in exceptional cases (an
example is the unit of issue for a site).
In retail article maintenance you should therefore be able to maintain some of the data that does
not differ from site to site at client level and therefore is independent of the sites in which the
article is carried. To map exceptions, you obviously need to be able to maintain this data on a
site-specific level.
Here is an extract of fields that can be maintained for an article at client level (MARA/MAW1) and
can be used for the corresponding data on a more specific organizational level
(MVKE/MBEW/etc). If this data is changed at client level, the data field is checked to see
whether the corresponding field was maintained differently on the more specific level (in other
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
words, if it had a different value before the change was made). If this is the case, the change is
not copied to this specific level, in any other case it is copied over.
Field Name
Description
Field Name
Description
MAW1-SSTUF Assortment Grade
MVKE-SSTUF
All listing data is only proposed
from if MAW1 has been
maintained for listing.
MAW1-PFLKS Assortment Priority
(External)
MVKE-PFLKS
MAW1-LSTAK Indicator To Show
That Listing Data
Has Been Created
Explicitly
MVKE-LSTAK
MAW1-LSTFL
Listing Procedure
For Stores
MVKE-LSTFL
MAW1-LSTVZ Listing Procedure
For DCs
MVKE-LSTVZ
MAW1-LDVFL Listing Period For
MAW1-LDBFL Stores
MVKE-LDVFL
MVKE-LDBFL
MAW1-LDVZL Listing Period For
MAW1-LDBZL DCs
MVKE-LDVZL
MVKE-LDBZL
MAW1-VDVFL Sales Period For
MAW1-VDBFL Stores
MVKE-VDVFL
MVKE-VDBFL
MAW1-VDVZL Sales Period For
MAW1-VDBZL DCs
MVKE-VDVZL
MVKE-VDBZL
4.3.3 Determining Organizational Levels for an Article
In contrast to the industry that maintains different data separately for an article’s organizational
levels, this procedure is not so useful for the large number of organizational levels within the
retail sector.
A quick and easy method is required for determining the organizational levels that need to be
created for an article.
These are the organizational levels that need to be taken into account:

Sites (DC/stores)

Valuation areas and valuation types (only with split valuation)

Distribution chains (sales organization and distribution channels)

Storage locations (for each site)

Warehouse numbers and storage types

Vendors and purchasing organizations
When you specify the organizational levels for which an article is to be maintained, the following
rules apply:
-
All organizational levels for which an article is to be created must be manually maintained
individually. This is done either by entering the appropriate organizational level in the initial
screen or using the button ’validity area’ in the individual views in article maintenance.
-
Organizational levels are not derived from the reference article – an exception to this is the
generic article as a reference article for variants (see below). If, however, an organizational
level is to be created for an article, the corresponding data for the same organizational level
of the reference article is used as a template.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
-
Sites and distribution chains are determined via listing. The selection of sites can be
influenced either manually or using the listing procedure. The distribution chains for which
the article is to be created are derived from the determined sites. A distribution chain is then
chosen, either when a selected site belongs to the distribution chain (T001W) or when the
site can deliver goods using the distribution chain (TVKWZ) or when the site can be supplied
via the distribution chain (KNVV).
-
Valuation areas are derived from the sites. In retail it is currently only possible to have a
valuation area that equates to the site, the result of this is a 1:1 relationship for sites and
valuation areas.
-
If a split valuation is customized (customizing) for an article and a site the default valuation
type for external procurement is created automatically. In addition to this default valuation
types for internal procurement and promotions are automatically created for reference sites.
This is done independent of the customized valuation type (mbew-bwtyp). The default
valuation types are defined in customizing for split valuation. Valuation types that are created
for a reference site (see below) are automatically created for all dependent sites if the
valuation type for the dependent site is activated and has not been maintained differently.
This means that default valuation types are automatically created for the dependent sites if
they were created in the reference site. You must determine all other valuation types
manually.
If you do not want all default valuation types to be automatically created for a site,
you should not customize split valuation for the reference site.
-
A principal storage location can be specified for each site and storage location data is then
automatically created for it. Additional storage locations (other than the main storage
location) must be specified manually. They are not determined automatically (for example,
from the reference article). Storage locations that are created for a reference site are
automatically created for all dependent sites, if the storage location is defined for the
dependent site (T001l).
-
Warehouse numbers and warehouse types must be maintained manually, they are not
defined automatically (for example, from the main storage location or from the reference
article).
-
Vendors and sales organizations must be specified manually, they are not defined
automatically (for example, from the reference article).
4.3.4 Comment on Mass Maintenance of Article Data for Same
Org. Levels
Mass maintenance of article data allows you to maintain article data for one article for all
organizational levels of the same type (for example, distribution center) in one step. This means
that there is no need to spend time maintaining article data separately on different organizational
levels.
Mass maintenance of article data is supported on the following organizational levels:

Listing data for all distribution chains.

Logistics data for all distribution centers.

Logistics data for all stores or for all stores in a specific distribution chain.

Accounting data for all distribution centers and a specific valuation type.

Accounting data for all stores or for all stores in a specific distribution chain and a
specific valuation type.

Storage location data for all distribution centers and for a specific storage location.

Storage location data for all stores or for all stores in a specific distribution chain and a
specific storage location.
© SAP SE
Page 6 of 8
SAP Best Practices

Sales data for all distribution chains.

Maintenance of POS data for all distribution chains.
Item Management (711): BPD
You rarely need to maintain purchasing data for all the vendors of an article. We recommend you
use the mass maintenance tool (it should also be used for maintaining warehouse data for all
warehouse numbers/storage types for an article in the integrated article maintenance).
An important prerequisite for article mass maintenance is to ensure the reference data is
retained and not just used for a maintenance process (for example, if logistics data is maintained
for all distribution centers).
4.3.4.1 Maintaining Logistics Data for all DCs/Stores
Use
The logistics data for an article is stored for each site (reference site).
Reference sites are introduced to maintain logistics data for all distribution centers or all stores.
Reference sites can be defined in customizing at site category level (DC/store) or at distribution
chain level (only for stores).
If logistics data is to be maintained for all DCs a reference DC must be defined. Maintaining
logistics data for the reference DC is done by not specifying a distribution center (DC is empty).
The data is then stored in the article master tables for the reference DC.
Logistics data can be maintained for all stores in the same way if a corresponding reference site
is defined. For stores, it is also possible to maintain the logistics data for all stores in a
distribution chain. In this case, you must define a reference store for this distribution chain. You
maintain logistics data for the reference store in the same way as for a distribution center, in
other words, either no information is provided for the store (store is empty) or only the
corresponding distribution chain is specified.
It is possible to define a general reference store and to only define special reference stores for
certain distribution chains (only for distribution chains to which the general reference store does
not belong). In the same way, it is possible just to define distribution chain-specific reference
stores and to work without the general reference store.
Logistics data for the reference sites is used as a template for connected sites. The reference
site to which a site belongs is defined using the site category and the distribution chain that
belong to the site. For changes to logistics data at reference site level, data is copied to all
corresponding sites, as long as they are not maintained differently there.
The following rules apply:
-
You can choose whether to define reference sites. If you do not use any reference sites,
logistics data must be maintained manually for each site. In this case no logistics data from
the reference article is used (note: in the reference article only the logistics data for
reference sites is used as a template).
-
You cannot maintain reference sites differently. You always forward your data to the
dependent sites. Therefore it is advisable to specify special reference sites that are not used
operationally.
-
A site only ever belongs to one reference site. For example, if a reference store is defined for
a distribution chain, the stores in this distribution chain belong to this reference store (not to
the general reference store).
-
Logistics data for the reference sites is always proposed by the corresponding data for the
reference article. If no data is maintained in the reference article for the reference store for a
distribution chain, the data from the general reference site is used as a template.
-
Changes to logistics data for the general reference store are not copied to the reference
stores for each distribution chain (and their corresponding stores). This means that changes
must always be maintained for each distribution chain if a reference store has been defined
for the distribution chain.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
The following section looks at mass maintenance of logistics data using the minimum lot size
field in the logistics store view as an example. The value of the minimum lot size is then updated
using mass maintenance for reference handling by leaving the store field blank in the initial
screen of transaction MM42 (change article) for all reference stores and for the client’s stores
(table MARC). The corresponding updated value is then double checked.
To perform reference handling, copy control must also be flagged in the field MARCBSTMI. You can monitor copy control by using transaction OMSR and then moving
to the detailed view for the field.
The article to be used was created in chapter 4.1.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change Article
2. On the Change Article (Initial Screen), make the following entries and choose Enter:
Field name
Description
User action and values
Comment
SINGLEART1xx
Article
3. Choose Logistics:Store view.
4. Choose Enter.
5. Choose RP/Forecast Data.
6. On the Change Article (RP/Forecast Data: Store) screen, make the following entries:
Field name
Description
Minimum Lot
Size
User action and values
Comment
Enter Any Value, For
Example, ‘88’
7. Choose Back.
8. Choose Save.
Afterwards you can check whether the value maintained at reference level was
copied to the dependent store M001.
9. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Display
Transaction code
MM43
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Master Data  Article  Article Master Data  Display Article
Business role menu
10. On the Display Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Article
SINGLEART1xx
Select View
Logistics:
Store
M001
Comment
11. Choose Enter.
12. Choose RP/Forecast Data.
The value for the minimum lot size should now have been copied using the template
(for example, 88). You can overwrite the field minimum lot size, which was
transferred from copy control in reference handling, to make specific changes for a
site. In this case an entry is written to table MABW (article management-retail
differences):
13. Choose Back.
14. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change Article
15. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Article
SINGLEART1xx
Store
M001
Comment
16. Choose Logistics: Store view.
17. Choose Enter.
18. Choose RP/Forecast Data.
19. On the Change Article: (RP/Forecast Data: Store) screen, make the following entries:
Field name
Minimum Lot
Size
Description
User action and values
Comment
Now change the value of
this field from ‘88’ to, for
example, ‘99’
20. Choose Back.
21. Choose Save.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
22. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
If the value of the minimum lot size for a site is maintained differently this change
can only be redefined again using copy control, if the change equals the value of the
reference maintenance.
You can check whether an entry is written to table MABW (article management-retail
differences) that reflects the change you made.
4.3.5 Work with Maintenance Groups
Use
A maintenance group consists of a quantity of field groups in the article master with the same
name. You can define a maintenance group as cross-application or application-specific. You can
use maintenance groups to specify the fields that can be used and displayed for the assigned
field groups in individual applications. In the processing of the core article master and in the
integrated mass maintenance, you can use maintenance groups to, for example, flexibly define
the displayed fields.
4.3.5.1 Creating a Maintenance Group
Use
You create a maintenance group in Maintenance Group Management. You create a
maintenance group for Core Master Data and one for Mass Maintenance.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Manage Maintenance Groups
Transaction code
WRFMGROUP
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Maintenance Groups  Maintenance
Group Management
2. Choose Show/Hide Tree to ensure that the group hierarchy tree is shown.
3. Choose Change Mode.
4. Choose the Cross-Application folder on the left hand side of the screen.
5. Right-click the folder, choose Create Maintenance Group from the context menu.
6. Maintain both name and description as MG f. Core Master Data.
You cannot change the internally-issued number.
7. Choose Select Field Groups.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
8. In the Field Group Selection dialog box, assign the following field groups to the maintenance
group (use key ‘Ctrl’ to select more than one group at the same time):
FG
Description
Propose
7
1: Assortment
Assignment
8
0: Variant Data
50
0: Art. Hierarchy
Nodes
51
0: Article Type
52
0: Article Category
53
0: Merchandise
Category
54
0: Base Unit of
Measure
Set indicator
55
0: Order Unit
Set indicator
92
0: Season
98
0: RTF Creation
Status
123
0: Short Text
Set indicator
140
0: Alternate UoM
Set indicator
141
0: HEAN/UPC Code
144
0: Weight of a UoM
Attributes
Set indicator
Set indicator
9. Choose Continue.
10. Choose Save.
11. Choose Change Mode.
12. Choose the Mass Maintenance - Seasonal Pr folder on the left hand side of the screen.
13. Right-click the folder, choose Create Maintenance Group from the context menu.
14. Maintain both name and description as MG for Mass Changes Basic Data.
15. Choose Select Field Groups.
16. In the Field Group Selection dialog box, assign the following field groups to the maintenance
group.
FG
Description
87
0: Price Band
Category
92
0: Season
98
0: RFT Creation
Status
99
0: RFT Mark
102
0: Fashion Grade
118
0: Purchasing Group
Propose
Attributes
17. Choose Continue.
18. Choose Save.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
19. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.5.2 Extension of a Maintenance Group by a Template
Use
You can create as many templates as you want for each maintenance group. In the template,
you enter default data for the initial screen for core article master data processing and for the
Creation Status - Retail Fashion of the core article master data. Default data for the initial screen
includes, for example, the article type, article category, merchandise category, and vendor.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Manage Maintenance Groups
Transaction code
WRFMGROUP
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Maintenance Groups  Maintenance
Group Management
2. Choose Show/Hide Tree to ensure that the group hierarchy tree is shown.
3. Select your maintenance group: MG f. Core Master Data in the hierarchy tree.
4. Choose Change Mode.
5. Create the template by clicking the Show/Hide button.
6. In the Maintain Templates section, maintain the following values for your template:
Creation
Status (CS)
Article Type (MTYP)
Purchasing
Organization
(POrg)
Vendor
Info
Record
Category
(Cat)
01
MODE
1000
PCS-V111
0
7. Choose Save.
8. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.5.3 Creating Core Master Article with Template
Use
The Core Master Article is a normal article master record that is created with ERP functions
instead of master data functions, for example, purchase order.
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
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
record with master data so that you can use it operationally as a complete article in every
application.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Process Core Master Data
Transaction code
WRFMATBODY
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Edit Article
Core Master Data
2. In the Select Maintenance Group dialog box, make the following entries:
Field name
User action and values
Comment
Maintenance
Group
Select the maintenance group
you created (MG f. Core Master
Data)
Template
The template you created
(Template 000001)
3. Choose Enter.
4. In the Maintain Article dialog box, maintain the following values during article creation apart
from the values that are defaulted by the template:
Field name
Description
User action and values
Comment
Article Type
MODE
Defaulted
Mdse Catgry
MC11451 (Fashion)
Artl Category
00
Single Article
Purchasing
Org.
1000
Defaulted
Vendor
PCS-V111 (Fashion)
Defaulted >Vendor1
Infotype
0
Defaulted
5. Confirm your entry by choosing Enter.
6. In the Maintain Article X view, choose Descriptions in the tree view.
7. Maintain the description in Germany (DE): Krawatte CMA.
8. Maintain the description in English (EN): Tie CMA.
9. Choose Enter.
10. In the Maintain Article view, choose Basic Data (Folder: Other Field Groups).
11. Define season and season year (Status is defaulted from the template).
Field name
Season
© SAP SE
Description
User action and values
Comment
0001
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
<enter the year of
next year>
Season Year
12. Choose Enter.
13. Confirm the dialog box: The season data was processed. Do you want to adjust the listing
and sales periods of the season, with Yes.
14. In the Maintain Article view, choose Article Hierarchy (Folder: Other Field Groups) and
choose a hierarchy node from (F4) Help.
Field name
Description
Hierarchy
Node
User action and values
Comment
B11252
Ties
15. Choose Save.
16. Note down the article number _______________________
17. The system message: Background processing started for article_________, displays.
18. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.5.4 Checking the Article Creation
Use
After saving the core article master data, you check whether the article was created correctly.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Display
Transaction code
MM43
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Display Article
2. On the Display Article (Initial Screen), make the following entries:
Field name
Description
Article
User action and values
Comment
Core Master Article created
in 4.3.5.3
3. Choose Basic Data view.
4. Choose Enter.
5. Check the attributes of the article.
6. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
4.3.5.5 Mass Maintenance Using Reference Sites
Use
To support grouping of sites for maintenance of logistics (tables: MARC, MAPR and PROP) and
replenishment data (table WRPL), a reference sites option has been added to reference
handling. This mass maintenance tool enables mass maintenance of fields that cannot be copied
using copy management from reference handling (customizing table T130F). For performance
reasons it is possible to buffer updates using BAPI posting.
The reference sites can be used, only for mass maintenance, at distribution chain level and at
merchandise category hierarchy/merchandise category level.
The prerequisite for this is that a reference site has already been assigned to the corresponding
sites. The reference store REFL has already been assigned here to the sites M001 – M002.
It is important that when you make an assignment or you change an existing assignment no data
is changed.
This chapter looks at the option of using copy control for logistics fields at reference site level.
When creating a new data record at article/site level the fields that have been defined and
maintained are proposed by the reference store. The first step is to create an article that is to be
explicitly excluded from the listing (synonymous with the fact that the site-specific logistics and
replenishment data (MARC, WRPL) are only available for the reference sites R100 and R110).
It is only when MARC and WRPL records are created that data records are also
proposed for the dependent sites. If these already exist no data record is copied.
Therefore neither listing conditions nor MARC and WRPL records are created for the
respective article in the following steps.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Create
Transaction code
MM41
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Create Article
2. On the Create Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Article
SINGLEART2xx
Article Type
MODE (Apparel
seasonal)
HAWA (Trading Goods)
HAWA or FRIP
(Perishables)
Merchandise
Category
© SAP SE
Comment
Fashion
Hardgoods
Food
MC11451 (Fashion)
MC14201 (Hardgoods)
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Comment
MC13202 (Food)
Article
Category
Single Article
3. Choose Basic Data view.
4. Choose Enter.
5. On the Create Article: Basic Data, make the following entries:
Field name
Description
User action and values
’Article Description’
Article
Description
Ct
Comment
GTIN category
IE
1st Line /Column Ct
6. Choose Enter.
The system message: The GTIN will be determined internally on the basis of the
GTIN category, displays.
7. Choose Enter twice.
8. Choose Yes to save your data.
9. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
In the second step, you maintain the maximum stock level for the reference site in
the article’s logistics store view.
10. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change Article
11. On the Change Article (Initial Screen), make the following entries:
Field name
Description
Article
User action and values
Comment
SINGLEART2xx
Store
12. Choose view Logistics: Store.
13. Choose Enter.
14. The System display message: You have not yet maintained the listing view. Confirm this
message with Enter.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
15. On the Change Article SINGLEART2XX (Logistics : Store) screen, make the following
entries:
Field name
Description
User action and values
Comment
Any Entry – For
Example, A
ABC indicator
16. Choose Enter.
17. The System Message: Do you want to save your data for this article first? displays.
18. Choose Yes.
19. The System Message: Article ... Changed, displays.
In the next step the ABC indicator (table MARC field MAABC) that was created for
the above article for the reference store, is proposed to a dependent store for further
processing, when you create site-specific data.
Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change Article
20. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Article
SINGLEART2xx
Store
M001
Comment
21. Choose view Logistics: Store.
22. Choose Enter.
23. System Message: You have not yet maintained the listing view, displays.
24. Choose Enter.
25. On the Change Article SINGLEART2XX (Logistics: Store) screen, make the following
entries:
Field name
ABC indicator
Description
User action and values
Comment
Value from the ref site is
proposed (copy control
from reference site)
26. Choose Enter.
27. System Message:” Do you want to save your data for this article first?” displays.
28. Choose Enter.
29. System Message: Article….Changed, displays.
30. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
You can also copy default data from the reference store to a special site using site
listing for the respective article (transaction WSP4).
4.3.5.6 Mass Maintenance Using Mass Maintenance Tool
Use
The following section shows how to maintain logistics data using the new mass maintenance
tool. The prerequisite for this is that the sites are assigned to the reference site.
We start by showing how sites are assigned to the reference site in the system.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Assortment/Listing  Mass
Maintenance  Reference Sites Management
Transaction code
REFSITE
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Site  Sites  Reference sites management
2. Expand the folder Logistics & Replenishment to the level of the reference site (REFL).
3. Double-click the reference site REFL. (the assigned sites (M001-M002) are displayed on the
bottom right-hand side of the screen and the sites still to be assigned are displayed on the
bottom left-hand side of the screen.)
4. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
In the next step there is an example of how to carry out mass maintenance using the
mass maintenance function for the ABC indicator (MARC-MAABC).
To make mass changes to this field, you need to switch off Copy field content in
transaction OMSR for the MARC-MAABC field. Then moving to the detailed view for
the field, switch on the Copy field content when you finish this procedure. (in the field
selection for mass maintenance using the mass maintenance tool only fields without
Copy field content are proposed).
5. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
© SAP SE
Logistics  Retailing  Master Data  Assortment/Listing 
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Mass Maintenance  Logistics/Replenishment Mass
Maintenance
Transaction code
MASS_MARC
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Master Data  Article  Mass Maintenance 
Logistics/Replenishment Mass Maint.
Business role menu
6. On the Logistic/Replenishment Mass Maintenance screen, make the following entries:
Field name
Description
User action and values
Comment
Article
Article From Chapter
4.3.5.5
For example,
SINGLEART2xx
Site
No Entry
7. Choose Select.
8. Double-click the reference site - a table structure for mass maintenance of logistics and
replenishment data for the article displayed in the window to the right.
9. Choose Select All.
10. Choose Mass Change.
11. On the Logistic/Replenishment screen, make the following entries:
Field name
Description
ABC indicator
User action and values
Comment
Enter a value, for
example,C
12. Choose Enter.
13. Choose Save.
14. Confirm the dialog box on parameters.
15. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
You can use this path to check changes made with the mass maintenance tool.
16. Access the transaction choosing one of the following navigation options
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data  Article 
Display
Transaction code
MM43
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Display Article
17. On the Display Article (Initial Screen), make the following entries:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Comment
Article
Article SINGLEART2xx
created in 4.3.5.5
For example,
SINGLEART2xx
Store
M001
18. Choose view Logistics: Store.
19. Choose Enter. The ABC indicator for the store should be the value maintained during mass
maintenance.
20. Choose Back.
4.3.5.7 Alternative Data Maintenance (Alternative
Organizational Levels)
Use
When you are maintaining the article master you can maintain certain data on organizational
levels. This means that, in addition to the article number, more keys appear, such as purchasing
organization, vendor, sites and distribution channel.
By maintaining the article data for each organizational level separately, alternatives (differences)
to the corresponding reference data appear. It is important here that individual maintenance at
an organizational data level is not overwritten by changes made to the reference data at a later
date. Of course, variances for certain data fields should not mean that changes to the reference
data can no longer be copied to dependent fields. For this reason, when changes are made to
reference data and existing variances, for each data field you must decide whether it has been
maintained differently or not. You should only copy the change if the field content of the variant
organizational level corresponds to the field contents of the reference data.
The site-specific article data has some characteristics that you should take into consideration:

A large amount of forecast data can be changed from the forecast. This data should not
simply be overwritten when you make changes to the template.

For site-specific data that depends on the requirements of the article in this site and on
the physical conditions in the site (for example, available storage bins) it makes no sense
to carry out mass maintenance at site category or distribution chain level.

In the standard software, you can define profiles for forecast and requirements planning
data for an article in which a specific data setting can be stored. Obviously, you must also
be able to use these profiles for articles and take them into consideration in reference
handling.
The following test case should explain the principle of data retention on different levels.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data 
Article  Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
© SAP SE
Master Data  Article  Article Master Data  Change Article
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
2. On the Change Article (Initial Screen), make the following entries:
Field name
Description
Article
User action and values
Comment
SINGLEART1xx
3. Choose view Logistics:Store.
4. Choose Enter.
5. Choose Validity Area.
6. On the Validity Areas screen, make the following entries:
Field name
Description
User action and values
Comment
M001
Store
7. Choose Enter.
8. On the Change Article (Logistics Store) screen, make the following entries:
Field name
Description
User action and values
Comment
2
Gr Proc.
Time
9. Choose Save.
10. The system message: Article…. Changed displays.
Next, you can check the article maintenance on the different data retention levels for
‘Article 1’. For this, the GR Processing Time is first displayed on the reference store
level (meaning the store field in the initial screen of transaction MM43 is left blank).
11. Choose View Logistics: Store.
12. Choose Enter.
13. Check the GR Processing Time: (5 days) field.
14. Choose Validity Area.
15. On the Validity Areas screen, make the following entries:
Field name
Store
Description
User action and values
Comment
M001
16. Choose Enter.
17. Check the GR Processing Time for store M001 field. The value should be 2.
18. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.5.8 Mass Maintenance Using the Article Monitor
Use
You can use this function to select articles for which subsequent functions have to be performed.
You use a maintenance group created for this process (see 4.3..5.1) and change Basic Data for
a selection of articles in the mass data maintenance.
Prerequisites
You have created a maintenance group for mass maintenance.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data 
Article  Article Monitor
Transaction code
WRFMATMON
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Monitor  Article Monitor
2. On the Article Monitor for Follow-On Processing screen, make the following entries:
Field name
Description
Creation
Status
User action and values
Comment
01
Status for core
articles
3. Choose Execute.
4. Select all articles by choosing Select All.
5. Choose Mass Maintenance.
6. On the Integrated Mass Change screen, choose Select Maintenance Group.
7. Select the maintenance group you have created earlier - MG for Mass Changes Basic Data.
8. Choose Continue.
9. The system message: Field catalog was changed; run a selection, displays.
10. Choose Execute Selection (F8).
11. The system message: You selected data for _____articles, displays
Make sure that the maintenance tree is shown, choose Show/Hide Tree
12. Double-click Basic Data folder.
13. Select the articles that you want to change.
14. Choose Fast Entry (a new sub-screen appears on the right hand side at the bottom of the
screen).
15. Change the creation status from ‘01’ to ‘blank’ (complete).
16. Mark the line in the Fast Entry Screen.
17. Choose Continue.
18. Mark the data record to be changed in the selection list.
19. Choose Save.
20. In the dialog box for Update parameters, choose Update Method Synchronized (2).
21. Choose Continue.
22. Choose Display Application Log to check whether the changes were made successfully.
23. Choose Execute in the Analyze Application Log screen.
24. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.5.9 Article Copy to Create a New Article
Use
You can use this function to copy article master records, to create new ones or change existing
ones. In addition to the basic article data, you can also copy other master data, such as
purchasing info records, purchase and sales conditions, bills of materials and replenishment
data.
In the following steps a new article is created.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data  Article 
Copy
Transaction code
WRFMATCOPY
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Copy Article
2. On the Copy Article screen, make the following entries:
Field name
Description
User action and values
Comment
Article
Article from 4.3.5.3 or
SINGLEART1xx
Screen area: Source
Article
Internal
Number
Assignment
Set indicator
Screen area: Target
Article
Merchandise
Category
MC11451 (Fashion) or
MC14201 (Hardgoods)
MC13202 (Food)
Article Type
MODE or HAWA
(Trading Goods) or
FRIP (Perishables)
Article
Category
00
Underlying
Article Data
Set indicator
Additional
Article Data
Set indicator
Screen area:
Processing Volume
3. Choose Segment Filters for Underlying Article Data to view the basic article data.
4. Choose Continue.
5. Choose Segment Filters for ‘Additional Article Data’ to view these.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
6. Choose Continue.
In the segment filters all segments are selected automatically and therefore are
copied from the source to the target article.
7. Choose Execute.
8. In the message overview the article number for the new article is displayed as well as the
assignment to the article hierarchy if applicable. Write down the article number.
9. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.5.10 Checking the Article Creation for the Copied Article
Use
After saving the copied article, you check whether it was created correctly.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change Article
2. On the Change Article (Initial Screen), make the following entries:
Field name
Description
Article
User action and values
Comment
Article created in 4.3.5.9
3. Choose Basic Data view.
4. Choose Enter.
5. Check the values of the new article and change the description.
6. Choose Save.
7. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.5.11 Article Discontinuation
Use
You can use this business process to exclude articles from your assortment as of a certain date,
for example, if you no longer sell certain articles or if they can no longer be delivered.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Discontinuation is particularly important in the fashion industry, whose seasonal nature means
that you have to discontinue large numbers of articles within a short period of time.
You create a worklist and use it in the discontinuation monitor. You discontinue one of the
articles you have already created.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data  Article 
Discontinue  Discontinuation Workbench
Transaction code
WRF_DIS_SEL
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Discontinuation  Seas. Proc. Article
Discontinuation
2. On the Client Wide Article Discontinuation screen, make the following entries:
Field name
Description
User action and values
Comment
Article
One of your articles
Article of your choice
Offline Check
Set indicator
Sub-screen:
Processing Type
Execute
follow-up
processing
Set indicator
Discontinue
immediately
Set indicator
Worklist
name
your own user
3. Choose Execute.
4. Confirm the dialog box for follow-up actions with Yes.
5. System message: 1 articles are being checked. The result appears in the work list, displays.
6. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
Result
The selected articles are checked, follow-up actions are carried out and the articles are marked
for deletion. The results are checked in the discontinuation monitor.
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data 
Article  Discontinue  Discontinuation Monitor
Transaction code
WRF_DIS_MON
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Discontinuation  Seas. Proc.
Discontinuation Monitor
2. Enter worklist name as, Your Worklist.
3. Choose Execute.
4. Flag the line representing your worklist.
5. Select Choose.
6. A list is displayed showing the articles with traffic lights indicating whether the
discontinuation was successful or not. In case a discontinuation could not be processed,
detailed reasons are listed. If you try to change the discontinued article a warning message
will be displayed.
7. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
4.3.5.12 Creating Article List
Use
The article list is a predefined selection of article numbers. It enables a defined set of article
numbers to be used across applications. As work is divided up across different system
landscapes, it is possible that a quantity of articles is determined in one system but has then also
to be used in other steps in another system. The integration of article lists is particularly useful
when SAP ECC is integrated with SAP BI.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Article List  Edit
Transaction code
WRF_AL
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article List  Article Lists
2. Choose Show/Hide Tree, in case the article hierarchy is not shown.
3. Choose Change Mode.
4. Select the top node in the hierarchy.
5. Choose Create Node.
6. Maintain the hierarchy node name and description, for example,: Userxx.
7. Choose Enter. (If a message appears regarding the holiday and public holiday calendars
appear, choose Yes/Enter).
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
8. Choose Create Article List, on the right hand side of the screen.
9. Maintain the description: Static article list Userxx.
10. Choose Enter.
11. Flag the list type: Static Type.
12. Choose Edit selection.
(If a message appears regarding the holiday and public holiday calendars appears, choose
Yes/Enter).
13. In the Edit Selection Parameters dialog box, choose a Hierarchy node: B11252.
14. Choose Enter.
15. Choose Results List to check the details.
16. Choose Back. Change the validity dates: Valid From: Current date; Valid to: Current date +
10 days.
17. Choose Enter. (If a message appears regarding the holiday and public holiday calendars
appeared, choose Yes/Enter).
18. Choose Back.
19. Change the list status currently Planned (1) via the F4 Help to Released (2). The status
Released can only be set by the list owner.
20. Choose Back.
21. Choose Save.
22. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
Dynamic article list: Dynamic article lists are made up of saved selection conditions
that can be used to determine the article number sets that are currently valid.
Static article list: Static article lists contain both the selection conditions and the
article numbers that corresponded to the selection conditions when the article list
was released in the system. If a static article list is created in SAP BI, for example,
the article numbers are saved in SAP ECC without the corresponding selection
condition.
4.3.5.13 Follow up and Replacement Articles
Use
This process allows you to assign one or more follow-up or replacement articles to the original
article. A follow-up article replaces an original article permanently, whereas a replacement article
only replaces it for a specific period of time.
You can make assignments on different levels using local assortments for one site, or general
assortments for a group of sites or all sites.
You can display, change, and delete existing assignments of follow-up or replacement articles
for original articles.
The follow up and replacement articles can be used in the procurement processes.
Procedure
1. Access the transaction choosing one of the following navigation options:
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data 
Article  Follow-Up/Replacement Articles  Edit
Transaction code
WRFFUART
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Follow-Up/Replacement Articles
 Maintain Succ./Subst. Article Name
2. Choose Article Selection.
3. In the Selection dialog box, maintain the following data:
Field name
Description
User action and values
Comment
Substitution
Profile
02 Replacement
Screen area:
Substitution Type
Merchandise
Category
MC11451 (Fashion)
>[MC-SA]
MC14201 (Hardgoods)
MC13202 (Food)
4. Choose Execute.
5. Select one of your single articles in the Article Selection screen (left hand side).
6. Choose Assignments.
7. Select the replacement article:
Field name
Description
Substitution
Article
User action and values
Comment
PCS-01-ART146
(Fashion)
PCS-06-ART432
(Hardgoods)
PCS-06-ART321 (Food)
Factor
1
Factor
1
Valid to
31.12.2012
Priority
01
8. Save your entries.
9. Confirm the dialog box Successor/subsitute article relationship with Yes.
10. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.6 Store Characteristic Values
Use
This process allows you to define characteristic values for a characteristic separately before
grouping and arranging these in a hierarchy. This method of managing characteristic values is
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
particularly useful for characteristics with numerous characteristic values, such as colors. The
system groups the characteristic values into clear partial quantities, to make it easier for you to
access required characteristic values.
You categorize characteristics to improve their integration into processes that work with color
and size characteristics. You can specify whether a characteristic relates to color, the main size,
or a secondary size. If you use the categorized characteristic to define variants of a generic
article, the system stores the characteristic valuation of the variant in the classification system
and at basic article data level. This improves the search for variants of a certain color or size.
If you want to use separate characteristic storage for other characteristics, you can choose a
characteristic type for characteristics that cannot be categorized.
Depending on the characteristic type you choose, you can add up to ten additional customerspecific values to provide the characteristic value with alternative value conversions.
The system only supports this form of characteristic value storage for characteristics:

from the Character Format data category

with a maximum of 18 characters/digits

whose value check is performed with a special function module
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Merchandise
Category Data  Characteristics  Characteristics
Management
Transaction code
CT04
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Master Data Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Classification  Characteristic 
Characteristics
2. Maintain the name PCS01 in the Characteristic field.
3. Choose Create.
4. Maintain the following details for the characteristic Color:
Field name
Description
User action and values
Comment
Basic data tab page
Description
Color
Data Type
CHAR
Number of
Chars
10
Values tab page
Function
WRF_CHECK_CHAR_VAL
Use pushbutton
‘Other value check’,
and then choose
Function module in
the dialog box.
5. Confirm your entries with Enter.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
6. Save your entries.
7. Create a characteristic size (children); maintain the name PCS02 in the Characteristic field.
8. Choose Create.
9. Maintain the following details for the characteristic Size:
Field name
Description
User action and values
Comment
Description
Size Children
Basic data tab
Data Type
CHAR
Number of
chars
10
Basic data tab page
Values tab page
WRF_CHECK_CHAR_VAL
Function
Use pushbutton
‘Other value check’,
and then
chooseFunction
module in the dialog
box.
10. Confirm your entries with Enter.
11. Save your entries.
12. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
13. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Merchandise
Category Data  Characteristics  Type Characteristics
Transaction code
WRFCHVALTYPE
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data Merchandise Group Data  Characteristics
 Maintain Characteristic Type Data
14. Choose New Entries.
15. Maintain the following data:
Field name
Description
User action and values
Internal char.
No.
PCS01
Characteristic
Name
PCS01
Char. Type
Color Characteristic
Check option
W Check
Characteristic
Values in Material
© SAP SE
Comment
Automatically filled on
return
Defaulted during
value maintenance
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Maint. w/Information
16. Save your entries.
17. Maintain the following data:
Field name
Description
User action and values
Internal char.
No.
PCS02
Characteristic
Name
PCS02
Char. Type
Size Characteristic
(Main Size)
Check option
W Check
Characteristic
Values in Material
Maint. w/Information
Comment
Automatically filled on
return
Defaulted during
value maintenance
18. Save your entries.
19. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
20. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Merchandise
Category Data  Characteristics  New Characteristic
Value Storage  Process Characteristic Values
Transaction code
WRFCHVAL
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Merchandise Group Data  Characteristics
 Edit Characteristic Values
21. Choose PCS01 from the value list.
22. Choose Change.
23. Maintain the following data in the Edit Characteristic Values screen:
Characteris
tic Value
Description
1
Analyzing
Color
Standard
Color Code
Panton
e
white
BLANC
1000
00001
11
snow white
BLANC
1001
00002
12
wool
BLANC
1024
00003
13
beige
BLANC
1038
00004
2
yellow
JAUNE
2000
00005
21
sunflower
JAUNE
2004
00006
22
orange
JAUNE
2200
00007
© SAP SE
Sort
(defaulted)
Page 6 of 8
SAP Best Practices
Characteris
tic Value
Description
23
Item Management (711): BPD
Sort
Analyzing
Color
Standard
Color Code
Panton
e
apricot
JAUNE
2681
00008
24
peach
JAUNE
2700
00009
3
red
ROUGE
3000
00010
31
coral
ROUGE
3010
00011
32
bordeaux
ROUGE
3011
00012
4
rose
ROUGE
3088
00013
41
dusky pink
ROUGE
3030
00014
42
mauve
ROUGE
3005
00015
43
lilac
ROUGE
3009
00016
44
green
VERT
4000
00017
45
petrol
VERT
4001
00018
46
olive
VERT
4400
00019
47
kiwi
VERT
4010
00020
5
blue
BLEU
5000
00021
51
royal blue
BLEU
5002
00022
52
blue annulate
BLEU
5004
00023
6
brown
MARRON
6000
00024
61
camel
MARRON
6001
00025
62
chocolate
MARRON
6200
00026
7
grey
GRIS
7000
00027
71
silver-greying
GRIS
7001
00028
8
black
NOIRE
8000
00029
British Size
Italian
Size
(defaulted)
24. Choose Save.
25. Choose Other characteristic.
26. Enter PCS02.
27. Choose Enter.
28. Maintain the following data in the Edit Characteristic Values screen:
Characteris
tic Value
Description
Sort
XS
XS
34
S
S
36
M
M
38
L
L
40
XL
XL
42
(defaulted)
European
Size
29. Save your entries.
30. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.6.1 Characteristic Value Grouping
Use
Grouping characteristic values simplifies the search for characteristic values when you are
creating articles. You use existing characteristic values to create a hierarchy grouping, which
enables you to divide the characteristic value total into manageable partial quantities. You can
assign a characteristic value to several groups.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Merchandise
Category Data  Characteristics  New Characteristic
Value Storage  Group Characteristic Values
Transaction code
WRFCHVALGRP
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data Merchandise Group Data  Characteristics
 Maintain Characteristic Value Group
2. In the Select the Desired Characteristic dialog box, choose the characteristic PCS01.
3. Choose Continue.
4. Choose Change Mode.
5. Choose Create Node in the context menu in the tree view.
6. Maintain the name and description, for example, Spring/Summer.
7. Confirm your entries.
8. Select the new group on the left hand side.
9. Choose Characteristic Values in the sub screen Merchandise Category Assignment (on the
right hand side).
10. Select one or more characteristic values (all of them are shown) and choose Enter.
11. Save your entries.
12. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
The characteristic has to be added to a characteristic profile, the characteristic
profile has to be assigned to a merchandise category for instance. Once these
prerequisites are fulfilled you can create a new generic article using the new
characteristic (see steps below).
4.3.6.2 Creating a Characteristic Profile with the New
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Characteristics
Use
Each merchandise category can be assigned descriptive characteristics or characteristics
profiles. A characteristic profile is used during article maintenance especially for generic articles.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master data  Merchandise
Category Data  Characteristics Profile  Create
Transaction code
CLWE
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Merchandise Groups  Characteristics
Profile  Create Characteristics Profile
2. Maintain the ID for the profile PCS01.
3. Choose Enter.
4. On the Basic data tab, maintain the description: Color/Size Children.
5. On the Char. tab, assign your characteristics: ‘PCS01’ and ‘PCS02’. For both choose in the
Relevancy Indicator as 2 (relevant for variants).
6. Save your entries.
7. The system message: Class type 026 Characteristics Profile created, displays.
8. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.3.6.3 Assigning the Characteristic Profile to a Merchandise
Category
Use
If you want to use a characteristic profile when creating articles for a specific merchandise
category, you have to assign those to be displayed during article maintenance.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master data  Merchandise
Category Data  Merchandise Category Change
Transaction code
WG22
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Master Data  Merchandise Groups  Change
merchandise categories
Business role menu
2. On the Merchandise category Change: Initial Screen, make the following entries:
Field name
Description
User action and value
Merchandise
category
MC11611
Characteristics profile
PCS01
Comments
3. Choose Assign Profile.
4. The system message: The assignment of PCS01 to MC11611 was created/changed without
value assignment, displays.
5. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.4
Generic Article
The generic article is a special form of configurable article that serves to structure the article
variants (for example, fashion article variants). In addition to variant-creating characteristics, the
generic article itself can also have non-variant-creating characteristics. If articles differ because
of their specific characteristics (for example, color, size or flavor), then the individual articles are
called variants and are grouped together under one generic article.
You can use variant-creating characteristics (for example, size, color or pattern) and/or nonvariant creating characteristics (for example, a set of fabrics), that are purely informative to
create variants in a generic article (header article). By creating variants, the administrative
header article becomes in fact an article (by means of the clearly identifiable variants). If a
generic article is entered in a purchase order item, the system immediately starts grid processing
of the individual variants.
The generic article makes the variant maintenance simpler, as you only need to create the data
that is common to all the variants once in the generic article. By differentiating between the
variants using a single characteristic / several characteristics, the common data can be specified,
created and stored centrally in the generic article.
4.4.1 Creating a Generic Article with Variants
Use
If the generic article that has been created is a seasonal article, then you should set the RP type
from ‘RP (replenishment planning) to ‘ND’ (no planning).
Two-level pricing is to be used for these articles.
In supply source determination, normal purchase orders (1) are set up to take place in the DC
while stock transfers are set up for stores to take place before normal purchase orders (4).
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
© SAP SE
Logistics  Retailing  Master Data  Article Data  Article 
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Create
Transaction code
MM41
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Create Article
2. On the Create Article: (Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
Article
GENERICARTxx
Article Type
MODE (Apparel
seasonal)
Fashion
Mdse Ctgry
MC11141 (Fashion)
>[MC-Ga]
Artl category
01
Generic article
3. Select the Basic Data view.
4. Choose Enter.
5. The message: You have entered a different article type; select the views you require,
appears.
6. Double-click one of the proposed characteristics profile(s).
7. On the Characteristic Value Assignment screen, choose Back.
8. On the Variants for gen. article screen, choose the characteristics you want from the variant
matrix.
9. Choose Next screen.
10. On the Create Article (Basic Data) screen, make the following entries:
Field name
Description
User action and values
Article
Description
’Article Description’
Alternative
Unit
PC
GTIN
Category
Comment
Screen area:
Standard Values for
entering Variants
GTINs
GTIN category
Assing
GTINs int
IE
Set the indicator
11. Choose the Variant GTINs button.
12. The system message: the GTIN will be determined internally on the basis of the GTIN
category, displays.
13. Choose Enter.
14. Choose Back.
15. Choose the Purchasing tab.
16. In the Areas of Validity dialog box, make the following entries:
Field name
© SAP SE
Description
User action and values
Comment
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Purchasing
Org.
1000
Vendor
PCS-V112 (Fashion)
>Vendor 2
17. Choose Enter.
18. On the Create Article (Purchasing) screen, make the following entries:
Field name
Description
User action and values
Pur. Group
100
Net Price
<Value>
Comment
19. Choose the Sales tab.
20. Choose Validity Area.
21. In the Areas of Validity dialog box, make the following entries:
Field name
Description
User action and values
Sales Org.
1000
Distr.
Channel
30
Comment
22. Choose Enter.
23. On the Create Article: (Sales) screen, make the following entries:
Field name
Description
User action and values
PP Det Seq.
01
SP Determ.
Seq.
01
Final Price
<Value>
Save
Calculated
Price
X
Comment
24. Choose the Logistics: DC tab.
25. On the Create Article (Logistics: Distribution Center) screen, make the following entries:
Field name
Description
User action and values
RP Type
ND
Supply
Source
1
Avail. Check
KP
Comment
26. Choose the Logistics: Store tab.
27. On the Create Article (Logistics Store) screen, make the following entries:
Field name
Description
User action and values
RP Type
ND
Supply
Source
4
Avail. Check
KP
Comment
28. Choose Save.
29. The system message: The Generic Article ……. Will Be Created With Its Variants, displays.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
30. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.4.2 Process the Generic Article
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change
Article
2. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
GENERICARTxx
Article
3. Choose the Listing view.
4. Choose Enter.
5. On the Change Article (Listing) screen, make the following entries:
Field name
Description
User action and values
Comment
Assortment
Grade
Blank (Maximum
Assortment)
List.
Procedures
For Store
Listing
B1
Check the listing
period for the listing
processes
Listing
Procedures
for Distr.
Centers
B1
Check the listing
period for the listing
processes
Local
Assortments
Also
Set Flag
List
Supplying
Site
Set Flag
6. Choose Execute Listing.
7. Choose the Sales tab.
8. Choose Validity Area.
9. In the Areas of Validity dialog box, make the following entries:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Sales Org.
1000
Distr.
Channel
10
Comment
10. Choose Enter.
11. On the Change Article: Sales screen, make the following entries:
Field name
Description
User action and values
Final Price
<Value>
Save
Calculated
Price
X
Comment
12. Choose Save.
13. The System Message: The Generic Article....Will Be Changed With Its Variants, displays.
14. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
The Sales Price Calculation is described In more detail In the Pricing Process.
4.4.3 Reference Handling For Generic Article Variants
Use
The generic article is always used as a maintenance article for the variants belonging to it. In
contrast to other reference articles, all changes to the generic article are automatically carried
over to the variants. This way, the data is copied to all the variants and the same distribution
chain, as long as they have not been maintained separately from the generic article. You can
use mass maintenance for all the article master data, including the EANs (European article
numbers), consumption value and forecast value that have to be maintained for each variant.
The changes to the generic article are always copied over to the corresponding organizational
levels of the variants. An example of this would be a change to the listing data of a distribution
chain for the generic article where the change is copied to all the variants for the same
distribution chain. Even with changes to reference data for an organizational level (for example,
logistics data for a reference site), the change is still carried over to the reference for the variants
and then to all the variants.
If a generic article variant has certain article data that is different, it still has to be possible to
carry these changes through from the header article to the variants. If differences already exist,
you must decide for each data field whether it needs to be maintained separately. The change
may only be copied if the field content of the variant corresponds to the field content of the
header article before the change.
There are two main scope items for changes to generic articles:
1. No changes to reference data in the generic article (for example, the warehouse
management system data for the generic article is changed for a specific warehouse
number). Changes are copied to the warehouse management data of all variants with the
same warehouse number.
2. Changes to reference data for the generic article (for example, change to listing data for the
generic article for the reference distribution chain). Changes are copied to the listing data for
each distribution chain for the generic article, to listing data for the reference distribution
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
chain for each variant and to listing data for each distribution chain for all variants (two-step
change).
If purchasing info records or prices have been maintained separately for the generic
article variants, changes to the generic article data are not copied to the variants.
The variants have different data in this case means that there is a variance, even if
the data itself is no different from that in the generic article.
The following section looks at passing on a field change in the header article of a
generic article to the variants. A field in the basic data view is first checked and this
is then changed at header level. The change is then verified in the variant.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Display
Transaction code
MM43
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Display Article
2. On the Display Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
GENERICARTxx001
Article
3. Choose Basic Data view.
4. Choose Enter.
5. Check the entry for the transportation group 0001 in the area of the Internal logistics data.
6. Choose Back.
7. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
8. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
© SAP SE
Master Data  Article  Article Master Data  Change
Article
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
9. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
GENERICARTxx
Article
10. Choose view Basic Data.
11. Choose Enter.
12. On the Change Article: Basic Data screen, make the following entries:
Field name
Description
User action and values
Comment
0003
(Container)
Transport ation Group
13. Choose Save.
14. The system message: The generic article ……. will be changed with it variants, displays.
15. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP
Home (SAP NetWeaver Business Client).
16. Now display the article data for the variant again.
17. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Display
Transaction code
MM43
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Display
Article
18. On the Display Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
GENERICARTxx001
Article
19. Choose Basic Data view.
20. Check the entry for the Transportation Group in the area of the Internal logistics data.
21. Choose Enter.
22. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
For more detailed documentation on the topic of reference handling, see the SAP
library under http://help.sap.com and also the customizing guide for this topic.
4.4.4 Matrix Maintenance for Generic Articles
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Use
The variant processing has been noticeably improved and simplified. Besides the price matrix for
generic article variants for purchasing and sales price processing, variant processing was also
developed for most fields in the article master.
4.4.4.1 Price Matrix for Variants of Generic Articles
Use
The price matrix for variants is constructed in the same way as the variant matrix for defining
individual variant attributes. The system displays the prices for all existing variants in the matrix.
When doing this you must be aware that you may only process one validity period. To create a
new variant you can move to the basic data screen and define a new variant in the existing
variant matrix.
Using the price profile in the basic data for the generic article you can specify whether all the
variants that belong to it should have the same sales price or whether different prices can be
specified for the individual variants. You can also use a variant as a price article for which the
value can be calculated as the total of the prices of all other variants.
You cannot define individual prices for variants that get their sales price from the generic article
or from a variant used as a price article. No entries can be made in the price matrix in price fields
for variants like this. This allows you to see quickly which variants you can maintain and which
you cannot.
A copy rule is used in matrix maintenance that makes it easier to maintain prices of variants. The
copying rule simplifies maintenance by allowing you to:

Copy changes to next nodes in the column

Copy changes to next nodes (columns/rows)

Copy changes to next nodes in the row

Copy changes to next nodes (rows/columns)

Delete changes and adopt old prices

Cancel the last changes step by step
In the following steps an example for the maintenance matrix in the sales view for the article
(created in 4.4.1) is shown. Note that the pricing profile for the generic article is set to variants
calculated differently, generic articles not proposed as price articles (input field pricing profile in
the basic data view is set to blank).
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change
Article
2. On the Change Article (Initial Screen), make the following entries:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Article
GENERICARTxx
Sales Org.
1000
Distribution
Channel
10
Comment
3. Choose views Basic Data and Sales.
4. Choose Enter.
5. On the Basic Data view set pricing profile to ‘blank’.
6. Choose Enter.
7. The System Message: Maintain The Sales Price For The Variants, displays.
8. Choose Enter.
9. Choose Variant Prices on Sales view.
10. On the Change Article (Sales) screen, make the following entries:
Field name
Description
User action and values
Change The
Sales Price
1st Row/2nd
Column
Any Entry
Save sales
pr. conds
X
Comment
Screen area: Generic
Article Default Values
11. In the Generic Article Default Values screen area, set the Copy Rules as Copy changes to
subsequent nodes in the column.
12. Choose Use Rule.
13. Choose Back.
14. Choose Save.
15. Confirm any request for coverage of validity periods using Enter.
16. The system message: the generic article...will be changed with its variants, displays.
17. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Display
Transaction code
MM43
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Display Article
18. On the Display Article: Initial screen, make the following entries:
Field name
Description
User action and values
Article
GENERICARTxx002
Sales Org.
1000
Distribution
10
© SAP SE
Comment
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Comment
Channel
19. Choose views Basic Data and Sales.
20. Choose Enter.
21. In Sales tab, Current Price screen area, check Curr.FinalPrc has been changed to new one.
22. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.4.4.2 Matrix Handling for Master Data Fields for the Generic
Article
Use
In addition to the option of changing or editing prices at variant level using a matrix entry, matrix
handling for the generic article can also be used for any master data fields in the article master.
In the following table the field transport group in the basic data view for the article created in
4.4.1 can be changed as you wish at variant level.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change
Article
2. On the Change Article (Initial Screen), make the following entries:
Field name
Description
Article
User action and values
Comment
GENERICARTxx
3. Select Basic Data view.
4. Choose Enter.
5. Double-click the field Transportation Group.
6. The system message: Changes to field trans.group lead to different areas of validity,
displays.
7. Change the transportation group field at variant level (value help using button F4).
8. Choose Back.
9. Choose Save.
10. The system message: The generic article...will be changed with its variants, displays.
11. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
12. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Display
Transaction code
MM43
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Manager
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Display
Article
13. On the DisplayArticle (Initial Screen), make the following entries:
Field name
Description
Article
User action and values
Comment
GENERICARTxx00x
The variant you
changed in step 7.
14. Select view Basic Data.
15. Choose Enter.
16. Check if the Transportation Group field has been changed to new one.
17. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.5
Prepack
A prepack is a quantity of variants from one or more generic articles. The prepack is purchased
as an independent article, and therefore has its own article number, purchasing price and
purchasing conditions. Unlike a display, the components of a prepack must come from the same
merchandise category as the prepack itself. A prepack can be put together either by the retailer,
the manufacturer or the vendor. Prepacks are most frequently seen in the textile industry (for
example, tennis socks assortment).
In the wholesale trade, prepacks are used in both purchasing and sales. In retail, only the
components are sold. For this reason, physical inventory is carried out at prepack level in the
distribution center, but at component level in the stores.
4.5.1 Creating A Prepack
Use
The header article and the corresponding components are displayed and assigned to each other
using a bill of materials structure. Not only the components themselves, but also the quantities
have to be specified. The listing view does not have to be maintained in the component itself, but
all the other views do. For this reason, a generic article should be created for the prepack (see
section 4.4).
When creating a prepack article, it is important that the prepack header article and the generic
article, whose variants form the components of the prepack, belong to the same merchandise
category.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
In supply source determination, normal purchase orders (1) are used for the DC, and stock
transfers before normal purchase orders (4) are customized for the stores.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Create
Transaction code
MM41
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Create
Article
2. On the Create Article (Initial Screen), make the following entries and choose Enter:
Field name
Description
User action and values
Article
PREPACKARTxx
Article Type
MODE (Apparel
seasonal)
HAWA (Trading Goods)
HAWA or FRIP (Foods
excl. Perishables)
MC11141 (Fashion)
Material
Group
Comment
Fashion
Hardgoods
Food
‘MC-GA’
MC14402 (Hardgoods)
MC12003 (Food)
Prepack
Artl. Category
3. Select view Basic Data.
4. Choose Enter.
5. The system message: The reference article has a different article type, displays.
6. Choose Continue.
7. The characteristics profile is suggested based on the merchandise category.
8. Choose the Characteristic Profile you need and choose Continue.
9. On the Create Article (Basic Data) screen, make the following entries:
Field name
Description
User action and values
Comment
Article Description
Description
10. Choose Components (you need to scroll down to the end of the screen to see the button).
11. On the Create Component Assignment for Prepack Article screen, make the following
entries:
Field name
© SAP SE
Description
User action and values
Comment
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
PCS-01-Art111
(Fashion)
Gen. Article
> Article 1
PCS-02-LKP111
(Hardgoods)
PCS-01-ART201 (Food)
Quantity
Specified
Total
(used for matching of
Component Quantity)
12. Choose Enter.
13. On the Create Component Assignment for Prepack Article screen, make the following
entries:
Field name
Description
Quantity
User action and values
Comment
Quantity
Maintain a quantity
for every component
14. Choose Enter.
15. Choose Back.
16. Choose the Purchasing tab.
17. In the Areas of Validity dialog box, make the following entries:
Field name
Description
User action and values
Purchasing
Org.
1000
Vendor
PCS-V112 (Fashion)
Comment
>Vendor2
PCS-V202 (Hardgoods)
PCS-V202 (Food)
18. Choose Enter.
19. On the Create Article (Purchasing) screen, make the following entries:
Field name
Description
User action and values
Purchasing
Group
100
Net Price
Value
Comment
20. Choose the Sales tab.
21. Choose Validity Area.
22. In the Areas of Validity dialog box, make the following entries:
Field name
Description
User action and values
Sales Org.
1000
Distr.Channel
30
Comment
23. Choose Enter.
24. On Create Article Sales screen, make the following entries:
Field name
Description
User action and values
PP Det. Seq.
01
SP Determ.
Seq.
01
© SAP SE
Comment
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Final Price
<Value>
Save
Calculated
Price
X
25. Choose the Logistics: DC tab.
26. On the Create Article (Logistics DC) screen, make the following entries:
Field name
Description
User action and values
RP Type
ND
Supply
source
1
Avail. Check
KP
Comment
27. Choose the Logistics: Store tab.
28. On the Create Article (Logistics Store) screen, make the following entries:
Field name
Description
User action and values
RP Type
ND
Supply
source
4
Avail. Check
KP
Comment
29. Choose Save.
30. The message: Article Created, displays.
31. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.5.2 Processing the Prepack
Use
When listing a prepack only the header article is listed, the components are not listed.
As a goods receipt has to be posted for the prepack in this process (see section
4.5.4), the prepack components (all generic article variants) must have a valuation
price. As the valuation price can only be created for articles that are already listed,
the listing conditions for the generic article and its variants must already be
maintained in the system.
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data  Article 
Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Business role menu
Master Data  Article  Article Master Data  Change Article
2. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
PREPACKARTXX
Article
3. Choose Listing view.
4. Choose Enter.
5. On the Change article: Listing screen, make the following entries:
Field name
Description
User action and values
Assortment
Grade
Blank
LP For
Stores
B1
LP For Distr.
Centers
B1
Local
Assortments
Also
Set Flag
List
Supplying
Site
Set Flag
Comment
6. Choose Execute Listing.
7. Choose the Sales tab.
8. Choose Validity Area.
9. On the Areas of validity screen, make the following entries:
Field name
Description
User action and values
Sales Org.
1000
Distr.
Channel
10
Comment
Store Sales
10. Choose Enter.
11. On the Change Article (Sales) screen, make the following entries:
Field name
Description
User action and values
Final Price
<Value>
Save
Calculated
Price
X
Comment
12. Choose Save.
13. If popup “Errors as a Result of Overlapping Validity Period” appears, click Enter.
14. The system message: Sales pricing has been performed or changed, displays.
15. The system message: The article... Changed with its variants, displays.
The sales price calculation is described in more detail in the pricing process.
16. Access the transaction choosing one of the following navigation options:
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Assortment/Listing
 Evaluations  For Article  Listing Conditions
Transaction code
WSL1
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Non-Seasonal Buyer
(SAP_NBPR_NONSEASBUYER_RT_S)
Business role menu
Purchasing  Non -Seasonal Purchase Management 
Assortments  Assortments, selection lists
17. On the Listing Conditions screen, make the following entries:
Field name
Description
User action and values
Article
PREPACKARTXX
Display
Variants/Com
ponents
X
Comment
18. Choose Execute.
Since the prepack article is dealt with like a single article no components are
displayed.
4.5.3 Determining Valuation Prices for Prepack Components
Use
If no valuation price has been created for the prepack components (generic article variants), it
has to be created here, as valuation prices are checked in prepack goods receipts.
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Pricing  Environment
Value Assignment  Price determination  Change Price
Transaction code
MR21
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Pricing Manager
(SAP_NBPR_PRICING_RT_S)
Business role menu
Master Data  Pricing  Report  Price Change
2. On the Price Change - Overview Screen, make the following entries:
Field name
Description
User action and values
Company
Code
1000
Site
M001
Comment
3. Choose Enter.
4. On the Price Change - Overview Screen, make the following entries:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Article
Article1
Article1
Article1
Article1
Article1
Article1
Article1
Article1
-001
-002
-003
-004
-005
-006
-007
-008
New Price
30 Each Article
Comment
Enter the article
numbers of the
variants that is, the
number of the generic
article ( see <article
1> in 4.5.1) with the 3
digit suffix
5. Choose Enter.
6. Choose Save.
7. The system message: price change document……..posted, displays. If no other changes
have been made, the change document is created.
8. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.5.4 Goods Receipt without References
Use
The prepack particularity is displayed with a goods receipt in the store.
In customizing it is configured that the prepack is automatically transferred to its components
with the goods receipt in the store. So the article moves through the distribution center as a
complete prepack until it is received by the store. Alternatively you could configure the transfer
posting to happen in the DC already.
In the process described below, you post a goods receipt without any reference for the prepack
article.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Merchandise Logistics  Logistics
Execution  Inbound Process  Goods Receipt for Purchase
Order, Order, Other Transactions  Enter Goods Receipt for
Purchase Order
Transaction code
MIGO
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management  Consumption and Transfers 
Other Goods Movement
2. On the initial screen, make the following entries:
Field name
© SAP SE
Description
User action and values
Comment
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Business
Transaction
A01 – Goods
Receipt
Select A01 – Goods Receipt
from the 1st Drop-Down
Menu
Business
Transaction
R10 – Other
Select R10 – Other from the
2nd Drop-Down Menu
501
501 – Receipt without
purchase order into
unrestricted-use stock
Movement Type
3. Choose Enter.
4. On the Goods Receipt Other screen, Article tab, make the following entry and choose Enter:
Field name
Description
User action and values
Comment
PREPACKARTXX
Article
5. On the Goods Receipt Other screen, Quantity tab, make the following entry and choose
Enter:
Field name
Description
User action and values
Comment
10
Qty in Unit of
Entry
6. On the Goods Receipt Other screen, Where tab, make the following entries and choose
Enter:
Field name
Comment
User action and values
Site
M001
Storage Location
1000
Comment
7. Choose Enter.
8. Save your entries.
9. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
Afterwards, check the resulting article document:
10. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Merchandise Logisics  Inventory
Management  Article Document  Display
Transaction code
MB03
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Warehouse Manager
(SAP_NBPR_WAREHOUSE_RT_S)
Business role menu
Warehouse Management  Article documents  Display
Article Document
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
11. Choose F4 to open the selection screen and enter your prepack article PREPACKARTXX
12. Choose Execute
13. Choose the latest article document for your prepack article by doubleclicking the line
14. Choose Enter.
The article document shows the stock posting with movement type 501 and then the
automatic transfer posting of the prepack into its components with movement type
319 ‚Split structured material’.
4.6
Sales Set
Use
A sales set is a quantity of single articles or variants of one or more generic articles that can also
be sold as separate articles. As separate articles, they have their own article number, sales price
and a sales price condition. Inventory management is carried out at individual component level
or grouped together with the header article on header article level. Sales sets are used to boost
sales. The components can belong to different merchandise categories and can have different
tax rates. Only one tax rate can be assigned to the sales set.
4.6.1 Creating a Sales Set
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data  Article
 Create
Transaction code
MM41
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Create Article
2. On the Create Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Article
SALESSETxx
Article Type
MODE (Apparel
seasonal)
HAWA (Trading Goods)
HAWA or FRIP (Foods
excl. Perishables
Material
Group
MC11152 (Fashion)
Comment
Fashion
Hardgoods
Food
>MC-Vk-Set
MC14203 (Hardgoods)
MC12003 (Food)
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Comment
Sales Set
Article
Category
3. Choose Basic Data view.
4. Choose Enter.
5. Choose Continue when the dialog box for the assignment of a characteristic profile appears.
6. The message: The reference article has a different article type, displays.
7. On the Create Article (Basic Data) screen, make the following entries:
Field name
Description
User action and values
Comment
Article Description
Article
Description
8. Choose Components.
9. On the Create Component Assignment for Set Article screen, make the following entries:
Field name
Description
User action and values
Component
Component 1
PCS-01-ART146
(Fashion)
Comment
PCS-06-ART432
(Hardgoods)
PCS-06-ART321 (Food)
Component
qty
Quantity for
component 1
Quantity
Component
Component 2
PCS-01-ART111001
(Fashion)
PCS-01-ART204
(Hardgoods)
PCS-01-ART201001
(Food)
Component
qty
Quantity for
component 2
Quantity
10. Choose Enter.
11. Choose Back.
12. Choose Save.
13. The message: Article……Created, displays.
14. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.6.2 Processing a Sales Set
Use
Maintaining sales sets, logistics views (DC and stores), POS views and listing views.
Procedure
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Article Data  Article 
Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change Article
2. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Article
SALESSETxx
Sales Org.
1000
Distr.
Channel
30
Distr. Center
Blank
Store
Blank
Comment
3. Choose the Sales, Logistics: DC, Logistics: Stores, POS view.
4. Choose Enter.
5. Choose Enter to confirm the system message: You have not yet maintained the Listing view.
6. On the Change Article (Sales) screen, make the following entries:
Field name
Description
User action and values
PP Det. Seq.
02
SP Determ.
Seq.
01
Final Price
<Enter the Value>
Comment
Choose ENTER
Or Let The System
Determine The Value From
The Planned Markup
X
Save
Calculated
Price
7. Choose Enter.
8. Choose the Logistics: DC tab.
Field name
Description
User action and values
RPType
ND
Supply
Source
1
Avail. Check
KP
Comment
9. Choose the Logistics: Store tab.
Field name
© SAP SE
Description
User action and values
Comment
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
RP Type
ND
Supply
Source
4
Avail. Check
KP
10. Choose Enter. (If you receive a warning message regarding changing the source supply,
choose Enter again.)
11. The POS view is displayed in change mode.
12. Choose Save.
13. The message: Article changed, displays.
14. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
Only the header article is used in the listing for a sales set. The components are
already listed as they can also be sold as separate articles (in contrast to the
prepack components).
15. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change
Article
16. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
SALESSETxx
Article
17. Choose the Listing view.
18. On the Change Article: Listing screen, make the following entries:
Field name
Description
User action and values
Assortment
Grade
Blank (Maximum
Assortment)
Lp For Stores
B1
Lp For Distr.
Centers
B1
Local
Assortments
Also
Set Flag
List
Set Flag
© SAP SE
Comment
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Comment
Supplying
Site
19. Choose Execute Listing.
20. Choose the Sales tab.
21. Choose Validity Area.
22. On the Areas Of Validity screen, make the following entries:
Field name
Description
User action and values
Sales Org.
1000
Distr.
Channel
10
Comment
23. Choose Enter.
24. On the Change Article (Sales) screen, make the following entries:
Field name
Description
User action and values
Comment
R100
Vendor
<Enter the Value>
Final Price
Or Determine From
The Planned Markup
Save
Calculated
Price
X
25. Choose Save.
26. The message: Article ….. Changed, displays.
27. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
The sales price calculation is described in more detail in the pricing process.
Now check whether the header article and all the components are listed for the
structured article.
28. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Master Data  Assortment/Listing
 Evaluations  For Article  Listing Conditions
Transaction code
WSL1
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
(Retail Non-Seasonal Buyer)
(SAP_NBPR_NONSEASBUYER_RT_S)
Business role menu
Purchasing  Non -Seasonal Purchase Management 
Assortments  Assortments, selection lists
29. On the Listing Conditions screen, make the following entries:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Article
SALESSETxx
Display
Variants/Com
ponents
X
Comment
30. Choose Execute.
31. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.6.3 Goods Receipt without References
Use
To clarify the difference between the sales set and the individual components, post the goods
receipt (GR) to the individual components and then create your sales set.
In the process described below you post a GR without any reference for the components.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Merchandise Logistics  Logistics
Execution  Inbound Process  Goods Receipt for
Purchase Order, Order, Other Transactions  Enter Goods
Receipt for Purchase Order
Transaction code
MIGO
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management  Consumption and Transfers 
Other Goods Movement
2. On the initial screen, make the following entries:
Field name
User action and values
Comment
Business
Transaction
A01 – Goods
Receipt
Select A01 – Goods Receipt
from the 1st Drop-Down
Menu
Business
Transaction
R10 – Other
Select R10 – Other from the
2nd Drop-Down Menu
501
501 – Receipt without
purchase order into
unrestricted-use stock
Movement Type
Description
3. Choose Enter.
4. On the Goods Receipt Other screen, Article tab, make the following entry and choose Enter:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
Article
User action and values
Comment
PCS-01-ART146
(Fashion)
Enter the shelf life expiration
date for Food
PCS-06-ART432
(Hardgoods)
PCS-06-ART321
(Food)
5. On the Goods Receipt Other screen, Quantity tab, make the following entry and choose
Enter:
Field name
Description
Qty in Unit of
Entry
User action and values
Comment
1000
6. On the Goods Receipt Other screen, Where tab, make the following entries and choose
Enter:
Field name
Comment
User action and values
Site
M001
Storage Location
1000
Comment
7. Choose Enter.
8. Save your entries.
9. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.6.4 Setting up Structured Article
Use
To finally create the sales set, you must transfer the individual components. You need to do this
transfer manually as not necessarily every item in a component/article has to be sold as part of a
sales set. They can also be sold individually.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Merchandise Logistics  Inventory
Management  Goods Movement  Transfer Posting
Transaction code
MB1B
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Warehouse Manager
(SAP_NBPR_WAREHOUSE_RT_S)
Business role menu
Warehouse Management  Warehouse Controlling 
Transfer Posting
2. On the Enter Transfer Posting: Initial Screen, make the following entries:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Comment
Movement
Type
317
Creation of a
structured article
Site
M001
Storage
Location
1000
3. Choose Enter.
4. On the Enter Transfer Posting: New Items screen, make the following entries:
Field name
Description
User action and values
Article
SALESSETxx
Quantity
Quantity
UnE
PC
Comment
5. Choose Enter.
6. Choose Post (Save).
7. The message: Document…Posted, displays.
8. Access The Transaction Choosing One Of The Following Navigation Options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Merchandise Logisics  Logistics
Execution  Inbound Process  Goods Receipt for
Purchase Order, Order, Other Transactions  Display
Article Document
Transaction code
MB03
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Warehouse Manager
(SAP_NBPR_WAREHOUSE_RT_S)
Business role menu
Warehouse Management  Article documents  Display
Article Document
9. On the Display Article Document : Initial Screen, enter the material document number.
10. Choose Enter.
The articles that have been transferred are displayed with the relevant transaction
types.
Now you can check the new stock of individual components and the sales set.
11. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Merchandise Logistics  Inventory
Management  Environment  Stock  Stock Overview
Transaction code
RWBE
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Pricing Specialist
(SAP_NBPR_PRICING_RT_S)
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Business role menu
Master Data  Pricing  Report  Stock Overview
12. On the Stock Overview screen, make the following entries:
Field name
Description
Article
(Delete Any
Other
Restrictions)
User action and values
Comment
SALESSETxx
PCS-01-ART146
(Fashion)
PCS-06-ART432
(Hardgoods)
PCS-06-ART321 (Food)
PCS-01-ART111001
(Fashion)
PCS-01-ART204
(Hardgoods)
PCS-01-Art201001
(Food)
13. Choose Enter.
14. Choose Execute.
15. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.7
Display
A display is a quantity of single articles or variants of one or more generic articles that are put
together by the manufacturer. Examples of this include a display of socks or underwear in
various colors, or a display of pantyhose (for simplicity’s sake we are going to create a display
with a t-shirt as a component in this display). The display is dealt with as a single article in the
distribution center; only when it enters the store does it become a display (see customizing
guide: customizing settings). For this reason, physical inventory is carried out at display article
level in the distribution center, but at single component level in the stores. A display is purchased
as a single article and therefore has its own article number, purchasing price and purchasing
price conditions.
4.7.1 Creating Display
Use
The header article and the corresponding components are displayed and assigned to each other
using a bill of materials structure. You not only specify the components themselves, but also the
quantities.
The customizing settings have been defaulted so that the display is automatically transferred to
its components when the GR is posted for a store.
In supply source determination, the external supply source (normal, 1) is set for the DC, and the
internal before the external supply source (stock transfer before normal, 4) is set for the stores.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
SAP ECC menu
Logistics  Retailing  Master Data  Article Data
Article  Create
Transaction code
MM41
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Create
Article
2. On the Create Article: Initial Screen, make the following entries:
Field name
Description
User action and values
Article
DISPLAYxx
Article Type
MODE (Apparel
seasonal)
HAWA (Trading Goods)
HAWA or FRIP (Foods
excl. Perishables
Mdse Catgry
Merchandise category
Comment
Fashion
Hardgoods
Food
MC11152 (Fashion)
MC14402 (Hardgoods)
MC12003 (Food)
Display
Artl Category
3. Choose the Basic Data view.
4. Choose Enter.
5. In the Characteristic Profiles and Char. For Merchandise Category dialog box, choose any
characteristics profile, and choose.
6. On the Create Article (Basic Data) screen, make the following entries:
Field name
Description
User action and values
Comment
Article Description
Article
Description
7. Choose Components.
8. On the Create Component Assignment for Display Article screen, make the following entries:
Field name
Description
User action and values
Component
Component 1
PCS-01-ART146
(Fashion)
Comment
PCS-06-ART431
(Hardgoods)
PCS-01-ART331 (Food)
Component
Qty
Quantity for
Component 1
Quantity
Component
Component 2
PCS-01-ART147
(Fashion)
PCS-06-ART433
(Hardgoods)
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
Comment
PCS-01-ART322 (Food)
Component
Qty
Quantity for
Component 2
Quantity
Component
Component 3
PCS-01-ART148
(Fashion)
PCS-06-ART434
(Hardgoods)
PCS-01-ART323 (Food)
Component
Qty
Quantity
Quantity for
Component 3
9. Choose Enter.
10. Choose Back.
11. On the Create Article (Basic Data) screen, make the following entries:
Field name
Description
User action and values
Comment
Ct
GTIN category
IE
Screen Module Units
Of
Measure/Ean/Dimens
ions 1st Row, Column
Ct
12. Choose Enter.
The System Message: The GTIN will be determined internally on the basis of the
GTIN category, displays.
13. Choose Enter.
14. In the “You are about to exit” dialog box, choose Yes.
15. The message: Article XXXX created, displays.
16. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.7.2 Process Display
Use
Maintain the Purchasing, Sales, Logistics, POS and Listing views.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change
Article
2. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Article
DISPLAYxx
Purch. Org.
1000
Vendor
PCS-V111 (Fashion)
Comment
>Vendor1
PCS-V201 (Hardgoods)
PCS-V201 (Food)
Sales Org.
1000
Distr.
Channel.
30
Distr. Center
Blank
Store
Blank
3. Choose the Purchasing, Sales, Logistics: DC, Logistics: Stores view.
4. Choose Enter.
The system message: You have not yet maintained the listing view, displays.
5. Choose Enter.
6. On the Change Article (Purchasing) screen, make the following entries:
Field name
Description
User action and values
Purchasing
Group
100
Net Price
<Value>
Comment
7. Choose Enter.
8. On the Change Article (Sales) screen, make the following entries:
Field name
Description
User action and values
PP Det. Seq.
01
SP Determ.
Seq.
01
Final Price
<Enter the Value>
Comment
Or Choose The Calculated
Value Based On The Mc
Markup
Save
Calculated
Price
X
9. Choose Enter.
10. On the Change Article: Logistics DC screen, make the following entries:
© SAP SE
Page 6 of 8
SAP Best Practices
Field name
Item Management (711): BPD
Description
User action and values
RP Type
ND
Supply
Source
1
Avail. Check
KP
Comment
11. Choose Enter.
12. On the Change Article (Logistics Store) screen, make the following entries:
Field name
Description
User action and values
RP Type
ND
Supply
Source
4
Avail. Check
KP
Comment
13. Choose Enter.
14. Choose Save.
The system message: Article…changed, displays. Only the header article is used in
the listing for a display. The components are already listed, as they can also be sold
as separate articles
15. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Article Data 
Article  Change
Transaction code
MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Article  Article Master Data  Change
Article
16. On the Change Article (Initial Screen), make the following entries:
Field name
Description
User action and values
Comment
DISPLAYxx
Article
17. Choose the Listing view.
18. Choose Enter.
19. On the Change Article (Listing) screen, make the following entries:
Field name
Description
User action and values
Comment
Assortment
Grade
Blank (Maximum
Assortment)
Lp For Stores
B1
Check the listing
period
Lp For Distr.
Centers
B1
Check the listing
period
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Local
Assortments
Also
Set Flag
20. Choose Execute Listing.
21. Choose the Sales tab.
22. Choose Validity Area.
23. On the Areas of validity screen, make the following entries:
Field name
Description
User action and values
Sales Org.
1000
Distr.
Channel
10
Comment
24. Choose Enter.
25. On the Sales screen, make the following entries:
Field name
Description
User action and values
Final Price
Comment
<Enter the Value>
Or Choose The Calculated
Value Based On The Mc
Markup
X
Save
Calculated
Price
26. Choose Save.
The system message: Article…changed, displays. The sales price calculation is
described in more detail in the pricing process. The system now checks whether the
header article and all the components are listed for the structured article.
27. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Assortment/Listing
 Evaluations  For Article  Listing Conditions
Transaction code
WSL1
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Non-Seasonal Buyer
(SAP_NBPR_NONSEASBUYER_RT_S)
Business role menu
Purchasing  Non -Seasonal Purchase Management 
Assortments  Assortments, selection lists
28. On the Listing Conditions screen, make the following entries:
Field name
Description
User action and values
Article
DISPLAYxx
Display
Variants/Com
ponents
X
© SAP SE
Comment
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
29. Choose Execute.
30. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
4.7.3 Goods Receipt without References
Use
Post a goods receipt (GR). The customizing settings have been defaulted so that the display is
automatically transferred to its components when the GR is posted for a store.
Post a GR without a reference for the display article.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Merchandise Logisics Materials
Management  Inventory Management  Goods Movement 
Goods Movement (MIGO)
Transaction code
MIGO
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Warehouse Clerk
(SAP_NBPR_WAREHOUSECLERK_S)
Business role menu
Warehouse Management  Consumption and Transfers 
Other Goods Movement
2. On the initial screen, make the following entries:
Field name
Description
User action and values
Comment
Business
Transaction
A01 – Goods
Receipt
Select A01 – Goods Receipt
from the 1st Drop-Down
Menu
Business
Transaction
R10 – Other
Select R10 – Other from the
2nd Drop-Down Menu
501
501 – Receipt without
purchase order into
unrestricted-use stock
Movement Type
3. Choose Enter.
4. On the Goods Receipt Other screen, Article tab, make the following entry and choose Enter:
Field name
Article
Description
User action and values
Comment
DISPLAYxx
5. On the Goods Receipt Other screen, Quantity tab, make the following entry and choose
Enter:
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Field name
Description
User action and values
Comment
100
Qty in Unit of
Entry
6. On the Goods Receipt Other screen, Where tab, make the following entries and choose
Enter:
Field name
Comment
User action and values
Site
M001
Storage Location
1000
Comment
7. Choose Enter.
8. Save your entries.
9. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
10. Access The Transaction Choosing One Of The Following Navigation Options
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Merchandise Logistics  Inventory
Management  Environment  Stock  Stock Overview
Transaction code
RWBE
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Pricing Specialist
(SAP_NBPR_PRICING_RT_S)
Business role menu
Master Data  Pricing  Report  Stock Overview
11. On the Stock Overview screen, make the following entries:
Field name
Article
(Delete Any
Other
Restrictions)
Description
User action and values
Comment
DISPLAYxx
PCS-01-ART146
(Fashion)
PCS-06-ART431
(Hardgoods)
PCS-01-ART331 (Food)
PCS-01-ART147
(Fashion)
PCS-06-ART433
(Hardgoods)
PCS-01-ART322 (Food)
PCS-01-ART148
(Fashion)
PCS-06-ART434
(Hardgoods)
PCS-01-ART323 (Food)
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
12. Choose Enter.
13. Choose Execute.
In our example, the stock of components should have increased.
14. Check the article movements after processing the Good Receipt.
15. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing Merchandise Logisics  Logistics
Execution  Inbound Process  Goods Receipt for
Purchase Order, Order, Other Transactions  Display
Article Document
Transaction code
MB03
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Warehouse Manager
(SAP_NBPR_WAREHOUSE_RT_S)
Business role menu
Warehouse Management  Article documents  Display
Article Document
16. Choose F4 to open the selection screen and enter your display article created in 4.7.1.
17. Choose Enter.
18. Choose the article document for your display article.
19. Choose Enter.
The article movement 319 ‚Split structured material’ shows the details for the display
article and its components.
4.8
Department Store/ Shop Concept
Use
The new Department Store concept allows performing a detailed inventory management.
The store categories Department Store and Shop are enhancements in inventory management
for the site master data model in SAP Retail, based on the Store site category.
If you want to treat the existing departments in a store as standalone units, you must define the
departments as Shops, and the Store site category as Department Store. In this context, the
department store represents the organizational grouping of individual shops. If you use the store
categories Department Store and Shop, you can map multiple stock placement of articles in a
site. The system carries article-specific stock for the individual shops.
Two different models for mapping articles are the department store/shop model and the store
model with departments. The department store/shop model maps the articles in more detail than
the store model with departments, as the assortment is divided across the different shops and in
logistical terms can only be used within the shops.
The main difference between the department store/shop model and the store model with
departments is the division of the entire assortment between different shops. The vendor
subrange can only be retailed within the relevant shop. The department store is used to bundle
individual shops in organizational terms.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
The department store is an organizational unit in a retail company, which groups different areas
of consumption under one roof. A department store is mapped in SAP Retail as a store with an
additional indicator. Unlike a traditional store, a department store cannot manage inventory of
merchandise that is destined for the consumer, as article-based/value-based inventory
management takes place at shop level. Department stores can represent a comprehensive
inventory management level for consumable materials and presentation and sales additionals.
The department store groups shops under a physical address. However, this is not essential as
different shops can also exist in separate places and simply be assigned logically to one
department store.
You use shops to subdivide a department store in operational terms, to provide customers with a
complete overview of the articles available. You use shops to map multiple stock placements of
articles, grouped by merchandise category, within a department store. The system carries
article-specific stock for the individual shops. A shop is assigned merchandise areas for which it
performs the necessary retail processes (requirements planning, inventory management, sales
and planning). The assortment is divided between different shops and can only be used in
logistics terms within these shops.
4.9
Price Level Groups
Use
Price level groups allow you to analyze sales data in SAP BW. The assignment of a price group
to one or more article groups (merchandise category, article hierarchy) allows you to classify
sales with a price band category. The sale of a pair of jeans, for example, can then be assigned
with the sales price to the mid-range price band category. If a large amount of data is available it
can be used as a basis for business decisions.
The creation of a price level group is described in detail.
Prerequisites
In customizing you define whether a price level group can be assigned to merchandise
categories and/or to article hierarchy nodes and you create price level group categories. A "Price
Level Group" number range object with 6 purely numerical characters must have been created.
The existing price level group category '01' specifies that the price level group created on the
basis of this category can only be assigned to merchandise categories, and not to article
hierarchy nodes. You have to create your own price level group category for assigning price level
groups to an article hierarchy.
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Price Level Groups
 Create
Transaction code
WRF_PRGRP01
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Business role menu
Master Data  Price Level group  Price Level group 
Creation of Price Level Groups
2. Select the Price Level Group Categ. as Y2 (Price Level Group for Article Hierarchies).
3. In the field, Price Level Group, maintain a name.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
4. Choose Enter.
5. On the Create Price Level Group screen, maintain a description and price level currency.
6. Maintain the price levels and the price band categories.
7. Confirm your entries with Enter.
8. Save your entries.
9. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
The price level group can now be assigned to a hierarchy node within your article
hierarchy.
4.10 Direct Store Delivery (DSD)
Use
Direct Store Delivery (DSD) is a business process to sell and distribute goods via distributors
directly to the retailer's store, typically bypassing the retailer's warehouses. The direct business
relationships exist between the retailer and the distributors, which act as vendors.
The manufacturer determines the regional coverage responsibilities of the concerned
distributors. A distributor is allowed to deliver to a given region only. A store belonging to another
delivery region needs to be delivered by another distributor. Frequently the regional delivery
responsibilities of a distributor are subject to change.
The change of the regional delivery responsibilities of a distributor forces the retailer to change
the business relationship to a given distributor.
The Retail DSD Master Data Workbench offers mass maintenance functionality for the category
manager to maintain supply relationships and pricing conditions for the DSD articles.
The direct store delivery scenario should enable the retailers to procure articles directly from the
vendor (supplier/distributor). These supply relationships are subjects to legal requirements and
contractual negotiations. Nevertheless, changes from the supplier might happen due to changing
delivery responsibilities.
Consequently, category managers are given the capability to change the supply relationship of
corresponding articles before creating unique purchase orders. Furthermore, the updated costs
and prices applicable to multiple articles based on the new assignments should be reflected in
the purchase orders accordingly.
Procedure
The usage of the Direct Store Delivery Workbench enables the user to maintain the supply
relationships and to make (mass-) changes to the sales and purchase prices of articles.
The process of direct store delivery is facilitated from a master data perspective and support
category managers or other users processing master data in the area of DSD, when defining
supply relationships and during processing of store-specific cost and retail prices. The user is
given the capability to navigate directly from the workbench to the corresponding master data
information. All relations between vendor and articles are captured in the vendor info records.
Therefore, the DSD Workbench collects several existing master data maintenance transactions
in one common application to have a single point of entry, which also serves as a decision
cockpit for category managers.
4.10.1 Creating Supply Relationship
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics  Retailing  Master Data  Vendor Data
Environment  DSD Master Data Workbench
Transaction code
WDSD_WB
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Masterdata Specialist
(SAP_NBPR_MASTERDATA_RT_S)
Master Data  Direct Store Delivery Master Data
Workbench  DSD Master Data Workbench
Business role menu
2. On the Direct Store Delivery: Master Data Workbench screen, choose Personal Settings,
and maintain the personal settings as shown below:
General Settings
Overwrite Overlapping Future Relationships
Copy Purchase Prices
Copy Sales Prices
Create Missing Listing Conditions for local assortments
Allow multiple vendors per article and store
Enable sales price calculation
Display Settings
Display Text for Vendor/Store/Article in the Supply Relationships Tree
Display DSD logo in the HTML header
3. Choose Enter.
4. Choose Selection in order to choose one set of master data (Hardgoods or Food).
5. In the Selection of data dialog box, make the following entries:
Field
Values
To
Mandatory
Purch.
Organization
1000
Vendor
(Hardgoods
/Food)
PCS-V201
To
PCS-V202
X
Store
(Hardgoods/Food)
M001
To
M002
X
Article
(Hardgoods)
PCS-01-ART204
X
Scope item 1
with Hardgoods
PCS-06-ART431
PCS-06-ART433
PCS-06-ART434
Article
(Food)
© SAP SE
PCS-06-ART321
Scope item 2
with Food
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
PCS-01-ART331
PCS-01-ART322
PCS-01-ART323
Key date
Today´s date
Consider that this direct store delivery scenario is only relevant for the master data
set of Hardgoods and Food.
6. Choose Execute.
7. Choose Change Mode.
8. All selected vendors, stores and articles are displayed in the Selected Objects area on the
top left hand side of the screen.
9. Initiate and create the supply relationship between vendor-store-article by dragging from
Selected Objects screen at the top and drop those selected objects to the section below,
starting with Vendors  Stores  Articles; as displayed below:
For Hardgoods:
PCS-V201
M001
PCS-01-ART204
PCS-06-ART431
PCS-06-ART433
PCS-06-ART434
M002
For Food:
PCS-V201
M001
PCS-01-ART322
PCS-01-ART323
PCS-01-ART331
PCS-06-ART321
M002
Once you save these settings, you would have created new assignments for the
vendor-stores and articles and info records within vendor PCS-V201.
You might need to maintain the purchasing info records for the article-vendor on the
right area if an error occurs. Net price is 10,00 and Purchase Group is 101.
Remain in the Supply Relationships area
4.10.2 Copying Supply Relationship
Procedure
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
1. Remain in the Supply Relationships area and mark store M001 under vendor PCS-V201.
2. Choose the Copy to...
3. In the Copy Dialog, choose the store M002 as destination store by choosing the row with the
store M002. Choose Enter.
As a result you have created a new assignment for the articles of M001 with store
M002.
Optional:
With enhancement pack 5 you can allow multiple vendors per article and store.
Consider the personal settings and set the flag accordingly.
1. Open the Selected Objects area and select these articles by Choosing CTRL+article.
Article (Hardgoods)
PCS-06-ART431
PCS-06-ART433
PCS-06-ART434
Article (Food)
PCS-06-ART321
PCS-01-ART322
PCS-01-ART331
2. Use the drag and drop function to add these articles to vendor PCS-V202 and Store M001.
3. Save your entries.
You might need to maintain the purchasing info records for the article-vendor on the
right area if an error occurs. Net price is 10,00 and Purchase Group is 101.
4. After having maintained these data, the traffic lights should turn green.
As a result you have assigned additional articles the new store M001 of vendor
PCS-V202.
Remain in the Supply Relationships area
4.10.3 Changing Purchase/Sales Price
Procedure
Change the prices for articles assigned to store M001 of vendor PCS-V201.
1. Remain in the application: DSD Workbench (WDSD_WB) and go to the Supply
Relationships area and switch to Full screen mode.
2. Select the store M001 and click the right-mouse and choose Select all occurrences of these
stores.
3. Choose the Price Maintenance.
4. If the Purchase Info Records do not exist, please maintain the info records on the right hand
side window – Purchasing Info Record Data and choose Save.
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
5. If the Purchase Info records already exist, the purchasing and sales price of the
corresponding articles is displayed on the right side in Pricing Data window.
6. Change the missing purchasing and sales price for the articles displayed below and delete
the purchasing price for article PCS-01-ART204 (Hardgoods)/ PCS-01-ART322 (Food) as
shown:
For Hardgoods:
Vendor
Article
PP Store
SP Store
PCS-V201
PCS-01-ART204
Leave blank
Leave blank
PCS-V201
PCS-06-ART431
6
9
PCS-V201
PCS-06-ART432
7
10
PCS-V201
PCS-06-ART433
8
11
PCS-V202
PCS-06-ART431
9
9
PCS-V202
PCS-06-ART432
10
10
PCS-V202
PCS-06-ART433
10
11
Vendor
Article
PP Store
SP Store
PCS-V201
PCS-01-ART322
Leave blank
Leave blank
PCS-V201
PCS-01-ART323
8
13
PCS-V201
PCS-01-ART331
2
4
PCS-V201
PCS-01-ART321
5
10
PCS-V202
PCS-01-ART322
Leave blank
Leave blank
PCS-V202
PCS-01-ART331
2
4
PCS-V202
PCS-01-ART321
5
10
For Food:
7. Choose Save.
The new prices and values have now been updated and maintained in the
corresponding master data records.
Optional: Mass maintenance
Mass price changes are possible in case that a vendor-specific price is required to
be defined.
8. Stay in change mode.
9. Mark the rows as shown by choosing CTRL and mark the respective column for PP Store.
For Hardgoods:
Vendor
Article
PP Store
SP Store
PCS-V201
PCS-06-ART431
6
9
PCS-V201
PCS-06-ART432
7
10
PCS-V201
PCS-06-ART433
8
11
For Food:
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Vendor
Article
PP Store
SP Store
PCS-V201
PCS-01-ART323
8
13
PCS-V201
PCS-01-ART331
2
4
10. Choose Price Mass Maintenance to process with price change by percentage (10,00).
11. In the Increase/decrease Prices dialog box, enter 10,00 in the field Increase selected prices
by percentage.
12. Choose Enter.
13. Choose Save.
14. Choose Back (F3) to the SAP Easy Access screen (SAP GUI).
Or
Choose Exit (Shift+F3) to close the transaction (SAP NetWeaver Business Client).
Result
For Hardgoods:
Vendor
Article
PP Store
SP Store
PCS-V201
PCS-06-ART431
6,60
9,90
PCS-V201
PCS-06-ART432
7,70
11,00
PCS-V201
PCS-06-ART433
8,80
12,10
Vendor
Article
PP Store
SP Store
PCS-V201
PCS-01-ART323
8,80
14,30
PCS-V201
PCS-01-ART331
2,20
4,40
For Food:
4.10.4 Creating Purchase Order
Procedure
1. Access the transaction choosing one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC menu
Logistics Retailing Purchasing  Purchase Order 
Create  Vendor known
Transaction code
ME21N
Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role
Business role
Retail Non-Seasonal Purchaser
(SAP_NBPR_NONSEASBUYER_RT_S)
Business role menu
Purchasing Non-Seasonal Purchasing  Purchase
Orders  Create Purchase Orders
2. Create a purchase order for:
Header Level:
Field name
User action and values
Order Type
NB Standard Order
Vendor
PCS-V201
© SAP SE
Page 6 of 8
SAP Best Practices
Item Management (711): BPD
Purch.Org
1000
Purch. Group
101
Company Code
1000
3. For Hardgoods scenario:
Item Level:
Article
Quantity
Site
PCS-01-ART204
10
M001
PCS-06-ART431
10
M001
PCS-06-ART433
10
M001
PCS-06-ART434
10
M001
Article
Quantity
Site
PCS-01-ART322
10
M001
PCS-01-ART323
10
M001
PCS-01-ART331
10
M001
For Food:
Item Level:
4. Choose the Condition tab page to double-check if the prices have been adopted for each
article (store-specific purchase price with source list record) for and if the new vendorspecific purchase price (price maintained in the DSD workbench) is taken for articles. (see
previous chapter for further details)
Ignore the message such as Special procurement type U is used for article.
Ignore the warnings since this dummy purchase order should demonstrate the
adaption of the PP prices maintained in the previous step.
5. Cancel the process and do not save.
© SAP SE
Page 6 of 8
Téléchargement
Explore flashcards