Professional Documents
Culture Documents
Bonn � Boston
1 Introduction ................................................................. 17
4 Planning ....................................................................... 93
Acknowledgment . ........................................................................ 13
Preface ......................................................................................... 15
1 Introduction .................................................................. 17
4 Planning ........................................................................ 93
10
11
Appendices
Index.............................................................................................. 335
12
1 Introduction
The SAP offering for retail companies can take on different forms depend-
ing on the company’s needs. At its heart lies the SAP Retail retailing sys-
tem, which is accompanied by a range of software solutions, each with
its own, retail-specific purpose. The aim of this book is to illustrate how
these retail solutions interact with each other to give the reader a better
understanding of the solution offering.
E-business refers to online shopping, that is, sales on the Internet. End
customers can browse electronic catalogs on the Internet, select prod-
ucts, place an order, and pay immediately online. A lesser known term is
17
Principles for To keep up with the constantly growing demands of the market, every
success company must pay attention to the fundamental principles for success
and take action accordingly. These fundamental principles for success
are:
EE The customer is only happy if goods are available in the right place at
the right time and for the right price.
EE A company must be able to respond flexibly to changes in demand
patterns to retain its customer base and win new customers.
EE It is only possible to respond promptly to delivery delays if they are
known of in good time.
EE Working capital can only be freed up for important investments if
stock levels can be reduced through shorter lead times and procure-
ment cycles.
SAP AG helps its customers meet all of these challenges with innovative
technology so they can operate as part of a complex economic network
and respond effectively to market demands.
18
The aim of this book is to provide you with a comprehensive overview of Overall
SAP software for the retail sector by presenting the existing components understanding of
SAP for Retail
and their architecture and examining how they interact from a technical
perspective. This book will explain the most important business pro-
cesses in each of the components.
We have a particular image of you, the readers, in mind. This image has
helped us write this book, and we hope it will make it easier for you to
read.
19
We also assume that you already use SAP software or are currently decid-
ing whether to use SAP solutions. Regardless of whether you are using
our software already or are still at the assessment stage, this book will
assist you in understanding the software offering.
You would like to obtain an overview of the SAP offering for the retail
sector and discover new concepts and technologies. In this respect, this
book is also ideally suited to IT decision-makers, project managers, and
any other interested parties.
SAP partner Another important target group is our partners, who want an overview
companies of the offering to help identify any niches and develop products that
complement the portfolio.
To make sense of the content of the book, you need to have a basic tech-
nical understanding; knowledge of SAP products such as SAP ERP, the
Business Suite, or SAP NetWeaver® is an advantage.
Modular structure You can read the book chapter by chapter or skip over certain chapters
depending on your preference. If you read chapter by chapter, you will
experience a journey through the components of the SAP software offer-
ing for the retail sector. To establish a link to the real world of business,
we have included typical questions from both the consumer and retailer
perspectives in each chapter.
These questions constitute a guide to the book and enable readers to skip
over certain chapters and focus on the parts that are particularly relevant
for them. In this sense, the book is—to the greatest possible extent—
modular in structure to allow you to choose the parts you read according
to your preferences and needs.
20
EE Chapter 1 Introduction
What is the object of the book and who is it aimed at?
EE Chapter 2 SAP for Retail – An Overview
How do the components relate to each other? This chapter takes a
broad look at the architecture of the SAP software for the retail sec-
tor. It presents the ways in which SAP NetWeaver, SAP ERP, and SAP
Retail are interrelated, offers a brief outline of the history of SAP for
Retail, and provides some initial insight into the capabilities of the
components.
EE Chapter 3 Master Data, Forecasts, Analyses, and Connecting Appli-
cations
How do manufacturers and retailers know that they are dealing with
the same article? How do retailers know which articles they have to
offer, how many, when, and at what price? How can retailers analyze
and increase their operational efficiency and speed of response to
consumer behavior?
This chapter introduces you to the features of master data administra-
tion that are particular to the retail sector. The emphasis here is on the
apparel segment, whose master data presents specific requirements.
Furthermore, the chapter explains the foundations for determining
requirements and forecasting. In Section 3.6 The Analysis Solution –
SAP NetWeaver Business Intelligence, you become acquainted with
SAP NetWeaver BI and the possibilities presented by analytical appli-
cations. We also explain something that is essential to the understand-
ing of data flows, namely, SAP NetWeaver Process Integration, which
plays a pivotal part in connecting systems.
EE Chapter 4 Planning
How can you plan in order to satisfy demand as accurately as possi-
ble? How do you set prices that guarantee a decent margin but remain
affordable for consumers? How do you plan sales promotions and
assortments that will win you new retail customers and satisfy exist-
ing customers? How do you plan price reductions for articles?
This chapter presents the most important planning options, from
strategic planning and store planning to merchandise and assortment
planning.
21
EE Chapter 5 Purchasing
How can you best map relationships with vendors in the system?
How do you handle order proposals created automatically by the sys-
tem? When do you accept them, and when do you have to modify
them? What logistical factors must be taken into account in purchas-
ing? SAP Retail provides special functions tailored to the needs of the
retail industry that are not available in other SAP ERP components
(for example for durable goods, foodstuffs, fresh produce, and fash-
ion articles). Pricing, including free-goods discount and other forms
of discount, is also dealt with here.
EE Chapter 6 Order Processing – Supply Chain Management
Which factors contribute to optimal order processing with on-time,
complete, and error-free deliveries of goods to the consumer? How
do you arrive at the ideal requirement quantity? How can you keep
costs to a minimum?
Costs in the supply chain might, for instance, arise from logistics costs
such as those incurred for procurement and transportation, but also
from storage, aging, wear and tear, and breakage. Stock inventory also
result in costs such as interest on capital, depreciation, and insurance.
Logistics is a particularly important point for fast-moving consumer
goods. This chapter describes the functions that are significant for the
retail sector, in particular, when managing supply chains.
EE Chapter 7 Multichannel Retailing and Customer Service
What happens to purchasing data? Despite the large number of retail-
ers that operate online only, the traditional store still has a consider-
able part to play in multichannel retailing. Today’s consumers still
want to see, touch, and try goods in the real world. That said, as
consumers become increasingly familiar with the Internet, they will
use it more regularly for purchases in the future. The Internet has
changed not only the way in which consumers make purchase deci-
sions but also their expectations in terms of personalized information
and services. Nowadays, consumers want to decide themselves where
and when they shop. This is the very reason e-business has taken off
so quickly—with no end to the growth in sight. This chapter also
addresses the subject of managing customer relationships and dem-
onstrates how software can be used to improve customer retention.
22
Enjoy!
Heike Rawe
23
Other analytical applications are concerned with SAP MAP (see Chapter
4 Planning) and supply chain analytics. Supply chain analytics provides BI
Content for SAP Forecasting and Replenishment. The analytical applica-
tions for inventory management and stock ledger analytics supply data
for store profitability statements (for example, ending inventory and cost
of goods sold), for management reporting (for example, sales, margins,
ending inventory), and for other business processes such as open-to-buy
or pricing.
Analytical CRM Analytical CRM links customer information with information about mate-
and data mining rial groups and articles. Analytical CRM on the basis of SAP CRM offers
retail companies increased clarity of the degree of customer retention
and customer lifetime value, for example, with ABC loyalty analyses.
Furthermore, the methods of analytical CRM can be used to tap cross-
selling potential with assortment and sales analyses; customers and store
comparisons are possible with cluster analyses, and campaigns can be
measured in terms of their success.
Decentral system Many retail companies have IT landscapes that consist of isolated sys-
landscapes tems and datasets: POS systems are linked to back office solutions, which
are interlinked themselves. Such disparate system landscapes impede
cross-system business processes. Financial management, inventory track-
ing, and tracing in logistics and analyses are often associated with consid-
erable investment and personnel costs. It is not unusual for connections
between systems to be so inflexible that any adjustments to company-
specific requirements lead to long-lasting cost increases.
SAP NetWeaver PI This is where SAP NetWeaver Process Integration (SAP NetWeaver PI, also
known as SAP Exchange Infrastructure or SAP NetWeaver XI) comes
into play. This application acts as a central storage point for integration
knowledge from all connected systems. It removes the need to search
84
85
Figure 3.16 will help you gain a clearer understanding of the architecture
of SAP NetWeaver PI.
SAP
Systems
3rd Party
Integration Integration Integration Systems
Repository Directory Server
(IR) (ID) (IS) 3rd Party
Middleware
Component
Marketplace/
Business
Partner
Design
Interfaces and The first step is to draft the design in the Integration Repository of the
mappings Integration Builder, which includes the required interfaces and map-
pings. The interfaces can either be described as new, system-indepen-
dent interfaces and then be implemented as proxies (outside-in devel-
opment) or be based on existing functionality (inside-out development).
86
Configuration
The next step is the configuration of the Integration Builder in the Inte-
gration Directory, which involves setting up the collaborative process for
an actual system landscape. Design-time objects can be used as templates
for this purpose. In addition, conditions for selecting recipients (routing)
and mappings to the recipient interfaces can be defined.
The message flow in the Integration Server is then managed during run-
time on the basis of the configuration. The message flows themselves can
be monitored centrally.
The central storage locations for the design time (Integration Repository)
and the configuration time (Integration Directory) are processed in a
single tool, the Integration Builder.
Content from the System Landscape Directory serves as a basis for the
design, configuration, and runtime of SAP NetWeaver PI. This SAP prod-
uct is a central directory of descriptions of products, their software com-
ponents, logical and technical systems, and the product versions installed
on these systems.
Runtime
The SAP NetWeaver PI runtime consists of several components, which
are shown in Figure 3.17.
The central component is the Integration Server, which receives messages Integration Server
from the application systems (Integration Engine and Adapter Engine)
and forwards them on the basis of the central configuration (Integration
Engine). The message format used by the Integration Server is based
on XML, which has become an established exchange format, not only
on the Internet. Other standards and tools build on the XML standard
and make it easier to use, for example, XSD, XSLT, and Xpath. XSLT, for
instance, can be used to define mappings that are needed because two
87
Central Monitoring
Integration Server
Integration
Business Process Engine
Directory
Integration Engine
System
Landscape
Adapter Engine
Directory
XI XI
RosettaNet, … Protocol
Protocol
Local Partner
IDocs Connectivity
Integration Engine RFCs
File Kit
Proxy Runtime Apps of
DB 3rd Party
Business
JMS Apps Apps of
Proxy Partner
(small)
SAP Business
SAP Web AS 6.20 System Partner
All applications and systems exchange messages with each other by way
of the Integration Server because defining mappings in pairs (system to
system) would not be effective.
Integration Engine The Integration Engine receives messages by means of the message pro-
tocol and executes central services such as routing and mapping for the
messages it receives. The Integration Engine is also used for messaging
in application systems (Local Integration Engine) with the proxy runtime
(outside-in development).
Adapter Engine Adapters are used to connect other systems to the Integration Server.
With the exception of the IDoc adapter and plain HTTP adapter, all
88
adapters use the Adapter Engine, which provides the central services for
messaging, queuing, and security handling. Each adapter converts calls
or messages from a sender into the message format for the Integration
Engine. Conversely, the adapter also receives messages from the Integra-
tion Engine and converts them for the recipient. Therefore, instead of
having separate communication options for every combination of appli-
cation systems, one conversion into the respective message protocol is
all that is needed to enable communication with the Integration Server.
Expressed simply, the adapters and the Integration Engine restrict them- Business Process
selves to forwarding messages to the recipient(s) and, if necessary, per- Engine
EE A2A
For A2A integration, the standard shipment comes with adapters to
connect SAP systems (both by means of proxies and with RFC and
IDocs) and non-SAP systems, referred to as third-party applications
(for example, File, DB, JMS, SOAP, HTTP).
EE B2B
For B2B connections to business partners, the standard shipment
comes with adapters such as the RNIF adapter (RosettaNet) and the
CIDX adapter (Chem eStandards). In addition, smaller business part-
ners can be connected using what are known as partner connectivity
kits. These enable smaller business partners that do not have SAP
NetWeaver PI to exchange data with a business partner that uses SAP
NetWeaver PI.
EE Third party
SAP also works with partners that develop adapters for third-party
applications
89
Out-of-the-box In many cases, this enables out-of-the-box integration without any need
integration for complex developments. All Integration Repository objects are pro-
vided as part of the PI Content. In addition to interfaces, these objects
also include mappings, configuration templates for message flow, and
templates for specific adapter configurations that can be used to config-
ure customer-specific system landscapes with the support of a wizard.
SAP partners can also develop and offer PI Content. An overview of the
PI Content currently offered by SAP can be found in the SAP Developer
Network (SDN) at https://www.sdn.sap.com/irj/sdn.
90
BI, SAP NetWeaver MDM, and SAP Forecasting & Replenishment. SAP
NetWeaver PI always comes into play when data is exchanged in different
formats and when large amounts of POS data are to be processed in a cost-
effective way together with the PIPE, as demonstrated by volume tests.
On the basis of PI Content alone, POS integration allows the SAP POS Point of sale
solution, SAP POS and SAP Enterprise POS, to be connected to an SAP integration
R R R R R
R
Master data is sent from SAP Retail to the POS solution, and transaction
data flows back into the PIPE, which is part of SAP POS Data Management.
In addition, the PIPE and SAP Retail are still linked so that data that is not
aggregated and not based on SAP NetWeaver PI can be transferred.
91
Master data PI Content allows master data systems to be integrated with SAP
management NetWeaver Master Data Management Release 5.5 so that master data can
integration
be consolidated, harmonized, and managed centrally (see Figure 3.19).
File
Storage
Legacy
SAP ERP SAP SRM SAP CRM SAP Retail SAP BI
System
R R R R R R
R
SAP NetWeaver PI
First, reference data (fixed values and Customizing values) are sent once
to the SAP NetWeaver MDM server. After this initialization has taken
place, master data can be sent continuously from connected systems cen-
trally by means of SAP NetWeaver PI to the MDM server, where it can be
consolidated and harmonized. The cleaned master data then passes back
through SAP NetWeaver PI to the connected systems and into an SAP
NetWeaver BI system so that central analyses can be performed.
92
dates confirmed (for example, the vendor’s staging date) are compared
with the planned target dates.
If the target and actual dates differ to such an extent that a predefined
tolerance is exceeded, actions can be triggered automatically (for exam-
ple, a cancellation threat can be issued to the vendor) or the need for
manual intervention can be flagged. In the latter case, the user can make
adjustments to the order in a workbench provided especially for this
purpose.
150
Logistics Invoice
Verification
Check Basedon
Assignment Test
Goods Receipt
no Goods Receipt
Target ActualCost
Invoice Settlement
?
Payment ?
Payment
The assignment test function can still be used as a background process Assignment test
step prior to invoice verification. This function is used to ensure that the
system only starts invoice verification if open goods receipts exist for an
invoice. An assignment test is quicker than a complete invoice check in
the background, because the system is required to process less data from
the database (for example, no article data is required) and perform fewer
checks and evaluations.
Another option presented by logistics invoice verification is based on the Evaluated receipt
concept of evaluated receipt settlement (ERS). Here, the system creates a settlement (ERS)
target invoice based on the articles and quantities entered in the goods
receipt, and the amount determined is paid to the vendor. The extent
151
152
Invoices that are identified as correct are transferred to financial account- Correct invoices
ing in the form of a posting record, where they are then posted. If finan-
cial accounting is run in another SAP system or an external system, the
posting records are transferred by remote function call (RFC).
Retailers and their business partners meet at regular intervals (for exam- Volume-rebate
ple, at the start of each year) to negotiate rebate arrangements for the arrangements with
validity period
forthcoming period (usually that year). The prices for individual articles
can be set directly, or end-of-period rebates can be agreed for one or
more articles. The results of these negotiations are entered in the system.
It is possible to backdate the commencement of a rebate arrangement,
which means sales in the past can be assigned to a new arrangement by
performing a retrospective compilation of statistics.
153
335
e-business, 17
E-commerce, 290 H
E-marketing, 289
Embargo check, 165 Handling unit management, 205
Employee data, 272 Handling units, 189, 205
Enhancement Package, 38 Head office, 252
Enterprise service bundles, 307 Server, 246, 251
E-service, 291
ES Workplace, 312
European Union, 167 I
Evaluated receipt settlement, 151
Extensible Markup Language (XML), 87 Identification standard, 42
Extensible Stylesheet Language for Import and export control, 165
Transformation (XSLT), 87 Inbound interface, 243
Indirect purchase requisition, 174
Industry extension, 38
F In-store inventory management, 269
In-store processor, 257
Finding storage bins, 203 Integrated warning system, 229
Flow-through, 173 Integrating handhelds, 264
Merchandise-driven, 183 Integrating POS data, 261
Recipient-driven, 183 Integration directory, 87
Forecast-based planning, 176 Integration engine, 88
Forecast optimization, 127 Integration knowledge, 84
Forecasts, 69, 123, 272 Integration repository, 86
Foreign trade, 196 Integration server, 87
Franchise, 264 Intra-European-Union flows of goods,
167
Intranet, 260
G Inventory management, 192
Investment buying, 140
Generic article, 47 Invoice verification, 150
Global Data Synchronization, 59
Global transport management, 172
Goods issue, 188 J
In SAP EWM, 204
Posting, 190 J2EE, 250
Goods movements, 188 Just in time, 172
Goods receipt, 184
336
O
Offline capability, 257 Q
OLAP, 76
Operational Assortment Planning and Quality management, 204
Control (OAPC), 118, 136 Quantity optimizing, 140
Optimization procedure, 127 Quants, 205
Orchestration, 298
337
338
Y
U
Yard management, 202
Usability of the article, 193
339