INTRODUCTION
Point of sale (POS) or checkout is the location where a transaction occurs in exchange for goods or services. The point of sale often refers to the physical electronic cash register or dedicated POS hardware (or "terminal") used for checkout, but the POS is simply the location where the sale is conducted, money changes hands and a receipt is given, which can also occur on a smartphone, tablet, laptop, or mobile POS device when the right hardware and POS software is combined with the mobile device.
SAP POS DM (SAP Point-of-Sale Data Management): The SAP for Retail solution portfolio supports with a cost effective, comprehensive POS data management solution that enables "trickle-feed" processing. Cash register sales data from individual store locations can be transmitted to back-office systems on a regular basis throughout the business day. This application is called POS DM.
With POS DM you
• can cleanse and audit your Point-of-Sales transactions
• can see which products sell the strongest in all of its regions
• gauge price sensitivity across different markets or different areas within the market
• evaluate the effectiveness of promotions
• compare and contrasts how products sell when they are promoted versus being sold at everyday prices
BASIC PROCEDURE
Sales data is uploaded in a predefined cycle and mapped in such a way that it can be processed by SAP POS DM. The data is then aggregated and passed from POS DM to SAP Retail and SAP NetWeaver up to the last transaction. POS DM enables rapid inbound processing with regard to master data and duplicate checks.
POS DM does not, however, simply forward data but rather prepares it especially for subsequent processing. The preparatory work includes data cleansing that is, improving the data quality by eradicating simple errors such as incorrect article references. At this stage already, data can be aggregated for high performance further processing. The SAP POS Data Management application is based on the SAP NetWeaver Business Intelligence Solution.
Data is received either as an IDoc or in XML or BAPI format. SAP NetWeaver Process Integration (PI) can also play a part in converting the data, when it is utilized for the POS conversion. Sales and receipt data can be transmitted in an XML format derived from the data model of the Association for Retail Technology Standards (ARTS). This data is then converted and transmitted to SAP POS DM, where it is made available to back-end solutions for operational requirements.
The transmitted sales data is relevant for the following functions:
• Providing POS data to SAP Netweaver BI
• Providing POS data to the POS interface, inbound in SAP Retail
• Providing POS data to a variety of applications for multiple purposes, e.g. to SAP Forecasting and Replenishment
BUSINESS PROCEDURE
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 statements. Due to its volume and high level of detail, this data is one of the major challenges to a retailer's IT landscape.
ABAP'S ROLE
The SAP POS Data Management (SAP POS DM) application is used to receive, audit, process and analyze transactional data from your stores.
It includes the following integral parts:
Generation of POS Transactions
You wish to create POS transactions in the PIPE in order to check them in the PIPE and to be able to forward the related data to the linked follow-on systems.
There are several ways to generate POS transactions:
• POS Inbound via BAPI
This function enables you to transfer POS transaction data synchronously from the POS store system to the PIPE. The use of the BAPI /POSDW/BAPI_POSTR_CREATE is the preferred method for sending POS transaction data from a store to the PIPE and, if appropriate, processing the data immediately (see also Real-Time Individual Processing (Trickle Feed)).
• POS Inbound via IDoc
You can use different IDoc types in order to transfer different data from the POS system to the PIPE. In addition to the standard POS IDoc types, a generated IDoc (message type /POSDW/POSTR_CREATEMULTIPLE) is also available:
POS IDoc types:
You can use the following POS IDoc types for data transfer:
• WPUBON: Transfer Detailed Sales Data to PIPE
• WPUUMS: Transfer Sales Data Without Means of Payment Info to PIPE
• WPUTAB: Transfer Means of Payment Information to PIPE
• WPUFIB: Transfer Financial Transactions to PIPE
• WPUKSR: Transfer Cashier Data to PIPE
• WPUWBW: Transfer Goods Movements to PIPE
• Generated ALE Interface: You can use the generated message type /POSDW/POSTR_CREATEMULTIPLE for data transfer to PIPE. This way you can transfer the same POS transaction data as with BAPI /POSDW/BAPI_POSTR_CREATE since the structure of the message type comprises all elements of the BAPI structure. The interface then matches. The only difference is that the transfer is asynchronous with use of the IDocs.
•Create Using the POS Workbench
You manually generate POS transactions in the PIPE in order to use them productively or for test purposes. Start the POS Workbench and generate whatever POS transactions you wish as described under Editing POS Transaction Data.
•Using the Point Of Sale Transaction In inbound service interface
Analytics, including:
Customers implementing SAP POS DM on SAP NetWeaver BW powered by SAP HANA can also take advantage of the POS In-Memory Analytics content available for SAP POS DM.
Example Code:
METHOD /posdw/if_ex_fre_output~call.
DATA: ls_transaction TYPE /posdw/transaction_int,
ls_plant TYPE /rtf/_s_plant,
ls_settings TYPE /posdw/ref_settings.
FIELD-SYMBOLS: <fs_timelines> TYPE /posdw/fre_values_no_sty.
READ TABLE it_transactions INDEX 1 INTO ls_transaction.
IF sy-subrc = 0.
CALL FUNCTION '/POSDW/SETTINGS'
IMPORTING
o_settings = ls_settings.
CALL METHOD /rtf/cl_plant=>plant_single_read_by_customer
EXPORTING
i_custpl = ls_transaction-retailstoreid
i_infoobject = ls_settings->md_bwio_plant
IMPORTING
es_plant = ls_plant.
* We can be sure that the site exists because of master data checking!
LOOP AT it_timelines ASSIGNING <fs_timelines>.
<fs_timelines>-locnr = ls_plant-plant.
ENDLOOP.
ENDIF.
ENDMETHOD
TRANSACTIONS
/POSDW/MON0 - POS WB: Selection and Overview Project Systems - Project Planning Board
/POSDW/QMON - Monitor for Inbound Queue CO - Product Cost Controlling Information System
SARA - Archive Administration Basis - Archive Development Kit
/POSDW/MON1 - POS WB: Overview Yesterday and Today CO - Profitability Analysis
WE21 - Port definition Basis - ALE Integration Technology
/POSDW/PDIS - POS Data Parallel Processing MM - General Functions
/POSDW/LOGS - Log Display POS Data Management BW - OLAP Technology
ONCE - IS-HCM List of partner system sett. IS - Basic Data
/POSDW/ODIS - PIPE Outbound Processing QM - Inspection Planning
WE60 - Documentation for IDoc types Basis - ALE Integration Technology
STANDARD POS-DM PROGRAMS/Function Modules/Methods
Search using F4 help with the keyword /POSDW/*
