POS Data Management

POS Data Management

Contents: Introduction

POS Data Management: Objectives will be able to: At the conclusion of this unit, you
Describe the move to POS

Data Management from the R/3 Inbound POS Interface. Describe an overview of POS DM and BW Content Explain the basics of POS Data Management

POS DM Workshop Overview

Unit 1 Introduction
Unit 2 POS Inbound Interface Unit 3 POS Workbench Unit 4 Customizing POS DM Unit 5 POS Analytics Unit 6 POS Outbound Unit 7 Conclusion

mySAP POSOpen Standards Data Management

CRM SCM
Administration & Securities

mySAP POS Data Management is a complete and open solution that provides accessibility, collaboration and deployment of relevant, timely and insightful information to anyone, anywhere at anytime to understand, optimize and align their business.

POS Data Management: Challenges for each store, Understand consumer behavior

event, week, in a better way Ensure an effective store measurement Increase profitability by utilizing POS data for near real-time controlling of retail processes Realize the vision of an effective consumer centric supply chain through real time POS Data

A Central Repository of POS Data serves all Areas of Retail

Supply Side
Category Management & Planning Forecasting & Replenishment Store Operations

Demand Side

Human Resources

Merchandising

Financials

Supply Chain Management

POS Data Management

Customer Relationship Management

Overview Analyses of POS Data Sales

SAP BW
PIPE
POS Inbound Processing Engine

Outbound interface

mySAP Solutions 3rd Party Landscape

Upload of POS Data to SAP BW via POS Inbound Processing Engine

Prior POS Interface to SAP Retail

Replenishment
IDES Smart Retailer Inc. IDES Smart Retailer Inc.

Store Backoffice

Outbound Inbound Nightly: Sales Tenders Financial Trans. Loss Prevention Store Orders Goods Receipt

BW

Converter

TLOG (Transaction Log)

Store 1
TLOG

All data captured at the point of sales are recorded in the TLOG file. The data can be stored in the POS terminal itself or in a central POS server.

Store 2
TLOG

TLog Replication from Store to PIPE

SAP BW

Store 1
TLOG

TLOG
Data transfer Conversion

Store 2
TLOG

PIPE

POS Analytics Content: Challenge The old POS Content is not able to get connected to the PIPE, therefore the Redesign
new POS Analytics Content was developed . The challenge of the new POS Analytics Content for the future is to remove the old POS Content.
old POS Content new POS Analytics Content

Reporting Enhancements with POS Analytics

Customer Views Store Views

By month By week By day By hour

Product Views

Seamless Integration in Enterprise Portal

Makes POS available for Marketing Manager Buyer Administrator Store manager ...

SAP BW

PIPE
POS Inbound Processing Engine

mySAP Solutions 3rd Party Landscape

Key Benefits of the PIPE (1/2)

Splitting subsequent functions Compatibility with previous releases Simplification of inbound interfaces Use of standard interfaces Stability / Accurancy / Reliability Performance Decoupling
SAP BW

PIPE
POS Inbound Processing Engine

mySAP Solutions 3rd Party Landscape

Key Benefits of the PIPE (2/2)

Repetition of processing / Regeneration of data for subsequent functions Administration Automatic check rules Automatic error correction Lean processing Extendibility
SAP BW

PIPE
POS Inbound Processing Engine

mySAP Solutions 3rd Party Landscape

POS Data Management Summary

You are now able to: Describe the move to POS Data Management from the R/3 Inbound POS Interface Describe an overview of POS DM and BW Content Explain the basics of POS Data Management