Saphelp Posdm

(1)

SAP POS Data Management

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_posdm/helpdata/en/c8/642344102740f1ba74a9be390e4ac5/content.htm Created on August 12, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included. The selected structure has more than 150 subtopics. This download contains only the first 150 subtopics. You can manually download the missing subtopics.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

(2)

Table of content

1 SAP POS Data Management

1.1 POS Inbound Processing Engine

1.1.1 Generation of POS Transactions

1.1.1.1 POS Inbound

1.1.1.1.1 Use of the BAPI /POSDW/BAPI_POSTR_CREATE

1.1.1.1.2 Use of IDocs

1.1.1.2 Generation Using the POS Workbench

1.1.1.3 Real-Time Individual Processing (Trickle Feed)

1.1.2 Aggregation of POS Transactions

1.1.2.1 Aggregation in Task Processing

1.1.2.2 Forming of Aggregates

1.1.3 Task Processing

1.1.3.1 Sending Data to SAP CRM

1.1.3.2 Using the PIPE Dispatcher

1.1.3.3 Sending Data to POS Analytics

1.1.3.4 Sending Data to SAP Retail

1.1.3.4.1 Sending Sales Data via IDoc WPUBON

1.1.3.4.2 Sending Sales Data via IDoc WPUUMS

1.1.3.4.3 Sending Means of Payment Data via IDoc WPUTAB

1.1.3.4.4 Sending Financial Transaction Data via IDoc WPUFIB

1.1.3.4.5 Sending Goods Movement Data via IDoc WPUWBW

1.1.3.5 Sending Data to SAP F&R

1.1.3.6 Sending Data to Credit Card Settlement

1.1.3.7 Outbound of sales data to SAP DMF-based applications

1.1.3.8 Task Processing for POS In-Memory Analytics

1.1.3.8.1 Enhancing Transaction Data for POS In-Memory Analytics

1.1.3.8.2 Supplying POS In-Memory Analytics with Distributed Transaction D

1.1.3.8.3 Determining Transaction Data Status

1.1.3.9 Aggregation Tasks

1.1.3.10 Using Outbound Tasks

1.1.3.11 Tasks for Checking Transactions

1.1.3.11.1 Check for Duplicate Transaction Numbers

1.1.3.11.2 Displaying Gaps in Receipt Numbers

1.1.3.11.3 Checking Comparisons for Totals Transactions

1.1.3.12 Rules

1.1.3.12.1 Check for Balanced Transaction

1.1.3.12.2 Comparing Receipt Data and Cash Desk Totals

1.1.3.12.3 Check for Performance of Sales Audit

1.1.3.12.4 Credit Card Data Check

1.1.4 Outbound Processing of Aggregates

1.1.4.1 Performing Outbound Processing

1.1.5 Archiving Transaction Data

1.1.6 Providing POS Transactions for Online Stock Queries and Inventor

1.1.7 Encryption of Payment Cards

1.1.8 Roles

1.1.8.1 Sales Auditor/POS Monitoring

1.1.8.2 POS Inbound Processing Engine (PIPE) Administration

1.1.9 Enterprise Services

1.1.9.1 Point Of Sale Transaction Processing

1.1.9.1.1 Point Of Sale Transaction

1.1.9.1.1.1 Point Of Sale Transaction In

1.1.9.1.1.1.1 Create Point Of Sale Transaction as Bulk

1.1.9.1.1.2 Point Of Sale Transaction Out

1.1.9.1.1.2.1 Request Loyalty Membership Activity Journal as Bulk

1.2 Carrying Out of Sales Audits

1.2.1 Use of the POS Workbench

1.2.1.1 Display of Secure Data

1.2.1.2 Selection and General Settings

1.2.1.3 Checking the Data Transfer

1.2.1.4 Control of Task Processing

(3)

1.2.1.5 Analyzing Errors and Messages

1.2.1.6 Display of Processing History and Follow-On Documents

1.2.1.7 Editing POS Transaction Data

1.2.1.8 Searching for POS Transactions

1.2.1.9 Mass Changes to POS Transactions

1.2.1.10 Display of Stores Without Communication

1.2.1.11 Carrying Out Ad Hoc Analyses

1.2.1.12 Monitoring of POS Aggregates

1.2.2 Automatic Checks

1.2.2.1 Master Data Checks

1.2.2.2 Rules

1.2.3 Short/Over Balancing

1.2.3.1 Determining Short/Over Differences

1.2.3.2 Checking the Short/Over Status

1.2.3.3 Verifying/Manually Processing Short/Over Differences

1.2.3.4 Sending Short/Over Differences Using IDoc WPUFIB

1.3 Analytics

1.3.1 POS Analytics

1.3.2 Trade Foundation Analytics

1.3.3 POS In-Memory Analytics Content

1.3.3.1 Roles

1.3.3.2 Analytic Views

1.3.3.2.1 Average Number of Items per Transaction

1.3.3.2.2 Average Sales per Transaction

1.3.3.2.3 Sales

1.3.3.2.4 Markdown Sales

1.3.3.3 Key Figures

1.3.3.3.1 Counter

1.3.3.3.2 Discount Value

1.3.3.3.3 Distributed Discount

1.3.3.3.4 Distributed Included Transaction Tax

1.3.3.3.5 Normal Sales Value

1.3.3.3.6 Tax Included

1.3.3.4 Characteristics

1.3.3.4.1 Business Transaction

1.3.3.4.2 Calendar Day

1.3.3.4.3 Calendar Month

1.3.3.4.4 Calendar Week

1.3.3.4.5 Calendar Year

1.3.3.4.6 Classification of Sales Item: Category

1.3.3.4.7 Classification of Sales Item: Subcategory

1.3.3.4.8 Credit/Debit Indicator at Line Item Level

1.3.3.4.9 Credit/Debit Indicator at Transaction Level

1.3.3.4.10 Customer Number of Plant/Store

1.3.3.4.11 Hour

1.3.3.4.12 Item ID

1.3.3.4.13 Markdown Sales Transactions

1.3.3.4.14 Material Group

1.3.3.4.15 Offer

1.3.3.4.16 Promotion

1.3.3.4.17 Reason

1.3.3.4.18 Record Qualifier

1.3.3.4.19 Retail Type Code

1.3.3.4.20 Retailstrid, Bussdaydate & TransIndx

1.3.3.4.21 Start Date

1.3.3.4.22 Start Time Stamp (Time)

1.3.3.4.23 Task Canceled

1.3.3.4.24 Transaction Type Code

1.3.3.5 MultiProviders

1.3.3.5.1 Sales

1.3.3.5.2 Markdown Sales

1.3.3.5.3 Number of Sales

(4)

1.3.3.5.4 Average Sales per Transaction

1.3.3.5.5 Average Number of Items per Transaction

1.3.3.6 Info Cubes

1.3.3.6.1 Sales

1.3.3.6.2 Markdown Sales Transactions

1.3.3.6.3 Number of Transactions

1.3.3.6.4 Averages Sales per Transaction

1.3.3.6.5 Average Number of Items per Transaction

1.3.3.7 Queries

1.3.3.7.1 Sales Summary

1.3.3.7.2 Gross Sales

1.3.3.7.2.1 Gross Sales Summary

1.3.3.7.2.2 Gross Sales Rolling Time Period Trend

1.3.3.7.2.3 Gross Sales Top Location Performers

1.3.3.7.2.4 Gross Sales Bottom Location Performers

1.3.3.7.2.5 Gross Sales Top Merchandising Category Performers

1.3.3.7.2.6 Gross Sales Bottom Merchandise Category Performers

1.3.3.7.2.7 Departments Gross Sales for a Given Location and Items Gross Sal

1.3.3.7.3 Net Sales

1.3.3.7.3.1 Net Sales Summary

1.3.3.7.3.2 Net Sales Rolling Time Period Trend

1.3.3.7.3.3 Net Sales Top Location Performers

1.3.3.7.3.4 Net Sales Bottom Location Performers

1.3.3.7.3.5 Net Sales Top Merchandising Category Performers

1.3.3.7.3.6 Net Sales Bottom Merchandise Category Performers

1.3.3.7.3.7 Departments Net Sales for a Given Location and Items Net Sales f

1.3.3.7.4 Discounts

1.3.3.7.4.1 Discounts Summary

(5)

1 SAP POS Data Management

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:

POS Inbound Processing Engine (PIPE) Analytics, including:

POS Analytics

POS Analytics data supplied to Trade Foundation Analytics

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.

Loss Prevention Analytics

Loss Prevention Analytics (LPA), a set of analytical tools helping you to identify critical POS transactions, can only be used if you use SAP POS Data Management. For more information, see the Loss Prevention Analytics application help.

1.1 POS Inbound Processing Engine

Using the POS Inbound Processing Engine (PIPE), you can receive and process movement data from your stores. The PIPE can process the following data: Sales and returns including the related tax data and discount information

Means of payment data Financial transactions Goods movements

Totals records and cashier statistics

The PIPE updates the transaction data and makes it available for further processing. You have the following options:

Checking and correction of the data from the transferred POS transactions Summarization of the data of POS transactions in order to reduce the data volume

Supply of follow-on systems (for example, SAP BI, SAP Retail or SAP F&R) with the data from the POS transactions for further processing.

Integration

The transferred sales data is relevant for providing the following functions in SAP for Retail with POS data: Supply of POS data to Business Content for POS Analytics and Point of Sale in SAP BI Supply of the POS Interface Inbound in ERP and SAP R/3 with POS data

Supply of SAP Forecasting and Replenishment in SAP SCM with POS data Supply of credit card settlement with POS data

(6)

Features

Generation of POS transactions:

This includes both the manual creation of POS transactions and the conversion of data that is received in different formats such as IDocs of message types WPUBON, WPUUMS, WPUTAB, WPUWBW, WPUFIB and WPUKSR or also in BAPI format.

Carrying out of the sales audit with the POS Workbench You have the following options:

Manual check of the data transfer Error and message analysis

Display of processing history and follow-on documents Search for POS transactions

Changing POS transactions Carrying out checks for transaction data This includes the following:

Carrying out of automatic master data checks Check for Duplicate Transaction Numbers Display of gaps in receipt numbers

Check for balanced sales and tender totals of POS transactions Comparing receipt data and cash desk totals

Checking credit card data

Summarization of transaction data using automatic aggregation when sending POS data to follow-on systems or by formation of aggregates Supply of follow-on systems with POS transaction data

This includes the following: Send data to SAP BI

Send sales data via IDoc WPUBON to SAP Retail Send sales data via IDoc WPUUMS to SAP Retail Send sales data via IDoc WPUTAB to SAP Retail

Send financial transaction data via IDoc WPUFIB to SAP Retail Send goods movement data via IDoc WPUWBW to SAP Retail Send data to SAP F&R

Send data to credit card settlement

1.1.1 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 POS Inbound via IDoc Create Using the POS Workbench

Using the Point Of Sale Transaction In inbound service interface

1.1.1.1 POS Inbound

This function enables you to transfer transaction data from the POS system to the PIPE for further checking and processing.

Features

The system provides the following alternatives for supplying the PIPE with POS transaction data: Synchronous Transfer with the Standard BAPI Structure

Asynchronous Transfer Using IDocs

Master data checks are automatically carried out during the inbound processing as described in Master Data Checks. By default, the following BAdIs are activate in the inbound processing:

BAdI: POS Transaction Aggregation on Header Level BAdI: POS Transaction Aggregation on Item Level BAdI: POS Transaction Aggregation on Tender Level BAdI: POS Transaction Data Distribution to Item Level

BAdI: POS Transaction Inbound Data Status Processing Enablement

For more information on the BAdIs listed above, refer to their corresponding descriptions in the SAP POS DM Customizing. Also, see Task Processing for In-Memory Analytics.

1.1.1.1.1 Use of the BAPI /POSDW/BAPI_POSTR_CREATE

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)).

(7)

Features

You have set up an RFC-capable program that transfers the POS transaction data from the store system to the BAPI and maps it to the required structures and fields.

Activities

The store system transfers the data of the POS transactions to the BAPI /POSDW/BAPI_POSTR_CREATE . The BAPI receives the data and posts it to the connected database. The POS transactions are generated automatically.

1.1.1.1.2 Use of IDocs

This function enables you to use IDocs to transfer POS transaction data from the POS store system to the PIPE and to make use of the advantages of asynchronous transfer.

Activities

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.

1.1.1.2 Generation Using the POS Workbench

In this process, you manually generate POS transactions in the PIPE in order to use them productively or for test purposes.

Process

Start the POS Workbench and generate whatever POS transactions you wish as described under Editing POS Transaction Data.

1.1.1.3 Real-Time Individual Processing (Trickle Feed)

You can use this function to transfer POS transactions from the POS system to the PIPE in order to process them in real time and to supply the follow-on systems with the corresponding data. Real-time individual processing therefore, comprises the complete processing of POS transaction data, and the POS inbound is only the first part of this.

Activities

You transfer the occurring transaction data regularly and in real time to the PIPE using one of the POS Inbound options. Prioritize the tasks to be carried out and assign them the task type Immediate Processing in order to carry out automatic checks and rules or to quickly supply follow-on systems with data. As soon as a POS transaction is posted in the PIPE, the system carries out all defined checks immediately and sends the transaction data to the follow-on systems if no errors have occurred. The processing there can now start.

Note

Carrying out certain checks (for example, the check for missing receipt numbers) can prove to be difficult in some situations with real-time individual processing.

1.1.2 Aggregation of POS Transactions

In this process, the data of POS transactions are summarized (aggregation). Then you can send this aggregated data to other systems.

(8)

Process

The system provides two options for aggregating POS transaction data. On the one hand, you can set up automatic aggregation for processing of tasks that are processed with the single-step procedure. On the other hand, you can form aggregates that are first stored in the database. These aggregates are then processed in a subsequent step.

1.1.2.1 Aggregation in Task Processing

You would like to group and aggregate POS transaction data during task processing.

Prerequisites

Ensure that you have assigned the required aggregation methods in the PIPE Customizing to the tasks to be processed in the Tasks One-Step Processing Tasks area. You can check the settings for the aggregation methods under Tasks One-Step Processing Tasks in Customizing and if you wish you can configure your own aggregation method.

Activities

The system automatically performs the aggregation of POS transaction data within task processing. You can choose between the following aggregation methods:

Aggregate Loyalty Items According to Customer Card Number:

The system aggregates loyalty data of POS transactions for each customer card number. The aggregation is also valid for loyalty data that is associated with the sales items.

The aggregation method is intended for use in connection with the task of creating and sending Loyalty Data to SAP CRM. Grouping According to Posting Date:

The system does not perform any specific aggregation for task processing, but simply groups the transactions to be processed according to their posting date. In this way they are always unique thanks to their posting date.

Aggregation According to Material:

The system aggregates sales item data of POS transactions for each material number, unit of measure and currency and creates packages within task processing.

The aggregation method is intended for use in connection with the task for creating and sending the IDoc WPUUMS. Aggregating Material with Conditions:

The system aggregates sales item data of POS transactions for each material number, unit of measure and currency. The corresponding taxes and discounts are also aggregated for the aggregation of the sales item data. The system creates the corresponding packages within the task processing. The aggregation method is intended for use in connection with the task for creating and sending the IDoc WPUUMS.

Aggregation according to F&R Type and Material:

The system aggregates sales item data of POS transactions for each material number, unit of measure and currency and creates packages within task processing.

The aggregation method is intended for use in connection with the task of sending data to SAP F&R and is generally to be used for this. Aggregation Means of Payment:

The system aggregates the means of payment of POS transactions for each posting date, means of payment type and means of payment currency and creates packages within task processing.

The aggregation method is intended for use in connection with the task for creating and sending the IDoc WPUTAB. Aggregation Means of Payment Enhanced:

The system aggregates the means of payment of POS transactions for each posting date, POS number and cashier and creates packages within task processing.

This aggregation method is intended for use in connection with the task for creating and sending the IDoc WPUTAB. Aggregate Sales Items According to ItemID and Qualifier:

The system aggregates sales item data of POS transactions for each itemID, qualifier, unit of measure, and currency, and creates packages within task processing.

The aggregation method is intended for use in connection with the task for creating and sending the IDoc WPUUMS. Aggregate Sales Items According to ItemID and Qualifier with Details:

The system aggregates sales item data of POS transactions for each itemID, qualifier, unit of measure and currency. The corresponding taxes and discounts are also aggregated for the aggregation of the sales item data. The system creates the corresponding packages within the task processing. The aggregation method is intended for use in connection with the task for creating and sending the IDoc WPUUMS.

For each of the named aggregation methods you can set an additional time grouping criterion, the aggregation period. This enables you to use the system for even finer aggregation. Only POS transactions that are in the same aggregation period are aggregated together. You can choose from the following aggregation period options:

10-minute schedule line for time stamp Posting Date

Posting date/Transaction currency Hour of time stamp

Day of time stamp Week of posting date Week of time stamp Month of posting date Month of time stamp

After aggregation the system sends the data aggregated within the task processing, for which the aggregation was performed, on to the corresponding follow-on system. For more information, see Task Processing.

1.1.2.2 Forming of Aggregates

(9)

You can use this function to summarize POS transaction data by updating it to aggregates in the database. Then, in a second step, you can process the summarized data further.

Prerequisites

Ensure that you have made the necessary settings in the PIPE Customizing. For more information, see Aggregation Tasks.

Features

Summarization of POS transaction data by way of formation of aggregates is carried out using separate tasks (aggregation tasks) that can be set for POS transactions.

For more information, see Aggregation Tasks.

1.1.3 Task Processing

In this process, you process one or more of the tasks provided by the system for specific transaction data.

Operations on POS transactions are called tasks. The system provides the following task types for processing POS transactions: Tasks for supplying follow-on systems with POS transaction data

Tasks that are to be carried out manually, where completion is retained in the PIPE as a reminder Tasks for checking transaction data

Aggregation tasks that serve to form aggregates by summarizing POS transaction data

The following table provides an overview of the tasks that are provided for processing in the standard system:

Task Code Task Description

0001 Supply BW Without Distribution

0002 Sales Audit Performed, Manual Task

0004 Supply BW with Distribution

0005 Supply of Old POS Content in BW

0009 Generate WPUBON IDoc (Non-Goods Items)

0010 Generate WPUBON IDoc

0011 Generate WPUWBW IDoc

0012 Generate WPUFIB IDoc

0013 Generate WPUTAB IDoc

0014 Generate WPUUMS IDoc

0015 Credit Card Settlement

0016 Confirmation of Credit Card Settlement

0017 Supply ERP Inventory Management

0018 Supply CRM Loyalty Interface

0020 Supply SAP Forecasting and Replenishment

0030 Check Balancing for Totals Transactions

0040 Perform Transaction Reversal

0050 Supply - DMF-Based Applications

0060 Calculation for Short/Over Balancing

0061 Send Short/Overs to ERP

0101 Oil & Gas SSR Payment Card Data Processing

1001 Check for Duplicate Transaction Numbers

1002 Check for Receipt Numbers Without Gaps

5001 LPA: Provision of Suspicious Transactions

8001 Aggregate Transaction Data for Analytics

8002 Supply Analytics Cont. with Distributed Transaction Data

8003 Determine Transaction Data Status

The specified aggregation tasks are listed under Aggregation Tasks.

Prerequisites

(10)

in PIPE Customizing.

Ensure that you have set the type of tasks to be carried out under Tasks One-Step Processing Define Tasks or Tasks Two-Step Processing Define Aggregation Task depending on the requirements to one of the values Immediate Processing , Collective Processing or Manual Processing .

Under POS Transactions , check the task group that is assigned to the relevant POS transaction and assign a task group if required. Under Tasks Define Task Group , ensure that the task group that is assigned to the transaction type of your POS transaction actually exists. Ensure that the task to be carried out is assigned to the relevant task group under Tasks Assign Tasks to Task Group .

Check also, if necessary, if processing of a task for a defined POS transaction type makes sense.

Process

Depending on the setting in PIPE Customizing for the type of task to be processed, you have the following options for carrying out task processing: Automatic task processing:

In the case of tasks with type Immediate Processing , the system carries out the processing immediately the POS transaction is created. The creation of POS transactions in the POS Workbench is an exception to this. In this case, no immediate processing takes place and you must carry out processing as described in the following section.

Task processing using POS Workbench or PIPE Dispatcher:

In the case of tasks with type Collective Processing , you must start processing of the task with an explicit call. To do this, you have the following two options:

You carry out the task processing using the POS Workbench. For more information, see Control of Task Processing.

You carry out task processing with the PIPE Dispatcher (transaction /POSDW/PDIS). For more information, see Using the PIPE Dispatcher.

Manual task processing and conversion of task status

In the case of tasks with type Manual Processing , you must set the task to Completed by way of the user interface as soon as you have completed it. To do this, use the POS Workbench.

For more information, see Control of Task Processing.

1.1.3.1 Sending Data to SAP CRM

In this process, you send the loyalty data of POS transactions to SAP CRM via the service interface LoyaltyMembershipActivityJournalCRMBulkRequest_Out .

Prerequisites

In Customizing, you created the outbound task by choosing in the IMG POS Data Management POS Inbound Processing Tasks One-Step Processing Define Tasks and by copying the Profile 0001 Task Code 0018 as a template. In the Parameters for this task, also ensure that in the Control Section, the Code for Aggregation Method is 0009.

Process

The Task Code 0018 Transfer Loyalty Data is available in the standard SAP system for sending loyalty data at header level or retail line item level that is available in POS transactions to CRM.

You send the relevant data aggregated by setting the aggregation method for task processing in task Customizing according to the customers' loyalty card number. For more information, see Aggregation in Task Processing.

You carry out processing of the task for the relevant POS transactions depending on the task type. For more information, see Task Processing. Once the task has been carried out successfully, the system sets the task status for all processed POS transactions to Completed .

1.1.3.2 Using the PIPE Dispatcher

You process one or more tasks for a quantity of POS transactions in the background.

Procedure

1. In the PIPE menu, choose POS Processing POS Data Parallel Processing and start the PIPE Dispatcher (transaction /POSDW/PDIS). 2. Set the data selection criteria you require. Enter the tasks to be processed by entering the corresponding task codes in the selection screen. In addition, you

can restrict the POS transactions to be considered by way of store, posting date, and business transaction. If you require further selection criteria, you can extend the data selection area by choosing the pushbutton Further Selections .

3. By selecting the appropriate checkbox in processing control you can: Carry out a processing test run:

The processing protocol displays the results of processing with your chosen selection criteria. The test run does not make any changes to the database.

Process errors:

Tasks that have status Error or Error During Cancellation are taken into account in processing if you first choose the status Ready or Ready to be Canceled . Remove the errors so that the system can process the relevant tasks.

Consider Customizing changes:

Tasks that have subsequently become active for POS transactions by way of Customizing changes are taken into account by the system. Switch off prioritization of task processing:

(11)

The system carries out processing of the tasks in the order in which they are entered on the selection screen. This way you can override the priorities assigned in task Customizing.

4. You can enable parallel processing using the PIPE Dispatcher. To do so, select the Parallel Processing checkbox and enter the appropriate parameters in the selection screen.

5. Then you can select the criteria for the processing protocol output. By selecting Protocols you can view the saved protocols of earlier processing. The system displays a specific selection screen for choosing the protocol. Here you can restrict the choice of the relevant protocol as well as set time restrictions, for example, for users or programs.

6. Perform the processing once you have made all the settings. The result is displayed in the processing protocol if you have activated this. If errors have occurred, the system displays a red status symbol with a corresponding error message. If a processing step was performed successfully, the system displays a green status symbol.

7. You can view the task status for individual POS transactions in the POS Workbench. More information, see Using the POS Workbench.

1.1.3.3 Sending Data to POS Analytics

In this process, you send the data from POS transactions to POS Analytics in order to create analyses and statistics such as sales analysis, error statistics, or loss prevention. For more information, see https://help.sap.com/bicontent BI Content Version Application Help Industry Solutions Trading Industries

Retail Trade Store Analytics POS Analytics .

Prerequisites

You have made the following settings in PIPE Customizing.

You have set the type of the task to be carried out under Tasks One-Step Processing Define Tasks depending on the requirements to either Immediate Processing or Collective Processing and you have checked the correctness of the other task settings.

Under POS Transactions , you have checked the task group that is assigned to the relevant POS transaction and you assign a task group if required. You have ensured that the task group, which is assigned to the transaction type of your POS transaction, exists under Tasks Define Task Group . You have ensured that the task to be carried out is assigned to the relevant task group under Tasks Assign Tasks to Task Group .

Process

The following tasks are available in the standard system for sending data to POS Analytics: 0001: Supply BW Immediately, Non-Aggregated, with Distribution

0004: Supply BW with Distribution

Carry out processing of the task for the relevant POS transactions depending on the task type. For more information, see Task Processing.

If the task has been carried out successfully, the system sets the task status for all processed POS transactions to Completed .

1.1.3.4 Sending Data to SAP Retail

You can send the data from POS transactions to SAP Retail in order to generate follow-up documents there or to process the data in other ways. The following options are available for sending POS transaction data to SAP Retail:

Send Sales Data via IDoc WPUBON Send Sales Data via IDoc WPUUMS

Send Means of Payment Data via IDoc WPUTAB Send Financial Transaction Data via IDoc WPUFIB Send Goods Movement Data via IDoc WPUWBW

Alternatively, you can also supply SAP Retail with data by generating aggregates and carrying out the corresponding outbound processing. For more information, see Outbound Processing.

1.1.3.4.1 Sending Sales Data via IDoc WPUBON

In this process you send the sales data of POS transactions, both individually and summarized, to SAP Retail. You can use the IDoc WPUBON for this to transfer the following data:

Header information of POS Transaction Data of sales items

Discount information Tax information Tender data

Prerequisites

(12)

You have ensured that the task group, which is assigned to the transaction type of your POS transaction, exists under Tasks Define Task Group . You have ensured that the task to be carried out is assigned to the relevant task group under Tasks Assign Tasks to Task Group .

Process

Both of the following tasks are available for sending sales data to SAP Retail when using the IDoc WPUBON. 0010 - Generate IDoc WPUBON

0009 - Generate IDoc WPUBON (Non-Merchandise Items)

With the provision of a separate task for non-merchandise items, you can process this item data at an early stage independently of the merchandise item data and then send it to SAP Retail.

Carry out processing of the task for the relevant POS transactions depending on the task type.

1.1.3.4.2 Sending Sales Data via IDoc WPUUMS

In this process you can send the sales data of multiple POS transactions, summarized, to SAP Retail. You can use the IDoc WPUUMS for this to transfer the following POS transaction data:

Header data: Store Posting date Transaction currency Data of sales items Discount information Tax information

Note

Transfer of tender data via IDoc WPUUMS is not possible. If you wish to transfer this data also to SAP Retail, you send, in addition to IDoc WPUUMS also the IDoc WPUTAB to SAP Retail.

Prerequisites

Process

The task 0014 Generate IDoc WPUUMS is available for sending sales data to SAP Retail when using the IDoc WPUUMS.

If you wish to send the relevant data aggregated, you have to set an appropriate aggregation method for task processing in task Customizing. For more information, see Aggregation in Task Processing.

Carry out processing of the task for the relevant POS transactions depending on the task type. For more information, see Task Processing. If the task has been carried out successfully, the system sets the task status for all processed POS transactions to Completed .

1.1.3.4.3 Sending Means of Payment Data via IDoc WPUTAB

In this process you can send means of payment data of multiple POS transactions (summarized) to SAP Retail. You can use the IDoc WPUTAB for this to transfer the following POS transaction data:

Header data: store, posting date, department, POS number, and cashier Means of payment data

Prerequisites

(13)

The task 0013 Generate IDoc WPUTAB is available in the standard system for sending means of payment data to SAP Retail using the IDoc WPUTAB. If you wish to send the relevant data aggregated, you have to set an appropriate aggregation method for task processing in task Customizing. For more information, see Aggregation in Task Processing.

Carry out processing of the task for the relevant POS transactions depending on the task type. For more information, see Task Processing. If the task has been carried out successfully, the system sets the task status for all processed POS transactions to Completed .

1.1.3.4.4 Sending Financial Transaction Data via IDoc WPUFIB

In this process you can send financial transaction data related to POS transactions to SAP Retail. You can use the IDoc WPUFIB for this to transfer the following POS transaction data:

Header data: Store Posting date Transaction number Cashier

Financial transaction data

Prerequisites

Process

The task 0012 Generate IDoc WPUFIB is available in the standard system for sending financial transaction data to SAP Retail using the IDoc WPUFIB. You carry out processing of the task for the relevant POS transactions depending on the task type. For more information, see Task Processing. If the task has been carried out successfully, the system sets the task status for all processed POS transactions to Completed .

1.1.3.4.5 Sending Goods Movement Data via IDoc WPUWBW

In this process you can send goods movement data from POS transactions to SAP Retail. You can use the IDoc WPUWBW for this to transfer the following POS transaction data: Header data Store Posting date Transaction number Cashier

Goods movement data

Prerequisites

Process

The task 0011 IDoc WPUWBW is available in the standard system for sending goods movement data to SAP Retail using the IDoc WPUWBW. Carry out processing of the task for the relevant POS transactions depending on the task type. For more information, see Task Processing. If the task has been carried out successfully, the system sets the task status for all processed POS transactions to Completed .

Sending Data to SAP F&R

(14)

Prerequisites

Process

The task 0020 Supply SAP Forecasting and Replenishment is available in the standard system for sending sales data, goods receipt information, and goods issue information to SAP F&R.

You should send the relevant data aggregated by setting the aggregation method for task processing in task Customizing according to the F&R type and material. For more information, see Aggregation in Task Processing.

You carry out processing of the task for the relevant POS transactions depending on the task type. For more information, see Task Processing. If the task has been carried out successfully, the system sets the task status for all processed POS transactions to Completed .

1.1.3.6 Sending Data to Credit Card Settlement

In this process, you send transaction data from credit card payments to credit card settlement and receive confirmation of the processing status.

Prerequisites

Process

The standard system provides the following tasks for sending transaction data to credit card settlement: 0015: Credit Card Settlement

0016: Confirmation of Credit Card Settlement

Using task 0015, you can transfer the settlement data to credit card settlement.

You carry out processing of the task for the relevant POS transactions depending on the task type. For more information, see Task Processing. The external system further processes the data asynchronously and, on completion of settlement, provides confirmation of the result of processing. The corresponding status is updated as status of the manual task 0016 in the PIPE.

1.1.3.7 Outbound of sales data to SAP DMF-based applications

You can use this function to send the sales and related data from POS sales transactions to SAP DMF-based receiver systems. This data is needed by SAP Demand Management Foundation (SAP DMF) to create suitable demand models. In addition, other applications besides SAP DMF that require up-to-date sales information can also make use of this data.

The following information is transferred:

Data for the combination of store, day, product and offer: Sales in base unit of measure

Net sales in local currency of the store Gross sales in local currency of the store Transaction count

Squared sales in base unit of measure (squared sales is calculated per transaction and then added to existing data) Cubed sales in base unit of measure (cubed sales is calculated per transaction and then added to existing data) Data for the combination of store and day:

Store traffic

You can perform the transfer in either of two ways:

One-step process - In the standard customizing (profile 0001) this is provided as the task with code 0050. Two-step process:

The aggregation of the transactions in a POS aggregate is done in the first step. The outbound of the aggregated data is done in the second step.

In the standard customizing this function is provided as follows: Aggregation of transactions is done by the task with code 2050. The POS aggregate has code 0050.

The corresponding outbound task is done by the task with code 3050.

(15)

Choose either the one-step process or the two-step process based on your processing requirements:

The advantage of the one-step process is that it has the minimum overall resource consumption (runtime, disk space). This advantage occurs when the block size is not restricted and all data to be sent is available. (The transfer of POS data takes place after shop closing when the complete POS upload has taken place). If either the block size is restricted or the transfer starts when not all data is available, sales records might be sent several times. This increases the network load as well as the workload on the receiver system.

The advantage of the two-step process approach is that each sales record is sent only once if the outbound task is executed after all transactions have been aggregated in the POS aggregate. This reduces the network load and the workload on the receiver system. In addition, if you execute the aggregation task (in a trickle feed scenario) multiple times during the day, the multiple execution as well as the restriction of the package size will have no

consequences for the transfer of data itself. If you restrict the package size you have more control over the main memory consumption. Additionally, if you execute the aggregation task multiple times during the day, you reduce the workload in the critical night window. The drawback of this approach is the higher overall workload because the POS aggregates have to be updated on the database.

Prerequisites

You have made the following settings in Customizing for POS Inbound Processing (PIPE):

You have created a suitable customizing profile by choosing General Settings Define Profiles . You have assigned the transfer relevant stores to that profile by choosing General Settings Store Settings .

You have maintained a task group for the aggregation and transfer of sales transactions by choosing Tasks Define Task Group . Transaction types:

You have maintained a transaction type group for the transfer relevant (sales) transactions by choosing POS Transactions Define Type Group for POS Transactions .

You have maintained the transfer relevant transaction types and assigned them to the corresponding transaction type group and task group by choosing POS Transactions Define POS Transaction Type .

Sales item types:

You have maintained the relevant sales item type groups by choosing POS Transactions Define Type Group for Sales Items .

You have maintained the transfer relevant sales item types and assigned them to the corresponding item type group and task group by choosing POS Transactions Define Sales Item Types .

Tax types:

You have maintained the relevant tax type groups by choosing POS Transactions Define Type Group for Taxes .

You have maintained the relevant tax types and assigned them to the corresponding tax type groups and task group by choosing POS Transactions Define Tax Types .

Discount types:

You have maintained the relevant discount type groups by choosing POS Transactions Define Type Group for Discounts .

You have maintained the relevant discount types and assigned them to the corresponding discount type groups and task group by choosing POS Transactions Discount Type .

When using the one-step process:

You have created the outbound task by choosing Tasks One-Step Processing Define Tasks (using task 0050 for profile 0001 as a copy template). You have set the task type to 1 (Collective processing). You have set the parameter DMF_APPS to a suitable value depending on the set of applications running on the receiver system.

You have maintained the RFC destination of the receiver system by choosing Tasks Define Additional Details for Tasks .

You have assigned the task to the corresponding task group for the transfer of sales transactions by choosing Tasks Assign Tasks to Task Group . When using the two-step process:

You have created the task for the aggregation of data in Customizing by choosing Tasks Two-Step Processing Define Aggregation Task (using task 2050 for profile 0001 as a copy template). You have set the task type to 1 (Collective processing). You have set the parameter DMF_APPS to a suitable value depending on the set of applications running on the receiver system.

You have created the task for the outbound of data by choosing Tasks Two-Step Processing Define Outbound Tasks (using task 3050 for profile 0001 as a copy template).

You have maintained the RFC destination of the receiver system by choosing Tasks Additional Details for Outbound Tasks .

You have assigned the aggregation task to the corresponding task group for the transfer of sales transactions by choosing Tasks Assign Tasks to Task Group .

If you have set the parameter DMF_APPS: You have ensured that for the value of this parameter an active implementation for the BAdI

/POSDW/DMF_RELEVANCE exists (see Customizing activity Integration with other SAP components DMF based applications Control the transfer relevance of products ).

Activities

The aggregation and outbound of sales data is executed using the existing PIPE framework. You can find further information under Task Processing.

1.1.3.8 Task Processing for POS In-Memory Analytics

If you have implemented SAP POS DM on SAP NetWeaver BW powered by SAP HANA and want to accelerate decision making in your business using the POS In-Memory Analytics content, the following tasks are provided for processing in the standard system:

8001 Aggregate Transaction Data for Analytics

8002 Supply Analytics Cont. with Distributed Transaction Data

(16)

For more information on tasks for POS In-Memory Analytics, see: Enhancing Transaction Data for POS In-Memory Analytics

Supplying POS In-Memory Analytics with Distributed Transaction Data Updating Transaction Data Status

Prerequisites

To use POS In-Memory Analytics and to process the associated tasks, SAP POS DM must be implemented on SAP NetWeaver BW powered by SAP HANA.

1.1.3.8.1 Enhancing Transaction Data for POS In-Memory

Analytics

In this process, you enhance the transaction header, item, or tender information to accelerate the querying of data when you use the POS In-Memory Analytics content.

By default, the enhancement of transactional data is performed during the POS Inbound process by the following activated BAdIs:

BAdI Implementation Transaction Data Enhancement Description

POS Transaction Aggregation on Header Level /POSDW/ANALYTIC_AGG_HEADER_IMP The start timestamp (or business day date, if no start timestamp is present) contained in the transaction header is decomposed into separate year, month, day, hour, and calendar week values. This accelerates grouping by time period when querying the transactional data.

POS Transaction Aggregation on Item Level /POSDW/ANALYTIC_AGG_ITEM_IMP The included taxes and discounts for individual transaction line items are totaled and written to dedicated item analytics fields in the TLOGF table. This eliminates the need for complex and time-consuming joins when querying data.

Note that the taxes and discounts included in the transaction header, and which are distributed to the transaction line items, are not included in these sums. POS Transaction Aggregation on Tender Level n/a Currently, no default implementation is provided.

If you disable the execution of these BAdIs during the POS Inbound process, you can still perform the enhancement of transactional data by using task 8001 Aggregate Transaction Data for Analytics .

For more information about the BAdIs listed above, see their accompanying documentation in the Customizing under Customer-Specific Enhancements and BAdI Implementations Enhancements for In-Memory Analytics .

Voided Transactions and Line Items

Whether you are using the POS Transaction Aggregation on Header Level BAdI, the POS Transaction Aggregation on Item Level BAdI, or task 8001 Aggregate Transaction Data for Analytics , voided transactions and line items are flagged by SAP POS DM (DISTVOID field of the TLOGF table). This allows voided transactions and line items to be excluded from the calculations performed by the POS In-Memory Analytics content.

For more information on how SAP POS DM populates the DISTVOID field, refer to the documentation accompanying the POS Transaction Aggregation on Header Level and the POS Transaction Aggregation on Item Level BAdIs.

Prerequisites

SAP POS DM implemented on SAP NetWeaver BW powered by SAP HANA.

If you are using task 8001 Aggregate Transaction Data for Analytics , you have made the following settings in PIPE Customizing:

You have set the Type of Task to be carried out under Tasks One-Step Processing Define Tasks as required for your implementation and you have checked the correctness of the other task settings.

Under POS Transactions , you have checked the task group that is assigned to the relevant POS transaction and you assign a task group if required.

You have ensured that the task group, which is assigned to the transaction type of your POS transaction, exists under Tasks Define Task Group .

You have ensured that the task to be carried out is assigned to the relevant task group under Tasks Assign Tasks to Task Group .

Process

By default, the BAdI implementations for the transaction data enhancements are activated in the POS Inbound process.

If you have chosen to deactivate the BAdI implementations for transaction data enhancements, you can use task 8001 Aggregate Transaction Data for Analytics to perform the transaction data enhancements on transactions in the TLOGF table. For more information, see Task Processing.

1.1.3.8.2 Supplying POS In-Memory Analytics with Distributed

Transaction Data

(17)

In this process, you distribute the discount, tax, and tender information contained on the header level of a POS transaction to the individual transaction line items. This distribution reduces the execution time of POS In-Memory Analytics queries.

Caution

The distribution performed in this process assumes a standard implementation of the SAP POS DM and does not take into consideration any custom sales item types or distribution requirements. Distribution can significantly impact analytic reports built on POS In-Memory Analytics Content; ensure that the standard distribution calculations fulfill your business requirements.

By default, the distribution is performed during the POS Inbound process by the following activated BAdI:

POS Transaction Data Distribution to Item Level /POSDW/ANALYTIC_DIST_ITEM_IMP The discount, tax, and tender information contained on the header level of a POS transaction is distributed to the individual line items. The distributed figures are stored in dedicated fields of the /POSDW/TLOGF table. The distribution is performed based on the line item's sales amount within a transaction as follows:

line item discount amount = transaction discount amount * [ | line item sales amount | ÷ (sum of all | transaction line item sales amounts |) ] Discounts are not distributed to line item types for which the Remove f. Distr. of Header Discounts option of the POS Inbound Processing POS Transactions Define Sales item Types Customizing activity is enabled.

line item tax amount = transaction tax amount * [ | line item sales amount | ÷ (sum of all | transaction line item sales amounts |) ]

Excluded taxes are not considered in the distribution. In the SAP POS DM Customizing under POS Inbound Processing → POS Transactions → Define Tax Types , use the Tax Included checkbox to specify if a tax type is “included” or “excluded”.

Furthermore, taxes are not distributed to line item types for which the Remove Item fr. Distr of Header Tax option of the POS Inbound Processing POS Transactions Define Sales item Types Customizing activity is enabled. line item tender amount = transaction tender amount * [ | line item sales amount | ÷ (sum of all | transaction line item sales amounts |) ] Tenders are not distributed to line item types for which the Remove from Distribution of Tender option of the POS Inbound Processing POS Transactions Define Sales item Types Customizing activity is enabled.

Note

Absolute values are used for the line item and transaction sales amounts to ensure that the ratio between the two results in a positive value.

If you disable the execution of this BAdI during the POS Inbound process, you can still perform the data distribution by using task 8002 Supply Analytics Cont. with Distributed Transaction .

For more information about the BAdI listed above, see its accompanying documentation in the Customizing under Customer-Specific Enhancements and BAdI Implementations Enhancements for In-Memory Analytics .

Prerequisites

SAP POS DM implemented on SAP NetWeaver BW powered by SAP HANA.

If you are using task 8002 Supply Analytics Cont. with Distributed Transaction , you have made the following settings in PIPE Customizing:

You have set the Type of Task to be carried out under Tasks One-Step Processing Define Tasks as required for your implementation and you have checked the correctness of the other task settings.

Process

By default, the BAdI implementation for data distribution is activated in the POS Inbound process.

If you have chosen to deactivate the BAdI implementations for data distribution, you can use task 8002 Supply Analytics Cont. with Distributed Transaction Data to perform the data distribution on transactions in the TLOGF table. For more information, see Task Processing.

(18)

1.1.3.8.3 Determining Transaction Data Status

The POS In-Memory Analytics content allows you to perform analysis directly on the POS transactional data stored in the TLOGF table in the SAP HANA database.

In this process, you verify the transactional data stored in the database prior to querying it. As a result, a data status value is stored in the TLOGF table for each transaction. SAP POS DM maintains the data status of a transaction record:

During inbound processing and when the editor is started for a particular POS transaction within the POS Workbench. The data status is determined using the following BAdI, which is activated in the POS Inbound process by default:

POS Transaction Inbound Data Status Processing Enablement

/POSDW/ANALYTIC_INB_DATASTATUS The data status is maintained for the transaction.

For more information about the BAdI listed above, see its accompanying documentation in the Customizing under Customer-Specific Enhancements and BAdI Implementations Enhancements for In-Memory Analytics .

During task processing, using task 8003 Determine Transaction Data Status . The data status of a transaction is set to one of the following values:

Data Status Description

0 (Undefined) This status is assigned to transactions on which no master data checks have been performed and no tasks have been processed.

1 (Error) This status is assigned to transactions which fail a master data check or for which at least one processing task has resulted in an Error status.

2 (Master Data Check OK; No Tasks Processed) This status is assigned to transactions that pass a master data check and for which no tasks have been processed.

3 (MD Check OK; One or More Tasks Processed, No Tasks in Error) This status is assigned to transactions that pass a master data check and for which: At least one task has been processed

All tasks that have been processed have no errors (not in Error state)

Prerequisites

SAP POS DM implemented on SAP NetWeaver BW powered by SAP HANA. You have made the following settings in SAP POS DM Customizing:

You have set the Type of Task to be carried out under Tasks One-Step Processing Define Tasks as required for your implementation and you have checked the correctness of other task settings.

You have enabled the Data Status Relevant Flag under Tasks One-Step Processing Define Tasks for all tasks that process transactional data stored in the TLOGF table and which you consider to have impact on the data status.

You have ensured that the task to be carried out is assigned to the relevant task group under Tasks Assign Tasks to Task Group . You have defined a check profile to used for data status determination under General Settings Define Check Profiles .

You have specified the identifier of a check profile in the Master Data Checks for Data Status Determination section of the General Settings Define Profiles Customizing activity.

You have enabled the Checks Using Check Profiles checkbox under General Settings Define General Settings . For more information , see Master Data Checks.

Process

Task 8003 Determine Transaction Data Status is available in the standard system for updating the data status of a transaction stored in the TLOGF table. When using task 8003 , we recommend that you also use rules to ensure that task 8003 is the last task to be executed on a transaction. For more information, see Task Processing.

Note

Manual task status changes in the POS Workbench are not detected by task 8003 Determine Transaction Data Status and will not trigger changes to the data status.

1.1.3.9 Aggregation Tasks

You use this function to summarize POS transaction data by forming aggregates that the system first stores in the database. This way you have the facility to send the summarized data to follow-on systems at a later date using the PIPE outbound processing.

Prerequisites

(19)

You have set the type of the task to be carried out under Tasks Two-Step Processing Define Aggregation Task depending on the requirements to either Immediate Processing or Collective Processing and you have checked the correctness of the other aggregation task settings.

You have ensured that the data of the aggregation level assigned to the aggregation task is set correctly under Tasks Two-Step Processing Define Aggregation Level .

Under POS Transactions , you have checked the task group that is assigned to the relevant POS transaction and you have assigned a task group if required.

Under Tasks Define Task Group , you have ensured that the task group that is assigned to the transaction type of your POS transaction actually exists.

Activities

The system summarizes POS transaction data by way of formation of aggregates using separate tasks (aggregation tasks) that you can set for POS transactions. The following table provides an overview of the aggregation tasks that are provided in the standard system. The description shows the type of aggregation:

2001 Material/Stock

2002 Material/Stock with Taxes and Discounts

2011 Register/Cashier/Department/Tender

2012 Means of Payment

2050 Material + Offer (DMF-Based Applications)

Carry out processing of the aggregation task for the relevant POS transactions depending on the task type. For more information, see Task Processing. During processing, the system forms a new aggregate if no open one exists for the chosen aggregation method. If another aggregate exists with aggregated data records, which has not yet been completed, the system aggregates the data of the POS transactions to be processed in this aggregate.

When the system has successfully carried out the aggregation task, it sets the status of the task for all processed POS transactions to Completed .

You can send the data of all the aggregates generated through aggregation tasks to other systems by way of the available outbound processing. The aggregation tasks provided, therefore, are only appropriate with use of certain outbound tasks. For more information, see Outbound Processing of Aggregates.

1.1.3.10 Using Outbound Tasks

With this function you can send data, which you have cumulated in the form of POS aggregates and updated in the database, for further processing to the follow-on system.

Prerequisites

You have made the following settings in PIPE Customizing:

You have assigned the correct aggregation task to the outbound task to be processed under Tasks Two-Step Processing Define Aggregation Task ; this must also adjust to the chosen outbound task BAdI filter.

You have checked that the further data of the outbound task is set correctly under Tasks Two-Step Processing Define Aggregation Task .

Activities

Using an outbound task and associated outbound processing, you can now send data that you previously updated in an aggregate in the aggregation task to the follow-on system. The following table provides an overview of the outbound tasks that are provided in the standard system. The description shows the type of outbound tasks:

3001 Sales data at WPUUMS IDoc

3002 Means of Payment as WPUTAB IDoc

Perform the processing of the outbound tasks for the POS aggregates required using the PIPE outbound processing. For more information, see Outbound Processing.

You can view the processing status of POS aggregates in the POS Workbench. For more information, see Monitoring POS Aggregates.

1.1.3.11 Tasks for Checking Transactions

You can check the POS transaction data using special tasks. The result of the check is reflected in the corresponding task status and remains evident until the task is processed successfully at a later time.

The system provides the following tasks in the standard for checking transaction data: 1001: Check for duplicate transaction numbers

1002: Check for Receipt Numbers Without Gaps 0030: Check Balancing for Totals Transactions