Sap retail master data

©SAP AG 2005

Masterdata

IBU Retail&Wholesale, SAP AG

©SAP AG 2005

Article HierarchyDepartment store/ Shop ConceptArticle Master Data - EnhancementsCharacteristic Value GroupsDiscontinuationArticle listFollow-up / Replacement articlePrice level groups

©SAP AG 2005


© SAP AG 2005

Business Concept of Article Hierarchy

An Article Hierarchy can be used to hold any given hierarchical Article Grouping e.g. a combination of articles in groups from asales perspective

The Article Hierarchy can be linked to shops to portray the presentation of certain sub-ranges on the sales floor

Optional Integration to Planning, Operations and Reporting on different levels of aggregation

© SAP AG 2005

Business Requirements

Use in Operations and Planning

Active and Planned versions

Time-phased assignments of Articles and Structures

Articles to receive multiple assignments

Parallel existence of Article Hierarchies for different distribution channels

Maintaining of Attributes like person responsible, price range, roles, strategies etc.

Article assignment using the article master transactions

Visibility in SAP BW

Reporting

…

© SAP AG 2005

Example for an Article Hierarchy

Trend

Women

Regular Sport

EspritEterna MEXX

T-Shirt Trousers

Hugo Boss

Suit Shirt

Company

Men

Business

ShirtTies

Children

… …

….

….

…

Brand

Area

Article groups

Theme

Company

© SAP AG 2005

Integration

Purchasing list

Planning

OTB

BW

Article Master / Pricat

Assortment

Price Planning Workbench

…

©SAP AG 2005


© SAP AG 2005

Business Scenario

In the scope of the department store concept, two new business objects were introduced: the “department store” and the “shop”.

For the already existing object “site” and the site category “store”the two objects were defined.

As soon as it is necessary for a store to be divided into departments, e.g. to enable procurement processes to be controlled, the departments can be modelled as “shops” and the store as a “department store” that builds the organisational frame for the various “shops”. The operational processes take place on the “shop” basis.

Usually, the “department store” appears only as part of the F4-help.

© SAP AG 2005

Illustration of Department Store/Shop: Definition

Department store = Organisational unit that unifies the various goods groups of the company under one umbrella. The department store has no inventory-managing character for goods that are intended for the consumer.

Shop = a grouping of goods of various article groups that ought to be presented to the consumer in a consistent overall picture. The shop is part of a department store.

Dep.store Cologne

Sweets Menswear WomenswearSportsdepDistrib.centre south

Type DC Type StoreStore category _

Type StoreStore category

Shop

Type StoreStore category Dep. store


Shop


Shop

© SAP AG 2005

Characteristics of the Store Category

Shop

Inventory-managed

To plan

Analysable

Independent profitability analysis

Central object in retailing

Department store

Aggregation level for the dependent shops

Analysable

Can be used for the administration of the consumables

Dep.store

Store Munich

Abteilung Kosmetik

Warenartikel

. . …….. . . …. …

. . …….. . . …. …

. . …….. . . …. …

. . …….. . . …. …

5T73 München

© SAP AG 2005

New Functionalities/Add-ons

Site master add-on:1. Possibility to maintain a department store2. Possibility to maintain a shop with assignment to a department store

New maintenance dialogues for shops1. Simplified creation of shops via a department store2. Simplified creation of shops via a category

Supporting business processes 1. Closing and locking of several shops2. Changing of the supply relationship for several shops3. Changing of the supply region for several shops4. Assignment of new merchandise categories to several shops

Site search add-on

By default changes of department stores and shops happen in the site master maintenance

©SAP AG 2005


©SAP AG 2005

Article CopyCore Master DataIntegrated Mass ChangeArticle MonitorMaintenance GroupsNew Fields in Article Master

©SAP AG 2005


© SAP AG 2005

Article Copy: Benefits

With the new Article copy function articles can easily be created

Several segments can be copied to already existing articles, but only those segments that are newly added

No existing data will be overwritten

Manual change/ overwriting can be done in the MM42 or the integrated mass change

© SAP AG 2005

Article Copy: Use

All field values for the selected segments are copied

Copy of a source article

The volume of the copy can be defined by limitation of the segments to be copied; e.g. info records, listing conditions or prices

All field values of the source article are copied without variances on variant or site level

Copy of a source article without deviant fields

Individual control of the segments to be copied

©SAP AG 2005


© SAP AG 2005

Core Master Data: Benefits

Uncomplicated, ad hoc creation of new articles

Creation or further processing of newly created articles in the calling transaction

Can be called as an independent transaction or out of the supporting transactions

Grouping of only those fields of an article in a maintenance group that are relevant for the use in a specific transaction

© SAP AG 2005

Core Master Data: Use

Just enough data to carry out the calling transaction e.g. purchase orderCan obtain a separate creation status

Consideration of field-specific settings Only fields are copied from the reference article that are marked as copy relevant in the maintenance group settings

Only maintenance of core data

Optional field control of maintenance groups

Completion of core master data out of the Article monitor

E.g. attributes in the basic data like season, brand etc.All fields that are necessary for use in other transactions are filled

©SAP AG 2005


© SAP AG 2005

Integrated Mass Change: Benefits

New mass maintenance dialogue, where next to general article data also additional data like info records can be changed

New and comfortable possibility to change huge amounts of existing articles (creation of new articles and article segmentsis not possible)

Use of maintenance groups to ease the editing

© SAP AG 2005

Integrated Mass Change: Use

Mass change of existing articlesCreation of new articles is not possible

By use of a maintenance group one can control which fields are to be shown while editing articlesMaintenance group itself can be changed temporarily, thoughMaintenance group can be set as default user-specifically

Integrated mass change

Use of maintenance groups

©SAP AG 2005


© SAP AG 2005

Article Monitor: Benefits

New and comfortable possibility to select articles via several restrictions

Potential use of maintenance groups to vary the view

For completion direct access to the integrated mass change or article maintenance (MM42)

© SAP AG 2005

Article Monitor: Use

E.g. select the core master data that has been created in purchasing or assortment planningThe selection screen offers various restriction possibilities

The selected articles can easily be completed in the WRFMASSMAT or MM42 Direct change of the article type possible

Eases the selection of specific articles

Direct access to integrated mass change or article maintenance

© SAP AG 2005

Article Monitor: Use 2

The selected articles are displayed in a list, whose columns are fixed by the maintenance group

Use of a maintenance group vary the view

An article list can be generated from the selected articles, printed or mailed

Generate article list

©SAP AG 2005


© SAP AG 2005

Maintenance Groups: Benefits

Facilitate the editing or view of articles as the number of fields shown can be limited

Several maintenance groups can be created per application

The field groups, that together build the maintenance group, are logically grouped and can be complemented by customer individual fields

Default values can be assigned to all fields

© SAP AG 2005

Maintenance Groups: Use

Facilitates the editing or view of articles as the number of fields can be limitedDefault values can be assigned to all fields

Ease the maintenance of articles

The selected articles are displayed in a list, whose columns are fixed by the maintenance groupOnly the required fields necessary in the calling transaction are to be maintained

Use of a maintenance group eases the editing of articles

Field groups group the fields that need to be maintained together, this is preset in customizing and can be complemented by customer individual fields

Field groups ease the maintenance

©SAP AG 2005


© SAP AG 2005

New Fields in Article Master

Basic Data

Screen DataAssignment to article hierarchy Fashion grade, brand

Listing

Assortment type

Logistics

Sales

Price band category

Purchasing ( purchasing info record)

Transport chain

Staging time

Color, size1, size2, free characteristic

Care code, fiber code 1-5

Creation status

Across purchasing group

Goods issue processing time

Consignment control

©SAP AG 2005


© SAP AG 2005


Maintenance of characteristic values and their groupings via an independent tool

Better menu navigation within the search help and the possibility to select a group of values

Customer-specific attributes are shown in the search help to ease the selection of characteristic values

Improved selection of characteristic profiles in article creation

© SAP AG 2005

Business Requirements 2

Typing of characteristics (“Color”, “Main Size” and “Second Size”) to make characteristic-based processes possible (e.g. Price Planning Workbench)

Redundant storage of color and size characteristic values in the article master (table MARA)

Goal: Huge quantities of characteristic values can be better handled

© SAP AG 2005

Characteristic Value Maintenance

…….

……

STAN5692001267-TCRed3Merlot0003

STAN7834001227-TCRed2Beaujolais0002

STAN2324001214-TCRed1Bordeaux0001

Customer-specific Value 3


e.g. Pantone Color


e.g. Analyzing Color

SortingDescriptionValue

Updated in the basic data field in article

master (table MARA)

One of the customer-specific values can be updated in the article

master (table MARA) via BAdI

Maintained in Customizing

© SAP AG 2005

Characteristic Value Grouping

Sizes

Big Sizes

Regular Sizes

Winter

Autumn

Egg WhiteRedBright BlueNavy

MC11411

MC11412

MC11413

545658

WhiteBright RedPinkAqua

MC11111

MC11112

MC11113

Summer

Spring

ColorCharacteristic

Merchandise Categories

Characteristic Values

The assignment of characteristic values to merchandise categories

is optional

©SAP AG 2005


© SAP AG 2005


Fashion-related selection criteria of articles to be discontinued e.g. season, article list, article hierarchy nodes

Additional checks in discontinuation like generic articles, follow-up/replacement articles …

Checks can be reduced e.g. for manufacturing materials

User-specific worklists for discontinuation

Automated processing of worklists

Display of worklists offersAdditional sorting criteriaFiltersDiscontinuation logs

©SAP AG 2005


© SAP AG 2005

Article List: Benefits

New maintenance application for article lists and the article list hierarchy

Article lists are a pre-defined amount of articles

They can be utilized in various applications

They are available in the F4-help as part of the “search for article number”

Differentiation between dynamic and static article lists

© SAP AG 2005

Consist of both the selection criteria, the dependent articles and show those articles that have been assigned manually

Article List: Use

Consist of stored selection criteria, with which the actual article data can be determined each time

Dynamic article lists

Static article lists

© SAP AG 2005

Article List: Use

E.g. use a query for bestseller/slowseller articles and export this list to SAP ECC

Article lists can be exchanged with a BW

To create and maintain article lists, the creation of exactly one article list hierarchy is necessary.Each article list is assigned to exactly one end node in the hierarchy.The hierarchic grouping is concise and facilitates the selection of a specific article list.

Article list hierarchy

©SAP AG 2005


© SAP AG 2005

Business Concept

A follow-up article substitutes its original article permanently, whereas a replacement article comes into place only temporarily

New (mass maintenance) dialog to assign follow-up/ replacement articles

Different assignment types can be defined in customizing

Assignments can be scheduled

For follow-up articles, priorities can be defined

Assignments can be maintained on different levels: all sites, assortments, single site

Reorganisation of outdated assignments possible by a background job

©SAP AG 2005


© SAP AG 2005

Price level groups

Price level groups are created with a price pattern and their pricelevels

To every price level, a price band category has to be assigned

© SAP AG 2005

Price level groups

Price level groups can be assigned to a merchandise categoryand/or an article hierarchy node

The price pattern can be used for reporting sales data in BW

© SAP AG 2005

Copyright 2005 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, 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, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation 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. MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Documents

Sap retail master data