Show TOC

Function documentationAggregation Tasks Locate this document in the navigation structure

 

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

You have made the following settings in PIPE Customizing.

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

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

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:

Task Code

Task Description

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.