In this process, you enhance the transaction header, item, or tender information to accelerate the querying of data using SAP HANA Content for SAP Customer Activity Repository.
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 |
|
| 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. |
|
| The included taxes and discounts for individual transaction line items are totaled and written to dedicated item analytics fields in the 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. |
| 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
.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 Customer Activity Repository (DISTVOID
field of the TLOGF
table). This allows voided transactions and line items to be excluded from the calculations performed by SAP HANA Content for SAP Customer Activity Repository.
For more information on how SAP Customer Activity Repository 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.
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 as required for your implementation and you have checked the correctness of the other task settings.
Under
, 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
.You have ensured that the task to be carried out is assigned to the relevant task group under
.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.