Features
Features:

Product Tour >

Edraw AI >

Paid Plans:

Individuals >

Business >

Eduaction >
Resources
Blog

History

How-tos & Tips

Discovery

Biography

Business Analysis

Examples

AI concept Map

Free AI Mind Map Generator

Onenote Mind Map

Bcg Matrix Examples

Nike Marketing Strategy

Unilever SWOT Analysis

Make Mind Maps in Google Docs

Guide

FAQs

What's New

Resource Center
Templates
All Templates

Brain Storming Templates

Strategy and Planning Templates

Project Management Templates

Product Management Templates

Human Resources Templates

Agile Workflow Templates

Marketing Templates

Education Templates

Fun and Games Templates

User Gallery
Download
Pricing
Enterprise

MindMap Gallery SAP POS DM

SAP POS DM

This mind map is about SAP POS DM. Start to use a mind map to express and organize your ideas and knowledge right now.

Edited at 2020-10-08 08:27:59

Captain O Captain

Recent works View more works>>

SAP POS DM

Captain O Captain

Recent works View more works>>

Recommended to you
Outline

40k classes
- 2.1k
- 3
- 1
Oliveettom
Cisco IOS interface
- 640
- 6
Roy Mustang
application development and deployment
- 926
- 14
- 2
Roy Mustang
Data Sanitization Tools
- 428
- 4
- 1
Roy Mustang
DATA COLLECTION MEASURES
- 702
- 5
- 1
Roy Mustang
Android
- 489
- 2
- 1
Roy Mustang
Java Training
- 1.9k
- 16
- 2
Roy Mustang
Active reading techniques
- 629
- 5
- 3
Study Smarter
Classification of visual languages
- 383
- 3
Study Smarter
Game Theory
- 1.4k
- 15
- 4
Fiona_

SAP POS DM

WORK IN PROGRESS

more content comingsoon

Important TCodes

display info object: rsd2

POSDM

TCodes generally startwith /posdw/

Workbench: /posdw/mon0

Customising: /posdw/img

1-step OutboundDispatcher: /posdw/pdis

2-step OutboundDispatcher: /posdw/odis

delete (without archiving):/posdw/dele

change task status: /posdw/tsch

recreate workbench index:/posdw/refi

Message Logs

view logs across branches:sa38 -&gt; /posdw/display_messagelog

enhanced error report inc. financialimpact: sa38 -&gt; /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 InboundProcessing Engine

storage

/POSDW/TLOGS TLog information

/POSDW/TLOGL TLog information forvery large TLogs to improve storageefficiency

rarely used

only header fields arevisible using SE16

line items and supplemental datastored as binary strings in LRAWfields not visible in SE16

can be accessed usingfunction 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 &amp; 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 differentreceiving systems

master data look-up (enrichment)

increased performance of ERP(less transactional load)

Data Model

Transaction Log (TLog)

XML-based standard datamodel of a POS transaction

maps directly to a customerinteraction at the POS

Header-levelinformation about atransaction

operator ID

store ID

start &amp; end date

etc.

Records for each articlepurchased as line items

article identifier (e.g. EAN barcode)

quantity

Unit of Measure (UOM)

Price

Tax impact

Supplemental Data

free-form XML space forcustomer-specific dataextensions

directly associated with a line item

processed as a &quot;BLOB&quot; inPOSDM by default

Records for each tenderaction

allows for multiple differentmethods of payment

may contain payment details(e.g. cheque number)

Supplemental Data

free-form XML space for customer-specificextensions at the transactionlevel

logically at the same level asheader elements

installed on a BI system

included with BI_CONT(POS Analytics only)

logically separate andindependent from SAP BI

Application ComponentBW-BCT-ISR-PIPE (PIPEonly)