SAP POS DM & Retail Sales

Process overview

Prepared by
Marvin Khedia
SAP IS Retail & POSDM Consultant
Content of Presentation
RetailBusiness Functions & Overview
SAP IS Retails Landscape (Outbound &
Inbound)
Sales Process Overview & Challenges
SAP POS DM & SAP CAR/POS DTA System
understanding with Landscape.
SAP POS DM Process overview
SAP POS DM Advantages & Summary
SAP POS DM Configuration overview
SAP ECC Configuration overview
Retail Business Functions
What is Retail business & How it is differ from
Manufacturing business ?
Core Business functions of Retail Business
 Plan
 Buy
 Move
 Sale
Briefing of Retail Processes
 Plan
◦ Management/Business mangers will plan what
product / merchandise needs to be Sale at Stores .
◦ From which Vendor/wholesales they will purchase
products.
◦ Agreement / commercial terms with Vendor ?
 What will be the purchase prices ?
 What will be the margin on Brand / Product ?
 Payment terms etc.
◦ Retails Master data creation (Article, MC , Brand,
Product hierarchy, Site, Vendor, PIR, etc.)

 Buy
◦ After Plan, Buying will happens
◦ Purchasing order and other process.
 Briefing of Retail Processes
 Move (SCM & Logistics Processes)
◦After Purchasing , Product will be received from Vendor on
the basis of Purchase Order.
◦Goods Inbound
◦Goods movements to Store for selling according to the
requirement from Distribution Center (Warehouse) via STO.

 Sale
◦Customer sales will happens to Stores level on POS
machines (Point Of Sales) according to Retail Master data
availability.
i.e Article, Merchandise Cat., Pricing , Promotions & etc.
 SAP IS Retails Landscape
 OutboundFlow
◦ SAP ECC/FMS to POS System

SAP IS Retail Retail SAP PI / FTP Conversion POS System

ECC/FMS Masters data Location of Master DB
IDocs data

Retail Master IDocs

1.Article Master
2.EAN Master POS No 1 POS No 2 POS No 3
3.MC Master
4.Pricing
5.Promotions
6.Assortment & Listing
7.Sales Set
 SAP IS Retails Landscape
 Inboundflow (Before POS DM got introduced)
◦ POS System to SAP ECC/FMS

Sales &
SAP IS Retail Sales & SAP PI / FTP Tender POS System
ECC/FMS Tender Location details file DB
IDocs i.e. Store +
Date
Sales & Tender IDoc

1.Aggregated Sales IDoc POS No 1 POS No 2 POS No 3

 Billing & Article doc.
2.Aggregated Tender IDoc
 Billing document
3.Financial detail IDoc
 A/C document
Sales Process overview &
challenges
 In conventional inbound process Aggregated Sales data
reached to ECC after the day end process (EOD)
completed from stores.
 System will have correct inventory visibility for Store +
Article combination next day after Sales IDoc posted
successfully.
 Requirement planning (Replenishment) process will be
affected, if Sales IDocs failed in ECC/FMS system.
 Sales IDocs error correction needs to be performed
periodically for correct inventory visibility & RP
process run.
 Sales data reconciliation process need to carried out
with compare to POS data.
◦ i.e POS Data needs to be send in reporting system. Like
Informatica tool with Greenplum DB.
Sales Process overview &
challenges
 Data management activities performances (i.e. Missing
Sales, Wrong Sales Values, Double sales posting, Store
having connectivity issue etc.)
 Sales Reversal process needs to perform for wrong sales
posting & reload with correct sales data.
 Vendor payment / Rebate process will be delayed.
 To Perform Data management activities more team
bandwidth required.
 Clear Sales picture will not be available to Management
& Lacking of end to end processes around Store data.
 Raw Sales data reporting is not possible as aggregated
data is coming from POS.
 In multiple POS System organization faced challenge of
non integrated landscape.
SAP POS DM & POS DTA System
overview
POS Data Management :-
SAP first introduced SAP POS Data Management system with
BW.
POSDM resided on anyDB or HANA.
SAP POS DM basically designed for Single channel “Brick &
Mortar” retailers.
POS DM is dependent on BI/BW content for Master data &
Analytics.
POSDM Allows for easy integration with other applications
provided by SAP (like ERP Retail, F&R or CRM) or developed
by partners and customers.
Optional in-memory reporting when running on BWoH (BW
on Hana).
SAP POS DM & POS DTA System
overview
POS Data Transfer & Audit :-
POS Data Transfer & Audit system is introduced as part for SAP CAR
component. Its modified version of SAP POSDM.
Both system are different, we cant say that POSDTA is successor of
POSDM, As POSDM is available as separate solution.
POSDTA resided on HANA DB.
Designed for retailers with multiple channels – order channel get’s assigned
to the POS transactions.
◦ i.e Store Sales, Omni Channel Sales, Telephonic Sales etc.
Functional scope is essentially identical to POS Data Management – main
difference is that TLOGF has been enriched to support ‘Channel
Identification’ & used for detailed report generation.
POS DTA has no hard dependency to BW/BI Content.
SLT will be used to transfer Retails Master data from ECC to Hana DB.
POSDTA Allows for easy integration with other applications provided by
SAP (like ERP Retail, F&R or CRM) & Consuming application built on top of
CAR (Promotion Management for Retail – PMR ).
SAP POS DM Landscape
SAP POS DM high level Architecture
Overview of Components in POS DM
SAP POS DTA Landscape with SAP
CAR
POS DM Process overview (POS
Data Processing/Auditing)
 Data validation, Ability to implement own check
rules.
 Efficient error handling and intuitive User Interface.
 Flexible set-up and control of processing steps.
 Tracking of data changes.
 Aggregation/enrichment of data for subsequent
processing.
 Sales Data Audit @ Transaction levels.
 Cashier Performance
 Loyalty Marketing/Customer Data
 POS Transaction Types handling.
POS Transaction Types
 Sales Transactions
 Sales transactions including means of payment &
customer loyalty information.
 Finance Transactions
 Cash register extraction, pay in, pay out, petty cash.
 Good Movements
 Goods receipt, goods issue, markdowns.
 Cancellations
 Control Transactions
 Cashier log on/off, drawer opened, system start.
 Sum Records
 Sales, discounts, taxes, cashier statistics, register
closing.
POS DM Sales Auditing process
Sales Data Audit is one of the key benefits of POSDM which based on some
checks & validation shown below.
◦ Master Data check
 Item Validity ( Article / EAN)
 Store Validity (Site)
 UOM Validity ( Unit of measurement )
 Tender Validity
◦ Gap Sequencing Check (Day, Store, POS-Number, Transaction
number).
◦ Duplicate Transaction check
◦ Transaction Balancing (Total Sales = Total Payments)
◦ Valid means of Payment
◦ Valid Tax Type
◦ Valid Discount Type
◦ Valid Transaction Type
◦ Valid Reason Code
◦ Totals Balancing (requires Totals to be sent according to standard POS
DM behavior per POS or Cashier, per business item type)
◦ Enhanced handling of error situations.
POS DM Process overview (POS
Data Processing/Auditing)
Inbound to SAP for Retail
◦ Detailed transactional data (non-aggregated) to SAP
BW.
◦ Sales Receipt wise sales IDoc for Retail (IDoc –
WPUBON).
◦ Aggregated sales to SAP for Retail (IDoc-
WPUUMS).
◦ Aggregated tenders (methods of payment) to SAP
for Retail (IDoc-WPUTAB).
◦ Transactional posting of financial movements (paid-
ins, paid-outs) via IDoc WPUFIB.
◦ Automated reversal (post void) postings.
POS Data flow in POSDTA
IDoc creation as per POS data.
Inbound Queue Monitoring & Processing
Workbench
◦ Sales data Validation
◦ Audit
◦ Aggregation
◦ Transfer / IDoc Creation to ECC via RFC
Outbound IDoc Monitoring
Sales, Tender & Finance IDoc generation and
processing in ECC
POS Data flow in POSDTA
 IDoc creation as per POS data.(/posdw/postr_createmultiple)
POS Data flow in POSDTA
 Inbound queue monitoring and processing.
 T-Code - /posdw/qmon
POS Data flow in POSDTA
 Inbound queue monitoring and processing.
 T-Code - /posdw/qmon
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0)
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0)
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) To view only error Transaction
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) To view only error Transaction
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0)
Sales Transaction looks as below in workbench
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0)
Sales Transaction Task status looks like below
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) Master Data Errors Screens
Article not listed to particular site .
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) Master Data Errors Screens
MAP (Moving Average Price) not maintained for Article + Site combination
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) Master Data Errors Screens
Unknown Article error
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) Master Data Errors Screens
Sum of Item does not equal to Sum of Payment (Tender)
 POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) Master Data Errors Screens
Control Transactions looks as below

Task of
Control
Transaction
 POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) Master Data Errors Screens
Total Sales Transactions looks as below

Task of Total
Sales
Transaction
POS Data flow in POSDTA
 Workbench (T-Code - /posdw/mon0) Master Data Errors Screens
Total Tender/Collection/Financial Transactions looks as below
POS Data flow in POSDTA
 Outbound IDoc from POSDTA to ECC
POS Data flow in POSDTA
 Outbound IDoc from POSDTA to ECC
POS Data flow in POSDTA
 Outbound IDoc from POSDTA to ECC
Sales IDocs Detail in ECC/IS Retail
 Tender IDoc in ECC – WPUTAB
Sales IDocs Detail in ECC/IS Retail
 TenderIDoc in ECC – WPUTAB
◦ Accounting Doc Details
Sales IDocs Detail in ECC/IS Retail
 Sales IDoc in ECC – WPUUMS
 Sales IDocs Detail in ECC/IS Retail
 Sales IDoc in ECC – WPUUMS
◦ Billing Document Details
Sales IDocs Detail in ECC/IS Retail
 Sales IDoc in ECC – WPUUMS
◦ Accounting Doc for Billing
Sales IDocs Detail in ECC/IS Retail
 Sales IDoc in ECC – WPUUMS
◦ Article Document detail
Sales IDocs Detail in ECC/IS Retail
 Sales IDoc in ECC – WPUUMS
◦ Article Document Accounting detail
Sales IDocs Detail in ECC/IS Retail
 Financial IDoc in ECC – WPUFIB
Sales IDocs Detail in ECC/IS Retail
 Financial IDoc in ECC – WPUFIB
SAP POS DM/POSDTA Advantages
& Summary
 Real Time Inventory - For use with all channels: Stores,
POS, On-line, Mobile etc.
 A new data foundation in which retail data are collected, that
were previously spread over multiple applications.
 Clean, correct and enrich POS Transactions via Sales Audit.
 Support high speed analytics and calculation of mass data.
 Instant aggregation to any level without losing the detailed
sales information (data at item level).
 Friendly easy to use workbench to resolve issues.
 Single interface to ECC/BI for Multiple POS system.
 ECC window reduced due to aggregation and trickle feed
(Reduce in overnight batch jobs for processing).
SAP POS DM/POSDTA Advantages
& Summary
 Reporting and Analysis available through POSDM/POSDT
Analytics.
 Data enriched as required using SLT/BW/ECC master data.
 Standard data distribution to SAP systems.
 Recording all POS transactions on the run.
 Repository for Master data table like Customer, Sales,
Vendor etc.
 Easy integration with CRM, BI, PMR, Omni channel
systems etc.
 Helps retailers to step by step transform their system
landscapes from tradition database technology to
revolutionary in memory technology.
SAP POS DM/POSDTA
Configuration overview
 Inbound Profile  Discount Groups
 Check Profile  Discount Types
 Define Profile  Tax Group
 General Settings
 Tax Types
 Standard Values
 Tender Groups
 Store Settings
 Tender Types
 Define Task Group
 Financial Transaction
 Define Task
 Assign Task to Task
Groups
 Financial Types
group
 Define type group for  Transaction Groups
Sales Items  Transaction Types
 Sales Item types
SAP ECC Configuration overview
 Retail Master Creation/Distribution with IDocs.
◦ With in the SAP Landscape.
◦ With Legacy system like POS.
 Site Outbound Profile creation/maintenance.
 Site Inbound Profile creation/maintenance.
 Pricing Procedure configuration.
 Revenue Account Settings (Sales Posting G/L Settings).
 Financial transaction definition and settings with G/L.
 Inbound/Outbound IDoc flow settings.
◦ Partner
◦ Port
◦ RFC