Vous êtes sur la page 1sur 59

Master Guide

SAP for Retail


Business Suite 2005
Document Version 1.20 December 2006

SAP AG Neurottstrae 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

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. These materials are subject to change without notice. These materials 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. Any Java Source Code delivered with this product is only to be used 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. Documentation in the SAP Service Marketplace MaxDB is a trademark of MySQL AB, Sweden. You can find this documentation at the following Internet address:
service.sap.com/instguides

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.

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 Library document classification: PUBLIC

Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

by SAPs Support Services and may not be modified or altered in any way.

Typographic Conventions
Type Style Example Text Represents 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 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. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons
Icon Meaning Caution Example

Note Recommendation Syntax

EXAMPLE TEXT

Example text

Example text

<Example text>

EXAMPLE TEXT

Contents Overview

Contents
SAP for Retail ............................................................................................................................ 5 Overview ................................................................................................................................ 5 History of Changes ................................................................................................................ 7 Getting Started .......................................................................................................................... 8 The Main SAP Documentation Types ................................................................................... 9 Related Information ............................................................................................................. 11 Related Master Guides ........................................................................................................ 12 SAP Solution Manager ........................................................................................................ 12 Important SAP Notes ........................................................................................................... 13 Business Scenarios of SAP for Retail ..................................................................................... 14 Allocation ............................................................................................................................. 14 Assortment Management..................................................................................................... 15 Category Business Planning ............................................................................................... 16 Demand Modeling and Forecasting..................................................................................... 17 Forecasting & Replenishment ............................................................................................. 19 Instore Customer Relationship Management ...................................................................... 21 In-Store Workforce & Task Management ............................................................................ 23 Markdown Planning & Optimization..................................................................................... 25 Merchandise and Assortment Planning............................................................................... 28 Merchandise and Assortment Planning (Integrated) ........................................................... 30 Multi Channel Loyalty Program Management ..................................................................... 32 Point of Sale GM.................................................................................................................. 34 Point of Sale TE................................................................................................................... 37 Promotion Planning & Optimization..................................................................................... 39 Purchase Order Management ............................................................................................. 42 Requirements Planning and Replenishment ....................................................................... 45 Retail Price Planning & Optimization................................................................................... 47 Returns Authorization .......................................................................................................... 50 Store Analytics..................................................................................................................... 53 Store Connectivity................................................................................................................ 55 Store Merchandise Management ........................................................................................ 58

SAP for Retail Overview

SAP for Retail


Overview
SAP for Retail creates a competitive advantage for retailers by enabling them to achieve maximum profitability by driving down their costs and increasing their revenues through collaborative processes tailored to their customers' needs. The processes are easy to use and deliver a quick ROI. SAP for Retail provides web-enabled applications in a fully integrated system that creates value for retailers in important areas of their business. It helps retailers build their business on a solid transactional backbone, integrate different sales channels, better understand customer preferences, and manage their supply chain more efficiently. SAP for Retail brings all the speed, efficiency, and flexibility of the Internet to every aspect of your enterprise. SAP for Retail focuses your entire value chain -- from the way you manage customer contacts and fulfillment to how you maintain inventory and analyze performance -on your customers, generating measurable benefits in cost, revenue, and strategy. Impact on Cost By seamlessly integrating merchandise planning, demand forecasting, allocation, and replenishment functions, you ensure a more responsive, flexible supply chain, enhancing efficiencies and minimizing expenses. Our powerful, easy-to-use Web-based store portal gives you more accurate point-ofpurchase data and helps increase employee efficiency, keeping down training and operating costs. Impact on Revenue Multichannel relationship and transaction management, coupled with automated marketing and customer self-service, helps you boost sales, increase shopping frequency, raise customer retention, and more effectively attract new customers. Assortment, shelf management, mass customization, and cross-selling functions let you cut stock levels and improve shelf space efficiencies, giving you extended product lifecycles and greater profitability. Impact on Strategy Sophisticated reporting and analysis capabilities -- plus integrated merchandising, customer, financial, and employee data -- give you deeper insights into your customers and your operations, allowing you to adapt faster to market changes.

This SAP for Retail Master Guide provides a central starting point for the technical implementation of the following business scenarios of SAP for Retail: Allocation Assortment Management Category Business Planning Demand Modeling and Forecasting Forecasting & Replenishment Instore Customer Relationship Management In-Store Workforce & Task Management Markdown Planning & Optimization Merchandise & Assortment Planning

SAP for Retail Overview Merchandise and Assortment Planning (Integrated) Point of Sale GM Point of Sale TE Promotion Planning & Optimization Purchase Order Management Requirements Planning & Replenishment Retail Price Planning & Optimization Returns Authorization Store Analytics Store Connectivity Store Merchandise Management

You can find an overview about the whole functionality of SAP for Retail in the solution map: service.sap.com/bmet SAP Business Maps IndustrySpecific Maps Retail.

The business scenarios that are presented here serve as examples of how you can use SAP software in your company. The business scenarios are only intended as models and do not necessarily run the way they are described here in your customer-specific system landscape. Ensure to check your requirements and systems to determine whether these scenarios can be used productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors before going live.

SAP for Retail History of Changes

History of Changes
The Master Guide is updated on a regular basis in SAP Service Marketplace at: service.sap.com/instguides

Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace right before the installation. The following table provides an overview on the most important changes that were made within the latest versions. Master Guide Version 1.00 (October 2005) 1.10 (December 2005) 1.20 (December 2006) Business scenario Forecasting and Replenishment added New Business Scenarios added: Demand Modeling and Forecasting In-Store Workforce & Task Management Markdown Planning & Optimization Point of Sale GM Point of Sale TE Promotion Planning & Optimization Retail Price Planning & Optimization Returns Authorization Promotion Planning & Management Retail Price and Revenue Management Vendor-Managed Inventory Workforce Deployment - Limited Access for Manager Workforce Deployment - Open Access for Manager Workforce Deployment with ERP Important Changes

Obsolete Business Scenarios removed:

Getting Started History of Changes

Getting Started
This Master Guide provides the information about which components and which guides are required during this process. Getting Started [page 7] contains valuable information about using this document and related information (documentation and SAP Notes) crucial to the installation and upgrade. Business Scenarios of SAP for Retail [page 14] contains the following information for each business scenario: A short overview about the business scenario Minimal system landscape A software component matrix for each business scenario that provides the information which components the business scenario uses and if the corresponding component is mandatory or optional Where you can find further information about the business scenario

You can find the most current information about the technical implementation of SAP for Retail and the latest installation and configuration guides on the SAP Service Marketplace under: service.sap.com/instguides We strongly recommend that you use the documents available here. The guides are regularly updated.

Getting Started The Main SAP Documentation Types

The Main SAP Documentation Types


Several documents have been created to assist you in installing, implementing, operating and upgrading your SAP solutions. The Solution Master Guide (this document) is the first document you obtain. Although strongly related to each other, the different documentation types should help you solve problems on different levels at different solution phases. The following figure shows an overview of the most important documentation types that you need in the various phases in the life cycle of an SAP solution. Documentation types in the software life cycle

Implementation

Operation

Upgrade

SAPterm

SAP Library

Master Guide Component Installation Guide Security Guide Configuration Documentation Implementation Guide (IMG) Solution Management Guide

Upgrade Master Guide Component Upgrade Guide

Release Notes

Delta and Upgrade IMG

Cross-Phase Documentation
SAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many definitions and glossary entries in English and German. To use SAPterm, visit SAP Service Marketplace at service.sap.com/sapterm. The SAP Library is a collection of function- and process-oriented documentation for SAP components. It is located on SAP Help Portal at help.sap.com. SAP Library also contains Business Scenario Descriptions. These are found on SAP Service Marketplace at service.sap.com/ibc. The Implementation Guide (IMG) is a tool for configuring the SAP system to meet customer requirements. Its structure and documentation are component-oriented. It is located in the SAP Easy Access menu of the SAP system under Tools Customizing IMG. The Security Guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for the SAP NetWeaver technologies like SAP Web Application Server (SAP Web AS). This document contains general guidelines and suggestions about system security. Other technologies and individual applications have a Security Guide of their own.

Getting Started The Main SAP Documentation Types The current version of the Security Guide is located on SAP Service Marketplace at service.sap.com/securityguide.

Implementation
The Component Installation Guide describes the technical implementation of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. The Component Installation Guides for the different components can be found on SAP Service Marketplace at service.sap.com/instguides. The Configuration Documentation is contained in the SAP Solution Manager. SAP Solution Manager is a tool with various functions, one of its main functions being the configuration of SAP solutions and Business Scenarios. It contains IMG activities, transactions, and so on, as well as documentation.

Production Operation
The Solution Operations Guide is the starting point for operating an SAP solution. The guide refers users to the tools and documentation that are needed to carry out various tasks, such as monitoring, backup/restore, master data maintenance, transports, and tests. It also refers users to other documents, for example the SAP Library, the Master Guide, and the Component Management Guides. The current version is located on SAP Service Marketplace at service.sap.com/instguides.

Upgrade
The Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and followup of an upgrade. It also refers to other documents, such as the Component Upgrade Guides and SAP Notes. Instead of an Upgrade Master Guide, there may be several Business Scenario Upgrade Guides or a Solution Upgrade Guide for earlier shipments of the Business Scenarios of an SAP solution. The current Version is located on SAP Service Marketplace at service.sap.com/instguides. The Component Upgrade Guide describes the technical upgrade of an SAP component, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration. The current version is located in the SAP Service Marketplace at service.sap.com/instguides. Release notes are documents that contain short descriptions of new features or changes in an SAP component since the previous release. Release notes about ABAP developments enable the SAP system to generate delta and upgrade IMGs. The current version is located on SAP Service Marketplace at service.sap.com/releasenotes or in the SAP menu of the SAP system under Help Release information. Upon reviewing this description of the supplementary information sources at your disposal, you will be ready to get started.

10

Getting Started Related Information

Related Information
The following list contains links to crucial information for implementing this solution. List of Related Documentation Content Information about technical and release planning issues on SAP components Information about the latest version of installation and upgrade guides for SAP components Information about SAP Notes Information about released platforms Information about sizing, calculation of hardware requirements (such as CPU, disk and memory resource) with the Quick Sizer tool Information about network security SAP Security Guide Information about network integration Information about high availability Information about creating error messages Performance Map Documentation on SAP Help Portal Location service.sap.com/pam

service.sap.com/instguides

service.sap.com/notes service.sap.com/platforms service.sap.com/sizing

service.sap.com/securityguide

service.sap.com/network service.sap.com/ha service.sap.com/message service.sap.com/performancemap help.sap.com/

11

Getting Started Related Master Guides

Related Master Guides


This Master Guide is based on Component Master Guides. You will find detailed information about the relevant components in the following documents: List of Related Master Guides Content mySAPTM ERP 2005 SAP NetWeaverTM 2004s mySAPTM Supply Chain Management Location service.sap.com/erp-inst mySAP ERP 2005 service.sap.com/installNW2004s service.sap.com/instguides mySAP Business Suite Solutions mySAP SCM Using SAP SCM 4.1 Server service.sap.com/instguides mySAP Business Suite Solutions mySAP CRM SAP CRM 5.0 service.sap.com/instguides mySAP Business Suite Solutions mySAP SRM Using SAP SRM Server 5.0

mySAPTM Customer Relationship Management mySAPTM Supplier Relationship Management t

SAP Solution Manager


SAP provides the SAP Solution Manager as the highly recommended platform to efficiently support the implementation of your solution. Using SAP Solution Manager will significantly accelerate the implementation process and help you to achieve your business goals. At the same time, SAP will be able to deliver Support Services based on the business scenarios designed and documented in SAP Solution Manager. Implementation content for your solution may further accelerate the implementation process. For information about availability of content specifically tailored to your solution, see SAP Service Marketplace under service.sap.com/solutionmanager.

12

Getting Started Important SAP Notes

Important SAP Notes


This section contains important SAP Notes for SAP for Retail.

Read the installation SAP Notes before beginning the installation. These contain the most recent information regarding the installation, as well as corrections to the installation documentation. Make sure that you have the most recent version of each SAP Note. They are located on the SAP Service Marketplace (service.sap.com/notes) or in SAPNet - R/3 Frontend. List of Related SAP Notes SAP Note General 852235 874967 Release Limitations for mySAP ERP 2005 Release Limitations for mySAP Retail This note provides information about limitations in mySAP ERP 2005. This note provides information about limitations in mySAP Retail. Title Description

13

Business Scenarios of SAP for Retail Allocation

Business Scenarios of SAP for Retail


Allocation
Overview
You can use this business scenario to distribute a centrally planned quantity of goods to a large number of stores on specific delivery dates. This quantity distribution can occur dynamically by means of allocation strategies (with optional access to SAP BW, for example). The flow of products is then triggered by follow-on processing, that is, procurement and issue documents are automatically created by the system. Alternatively, you can also generate allocation tables automatically with reference to standard purchase orders or vendor orders that have been generated or created based on detailed assortment planning (in particular, purchasing lists). This way, quantity distribution of the planned assortment in the purchase list is performed to the recipients. Allocation tables are used, for example, to allocate seasonal merchandise, eliminate warehouse stocks, initially distribute new products and distribute promotional goods. You can use advices as communication between the head office and recipients.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Allocation.

BI Server ERP Server SAP ERP 2005 SAP ECC BI CONT 7.02 RDBMS RDBMS SAP NetWeaver 2004s usage type BI

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Allocation. Component SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type BI Mandatory X X Optional

14

Business Scenarios of SAP for Retail Assortment Management

Assortment Management
Overview
You can use this business scenario to define assortments and, using a certified space management program, optimize these assortments so that the best possible use is made of the available fixtures.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Assortment Management.

BI Server ERP Server SAP ERP 2005 SAP ECC BI CONT 7.02 RDBMS RDBMS SAP NetWeaver 2004s usage type BI

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Assortment Management. Component SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type BI Mandatory X X Optional

Further Information
The following documents provide more information about Assortment Management. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

15

Business Scenarios of SAP for Retail Category Business Planning

Category Business Planning


Overview
You can use this business scenario to manage your categories as strategic business units in order to achieve improved results by increasing the benefit to the customer. Producers and retailers work closely on the development, implementation, and monitoring of a category business plan.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Category Business Planning.

BI Server SAP NetWeaver 2004s usage type BI BI CONT 7.02 RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Category Business Planning. Component SAP NetWeaver 2004s usage type BI Mandatory X Optional

Further Information
The following documents provide more information about Category Business Planning. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

16

Business Scenarios of SAP for Retail Demand Modeling and Forecasting

Demand Modeling and Forecasting


Overview
You use this business scenario to perform all data modeling required for forecasting, as well as price optimization, promotion optimization and markdown optimization. The result is a demand-based understanding of customer purchasing behavior, which you can leverage to help attain business goals. Since you can use the data in many business decisions, it helps move you toward one central understanding of your demand, and one version of the truth as it relates to forecasting and optimization.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Demand Modeling and Forecasting.

SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail) RDBMS

BI Server SAP NetWeaver 2004s usage type BI BI CONT 7.03 RDBMS

PI/XI Server SAP NetWeaver 2004s usage type PI XI Content Demand Management
XI Content SAP ERP ENHANCE PACKAGE 2005.1

Demand Management Server DM Web Application

DM Job Processing RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Demand Modeling and Forecasting.

17

Business Scenarios of SAP for Retail Demand Modeling and Forecasting

Component SAP DEMAND MANAGEMENT 6.4 SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type BI SAP Netweaver 2004s usage type PI/XI

Mandatory X

Optional

X X X

Further Information
The following documents provide more information about Demand Modeling and Forecasting. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

18

Business Scenarios of SAP for Retail Forecasting & Replenishment

Forecasting & Replenishment


Overview
Using the Forecasting & Replenishment business scenario, retail companies can optimize their internal logistics by improving the replenishment process. Forecasting & Replenishment helps you avoid stockout situations whilst also enabling you to reduce high reserves of stock. This equates to a significant potential for saving, since stockouts in distribution centers and stores lead to huge loss of sales and overstocks cause high capital lockup for retail companies. The highly automated replenishment planning in stores and distribution centers reduces the large amount of manual processing that is currently required. You increase transparency in the supply chain using effective analyses.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Forecasting & Replenishment.

BI Server SAP NetWeaver 2004s usage type BI BI CONT 7.02


RDBMS

SCM Server SAP F&R 5.0 ECC Server SAP ERP 2005 SAP ECC SAP F&R - Store UI 5.0
RDBMS

RDBMS

XI Server SAP NetWeaver 2004s usage type XI XI CONTENT SAP_APPL 600 XI CONTENT SCM 5.0 XI CONTENT SCM BASIS 5.0
RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Forecasting & Replenishment. Component SAP SCM 5.0 SCM Server Mandatory X Optional

19

Business Scenarios of SAP for Retail Forecasting & Replenishment SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type BI FRP 2.8.1 SUI 5.0 SAP NetWeaver 2004s usage type PI/XI X X X X X

Further Information
The following documents provide more information about Forecasting & Replenishment. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

20

Business Scenarios of SAP for Retail Instore Customer Relationship Management

Instore Customer Relationship Management


Overview
You can use this business scenario to map all customer-related processes in a retail store. This includes the processes for creating customer data and entering RFQs, quotations, orders and returns, as well as invoice processing. You can enter exact information on prices and dates, and inform customers about the status of their orders in real time. The existing tools for handling store-based processes use a browser-based user interface that is tailored specifically to the needs of stores. The interface combines the intuitive usability of a Web browser with the special store-based transactions of centralized retailing. As a result, even recently trained part-time staff can start working with the system quickly and efficiently.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Instore Customer Relationship Management.

SAPERP Server ECC 6.0 Server SAP ERP 205 (SAP ECC SAP ERP 2005 SAPRetail) RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Instore Customer Relationship Management. Component SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) Mandatory X Optional

Further Information
The following documents provide more information about Instore Customer Relationship Management. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see

Configuration Documentation

21

Business Scenarios of SAP for Retail Instore Customer Relationship Management service.sap.com/solutionmanager. Security Guide For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

22

Business Scenarios of SAP for Retail In-Store Workforce & Task Management

In-Store Workforce & Task Management


Overview
You use this business scenario to manage all aspects of staffing within the retail environment: Recruiting, hiring, and managing all phases of the talent management process. Recording, updating, and reporting employee data as a basis for making informed personnel decisions. Recording, managing, and evaluating internal and external employees time management data. Planning, creating, and maintaining employee schedules.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for In-Store Workforce & Task Management.

Workforce Management Server SAP Workforce MAnagement 3.0


RDBMS

BI Server SAP CRM 5.0 BI Content SAP NetWeaver 2004s usage type BI
RDBMS

ERP Server SAP ERP 2005 SAP ECC


RDBMS

Portal Server SAP NetWeaver 2004s usage type EP Business Package for Retail 2.0
RDBMS

E-Recruting Server SAP E-Recruting 6.0


RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of In-Store Workforce & Task Management. Component SAP Workforce Management 3.0 SAP NetWeaver 2004s usage type EP Core SAP NetWeaver 2004s usage Mandatory X X X Optional

23

Business Scenarios of SAP for Retail In-Store Workforce & Task Management type Portal Content with Business Package Retail 2.0 SAP ECC 6.0 SAP NetWeaver 2004s usage type BI SAP XMTT 2.0 SAP E-Recruiting 6.0 X X X X

Further Information
The following documents provide more information about In-Store Workforce & Task Management. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

24

Business Scenarios of SAP for Retail Markdown Planning & Optimization

Markdown Planning & Optimization


Overview
You use this business scenario to plan, optimize, and manage markdown events. Markdowns can be used for a variety of reasons, including: discontinued products, seasonal products, new models and store closings. The result is a recommended markdown schedule for all product-locations, as well as report information that allows users to drill down into low level detail about all aspects of the markdowns. In Slow Seller Management you plan markdowns (price reductions) for seasonal products. Using rule-based markdown controls, SAP BW automatically creates markdown proposals that provide analysis of sales data. Markdowns are proposed, and once accepted, are processed in the Price Planning Workbench in SAP Retail. If the retailer uses markdowns based on a predefined markdown schedule, the dates for the markdowns are defined beforehand and executed on those dates.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Markdown Planning & Optimization.

25

Business Scenarios of SAP for Retail Markdown Planning & Optimization

SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail) RDBMS

BI Server SAP NetWeaver 2004s usage type BI BI CONT 7.03 RDBMS

PI/XI Server SAP NetWeaver 2004s usage type PI XI Content Demand Management
XI Content SAP ERP ENHANCE PACKAGE 2005.1

Demand Management Server DM Web Application

DM Job Processing RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Markdown Planning & Optimization. Component SAP DM 6.4 SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type PI/XI SAP NetWeaver 2004s usage type BI X Mandatory X X X Optional

Further Information
The following documents provide more information about Markdown Planning & Optimization.

26

Business Scenarios of SAP for Retail Markdown Planning & Optimization

Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

27

Business Scenarios of SAP for Retail Merchandise and Assortment Planning

Merchandise and Assortment Planning


Overview
You can use this business scenario to implement integrated and complete planning within your company. You perform planning and reporting for all your business activities that involve assortments and merchandise. You can define sales, quantities, areas, stores and budgets, which are then transferred to an executing system for operational purposes and processed further. Merchandise and assortment planning primarily deals with four main planning areas strategic planning, merchandise planning, store planning, and assortment planning. This demonstrates that you can start on a high planning level and then move down to lower levels (top-down) or the other way round (bottom-up). When you integrate merchandise and assortment planning in SAP NetWeaver 2004s, usage type Business Intelligence with BI Content 7.0.2 Add-On (BI system), the system accesses various data from different areas. This has the advantage that you can optimize future developments for your company by comparing planning, actual, and historical data. In addition, you can continuously monitor defined objectives, and adapt to given developments and influencing factors.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Merchandise and Assortment Planning.

BI Server SAP NetWeaver 2004s usage type BI BI CONT 7.02 RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Merchandise and Assortment Planning. Component SAP NetWeaver 2004s usage type BI Mandatory X Optional

Further Information
The following documents provide more information about Merchandise and Assortment Planning. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For

28

Business Scenarios of SAP for Retail Merchandise and Assortment Planning more information about SAP Solution Manager, see service.sap.com/solutionmanager. Configuration Documentation The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Security Guide

29

Business Scenarios of SAP for Retail Merchandise and Assortment Planning (Integrated)

Merchandise and Assortment Planning (Integrated)


Overview
Retailers can use this business scenario to implement integrated and complete planning within their company. You perform planning and reporting for all your business activities that involve assortments and merchandise. You can define sales, quantities, areas, stores and budgets, which are then transferred to an executing system for operational purposes and processed further. Merchandise and assortment planning primarily deals with four main planning areas strategic planning, merchandise planning, store planning, and assortment planning. This demonstrates that you can start on a high planning level and then move down to lower levels (top-down) or the other way round (bottom-up). When you integrate merchandise and assortment planning in SAP NetWeaver 2004s, usage type Business Intelligence with BI Content 7.0.2 Add-On (BI system), the system accesses various data from different areas. This has the advantage that you can optimize future developments for your company by comparing planning, actual, and historical data. In addition, you can continuously monitor defined objectives, and adapt to given developments and influencing factors.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Merchandise and Assortment Planning (Integrated).

BI Server SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail) BI CONT 7.02 RDBMS RDBMS SAP NetWeaver 2004s usage type BI

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Merchandise and Assortment Planning (Integrated). Component SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type BI Mandatory X X Optional

Further Information
The following documents provide more information about Merchandise and Assortment Planning (Integrated).

30

Business Scenarios of SAP for Retail Merchandise and Assortment Planning (Integrated)

Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

31

Business Scenarios of SAP for Retail Multi Channel Loyalty Program Management

Multi Channel Loyalty Program Management


Overview
You use this business scenario to enhance the point of sale (POS) and assist retailers in meeting their unique business requirements. Allegiance 1 to 1 offers real-time CRM functionality for any integrated customer point of interaction, providing the following benefits: Cross-chain recognition that allows customers to take advantage of promotions and offers across all channels while the retailer is able to implement and enforce promotion limits. Ability to directly target information in a real-time, on-line environment. To accomplish this, pertinent data from your CRM analytical solution is synchronized with the Allegiance 1 to 1 database. This information is held centrally and provides that information to the customer point of interaction including POS systems, customer service desks, kiosks, and e-commerce applications.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Multi Channel Loyalty Program Management.

Allegiance Server ALLEGIANCE Server ALLEGIANCE DB Server

Loyalty Solutions Server

Transnet Client Transnet Server

Transnet Monitor Server

RDBMS

The following product is mandatory for the technical implementation of Multi Channel Loyalty Program Management. Component SAP Allegiance 6.0 Mandatory X Optional

32

Business Scenarios of SAP for Retail Multi Channel Loyalty Program Management

Further Information
The following documents provide more information about Multi Channel Loyalty Program Management. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

33

Business Scenarios of SAP for Retail Point of Sale GM

Point of Sale GM
Overview
You use this business scenario to handle the various steps involved with selling products and services to customers in a retail store environment. SAP Transactionware GM is a client/server point-of-sale (POS) solution and has long defined the standard of excellence in the POS industry. SAP Transactionware GM meets the needs of a wide variety of retailers, with extensive POS functionality and flexible definition and management of POS business rules and processes via a simple, table-driven configuration process. Retailers include department, c-store, liquor, gas, specialty, apparel, big box, and a number of other retail verticals. Additionally, the solution is offered with powerful in-store back office capabilities to enable store-level environment management and reporting. SAP Transactionware GM provides numerous benefits to retailers including: Improving Service Delivery Add 24x7 customer service Provide personalized customer interaction Ensure customers are treated based on predefined business rules Improve customer retention and loyalty Ensure more effective sales execution Reduce training costs

Improving Customer Service

Reducing Operating Costs and Increasing Efficiency

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Point of Sale GM.

34

Business Scenarios of SAP for Retail Point of Sale GM

Mobile POS Mobile POS 9.5

POS DOS Thin Client POS DOS Thin Client 9.5

POS Express Triversity Command line utilities POS Xpress 9.5 POS Thin Server POSW 9.5

Xpress Server Xpress Server 9.5

EFT

Databse Tools 9.5

Store Manager 9.5

EJV 9.5

RDBMS

Configurator Configurator 9.5 Software Dev. Kit SDK 9.5 Database Tools 9.5

EJV 9.5

RDBMS

The following product is mandatory for the technical implementation of Point of Sale GM. Component SAP Transactionware GM V9.5 Mandatory X Optional

35

Business Scenarios of SAP for Retail Point of Sale GM

Further Information
The following documents provide more information about Point of Sale GM. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

36

Business Scenarios of SAP for Retail Point of Sale TE

Point of Sale TE
Overview
You use this business scenario to handle the various steps involved with selling products and services to customers in a retail store environment. SAP Transactionware Enterprise is a Java 2 Enterprise Edition-based application that can be deployed across multiple operating systems, application servers and databases, allowing retailers to realize benefits that can transform the internal economics of retailing. SAP Transactionware Enterprise can meet the needs of a wide variety of retailers, with extensive POS functionality and flexible definition and management of POS business rules and processes by using a simple table-driven configuration process. Point of Sale TE provides the following benefits: Improved Customer Service Ensures that customers are treated in accordance with predefined business rules Improves customer retention and loyalty Reduced Operating Costs and Increased Efficiency Ensures more effective sales execution Reduces training costs Improved Service Delivery Adds 24x7 customer service Personalizes the customer interaction

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Point of Sale TE.

37

Business Scenarios of SAP for Retail Point of Sale TE

TE POS Store Server TE POS HO Server TE Server TE Server Transnet Site Client Transnet Site Client Deployment Manager RDBMS RDBMS

POS Client POS Client POS Loader

The following product is mandatory for the technical implementation of Point of Sale TE. Component SAP Transactionware Enterprise 2.5 Mandatory X Optional

Further Information
The following documents provide more information about Point of Sale TE. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

38

Business Scenarios of SAP for Retail Promotion Planning & Optimization

Promotion Planning & Optimization


Overview
You use this business scenario to plan retail promotions, create promotion layouts and release planning data for logistics and operations processing. You plan retail promotions in SAP Retail or SAP Demand Management. You can create retail promotions either using a dedicated application or in the Price Planning Workbench within Promotion Management. In the planning stage, you: Specify the articles that you want to include in the promotion and the stores or customers participating in the promotion. Specify distribution chains, price lists, or site groups and optionally define special promotional prices for the articles, or group conditions, such as discounts for merchandise categories. Plan the procurement of promotional goods by determining the vendors, defining purchase prices and procurement quantities.

You can also plan promotions via optimization which allows the system to determine which products and/or offers to promote based on historical sales data. In the layout stage, you specify: The graphic layout of the promotion including placement in an advertisement (such as, top right corner of the front page). The picture to display for the article. Any additional text to include in the advertisement.

When releasing promotions, you create the sales and purchasing conditions and purchase orders for the promotional goods using the allocation function in SAP Retail. You can inform the stores about upcoming promotions using the announcement function. When planning promotions using the Price Planning Workbench, you can use the budget function to monitor sales deductions. To do so, you need to create special budgets in SAP BI, which you send to SAP Retail using the Release Workbench.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Promotion Planning & Optimization.

39

Business Scenarios of SAP for Retail Promotion Planning & Optimization

SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail)

BI Server SAP NetWeaver 2004s usage type BI

RDBMS

BI CONT 7.03

RDBMS

PI/XI Server SAP NetWeaver 2004s usage type PI XI Content Demand Management
XI Content SAP ERP ENHANCE PACKAGE 2005.1

Demand Management Server DM Web Application

PML Server Visual Compos. Framework Server Visual Compos. Framework Client.

DM Job Processing

RDBMS

RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Promotion Planning & Optimization. Component SAP DM 6.4 SAP PML 6.7 SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type PI/XI SAP NetWeaver 2004s usage type BI X Mandatory X X X X Optional

40

Business Scenarios of SAP for Retail Promotion Planning & Optimization

Further Information
The following documents provide more information about Promotion Planning & Optimization. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

41

Business Scenarios of SAP for Retail Purchase Order Management

Purchase Order Management


Overview
This business scenario supports you in the area of ordering. In addition to general operational order processing, in which requirements determined automatically or manually for your stores, distribution centers, and customers are converted into vendor orders, this includes order optimizing, such as simple quantity rounding. Through investment buying, materials can be procured beyond the standard stock or current requirement when you expect a price increase from the vendor. Load building is an option for better utilization of transport capacities. In addition to the described order processing functions, this business scenario also features two procurement processes that are primarily motivated from the push approach: The seasonal procurement process gives you a fast, simple way to enter orders. An OTB check is also integrated, along with a monitor of existing schedules. The push approach is also followed in the process of plan-driven seasonal procurement. In this process, the generated purchase orders result from the planning results in operational assortment planning (see Operational Assortment Planning and Control). The OTB check, scheduling, and subsequent monitoring of the calculated dates are integrated in this process as well. Several workbenches are available to simplify the use of these two push processes: Workbenches from Procurement Monitoring (PO Monitor, Contract Monitor, OTB Monitor), Purchase Order Manager Workbench, OTB Procurement Workbench, OTB Procurement Special Release Workbench. A separate process is available to assist in the procurement of perishables (fruits and vegetables), enhanced with a process for managing live auctions. The cross-docking process can be used for optimized logistical processing of merchandise distribution. Collective purchase orders are used here. If you want to utilize the full functional scope, you can define vendor prepacking before the collective purchase order. Operational order processing is concluded by the invoice verification process.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Purchase Order Management.

42

Business Scenarios of SAP for Retail Purchase Order Management

BI Server SAP NetWeaver 2004s usage type BI BI CONT 7.02 RDBMS

SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail) RDBMS

SCM Server SAP SCM 5.0 RDBMS

SRM Server SAP SRM 5.0 RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Purchase Order Management. Component SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type BI SAP SCM 4.1 SCM Server SAP SRM 5.0 SRM Server Mandatory X X X X Optional

Further Information
The following documents provide more information about Purchase Order Management. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager.

Configuration Documentation

43

Business Scenarios of SAP for Retail Purchase Order Management Security Guide For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

44

Business Scenarios of SAP for Retail Requirements Planning and Replenishment

Requirements Planning and Replenishment


Overview
You can use this business scenario to ensure that goods are available when recipients (stores or customers) and consumers require them. To do this, you must procure requirement quantities on time. This involves the following activities:
...

Monitoring stocks Taking account of recipients sales and purchase orders Creating forecasts Calculating requirement quantities Creating follow-on documents for procurement

The stock planner defines the suitable forecast, requirements planning, and lot-sizing procedures for each article. You can use the scenario to map the following processes: Direct delivery The vendor delivers the goods direct to the recipient. The purchase order can be placed either by the recipient or the distribution center in this case. Delivery via a distribution center You can use this process to plan the supply of merchandise to stores via a distribution center. Your vendor delivers to a distribution center that in turn supplies the merchandise to the stores.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Requirements Planning and Replenishment.

SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail)

RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Requirements Planning and Replenishment. Component SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) Mandatory X Optional

45

Business Scenarios of SAP for Retail Requirements Planning and Replenishment

Further Information
The following documents provide more information about Requirements Planning and Replenishment. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

46

Business Scenarios of SAP for Retail Retail Price Planning & Optimization

Retail Price Planning & Optimization


Overview
You use this business scenario to perform all retail price optimization price file creation, product and zone selection, strategy definition, and optimization and forecasting. Within this scenario, users can perform what-if analysis on the results, at a summary and detail level and make user overrides to further refine the pricing strategy. The result is a pricing event with optimized prices at a product and zone level that can be sent to the customers ERP or pricing system to be implemented in the stores. In this business scenario, you can model all the processes for managing sales prices within your value chain. In particular, this involves calculating the sales prices for the articles you sell in the sales-related organizational units, such as distribution chain and store. You calculate the sales prices in SAP Retail. Depending on which pricing procedure you use, you first define pricing-relevant parameters such as planned markups, competitor prices, or price families. The three different applications that are available sales price calculation, market basket calculation, and Price Planning Workbench are each focused on different requirements in retailing. The sales prices calculated during costing are saved as conditions in SAP Retail. The Retail Price Planning application in the Price Planning Workbench is designed as an independent process due to its release procedure and automatic follow-on processing steps for price plans. From a functional perspective, this process represents an enhancement of sales price calculation. In Slow Seller Management you plan markdowns (price reductions) for seasonal articles or fashion merchandise. In rule-based markdown control, you define planning parameters in SAP BW to automatically create markdown proposals, which the system uses during analysis of the sales data. You process these markdown proposals further in the Price Planning Workbench in SAP Retail. When you plan based on a markdown plan, you define the dates for the markdowns beforehand.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Retail Price Planning & Optimization.

47

Business Scenarios of SAP for Retail Retail Price Planning & Optimization

SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail)

BI Server SAP NetWeaver 2004s usage type BI

RDBMS

BI CONT 7.03

RDBMS

PI/XI Server SAP NetWeaver 2004s usage type PI XI Content Demand Management
XI Content SAP ERP ENHANCE PACKAGE 2005.1

Demand Management Server DM Web Application

DM Job Processing

RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Retail Price Planning & Optimization. Component SAP DM 6.4 SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type PI/XI SAP NetWeaver 2004s usage type BI Mandatory X X X X Optional

Further Information
The following documents provide more information about Retail Price Planning & Optimization.

48

Business Scenarios of SAP for Retail Retail Price Planning & Optimization

Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

49

Business Scenarios of SAP for Retail Returns Authorization

Returns Authorization
Overview
Returns Authorization and Management is critical to improving margins, reducing fraud, and improving customer service. This module quickly and effectively links returns or exchanges to original purchases and validates the authenticity of the transaction. Express Returns is a centralized returns authorization application. At the heart of the application is the Express Returns database containing sale and return transactions, pricing history, and underlying business rules. The Express Returns authorization engine verifies return requests initiated at point of sale (POS) terminals in real time and generates return approvals or referrals. Express Returns can provide significant benefit to retailers including Reducing Operating Costs & Increasing Efficiency Reduce of error rate by use of automated processes Reduce transaction costs Increase Speed & Efficiency Better decisions with accurate and up-to-date information Improved quality and accuracy

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Returns Authorization.

50

Business Scenarios of SAP for Retail Returns Authorization

POS Xpress Server Transnet MT Client

Express Returns Server Common Dataload

POS Xpress 9.5

Express Returns

Xpress Server Xpress Server 9.5

EFT

Databse Tools 9.5

Store Manager 9.5

EJV 9.5

RDBMS

Configurator Configurator 9.5 Software Dev. Kit SDK 9.5 Database Tools 9.5

EJV 9.5

RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Returns Authorization. Component SAP POS Services 1.0 SAP Transactionware GM 9.5 Mandatory X X Optional

51

Business Scenarios of SAP for Retail Returns Authorization

Further Information
The following documents provide more information about Returns Authorization. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

52

Business Scenarios of SAP for Retail Store Analytics

Store Analytics
Overview
You can use this business scenario to perform numerous analyses for controlling and monitoring the retailing processes in your store. Evaluations are available for the area of merchandise analysis, starting with evaluations for store controlling to analyze the cost and revenue situation of your store. In addition to stock analyses, these also include evaluations on the flow of goods and markdowns. You can create analyses of warehouse stocks on a monthly basis, taking account of goods movements, price changes and markdowns. As part of customer sales analysis (consisting of customer analysis, sales analysis and Top 100 analysis), you can systematically prepare the sales promoting area and support sales in a targeted way for improved revenue and sales control. You can evaluate the logistical processing and sale of promotional merchandise using the promotion analysis, identify the benefit of a promotion and cover the sales margins of specific promotional articles (promotion analysis). POS data analysis can be used for prompt sales evaluation of cash register data at store and article level. POS data analysis includes the following components: Analysis of customer needs and behavior (for example, customer returns/complaints) Effective evaluation of key store figures High data quality and performance when processing mass data using the latest technology Increase in profitability through near-time controlling of retail processes

This package is extended to include analyses for fraud detection. It provides tips to internal reviewers on introducing countermeasures to reduce or prevent any instances of fraud in the cash register area.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Store Analytics.

BI Server SAP NetWeaver 2004s usage type BI BI CONT 7.02

RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Store Analytics. Component SAP NetWeaver 2004s usage type BI Mandatory X Optional

53

Business Scenarios of SAP for Retail Store Analytics

Further Information
The following documents provide more information about Store Analytics. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

54

Business Scenarios of SAP for Retail Store Connectivity

Store Connectivity
Overview
You can use this business scenario to connect and integrate point of sale (POS) systems to SAP for Retail merchandise applications. The POS data download provides outbound messages for initial and delta download to the point of sale. These messages are created as IDocs in the POS interface to cover various business processes. Updated data includes: Master data (item and price information) Movement data (for example, count lists for physical inventory)

During the data upload, SAP for Retail receives the following transaction data from the stores: Sales flows Goods movements Financial transactions Totals records Cancellation transactions Control transactions

The transaction data from the POS systems forms the basis for the main sales processes, such as store replenishment, sales analyses, promotion analyses, and profit and loss statement. Due to its volume and high level of detail, this data is one of the major challenges to a retailer's IT landscape. You can use POS Data Management for systematic and demanddriven processing of the data.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Store Connectivity.

55

Business Scenarios of SAP for Retail Store Connectivity

BI Server SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail) BI CONT 7.02 RDBMS RDBMS SAP NetWeaver 2004s usage type BI

PI/XI Server SAP NetWeaver 2004s usage type PI


XI Content SAP TRANSACTIONWARE GM 9.5

XI Content SAP ERP ENHANCE PACKAGE 2005.1

Triversity GM Server Xpress Server

RDBMS

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Store Connectivity. Component SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP NetWeaver 2004s usage type BI SAP NetWeaver 2004s usage type PI/XI Mandatory X X X Optional

Further Information
The following documents provide more information about Store Connectivity. Further Scenario Documentation

56

Business Scenarios of SAP for Retail Store Connectivity Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Configuration Documentation

Security Guide

57

Business Scenarios of SAP for Retail Store Merchandise Management

Store Merchandise Management


Overview
You can use this business scenario to map all the retailing processes in a retail store. This includes the processes required for the majority of a store's transactions, such as procurement, goods movement and sales postings, as well as processes for vendor, assortment and price management. There are also processes for physical inventory, promotions and food services/catering. The existing tools for handling store-oriented processes use an Internet-based user interface that is tailored specifically to meet the needs of stores. The interface combines the intuitive usability of a Web browser with the special store-based transactions of centralized retailing. As a result, even semi-skilled part-time staff can start working with the system quickly and effectively.

Technical System Landscape


The following diagram provides an overview of a possible system landscape for Store Merchandise Management.

SAP ECC 6.0 Server SAP ERP 2005 (SAP Retail) RDBMS SAP Business Connector 4.7

The following software components are either mandatory or optional, as indicated below, for the technical implementation of Store Merchandise Management. Component SAP ERP 2005 (SAP Retail with SAP ECC 6.0 Server) SAP Business Connector 4.7 Mandatory X X Optional

Further Information
The following documents provide more information about Store Merchandise Management. Further Scenario Documentation Scenario Description The scenario description is part of SAP Solution Manager. For more information about SAP Solution Manager, see service.sap.com/solutionmanager. The configuration documentation is part of SAP Solution Manager implementation content ST-ICO 150. For more

Configuration

58

Business Scenarios of SAP for Retail Store Merchandise Management Documentation information about SAP Solution Manager, see service.sap.com/solutionmanager. For more information, see service.sap.com/securityguide Industry Scenario Security Guides.

Security Guide

59