711 bpp item management

SAP ERP 6.0 EHP3August 2008

September 2008

711: Item Management

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices 711: Item Management - BPD

Copyright

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 104


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

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 AG of 104


Contents

1 Purpose........................................................................................................................................ 6

2 Prerequisites................................................................................................................................ 6

2.1 Scenario Menu and Basic Path.............................................................................................6

2.2 Required Master Data...........................................................................................................6

3 Process Overview Table...............................................................................................................8

4 Article Maintenance.................................................................................................................... 13

4.1 Process Flow....................................................................................................................... 13

4.2 Single Article....................................................................................................................... 14

4.2.1 Create a Single Article (Manually)................................................................................14

5 Process the Single Article...........................................................................................................17

5.1.1 Assortment Listing........................................................................................................17

5.1.2 Implement Listing.........................................................................................................20

5.1.3 Display a Generated Assortment Module.....................................................................21

5.1.4 Display the Profile Module for Store M001 Using Assortment Menu............................22

6 Reference Handling In the Article Master...................................................................................23

6.1 Reference Article as Copy Template...................................................................................23

6.2 Article Data with Client-Wide Validity..................................................................................24

6.3 Determine Organizational Levels for an Article...................................................................25

6.4 Comment on Mass Maintenance of Article Data From Same Org. Levels..........................26

6.4.1 Maintain Logistics Data for All DCs/Stores...................................................................27

6.5 Work with Maintenance Groups..........................................................................................30

6.5.1 Create a maintenance group........................................................................................31

6.5.2 Extension of a maintenance group by a template........................................................33

6.5.3 Create Core Master Article with Template....................................................................34

6.5.4 Check the Article Creation............................................................................................35

6.5.5 Mass Maintenance Using Reference Sites...................................................................36

6.5.6 Mass Maintenance Using Mass Maintenance Tool......................................................40

6.5.7 Alternative Data Maintenance (Alternative Organizational Levels)...............................43

6.5.8 Mass Maintenance Using the Article Monitor...............................................................45

6.5.9 Article Copy to Create a New Article............................................................................46

6.5.10 Check the Article Creation for the Copied Article.........................................................48

6.5.11 Article Discontinuation..................................................................................................49

6.5.12 Create Article List.........................................................................................................50

© SAP AG of 104


6.5.13 Follow up and Replacement Articles............................................................................52

6.6 Store Characteristic Values.................................................................................................53

6.6.1 Characteristic Value Grouping.....................................................................................58

6.6.2 Create a Characteristic Profile with the New Characteristics.......................................59

6.6.3 Assign the Characteristic Profile to a Merchandise Category.......................................60

7 Generic Article............................................................................................................................ 61

7.1.1 Create a Generic Article with Variants..........................................................................61

7.1.2 Process the Generic Article..........................................................................................64

7.1.3 Reference Handling For Generic Article Variants.........................................................66

7.2 Matrix Maintenance for Generic Articles..............................................................................69

7.2.1 Price Matrix for Variants of Generic Articles.................................................................69

7.2.2 Matrix Handling For Master Data Fields For The Generic Article.................................71

8 Prepack...................................................................................................................................... 73

8.1.1 Create A Prepack.........................................................................................................73

8.1.2 Process the Prepack....................................................................................................76

8.1.3 Determine Valuation Prices for Prepack Components.................................................79

8.1.4 Goods Receipt without References..............................................................................80

9 Sales Set.................................................................................................................................... 82

9.1.1 Create a Sales Set.......................................................................................................82

9.1.2 Process a Sales Set.....................................................................................................84

9.1.3 Goods Receipt Without References.............................................................................88

9.1.4 Set Up Structured Article..............................................................................................89

10 Display.................................................................................................................................... 91

10.1.1 Create Display..............................................................................................................92

10.1.2 Process Display...........................................................................................................94

10.1.3 Goods Receipt without References..............................................................................98

11 Department Store/Shop Concept..........................................................................................100

12 Price Level Groups...............................................................................................................104

© SAP AG of 104


Item Management

1 PurposeWithin the scenario Item Management, Article creation of single, Generic and structured articles will be 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 PrerequisitesNote the settings for this scenario 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 locs (fashion, food, hard goods) and can be referenced in the corresponding processes.

2.1 Scenario Menu and Basic PathThe following basic path is the basis for all other paths in the process documentation. As an alternative to the SAP menu, you can use the process menu for navigational purposes. You can access this using the [other menu] button in the SAP easy access menu.

Basic Path SAP Menu Logistics Retailing

2.2 Required Master DataTo execute the scenario, 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





VENDOR1 PCS-V111 PCS-V201 PCS-V201



MC SINGLEART-[MC-SA]

MC11451 MC14201 MC13202

© SAP AG of 104


FASHION HARDGOODS FOOD

MC GENERICART-[MC-GA]

MC11141 MC14402 MC12003

MC SALES SET MC11152 MC14203 MC12003

MC DISPLAY MC11152 MC14402 MC12003

© SAP AG of 104


3 Process Overview TableStep Step Name External

Process Reference

Business Condition

Role Transaction Code

Expected Results

4.2.1Create Single Article (Manually)

Retail Masterdata Manager

MM41

5.1.2 Implement Listing Retail Masterdata Manager

MM42

5.1.3 Display a Generated Assortment Module

Retail Assortment Planner

WSL11

5.1.4 Display the Profile Module for Store M001 Using Assortment Menu

Retail Assortment Planner

WSO7

6.4.1 Maintain Logistics Data for All DCs/Stores


MM42

6.5.1 Create a maintenance group


WRFMGROUP

6.5.2 Extension of a maintenance group by a template


WRFMGROUP

6.5.3 Create Core Master Article with Template


WRFMATBODY

6.5.4 Check the Article Retail MM43

© SAP AG of 104


Step Step Name External Process Reference

Business Condition


Expected Results

Creation Masterdata Manager

6.5.5 Mass Maintenance Using Reference Sites


MM41

6.5.6 Mass Maintenance Using Mass Maintenance Tool


REFSITE

6.5.7 Alternative Data Maintenance (Alternative Organizational Levels)


MM42

6.5.8 Mass Maintenance using the Article Monitor


WRFMATMON

6.5.9 Article Copy to Create a New Article


WRFMATCOPY

6.5.10 Check Article Creation for the Copied Article


MM42

6.5.11 Article Discontinuation


WRF_DIS_SEL 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

© SAP AG of 104



Business Condition


Expected Results

6.5.12 Create Article List Retail Masterdata Manager

WRF_AL

6.5.13 Follow up and Replacement Articles


WRFFUART

6.6 Store Characteristic Values


CT04

6.6.1 Characteristic Value Grouping


WRFCHVALGRP

6.6.2 Create a Characteristic Profile with the New Characteristics


CLWE

6.6.3 Assign the Characteristic Profile to a Merchandise Category


WG22

7.1.1 Create a Generic Article with Variants


MM41

7.1.2 Process Generic Article


MM42

© SAP AG of 104



Business Condition


Expected Results

7.1.3 Reference Handling For Generic Article Variants


MM43

7.2.1 Price Matrix for Variants of Generic Articles


MM42

7.2.2 Matrix Handling For Master Data Fields For The Generic Article


MM42

8.1.1 Create a Prepack Retail Masterdata Manager

MM41

8.1.2 Process Prepack Retail Masterdata Manager

MM42

8.1.3 Determining Valuation Prices for Prepack Components

Retail Pricing Manager

MR21

8.1.4 Goods Receipt without References

Retail Pricing Manager

RWBE

9.1.1 Create a Sales Set Retail Masterdata Manager

MM41

9.1.2 Process Sales Set Retail Masterdata Manager

MM42

9.1.3 Goods Receipt Retail Non- MB1C

© SAP AG of 104



Business Condition


Expected Results

Without References Seasonal Purchaser

9.1.4 Set Up Structured Article

Retail Store Manager

MB1B

10.1.1 Create a Display Retail Masterdata Manager

MM41

10.1.2 Process Display Retail Masterdata Manager

MM42


Retail Non-Seasonal Purchaser

MB1C

11 Department Store/Shop Concept


WRFDEP01

12 Price Level Groups Retail Masterdata Manager

WRF_PRGRP01

© SAP AG of 104


4 Article Maintenance

4.1 Process FlowMaster 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.

Listingdata on assortment layout, listing procedure, distribution chains, listing and sales periods.

Purchasingvendor-specific data such as purchasing price, order units, purchasing group, conditions, delivery times for each vendor.

Salessales-specific data for each distribution chain or site, such as sales units, purchasing dates and sales prices.

Logistics distribution centersite-specific data for distribution centers such as planning parameters, forecast parameters, storage data and general control parameters.

Logistics storesite-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

© SAP AG of 104


Groupings

General Data

Validities

Successor/Substitute Article

For detailed information refer to the various help options (e.g. 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:

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 customizing guide, 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 Create a Single Article (Manually)

UseTwo-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 Menu Master Data Article Data Article Create

Transaction Code MM41

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

© SAP AG of 104


Business role (name) SAP_BP_RT_MASTERDATA-S (Retail Master Data Manager)

Business role menu 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 SINGLEART1xx

Article Type MODE (Apparel seasonal)

HAWA (Trading Goods)

HAWA or FRIP (Perishables)

Fashion

Hardgoods

Food

Merchandise Category

MC11451 (Fashion)

MC14201 (Hardgoods)

MC13202 (Food)

If the system message You have entered a different article type… displays, choose a view as requested

Article Category

Single Article

3. Choose Basic Data View

4. Choose Enter

5. On the Create article: Basic data, make the following entries:


Article Description

’Article Description’

EAN category (EAN/UPC)

IE Units of Measure/Eans/Dimensions

1st Line /Column Ct

6. Choose Enter

The system message The EAN will be determined internally on the basis of the EAN category displays.

7. Choose Enter

The system message You are about to exit…Displays.

© SAP AG of 104


8. Choose Cancel.

9. Choose Tab Purchasing

10. On the Areas of validity screen, make the following entries:


Purchasing Org.

1000

Vendor PCS-V111 (Fashion)

PCS-V201 (Hardgoods)

PCS-V201 (Food)

>Vendor1

11. Choose Enter.

12. On the Create article: Purchasing screen, make the following entries:


Purchasing Group

'100'

Net Price <Value>

13. Choose the Sales tab.

14. Choose Validity Area.



Sales Org. '1000'

Distr. Chl '30'

16. Choose Enter.

17. On the Create article: Sales screen, make the following entries:


Pp det. Seq. ‘01‘

Sp determ. Seq.

‘01‘

Final Price <Value>

Save Calc. Price

'X'

© SAP AG of 104


If you change the Final Price, the system message Sales pricing has been performed or changed displays.

18. Choose the Logistics DC tab.

19. On the Create article: Logistics DC screen, make the following entries:


Rp Type ‘ND’

Supply Source

'1'

Avail. Check ‘KP'

20. Choose the Logistics : store tab.

21. On the Create article: Logistics Store screen, make the following entries:


Rp Type ‘ND'

Supply Source

'4'

Avail. Check 'KP'

GR Proc. Time (In Days)

‘5’

22. Choose Save

The System Message Article … Created Displays.

5 Process the Single Article

5.1.1 Assortment ListingIn general, 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

© SAP AG of 104


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 normally used to list articles that are carried over a long period of time and are very 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 will not be listed in any of the assortments assigned to the exclusion module for its validity period.

Rack jobber modules

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

© SAP AG of 104


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

© SAP AG of 104


K1 never any listing

There are three basic procedures for automatic listing:

Selection using siteand 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 scenario assortment management. This also deals in depth with the option of multiple assignments of general assortments to sites (n:m-assignment) and how to configure these. Implement Listing

UseThe following table describes how to assign the single article created in section 4.2 to all sites using the automatic listing procedure (B1).

Procedure



SAP Menu Master Data Article Data Article Change




Business role menu Article Article Master Data Change Article

2. On the Change article: Initial screen, make the following entries:



3. Choose Listing View

4. Choose Enter

5. On the Change article: Listing screen, make the following entries:


Assortment Grade

Blank

LP For Stores

B1 (Please Pay Attention To The Listing Periods Of The Different Listing

© SAP AG of 104



Procedures)

LP for distr.centers

B1

Local Assortments Also

Set Flag

List Supplying Sites

Set Flag

6. Choose Execute Listing

7. Choose Tab Sales

8. Choose Validity Area



Sales Org. 1000

Distr. Chl 10

10. Choose Enter

11. On the Change article: Sales screen, make the following entries:


Final Price Value

Save Calculated Price

X

12. Choose Save

13. The System Message Article ... Changed displays.

5.1.2 Display a Generated Assortment Module

UseThe assortment module from a site (for example, M001) is first determined from the hierarchy display.

Procedure



© SAP AG of 104


SAP Menu Logistics Retailing Master Data Assortment/Listing Evaluations For Article Tree Display Of Listing Conditions

Transaction Code WSL11


Business role (name) SAP_BP_RT_ASSORTMENTMAN-EC-S (Retail Assortment Planner)

Business role menu Assortment Master Data Listing condition Evaluation of Listing conditions

2. On the Evaluation of listing conditions screen, make the following entries:


Article 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 twice

5.1.3 Display the Profile Module for Store M001 Using Assortment Menu

Procedure



SAP Menu Logistics Retailing Master Data Assortment/Listing Assortment Module Assortment assignment Display

Transaction Code WSO7


Business role (name) SAP_BP_RT_ASSORTMENTMAN-EC-S (Retail Assortment Planner)

Business role menu Assortment Master Data Assortment Module IS-R Astmts, Display module -> store

2. On the Assortment module assignment to Assortment screen, make the following entries:


© SAP AG of 104


Module Module number see 5.1.3

Select Date 'Current Date'

3. Choose Items or confirm your entry

4. Choose two times Back

6 Reference Handling In the Article MasterDue 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 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.

6.1 Reference Article as Copy TemplateReference articles are used to determine default values when creating and extending article data. All data is proposed for the reference article apart from EANs, 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 you 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

© SAP AG of 104


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.

6.2 Article Data with Client-Wide Validity

UseIn 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 very 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 normally 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 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.

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-LDVFLMAW1-LDBFL

Listing Period For Stores

MVKE-LDVFLMVKE-LDBFL

MAW1-LDVZLMAW1-LDBZL

Listing Period For DCs

MVKE-LDVZLMVKE-LDBZL

MAW1-VDVFLMAW1-

Sales Period For Stores

MVKE-VDVFLMVKE-VDBFL

© SAP AG of 104


VDBFL

MAW1-VDVZLMAW1-VDBZL

Sales Period For DCs

MVKE-VDVZLMVKE-VDBZL

6.3 Determine Organizational Levels for an ArticleIn 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:

- Basically 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 period’ 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.

- 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

© SAP AG of 104


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.

Comment: 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).

6.4 Comment on Mass Maintenance of Article Data From Same Org. LevelsMass 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.

Sales data for all distribution chains.

Maintenance of POS data for all distribution chains.

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).

© SAP AG of 104


6.4.1 Maintain Logistics Data for All DCs/Stores

UseThe 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 will be 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.

The following section looks at mass maintenance of logistics data using the field minimum lot size 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

© SAP AG of 104


transaction MM42 (change article) for all reference stores and for the client’s stores (table MARC). The corresponding updated value is then double checked.

In order to perform reference handling, copy control must also be flagged in the field MARC-BSTMI. 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











3. Choose View Logistics:Store

4. Choose Enter

5. Choose RP/Forecast Data

6. On the Change article: RP/Forecast Data: Store screen, make the following entries


Minimum Lot Size

Enter Any Value, For Example, ‘88’

7. Choose Back

8. Choose Save.

© SAP AG of 104


Afterwards you can check whether the value maintained at reference level was copied to the dependent store M001.



SAP Menu Master Data Article Data Article Display




Business role menu Article Article Master Data Display Article

2. On the Display article: Initial screen, make the following entries:



Select View Logistics: Store

M001

3. Choose Enter.


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):

5. Choose Back







© SAP AG of 104






Store M001


9. Choose Enter.


11. On the Change article: MRP/Forecast Data: Store screen, make the following entries:


Minimum Lot Size

Now change the value of this field from ‘88’ to, for example, ‘99’

12. Choose Back

13. Choose Save

14. Choose Back Twice

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.

6.5 Work with Maintenance Groups

UseA 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, e.g. flexibly define the displayed fields.

© SAP AG of 104


6.5.1 Create a maintenance group

UseYou create a maintenance group in Maintenance Group Management. You will create a maintenance group for Core Master Data and one for Mass Maintenance.

Procedure



SAP Menu Logistics Retailing Master Data Article Data Article Manage Maintenance Groups

Transaction Code WRFMGROUP



Business role menu Article Maintenance Groups Maintenance Group Management

2. Choose Show/Hide Tree to ensure that the group hierarchy tree is shown

3. Go to the Change Mode

4. Choose folder Cross-Application on the left hand side of the screen

5. In the context menu choose: Create Maintenance Group

6. Maintain the following text for both name and description: MG f. Core Master Data

You cannot change the internally-issued number.

7. Choose Select Field Groups to 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 Attributes

7 1: Assortment Assignment

8 0: Variant Data

50 0: Art. Hierarchy Nodes

Set indicator

© SAP AG of 104



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: 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 Set indicator

8. Choose Continue

9. Choose Save

10. Choose Change Mode

11. Choose folder Mass Maintenance - Seasonal Procurement. on the left hand side of the screen

12. In the context menu choose: Create Maintenance Group

13. Maintain name and description: MG for Mass Changes Basic Data

14. Choose Select Field Groups to assign the following field groups to the maintenance group


87 0: Price Band Category

92 0: Season

98 0: Creation Status

99 0: Mark

102 0: Fashion Grade

118 0: Purchasing Group

15. Choose Continue

© SAP AG of 104


16. Choose Save

6.5.2 Extension of a maintenance group by a template

UseYou 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



SAP Menu Logistics Retailing Master Data Article Data Article Manage Maintenance Groups

Transaction Code WRFMGROUP



Business role menu 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. Switch to Change Mode

5. Create the template by clicking the button Show/Hide

6. 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

6.5.3 Create Core Master Article with Template

Use

© SAP AG of 104


The Core Master Article is a normal article master record that is created with ERP functions instead of master data functions, e.g. 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 record with master data so that you can use it operationally as a complete article in every application.

Procedure



SAP Menu Logistics Retailing Master Data Article Data Article Process Core Master Data

Transaction Code WRFMATBODY



Business role menu Article Article Master Data Edit Article Core Master Data

2. In the Select maintenance group select 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. Maintain the following values during article creation apart from the values that are defaulted by the template


Article Type MODE Defaulted


MC11451 (Fashion)

Article Category

‘00’ Single Article

Vendor PCS-V111 (Fashion) Defaulted >Vendor1

Infotype ‘0’ Defaulted

Purchasing ‘1000’ Defaulted

© SAP AG of 104


Organization

5. Confirm your entry by pushing Enter

6. In the Maintain Article view choose Descriptions in the tree view

7. Maintain the description in German: Krawatte CMA

8. Maintain the description in English: Tie CMA

9. Push 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)


Season ‘0001’

Season Year next year

12. Push Enter

13. Confirm the pop-up 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


Hierarchy Node

B11252 Ties

15. Press Save

16. Note down the article number _______________________

17. The system message Background processing started.for article_________displays.

6.5.4 Check the Article Creation

UseAfter saving the core article master data, you check whether the article was created correctly.

Procedure


© SAP AG of 104





Business role Retail Masterdata Manager






Article Core Master Article created in 6.5.3


4. Choose Enter

5. Check the attributes of the article

6. Choose Back

6.5.5 Mass Maintenance Using Reference Sites

UseTo 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 will look 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).

© SAP AG of 104


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














HAWA or FRIP (Perishables)

Fashion

Hardgoods

Food


MC11451 (Fashion)

MC14201 (Hardgoods)

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:


Article Description


© SAP AG of 104



IE Units of Measure/Eans/Dimensions

1st Line /Column Ct

6. Choose Enter

The system message The EAN will be determined internally on the basis of the EAN category displays.

7. Choose Enter (2 times)

8. Choose Save

In the second step, you maintain the maximum stock level for the reference site in the article’s logistics store view












Store ’REFL’


4. Choose Enter

5. The System Message You have not yet maintained the listing view displays.

6. Choose Enter

© SAP AG of 104


7. On the Change article: Logistics Store screen, make the following entries:


ABC indicator Any Entry – For Example, ‘A’

8. Choose Enter

9. The System Message Do you want to save your data for this article first? displays.

10. Choose Yes

11. 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.

In order to perform reference handling, you need to switch off copy control in transaction OMSR for the field MARC-MAABC. And then moving to the detailed view for the field. Please switch on the copy control when you finish this procedure.












Store ‘M001’


© SAP AG of 104


15. Choose Enter

16. System Message You have not yet maintained the listing view displays.

17. Choose Enter



ABC indicator Value from the ref site is proposed (copy control from reference site)

19. Choose Enter

20. System Message Do you want to save your data for this article first? displays.

21. Choose Enter

22. System Message Article….Changed Displays

You can also copy default data from the reference store to a special site using site listing for the respective article (transaction WSP4).

6.5.6 Mass Maintenance Using Mass Maintenance Tool

UseThe following section shows how to maintain logistics data using the new mass maintenance tool. As in chapter 3.1.3.8 the prerequisite for this is that the sites are assigned to the reference site.

We will start by showing how sites are assigned to the reference site in the system.

Procedure



SAP Menu Logistics Retailing Master Data Assortment/Listing Mass Maintenance Reference Sites Management

Transaction Code REFSITE



© SAP AG of 104


Business role menu Site Sites Reference site management

2. Expand the branch logistics & replenishment to the level of the reference site (REFL)

3. Doubleclick on 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

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 control in transaction OMSR for the field MARC-MAABC . And then moving to the detailed view for the field. Please switch on the copy control when you finish this procedure. (in the field selection for mass maintenance using the mass maintenance tool only fields without copy control are proposed).



SAP Menu Logistics Retailing Master Data Assortment/Listing Mass Maintenance Logistics/Replenishment Mass Maintenance

Transaction Code MASS_MARC



Business role menu Article Mass Maintenance Logistics/Replenishment Mass Maint.

6. On the Logistic/Replenishment Mass Maintenance screen, make the following entries:


Article Article From Chapter 6.5.5

Site No Entry

7. Choose Select

8. Double click on the reference site - a table structure for mass maintenance of logistics and replenishment data for the article is displayed in the window on the right hand side.

© SAP AG of 104


9. Choose Select All

10. Choose Mass Change

11. On the Logistic/Replenishment screen, make the following entries:


ABC indicator Enter a value, for example,’C’

12. Choose Enter

13. Choose Save

14. Confirm pop-up on parameters

15. Choose Back

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









Article Article 6.5.5

Store M001


19. Choose Enter. The ABC indicator for the store should be the value maintained during mass maintenance.

© SAP AG of 104


20. Choose Back

6.5.7 Alternative Data Maintenance (Alternative Organizational Levels)

UseWhen 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“(see also 3.1.3.8).

Procedure










© SAP AG of 104




4. Choose Enter


6. On the Validity Areas screen, make the following entries:


Store 'M001’

7. Choose Enter



Gr Proc. Time

’2’

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).


12. Choose Enter

13. Check the field GR Processing Time: (5 days)


15. On the Validity Areas screen, make the following entries:


Store 'M001’

16. Choose Enter

17. Check the field GR Processing Time for store M001: the value should be 2.

18. Choose Back Twice

© SAP AG of 104


6.5.8 Mass Maintenance Using the Article Monitor

UseYou can use this function to select articles for which subsequent functions have to be performed. You will use a maintenance group created for this process (see 3.1.3.5) and change Basic Data for a selection of articles in the mass data maintenance.

PrerequisitesYou have created a maintenance group for mass maintenance.

Procedure



SAP Menu Master Data Article Data Article Article Monitor

Transaction Code WRFMATMON



Business role menu Article Article Monitor Article Monitor

2. On the Article Monitor for Follow-On Processing selection screen, make the following entries:


Creation Status

01 Status for core articles

3. Choose Execute

4. Select all positions by clicking

5. Choose Mass Maintenance

6. In 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.

© SAP AG of 104


10. Choose Execute selection

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 on folder Basic Data

13. Select the articles that you want to change

14. Choose Fast Entry (a new subscreen 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. Press Continue

18. Mark the data record to be changed in the selection list

19. Press Save

20. Choose Update Method Synchronized (2) in the pop up for the ‘Update parameters’

21. Press Continue

22. Choose Display Application Log to check whether the changes were made successfully

23. Choose Execute in screen Analyze Application Log

24. Choose Back

6.5.9 Article Copy to Create a New Article

UseYou 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


© SAP AG of 104



SAP Menu Master Data Article Data Article Copy

Transaction Code WRFMATCOPY



Business role menu Article Article Master Data Copy Article

2. On the Copy article screen, make the following entries:


Article Article from 6.5.3 or SINGLEART1xx

Screen area: Source Article


Internal number assignment

Set indicator Screen area: Target Article


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 Screen area: Processing Volume

Additional Article Data

Set indicator

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

6. Choose Continue

In the segment filters all segments are selected automatically and therefore are copied from the source to the target article.

© SAP AG of 104


7. Choose Execute

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.

8. Choose Back

6.5.10 Check the Article Creation for the Copied Article

UseAfter saving the copied article, you check whether it was created correctly.

Procedure










Article Article created in 6.5.9


4. Choose Enter

5. Check the values of the new article and change the description

6. Choose Save

6.5.11 Article Discontinuation

Use

© SAP AG of 104


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. Discontinuation is particularly important in the fashion industry, whose seasonal nature means that you often have to discontinue large numbers of articles within a short period of time.

You will create a worklist and use it in the discontinuation monitor. You will discontinue one of the articles you have already created.

Procedure



SAP Menu Master Data Article Data Article Discontinue Discontinuation Workbench

Transaction Code WRF_DIS_SEL



Business role menu Article Discontinuation Seas. Proc. Article Discontinuation

2. On the Selection Screen Client Wide Article Discontinuation select:


Article ‘One of your articles’ Article of your choice

Offline Check Set indicator Subscreen: Processing Type

Execute follow-up processing

Set indicator

Discontinue immediately

Set indicator

Worklist name

‘your own user’

3. Choose Execute

4. Confirm the pop up for follow-up actions with yes

5. System message 1 articles are being checked. The result appears in the work list. Displays

ResultThe 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.

© SAP AG of 104




SAP Menu Master Data Article Data Article Discontinue Discontinuation Monitor

Transaction Code WRF_DIS_MON



Business role menu Article Discontinuation Seas. Proc. Discontinuation Monitor

7. Enter worklist name ‘Your Worklist’

8. Choose Execute

9. Flag the line representing your worklist

10. Select Choose

ResultA 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

6.5.12 Create Article List

UseThe 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



SAP Menu Master Data Article Data Article Article List Edit

Transaction Code WRF_AL

© SAP AG of 104




Business role menu 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, e.g.: Userxx

7. Push Enter

8. Choose Create Article List on the right hand side of the screen

9. Maintain the description: Static article list Userxx

10. Push Enter

11. Flag the list type: Static Type

12. Choose Edit Selection

13. Choose a Hierarchy node: B11252

14. Choose Enter

15. Choose Results List to check the details

16. Choose Back

17. Change the validity dates: Valid From: Current date; Valid to: Current date + 10 days

18. Choose Enter

19. Choose Back

20. 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.

21. Press Save

© SAP AG of 104


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.

6.5.13 Follow up and Replacement Articles

UseThis 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



SAP Menu Master Data Article Data Article Follow-Up/Replacement Articles Edit

Transaction Code WRFFUART



Business role menu Article Follow-Up/Replacement Articles Maintain Succ./Subst. Article Name

2. Choose Article Selection

3. Maintain the following data in the selection window:


Substitution Profile

‘02’ Replacement Screen area: Substitution Type

Merchandise MC11451 (Fashion) >[MC-SA]

© SAP AG of 104


Category MC14201 (Hardgoods)

MC13202 (Food)

4. Choose Execute

5. Select one of your single articles in the article selection screen

6. Click Assignments

7. Select the replacement article:


Substitution Profile

PCS-01-ART146 (Fashion)

PCS-06-ART432 (Hardgoods)

PCS-06-ART321 (Food)

Valid to ‘12/31/2008’

Priority ‘01’

8. Save your entries

9. Choose Back

10. Confirm the pop up Successor/subsitute article relationship with ‘Yes’

6.6 Store Characteristic Values

UseThis 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 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 customer-specific values to provide the characteristic value with alternative value conversions.

© SAP AG of 104


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



SAP Menu Master Data Merchandise Category Data Characteristics Characteristics Management

Transaction Code CT04



Business role menu Merchandise Group Data Characteristics Characteristics

2. Maintain in field Characteristic the name ‘PCS01’

3. Choose Create

4. Maintain the following details for the characteristic Color:


Description ‘Color‘ Basic data tab

Data Type'CHAR'

Number of chars

'10'

Function‘WRF_CHECK_CHAR_VAL’

Values data tab, Use pushbutton ‘Other value check’, Function module

5. Confirm your entries with Enter


7. Create a characteristic size (children); maintain in field Characteristic the name ‘PCS02’

8. Choose Create

© SAP AG of 104


9. Maintain the following details for the characteristic Size:


Description ‘Size Children‘ Basic data tab

Data Type'CHAR'

Number of chars

'10'

Function‘WRF_CHECK_CHAR_VAL’

Values data tab, Use pushbutton ‘Other value check’, Function module





SAP Menu Master Data Merchandise Category Data Characteristics Type Characteristics

Transaction Code WRFCHVALTYPE



Business role menu Merchandise Group Data Characteristics Maintain Characteristic Type Data

13. Choose New Entries

14. Maintain the following data


Internal char. No.

'PCS01'

Characteristic Name

‘PCS01’ Automatically filled on return

Char. Type'Color Characteristic'

Check option‘W Check Characteristic Values in Material Maint. w/Information’

Defaulted during value maintenance

© SAP AG of 104



16. Maintain the following data


Internal char. No.

'PCS02'

Characteristic Name

‘PCS02 Automatically filled on return

Char. Type'Size Characteristic (Main Size)'

Check option‘W Check Characteristic Values in Material Maint. w/Information’

Defaulted during value maintenance




SAP Menu Master Data Merchandise Category Data Characteristics New Characteristic Value Storage Process Characteristic Values

Transaction Code WRFCHVAL



Business role menu Merchandise Group Data Characteristics Edit

19. Choose PCS01 from the value list

20. Choose Change

21. Maintain the following data in the Edit Characteristic Values screen:

Characteristic Value

Description Sort

(defaulted)

Analyzing Color

Standard Color Code

Pantone

1 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

© SAP AG of 104



Description Sort

(defaulted)

Analyzing Color

Standard Color Code

Pantone

22 orange JAUNE 2200 00007

23 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

22. Choose Save

23. Choose PCS02 from the value list

24. Maintain the following data in the Edit Characteristic Values screen:


Description Sort

(defaulted)

European Size

British Size Italian Size

XXXS XXXS 92

XXS XXS 98

XS XS 110

S S 128

© SAP AG of 104


M M 140


6.6.1 Characteristic Value Grouping

UseGrouping 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



SAP Menu Master Data Merchandise Category Data Characteristics New Characteristic Value Storage Group Characteristic Values

Transaction Code WRFCHVALGRP



Business role menu Merchandise Group Data Characteristics Maintain Characteristic Value Groups

2. Choose the characteristic PCS01

3. Choose Continue

4. Choose Change hierarchy tree

5. Choose Create Node in the context menu in the tree view

6. Maintain the name and description, e.g. 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)

© SAP AG of 104


10. Select one or more characteristic values (all of them are shown) and press Enter


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).

6.6.2 Create a Characteristic Profile with the New Characteristics

UseEach merchandise category can be assigned descriptive characteristics or characteristics profiles. A characteristic profile is used during article maintenance especially for generic articles.

Procedure



SAP Menu Master data Merchandise category data Characteristics profile Create

Transaction Code CLWE



Business role menu Merchandise Group Data Characteristics Profile Create Characteristic Profile (MMS)

2. Maintain the ID for the profile ‘PCS01’

3. Press Enter

4. On the Basic Data Tab maintain the description: Color/Size Children

5. On the Characteristics Tab assign your characteristics: ‘PCS01’ and ‘PCS02’. For both choose in the Relevancy Indicator that they are relevant for variants (2)


7. The system message: Class type 026 Characteristics Profile created displays

© SAP AG of 104


6.6.3 Assign the Characteristic Profile to a Merchandise Category

UseIf 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



SAP Menu Master data Merchandise category data Merchandise Category Change

Transaction Code WG22



Business role menu Merchandise Group Data Merchandise Groups Change Merchandise Categories

2. Choose the merchandise category ‘MC11611’

3. For the Characteristics Profile choose your profile ‘PCS01’ from the value list (F4)

4. Choose Assign profile

5. The system message: The assignment of PCS01 to MC11611 was created/changed without value assignment displays

6. Choose Back.

7 Generic ArticleThe 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 non-variant 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

© SAP AG of 104


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.

7.1.1 Create a Generic Article with Variants

UseIf 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










Article GENERICARTxx



HAWA or FRIP (Foods excl. Perishables)

Fashion

Hardgoods

Food

Mdse Ctgry MC11141 (Fashion)

MC14402 (Hardgoods)

MC12003 (Food)

>[MC-Ga]

Artl category 01 Generic article

3. Select View ‘Basic data’

© SAP AG of 104


4. Choose Enter

5. In case of using the fashion-variant, the message: You have entered a different article type; select the views you require appears

6. Doubleclick on one of the the proposed characteristics profile(s)..

7. Choose Back

8. Select the characteristics you wish from the variant matrix.

9. Choose Next Screen

10. On the Create article: Basic Data screen, make the following entries:


Article Description


EAN category

’IE’ Screen area: Standard Values for Entering Variant EANs

Alternative Unit

EA

Assign EANs int.

Set the indicator

11. Choose Button Variant EANs

12. The system message the EAN will be determined internally on the basis of the EAN category displays.

13. Choose Enter.

14. Choose Back.




Purchasing Org.

'1000'



PCS-V202 (Food)

>Vendor 2

© SAP AG of 104


17. Choose Enter



Purchasing Group

‘100’

Net Price <Value>

19. Choose Tab Sales


21. On the Areas of Validity screen, make the following entries:


Sales Org. '1000'

Distr. Channel

‘30‘

22. Choose Enter

23. On the Create article: (Sales) screen, make the following entries:


PP Det Seq. ‘01‘

SP Determ. Seq.

‘01‘

Final Price <Value>


‘X‘

24. Choose Tab Logistics: DC



RP Type 'ND'

Supply Source

‘1‘

Avail. Check 'KP'

26. Choose Tab Logistics :Store


© SAP AG of 104



RP Type 'ND'

Supply Source

‘4‘

Avail. Check 'KP'

28. Choose Save

29. The system message The Generic Article ……. Will Be Created With Its Variants displays.

7.1.2 Process the Generic Article

Procedure











3. Choose View ‘Listing’

4. Choose Enter



Assortment Grade

Blank (Maximum Assortment)

List. Procedures For Store Listing

'B1' Check the listing period for the listing processes

© SAP AG of 104



Listng Procedures for Distr. Centers

'B1' Check the listing period for the listing processes


Set Flag

List Supplying Site

Set Flag


7. Choose Tab Sales


9. On the Areas of Validity screen, make the following entries:


Sales Org. '1000'

Distr. Channel

‘10‘

10. Choose Enter



Final Price <Value>


‘X‘

12. Choose Save

13. The System Message The Generic Article....Will Be Changed With Its Variants Displays.

The Sales Price Calculation Is Described In More Detail In The “Pricing” Process.

7.1.3 Reference Handling For Generic Article Variants

Use

© SAP AG of 104


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 scenarios 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 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 will not be copied to the variants. The fact that the variants have different data in this case means 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







© SAP AG of 104





Article GENERICARTxx001

3. Choose View Basic Data

4. Choose Enter

5. Check the entry for the transportation group 0001 in the area of the Internal logistics data.

6. Choose Back













10. Choose Enter

11. On the Change article: Basic Data screen, make the following entries:


Transport a-tion Group

’0003’(Container)

12. Choose Save

13. The system message The generic article ……. will be changed with it variants displays.

© SAP AG of 104


14. Now display the article data for the variant again.











17. Choose View ‘Basic Data’

18. Check the entry for the transportation group in the area of the Internal logistics data

19. Choose Enter

20. Choose Back

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.

7.2 Matrix Maintenance for Generic Articles

UseThe 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.

7.2.1 Price Matrix for Variants of Generic Articles

UseThe 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.

© SAP AG of 104

http://help.sap.com/


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 very 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 the 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 7.1.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











Sales Org. ’1000’

Distribution ’10’

© SAP AG of 104



Channel

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



Change The Sales Price 1st Row/2nd Column

Any Entry

Save sales pr. conds

‘X’ Screen area: Generic Article Default Values

11. In the screen group generic article default values set the copy rules “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.






© SAP AG of 104







Sales Org. ’1000’

Distribution Channel

’10’

19. Choose Views Basic Data and Sales

20. Choose Enter

21. In Sales tab screen area Current Price, check Curr.FinalPrc has been changed to new one.

22. Choose Back.

7.2.2 Matrix Handling For Master Data Fields For The Generic Article

UseIn 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 7.1.1 can be changed as you wish at variant level.

Procedure









© SAP AG of 104




3. Select View "Basic Data“

4. Choose Enter

5. Doubleclick On The Field Transportation Group…

6. The system message changes to field ’’trans.group’’ lead to different areas of validity displays.

7. Change the field transportation group 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










Article GENERICARTxx00x The variant you changed in step 7.

14. Select View "Basic Data“

15. Choose Enter

16. Check the Field Transportation Group has been changed to new one.

© SAP AG of 104


8 PrepackA 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.

8.1.1 Create A Prepack

UseThe 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 7).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.

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










Article PREPACKARTxx



HAWA or FRIP (Foods excl. Perishables)

Fashion

Hardgoods

Food

© SAP AG of 104


Material Group

MC11141 (Fashion)

MC14402 (Hardgoods)

MC12003 (Food)

‘MC-GA’

Artl. Category 'Prepack'

3. Select View ‘Basic Data’

4. Choose Enter

5. The system message the reference article has a different article type displays.

6. Choose Continue

The characteristics profile is suggested based on the merchandise category.

7. Choose Continue

8. On the Create article: Basic Data screen, make the following entries:


Description ’Article Description’

9. Choose Components

10. On the Create component assignment for Prepack Article screen, make the following entries:


Gen. Article PCS-01-Art111 (Fashion)

PCS-02-LKP111 (Hardgoods)


> Article 1

Specified Total

‘Quantity’ (used for matching of Component Quantity)

11. Choose Enter

12. On the Create component assignment for Prepack Article screen, make the following entries:


Quantity ‘Quantity’ Maintain a quantity for every component

13. Choose Enter

© SAP AG of 104


14. Choose Back




Purchasing Org.

‘1000‘



PCS-V202 (Food)

>Vendor2

17. Choose Enter



Purchasing Group

‘100‘

Net Price Value





Sales Org. ‘1000‘

Distr.Channel ‘30’

22. Choose Enter

23. On Create article Sales screen, make the following entries:


PP Det. Seq. ‘01‘

SP Determ. Seq.

‘01‘

Final Price <Value>


‘X‘


© SAP AG of 104




RP Type ‘ND‘

Supply Source

1

Avail. Check ‘KP‘

26. Choose Tab Logistics: Store



RP Type ‘ND‘

Supply Source

‘4‘


28. Choose Save

29. Message: Article Created.

8.1.2 Process the Prepack

UseWhen listing a prepack only the header article is listed, the components will not be listed.

As a goods receipt has to be posted for the prepack in this process (see section 8.1.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.






Business role (name) SAP_BP_RT_MASTERDATA-S (Retail Master Data

© SAP AG of 104


Manager)




Article PREPACKARTXX

3. Select View Listing

4. Choose Enter



Assortment Grade

Blank

LP For Stores

B1

LP For Distr. Centers

B1


Set Flag

List Supplying Site

Set Flag


7. Choose Tab Sales




Sales Org. '1000'

Distr. Channel

'10' Direct Sales

10. Choose Enter



© SAP AG of 104


Final Price <Value>


‘X‘

12. Choose Save

13. The system message Sales pricing has been performed or changed displays.

14. The system message The article... Changed with its variants displays.

The sales price calculation is described in more detail in the “pricing” process.



SAP Menu Master Data Assortment/Listing Evaluations For Article Listing Conditions



Business role (name) SAP_BP_RT_NONSEASBUYER-S (Retail Non-Seasonal Purchaser)

Business role menu Non -Seasonal Purchase Management Assortments Assortments, selection lists

16. On the Listing Conditions screen, make the following entries:



Display Variants/Components

'X'

17. Choose Execute

As the prepack article is dealt with like a single article no components are displayed.

8.1.3 Determine Valuation Prices for Prepack Components

Use

© SAP AG of 104


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.



SAP Menu Master Data Pricing Environment Value Assignment Price Determination Change Price

Transaction Code MR21


Business role (name) SAP_BP_RT_PRICING-S (Retail Pricing Manager)

Business role menu Pricing Report Price Change

2. On the Price Change Overview screen, make the following entries:


Company Code

'1000'

Site 'M001'

3. Choose Enter

4. On the Price Change Overview screen, make the following entries:


Article ' Article1 -001'’ Article1 -002'' Article1 -003'' Article1 -004'' Article1 -005'' Article1 -006'' Article1 -007'' Article1 -008'

Enter the article numbers of the variants i.e. the number of the generic article ( see <article 1> in 2.2) with the 3 digit suffix

New Price ‘25’ Each Article

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.


Use

© SAP AG of 104


The prepack particularity will be displayed for the goods receipt (GR).

The customizing settings have been defaulted so that the prepack is automatically transferred to its components when the goods receipt is posted. In order to see the stock changes check the stock overview before posting a goods receipt.

In the process described below, you post a goods receipt without any reference for the prepack article.

Procedure



SAP Menu Merchandise Logistics Inventory Management Environment Stock Stock Overview

Transaction Code RWBE



Business role menu Pricing Report Stock Overview

2. On the Stock Overview screen, make the following entries:


Article (Delete Other Restrictions)

PREPACKARTXX

3. Choose Execute

4. Now post the goods receipt.



SAP Menu Logistics Retailing Merchandise Logistics Logistics Execution Inbound Process Goods Receipt For Purchase Order, Order, Other Transactions Goods Receipt For Other Activities

Transaction Code MB1C


Business role (name) SAP_BP_RT_NONSEASBUYER-K (Retail Non-Seasonal Purchaser – Power User)

Business role menu Non -Seasonal Purchase Management Planning Other Goods Receipt

© SAP AG of 104


6. On the Enter Other Goods Receipts: Initial screen, make the following entries:


Movement Type

‘501‘

Site 'M001‘

Storage Location

‘1000‘

7. Choose Enter

8. On the Other Goods Receipts: New Items screen, make the following entries:




PCS-V201 (Food)

>Vendor 1


Quantity ’Quantity’

UnE ‘EA‘

9. Choose Enter

10. Choose Save

11. Message: Document…Posted.

12. Check the new stock of the variants and the stock of the prepack article










Article Components for

© SAP AG of 104


(Delete Other Restrictions)

PREPACKARTXX

15. Choose Execute

The stock of components or prepack articles changes depending on the phase in which the prepack is created (see documentation for customizing settings “settings for the structured article in the ‘goods receipt’ transaction”). From our example, the stock of components should have increased.

9 Sales Set

UseA 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 often 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.

9.1.1 Create a Sales Set

Procedure








2. On the Create Article: Initial screen, make the following entries:


Article SALESSETxx



HAWA or FRIP (Foods

Fashion

Hardgoods

Food

© SAP AG of 104



excl. Perishables

Material Group

MC11152 (Fashion)

MC14203 (Hardgoods)

MC12003 (Food)

>MC-Vk-Set

Article Category

'Sales Set'


4. Choose Enter

5. Choose Continue when the pop-up for the assignment of a characteristic profile appears.

6. Message: the reference article has a different article type

7. On the Create Article: Basic Data screen, make the following entries:


Article Description



9. On the Create Component assignment for Set Article screen, make the following entries:


Component PCS-01-ART146 (Fashion)



Component qty

’Quantity’




Component qty

’Quantity’

10. Choose Enter.

11. Choose Back

© SAP AG of 104


12. Choose Save

13. Message: Article……Created.

9.1.2 Process a Sales Set

UseMaintaining sales sets, logistics views (DC and stores), POS views and listing views.

Procedure








2. On the Change Article: Initial screen, make the following entries:


Article SALESSETxx

Sales Org. ‘1000’

Distr. Channel

‘30’

Distr. Center Blank

Store Blank

3. Choose view ’Sales, Logistics : DC, Logistics: stores, POS’

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:


© SAP AG of 104



SP Determ. Seq.

‘01‘ Choose ENTER

Final Price <Value> Or Let The System Determine The Value From The Planned Markup


‘X‘

7. Choose Enter



RPType 'ND'

Supply Source

'1'

Avail. Check 'KP'

9. Choose Tab Logistics: Store


RP Type 'ND'

Supply Source

'4'

Avail. Check 'KP'

10. Choose Enter

11. The POS view is displayed in change mode

12. Choose Save

13. Message: Article Changed.

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).




© SAP AG of 104








Article SALESSETxx

16. Choose View Listing

17. On the Change Article: Listing screen, make the following entries:


Assortment Grade


Lp For Stores 'B1'

Lp For Distr. Centers

'B1'


Set Flag

List Supplying Site

Set Flag




21. On the Areas Of Validity screen, make the following entries:


Sales Org. '1000'

Distr. Channel

'10'

22. Choose Enter

© SAP AG of 104




Vendor R100

Final Price<Value> Or Determine From The Planned Markup


‘X‘

24. Choose Save

25. Message: Article ….. Changed.

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.










Article SALESSETxx


X

28. Choose Execute

9.1.3 Goods Receipt Without References

UseTo 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.

© SAP AG of 104


In the process described below you post a GR without any reference for the components.

Procedure



SAP Menu Merchandise Logistics Logistics Execution Inbound Process Goods Receipt For Purchase Order, Order, Other Transactions Goods Receipt For Other Activities



Business role (name) SAP_BP_RT_NONSEASBUYER-K (Retail Non-Seasonal Purchaser - Power User)

Business role menu Non -Seasonal Purchase Management Planning Other Goods Receipts



Movement Type

‘501‘

Site 'M001‘

Storage Location

‘1000‘

3. Choose Enter



Article PCS-01-ART146 (Fashion)




UnE ‘EA’

Article PCS-01-ART111001 (Fashion)


PCS-01-Art201001 (Food) Maintain the Best-Before-Date if

© SAP AG of 104


required


UnE ‘EA‘

5. Choose Enter

6. Choose Save


9.1.4 Set Up Structured Article

UseIn order 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



SAP Menu Merchandise Logistics Inventory Management Goods Movement Transfer Posting

Transaction Code MB1B


Business role (name) SAP_BP_RT_STOREMANAGER-E (Retail Store Manager)

Business role menu In-store Inventory Management Inventory Adjustment Transfer Posting

2. On the Enter Transfer Posting: Initial screen, make the following entries:


Movement Type

‘317‘

Site 'M001‘

Storage Location

‘1000‘

3. Choose Enter

4. On Enter Transfer Posting: New Items screen, make the following entries:


© SAP AG of 104


Article SALESSETxx


UnE ‘EA‘

5. Choose Enter

6. Choose Post (Save)


8. Access The Transaction Choosing One Of The Following Navigation Options


SAP Menu Transfer Posting Display

Transaction Code MB03


Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Article documents Display Article Document (MB03)

9. Document Number Is Displayed

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.










© SAP AG of 104


Article (Delete Any Other Restrictions)

SALESSETxx






PCS-01-Art201001 (Food)

13. Choose Enter

14. Choose Execute

10 DisplayA display is a quantity of single articles or variants of one or more generic articles that are generally 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.

10.1.1 Create Display

UseThe 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





© SAP AG of 104





2. On the Create Article: Initial screen, make the following entries:


Article DISPLAYxx



HAWA or FRIP (Foods excl. Perishables

Fashion

Hardgoods

Food

Material Group

MC11152 (Fashion)

MC14402 (Hardgoods)

MC12003 (Food)

Artl Category 'Display'


4. Choose Enter

5. Choose Continue to confirm the proposal for the characteristics profile



Article Description



8. On the Create Component Assignment for Display Article screen, make the following entries:





Component Qty

’Quantity’


PCS-06-ART433

© SAP AG of 104



(Hardgoods)


Component Qty

’Quantity’




Component Qty

’Quantity’

9. Choose Enter

10. Choose Back




IE Screen Module Units Of Measure/Ean/Dimensions 1st Row, Column Ct

12. Choose Enter

The System Message The EAN will be determined internally on the basis of the EAN category displays.

13. Choose Enter

14. Choose Yes

15. Message: Article. Created

10.1.2 Process Display

UseMaintain The Purchasing, Sales, Logistics, POS And Listing Views.

Procedure

© SAP AG of 104











Article DISPLAYxx

Purch. Org. '1000'



PCS-V201 (Food)

>Vendor1

Sales Org. '1000'

Distr. Channel.

'30'

Distr. Center Blank

Store Blank

3. Choose View 'Purchasing, Sales, Logistics: DC, Logistics: Stores, POS’

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:


Purchasing Group

‘100‘

Net Price <Value>

7. Choose Enter

© SAP AG of 104





SP Determ. Seq.

‘01‘

Final Price Enter <Value> Or Choose The Calculated Value Based On The Mc Markup


‘X‘

9. Choose Enter

10. On the Change Article: Logistics DC screen, make the following entries:


RP Type ‘ND‘

Supply Source

‘1‘

Avail. Check ‘KP’

11. Choose Enter

12. On the Change Article: Logistics Store screen, make the following entries:


RP Type ‘ND‘

Supply Source

‘4‘


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



© SAP AG of 104









Article DISPLAYxx

17. Choose View 'Listing’'

18. Choose Enter

19. On the Change Article: Listing screen, make the following entries:


Assortment Grade


Lp For Stores 'B1' Check the listing period

Lp For Distr. Centers

'B1' Check the listing period


Set Flag






Sales Org. '1000’

Distr. Channel

‘10‘

24. Choose Enter

25. On the Sales screen, make the following entries:

© SAP AG of 104



Final Price Enter <Value> Or Choose The Calculated Value Based On The Mc Markup


‘X‘

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.










Article DISPLAYxx


'X'

29. Choose Execute


UsePost 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.

© SAP AG of 104


Procedure1. Access the transaction choosing one of the following navigation options:


SAP Menu Merchandise Logistics Logistics Execution Inbound Process Goods Receipt For Purchase Order, Order, Other Transactions Goods Receipt For Other Activities



Business role (name) SAP_BP_RT_NONSEASBUYER-K (Retail Non-Seasonal Purchaser – Power User)

Business role menu Non -Seasonal Purchase Management Planning Other Goods Receipts



Movement Type

‘501‘

Site 'M001‘

Storage Location

‘1000‘

3. Choose Enter





PCS-V201 (Food)

>Vendor1

Article DISPLAYxx


UnE ‘EA‘

5. Choose Enter

6. Choose Save


8. Access The Transaction Choosing One Of The Following Navigation Options

© SAP AG of 104










Article (Delete Any Other Restrictions)

DISPLAYxx










10. Choose Enter

11. Choose Execute

In our example, the stock of components should have increased.

12. Check the article movements after processing the Good Receipt.



Transaction Code Logistics Logistics Execution Inbound Process Goods Receipt for Purchase Order, Order, Other Transactions Display Article Document

Transaction Code MB03


© SAP AG of 104


Business role (name) SAP_BP_RT_WAREHOUSESPECIAL-S (Retail Warehouse Clerk)

Business role menu Warehouse Management Article Documents Display Article Document (MB03)

14. Open the selection screen and enter your display article.

15. Choose Enter

16. Choose the article document for your display article.

17. Choose Enter

The article movement 319 ‚Split structured material’ shows the details for the display article and its components.

11 Department Store/Shop Concept

UseThe 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.

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.

© SAP AG of 104


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 usually 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.

The creation of a department store (with an existing plant profile) and the creation of a new shop to a department store is described in general.

Procedure



SAP Menu Logistics Retailing Master Data Site Data Department Store/Shop Create Department Store

Transaction Code WRFDEP01



Business role menu Site Department Store/Shop Create New Department Store


Field Description User action and values Comment

Department Store

‘D100’

Plant Profile ‘P120’

3. Choose Continue

4. Confirm the pop-up on reference site with yes

5. Press Enter

6. Maintain a description and the mandatory fields like language and country (in the address data).

7. Press Save.

8. Confirm Customer data and copy Customizing for site by choosing ENTER.

9. Press Save.

© SAP AG of 104


10. Confirm the pop-up screen: Classification with Yes.

11. Choose Back.

12. Choose Confirm in Department Store Create: Copy Customizing for site screen.

Depending on the general client settings a customizing request will have to be created. You can check whether the store has the correct store type by accessing table T001W-checking field STORETYPE (1 Department Store) for your new department store (transaction se16)



SAP Menu Master Data Site Data Department Store / Shop Create Shops via Department Store

Transaction Code WRFSHOPDEP



Business role menu Site Department Store/Shop Create Shops w/Initial Dept. Store



Department Store

D100

Hierarchy B1

15. Choose Create Shops

16. Create a shop by entering the following data:


Shop name e.g. ‘Sports shop’

Shop ‘S006’ In case internal number assignment is used, the shop ID is assigned automatically

Category Existing category e.g. ‘Sports’

You could have created a new category node ‘Sports’ in the article

© SAP AG of 104


hierarchy beforehand, if you do not want to create a shop for an existing category node

Opening date <Current date>


18. Select the appropriate row and choose Set up shop data

19. For further maintenance for your shop choose Det. Maint.

20. Maintain the general shop master data:


Sales area – Unit of measure

e.g. ‘1000’ – ‘M2’ The sales area is the selling area

21. Choose Back to leave the detail maintenance


Depending on the general client settings a customizing request will have to be created.

You can display a list of all shops assigned to a department store using transaction WB03 (or the SAP Menu) using the following search options: tab strip: Shop over Department Store, entering your department store as Superior Dept. Store and choose Start Search.

12 Price Level Groups

UsePrice 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 will be described in general.

Prerequisites

© SAP AG of 104


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



SAP Menu Master Data Price Level Groups Create

Transaction Code WRF_PRGRP01



Business role menu Price Level Group Price Level Group Creation of Price Level Groups

2. Select the price level group category that is relevant for article hierarchies

3. Maintain a name

4. Choose Enter

5. Maintain a description and price level currency

6. Maintain the price levels and the price band categories



The price level group can now be assigned to a hierarchy node within your article hierarchy.

© SAP AG of 104