My Oracle Support Banner

Inaccurate SLS_TRX_COUNT In Customer Sales Aggregate Table (Doc ID 2984111.1)

Last updated on OCTOBER 31, 2023

Applies to:

Oracle Retail Merchandising Insights - Version 16.0.1 and later
Information in this document applies to any platform.

Symptoms

Inaccurate SLS_TRX_COUNT in Customer Sales Aggregate table

Transaction count in W_RTL_SLS_CUST_LC_DY_A is overstated due to the grouping of sales by RTL_TYPE_WID. If a certain TRAN_SEQ_NO or SLS_TRX_ID both has Regular and Promo items, that certain transaction will count as 2 transactions when loaded to W_RTL_SLS_CUST_LC_DY_A sales table

 
Steps to reproduce:
-----------------------
1. Run ODI Batch PLP_RetailSalesCustLcDyFactAggregateLoad or slscslcdyaplp.ksh
2. Verify the TMP data and Merge query.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.