SAP POS DM

SAP POS DM
WORK IN PROGRESS
more content coming
soon
Important TCodes
BI
display info object: rsd2
POSDM
TCodes generally start
with /posdw/
Workbench: /posdw/mon0
Customising: /posdw/img
1-step Outbound
Dispatcher: /posdw/pdis
2-step Outbound
Dispatcher: /posdw/odis
delete (without archiving):
/posdw/dele
change task status: /posdw/tsch
recreate workbench index:
/posdw/refi
Message Logs
view logs across branches:
sa38 -> /posdw/display_messagelog
enhanced error report inc. financial
impact: sa38 -> /posdw/display_messages_agg
XML transaction
import: /posdw/xml_in
export: /posdw/xml_out
Basis
Archive administration: sara
view application log: slg1
list TCodes: se93
BFC/BAPI
function builder: se37
IDoc
create: we19
process from queue: bd87
find: we02
process all selected: we14
Database
DB structure: se11
DB data: se16
PIPE
stands for POS Inbound
Processing Engine
storage
/POSDW/TLOGS TLog information
/POSDW/TLOGL TLog information for
very large TLogs to improve storage
efficiency
rarely used
only header fields are
visible using SE16
line items and supplemental data
stored as binary strings in LRAW
fields not visible in SE16
can be accessed using
function modules
POS Analytics
based on BI
deployed as part of BI_CONT
default views on transaction data
by Article/Store
by Receipt/Article
Store Performance
Cashier Performance
role-based reporting
default roles:
Store Manager
Regional Manager
National Manager
different levels of reports
delivered via portal & BI web reports
uses BI InfoObjects for data storage
Standard Architecture
POSDM Benefits
decoupling of POS system(s)
with back end
perform data checks and validation
reprocess failed transaction data
data processing
aggregation
forward data to different
receiving systems
master data look-up (enrichment)
increased performance of ERP
(less transactional load)
Data Model
Transaction Log (TLog)
XML-based standard data
model of a POS transaction
maps directly to a customer
interaction at the POS
Header-level
information about a
transaction
operator ID
store ID
start & end date
etc.
Records for each article
purchased as line items
article identifier (e.g. EAN barcode)
quantity
Unit of Measure (UOM)
Price
Tax impact
Supplemental Data
free-form XML space for
customer-specific data
extensions
directly associated with a line item
processed as a "BLOB" in
POSDM by default
Records for each tender
action
allows for multiple different
methods of payment
may contain payment details
(e.g. cheque number)
Supplemental Data
free-form XML space for customer-specific
extensions at the transaction
level
logically at the same level as
header elements
installed on a BI system
included with BI_CONT
(POS Analytics only)
logically separate and
independent from SAP BI
Application Component
BW-BCT-ISR-PIPE (PIPE
only)
18