Master Data in SAP for Retail, IRT310 Col16

Este material aborda a gestão de dados mestres no SAP S/4HANA Retail for Merchandise Management. O conteúdo cobre desde a visão geral das estruturas organizacionais até a manutenção de parceiros de negócios, sites e agrupamentos de artigos.

Além disso, apresenta o gerenciamento de sortimentos, artigos simples e estruturados, variantes e artigos genéricos, fornecendo uma base prática para lidar com os principais elementos de dados mestres no varejo. Esse conhecimento é essencial para assegurar consistência, eficiência e precisão nas operações de gestão de mercadorias.

1. IRT310
Master Data in SAP for Retail
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 16
Course Duration: 5 Days
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

2. SAP Copyrights, Trademarks and
Disclaimers
© 2025 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries. Please see https://
www.sap.com/corporate/en/legal/copyright.html for additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary
software components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical
errors or inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind, and SAP
SE or its affiliated companies shall not be liable for errors or omissions with respect
to the materials. The only warranties for SAP SE or SAP affiliate company products
and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any
course of business outlined in this document or any related presentation, or to
develop or release any functionality mentioned therein. This document, or any related
presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject
to change and may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned not to
place undue reliance on these forward-looking statements, which speak only as of
their dates, and they should not be relied upon in making purchasing decisions.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

3. Typographic Conventions
American English is the standard used in this handbook.
The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control
Example text
Window title
Example text
© Copyright. All rights reserved. iii
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

4. iv © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

5. Contents
vii Course Overview1 Unit 1: Organizational Structures in Retail2 Lesson: Organizational Structures in Retail13 Exercise 1: Set Up Default Values19 Exercise 2: Display the Organizational Structures27 Unit 2: Business Partners28 Lesson: Business Partners43 Exercise 3: Create a Vendor and Display related Customizing
Settings
55 Unit 3: Sites56 Lesson: Sites - Configuring and Maintenance67 Exercise 4: Configure a Site Profile and Display Customizing
Settings for Sites
73 Exercise 5: Create a Site85 Unit 4: Article Groupings86 Lesson: Classification and Merchandise Categories93 Exercise 6: Display and Extend the Merchandise Category
Hierarchy
103 Exercise 7: Explain the Correlation between Sites and
Merchandise Categories
110 Lesson: Article Hierarchy117 Exercise 8: Enhance the Article Hierarchy129 Unit 5: Assortment Management131 Lesson: Assortment149 Exercise 9: Create General Assortments 158 Lesson: Listing Procedures167 Exercise 10: Analyze Listing Procedures174 Lesson: Layout179 Exercise 11: Create a New Layout and Layout Modules189 Lesson: Assortment List195 Exercise 12: Display the Customizing Settings for an
Assortment List and Generate an Assortment List
© Copyright. All rights reserved. v
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

6. 205 Unit 6: Single Articles206 Lesson: Retail Article Master — Create a Single Article219 Exercise 13: Create a Single Article229 Exercise 14: Define a new Global Trade Item Number (GTIN)236 Lesson: Configuring the Article Master245 Exercise 15: Configure the Article Master259 Unit 7: Article Maintenance261 Lesson: Article Fast Entry271 Exercise 16: Use the Maintenance Group and Create a Core
Article Master
277 Exercise 17: Use Article Monitor and Mass Maintenance281 Exercise 18: Explain the Article Copy286 Lesson: Global Data Synchronisation293 Exercise 19: Create an Article from an Existing Catalog (Pricat
Inbound)
300 Lesson: Article List305 Exercise 20: Create an Article List 310 Lesson: Article Discontinuation317 Exercise 21: Execute an Article Discontinuation327 Unit 8: Generic Articles and Variants328 Lesson: Characteristics337 Exercise 22: Maintain Characteristics346 Lesson: Creating a Generic Article355 Exercise 23: Create a Generic Article365 Exercise 24: (optional) Create a Generic Article with 3
Characteristics
375 Unit 9: Structured Articles376 Lesson: Structured Articles389 Exercise 25: Maintain Displays in Logistical Processes393 Exercise 26: Optional: Manage Full Products and Empties Stock
vi © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

7. Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
●Data Manager
●Project Manager
●Application Consultant
●Development Consultant
●Data Consultant
●Industry / Business Analyst Consultant
●Super / Key / Power User
●Business Process Owner/Team Lead/Power User
●Developer
●Industry Specialist
●Solution Architect
© Copyright. All rights reserved. vii
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

8. viii © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

9. UNIT 1
Organizational Structures in
Retail
Lesson 1
Organizational Structures in Retail
2
Exercise 1: Set Up Default Values
13
Exercise 2: Display the Organizational Structures
19
UNIT OBJECTIVES
●Show that the organizational structures and their assignments, which are supported by
SAP Retail, are a basic requirement for working in SAP Retail
© Copyright. All rights reserved. 1
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

10. Unit 1
Lesson 1
Organizational Structures in Retail
LESSON OVERVIEW
Business Example
You have decided to implement the Industry Solution SAP for Retail. You have analyzed your
current organizational structures and discussed mapping them onto the corresponding
structures in SAP Retail. You now create the organizational units and their assignments in
SAP Retail.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Show that the organizational structures and their assignments, which are supported by
SAP Retail, are a basic requirement for working in SAP Retail
SAP Retail Overview
From an application point of view, we are going to focus on the SAP S/4HANA Retail for
merchandise management (on premise) solution capabilities in this course. For simplification
reasons, this solution is referred to as SAP Retail in our IRT310 course. SAP Retail core
features and functions for example include master data management, buying, logistics, sales,
and store operations.
Note:
In the retail industry, specific terms differ from the standard terms used in other
lines of business. The following terms are used synonymously in this document:
Table 1:
Standard Terms in Lines of Business SAP RetailMaterial, Product ArticleMaterial group, Product group Merchandise categoryPlant, Location SiteSupplier Vendor
Organizational Structures
Flexible organizational units in SAP Retail make it possible to map even complex
organizational structures. A large number of organizational units makes it possible to map the
legal and organizational structure of a retail company from different business viewpoints.
Many organizational units are also data retention levels, which means that, when there are
several organizational units like this, different data can be stored for each one.
2 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

11. SAP Retail is client-capable. A client is a corporate group that can subdivide into subsidiaries.
In SAP Retail, organizational units can be set up for the individual departments of a company.
This means that the organizational units reflect the subdivision of a company from a business
viewpoint in SAP Retail.
Figure 1: Organizational Structures
The variable organizational structures in the SAP system offer the following advantages:
●The flexibility to be able to map complex company structures
●Separate logistical views (purchasing, sales and distribution), the managerial accounting
view and the external accounting view
●The option of cross-company-code processing
Organizational structures are maintained in Customizing (Implementation Guide). They must
be created individually and then assigned to each other.
The most important organizational units in SAP Retail are listed below.
Lesson: Organizational Structures in Retail
© Copyright. All rights reserved. 3
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

12. Figure 2: Organizational Structures in Financial Accounting and Controlling
Organizational structures are used to:
●Map the individual parts of a company (for example, Purchasing, Sales)
●Ensure that all subareas of the company are linked together in the organizational structure
A client corresponds to a corporate group, which can be subdivided into subsidiaries.
From an (external / legal) Financial Accounting point of view, an enterprise is subdivided into
company codes. A company code is an independent organizational unit that balances
accounts in accordance with legal requirements. It can be divided into business areas. This
means that all the transaction figures and financial statistics (for example, P&L) can be
managed and analyzed for each business area.
In a central organization, one uniform, usually a maximum chart of accounts is created at
corporate group level and this is then valid for all company codes. In a decentralized
organization, the chart of accounts is assigned on company code level.
Each valuation-relevant transaction creates a Financial Accounting document, which lists the
G/L accounts posted to and the details of the posting.
The controlling area is the organizational unit used to subdivide the business organization
from a cost accounting standpoint. Cost centers are organizational units within a controlling
area and represent a defined location of cost incurrence. They can be defined based on
functional requirements, allocation criteria, physical location, or responsibility for costs.
The operating concern is an organizational unit in (internal) accounting (Controlling), which
structures an enterprise from the Profitability Analysis point of view. You can calculate an
operating profit or contribution margin for the individual market segments that are defined by
a combination of classifying characteristics (such as merchandise category, country, or
distribution channel). Several controlling areas can be assigned to one operating concern.
Unit 1: Organizational Structures in Retail
4 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

13. Profitability Analysis represents a market-oriented approach with the aim to provide your
sales, marketing, product management and corporate planning departments with information
to support internal accounting and decision-making.
The profit center is an organizational unit in accounting that reflects a branch or division of a
company that is accounted for independently for the purpose of profit calculation. Retailers
often use the organizational level of profit center in order to measure and compare profit and
losses of their stores from a finance perspective.
Figure 3: Organizational Structures: Valuation
A site can be a store, a distribution center, or a production location. In SAP Retail, the site is
the selling and inventory management organizational unit. Every site belongs to just one
company code.
Stocks are updated by goods movements on both a quantity and value basis. The relevant
G/L accounts in accounting, which are affected by this transaction, are determined and
posted to via automatic account determination.
A valuation area is the organizational unit for value-based inventory management. In SAP
Retail, the valuation area must always correspond to a site. Inventory management on a
value-only basis is carried out at valuation area level.
Every site is a valuation area in SAP Retail. This is already determined when the system is set
up as a Retail system and it is unchangeable. The valuation area does not appear on the
screen, it is controlled internally.
Franchisees
Generally: Franchisees can be represented in the central SAP Retail system as sites or
customers, and the decision depends on the actual business requirements.
The tighter the integration to the Retailer’s business processes, the more likely a site master
will be created for a franchisee. If only a common marketing concept is in place, but otherwise
the franchisee acts as a more or less fully independent customer, a customer master record
may be sufficient.
A franchisee can be modeled as a site:
Lesson: Organizational Structures in Retail
© Copyright. All rights reserved. 5
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

14. If Financial Accounting is not active for the franchisee, all franchisees can be assigned to one
company code. This company code can be considered a "dummy" company code.
If Financial Accounting is active for the franchisee, it must be assigned to its own (active)
company code. All the stores of a franchisee are assigned to the appropriate company code.
You can activate Inventory Management for a franchisee’s site(s), regardless of whether FI is
active or not (own active or dummy company code). You must make the relevant Customizing
settings for updating quantities and values for each material type. When inventory
management is active, for example the standard SAP Retail replenishment functions can be
set up for the franchisee.
Note: If the retail store operations apps should be used for merchandise management
functions by the franchisee, franchisees must be modeled as sites.
A franchisee can be modeled as a customer:
If e.g. financial accounting and inventory management should not be supported in the central
SAP Retail system for the franchisee. The franchisee’s stock can be separated against own
stock using customer consignment.
Logistics
Figure 4: Organizational structures in Purchasing
A purchasing organization procures merchandise for several sites and negotiates purchase
conditions with the vendors. This is the business unit legally responsible for all purchasing
activities, and serves as a data retention level (key field) for purchasing-related master data
and conditions, as well as in business documents, e.g. a purchase order. Authorizations for
master data maintenance and purchasing management are assigned per purchasing
organization.
A purchasing organization can be assigned to one company code. If this is the case, the
purchasing organization can only purchase for sites that belong to the same company code.
A reference for one purchasing organization can also be applied to another purchasing
organization, so that the conditions, contracts and purchasing info records can be used
together.
Unit 1: Organizational Structures in Retail
6 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

15. A purchasing group consists of one or more buyers and in that represents a purchasing
department. Purchasing groups are responsible for maintaining master data and control data,
and for operational purchasing activities. Authorizations can be assigned to each purchasing
group individually. The purchasing group is not a data retention level.
* A purchasing area can (optionally) be used as a connecting link between the purchasing
organization and the purchasing group. It is then used as an additional hierarchy level for
reporting. However, it is not a data retention level. In order to map this connecting link, one
purchasing area is assigned to a combination of a purchasing organization and one or more
purchasing groups in Customizing. (IMG: → Materials Management → Purchasing → Maintain
Purchasing Area, and: … → Purchasing Area Determination).
Figure 5: Organizational Structures: Inventory Management
To be able to keep track of the goods flow in the company, article stocks must be managed on
a quantity basis in the system. Stocks are managed for each individual site and storage
location.
In SAP Retail, the site is the selling and inventory-managing unit. A site can be a store or a
distribution center.
The storage location is an organizational unit that makes it possible to differentiate between
stocks in a site. In a distribution center, different storage locations are used to map various
logistical functions: For example, a full warehouse management storage location, a cross-
docking storage location, a lean-WM managed storage location. A distribution center is
usually subdivided into more than one storage location to map the physical structure, for
example, to distinguish between a high-rack storage building and an outside warehouse, and
to allow separate inventory management for each storage location. Individual storage
locations of a distribution center can be connected to a warehouse management system
using a warehouse number. This is a 3-digit number in case of SAP Warehouse Management
(WM), and a 4-digit number in case of SAP Extended Warehouse Management (EWM).
Usually a store has one storage location, but an additional storage location could for example
be defined for a separate sales section, such as an outdoor stock sales area (camping articles,
garden furniture).
Lesson: Organizational Structures in Retail
© Copyright. All rights reserved. 7
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

16. In the distribution center, you can differentiate between stocks of an article within one storage
location on the basis of batches. It is also possible to maintain expiration dates, for example
through the relevant information on the storage unit (does not require batch management
then).
Figure 6: Inventory Management in the Distribution Center
eWM: extended Warehouse Management
MM: Materials Management
Transactions that cause a change in stock and the resulting stock updates are entered in the
system in real time, enabling physical stock levels to be mirrored exactly in the inventory
management.
There are three different organizational structure options in a distribution center: inventory
management on the storage location (MM-managed storage location), inventory
management on the storage location with a storage location that is managed by a lean WM,
and inventory management on the storage bin with a WM-managed storage location =
Warehouse Management system.
For complex distribution centers, the Warehouse Management system allows stock to be
differentiated up to storage bin level. This means that structures, such as those of a high rack
storage area, can be displayed.
The Warehouse Management system is integrated into the whole system by connecting a
storage location to a warehouse number. If, for example, a goods receipt is posted to the
inventory management, an action to put away the goods is triggered in the Warehouse
Management. A complex warehouse structure is managed under a warehouse number.
Various partial warehouses, the organizational and technical attributes of which differ, are
defined as storage types, such as the goods receipt area, goods issue area, high rack storage
area and picking bin. The individual storage bins are defined in a storage type. They are the
Unit 1: Organizational Structures in Retail
8 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

17. smallest organizational units that can be called in the system. They can be called using
coordinates such as 05-04-03 for aisle 05, stack 04, level 03. When an article appears on a
storage bin, it is flagged as quant.
Transport orders are used to transport the articles within the warehouse (for example, from
the goods receipt area to the storage bin).
The Lean WM is a warehouse structure with which transport orders can be used as pick
orders, even in simply structured warehouses. Transport orders can be created for deliveries
(excluding goods receipts or goods issue), even if storage bins are not managed in the WM.
Inventory management occurs at storage location level only. The system does not use quants
to update the stock data at storage bin level, but display fixed bins for information only.
You can use the Lean WM if you want to pick deliveries using transfer orders in a warehouse
that you do not manage with the Warehouse Management system.
Figure 7: Organizational Structures in Sales
The sales organization is an organizational unit in logistics, which subdivides the company
according to the requirements of sales and distribution.
Every sales organization represents a selling unit in the legal sense and is, for example,
responsible for product liability and any customer's rights of recourse. It is also responsible
for the sales and distribution of the article, and negotiates sales conditions. You can use sales
organizations to divide your market into regions, for example, into countries. A complete
business transaction in sales and distribution is always managed in a sales organization.
In SAP Retail, a sales organization can be assigned to a purchasing organization. For
statistical purposes, this may be of interest.
A sales organization can reference another sales organization at sales document type level.
This means that the sales organization can then use the same sales document types as
defined for the referenced sales organization.
A retailer can sell products through various channels, which are represented in the system as
distribution channels. Possible distribution channels for sales to the consumer include, for
example, various store chains, digital commerce channels (such as e-commerce, mobile
commerce), or mail order. In combination with the distribution channel, the sales organization
Lesson: Organizational Structures in Retail
© Copyright. All rights reserved. 9
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

18. forms a distribution chain. This means, the distribution channel is assigned to a sales
organization. The distribution chain for example serves as both reporting and data retention
level, for example master data, and sales price conditions can be defined on this level.
In SAP Retail, the distribution chain category of a distribution chain determines, if it will be
used to supply sites or wholesale customers respectively, or to supply consumers. For
example, assignments of a distribution chain to a site can be deleted in customizing (IMG: →
EnterpriseStructure →Assignment →Salesand Distribution →AssignSales Organization —
Distribution Channel — Plant). The related distribution chain will then also be removed from
the site in the master data (WB03).
References to other distribution chains in the same sales organization can be created for a
distribution chain. This means that customer and article master data, as well as condition
data can be accessed from the distribution chain that is being referenced.
A division must be defined, although SAP Retail does not use it in the retail functions.
Together with the division, a distribution chain forms a sales area. If just one division is
created (in general recommended for SAP Retail), then the sales area is functionally almost
identical to the distribution chain for retail.
Copy Function
Figure 8: Organizational Structures: Copy Function
In the SAP System, you have the option of processing existing organizational structures. The
following functions are available:
●Copy:
Use this function if you want to create a new organizational unit and want to use the
existing settings as a template. For example, you can copy the distribution channel in
customizing (IMG: → EnterpriseStructure →Definition →Salesand Distribution
→Define,copy, delete, check distribution channel → Copy, delete, check distribution
channel).
Unit 1: Organizational Structures in Retail
10 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

19. ●Delete:
Use this function if you want to delete an existing organizational unit with all dependent
entries.
●Check:
Use this function to check all the settings for an existing organizational unit.
Please note that only the system settings (in Customizing) are copied or deleted. Master data
is not included in this process. However, for example when using the copy function, the
relevant master data assignments are copied as well.
If you only want to process mandatory activities in the system settings, for example to reduce
manual configuration efforts, then you must use the copy function to create the new
organizational units. This is the only way you can make sure all the necessary system settings
will be created.
Lesson: Organizational Structures in Retail
© Copyright. All rights reserved. 11
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]

20. Unit 1: Organizational Structures in Retail
12 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]