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.