PSP Transaction Module

This module displays transaction and forecast data about products.

Module Visible Elements

Visible elements of the Transaction module are Sales Volume YTD, Turnover YTD, Last Year Sales Volume, Last Year Turnover, Last Period Volume, Last Period Turnover, Sales Volume Forecast, and Turnover Forecast. These elements display transaction and forecast data of the product, which are sales data for the last year and forecast data for the next year.

Last Period Calculation

The last period configuration allows flexible data lookup. The time units used in this calculation (days, weeks, months, and years) are not days counting from the beginning. In other words, when specifying the last period time as 1 week, it does not mean taking 7 days from the calculation day backward.  The calculation takes only periods that are finished and a week starts on Sunday, ends on Saturday.

For example, the calculation date is 22 September 2020, and the last period configuration "1 week". The result will be the data from 13 September to 19 September.

Forecast Types

To configure the forecast type, see Forecast Config (PriceSettingConfig).

Currency Exchange

Transaction data may point to Product Extensions, Datamart or Data Source. In the Price Setting Package, the PL/PG logic will ignore the “currency" field in Datamart source tables as the exchange rate has been applied during the data transition from Data Source to Datamart. The exchange rate is only applied when the Datamart’s currency and the calculation's currency are different.

When the transaction data source points to Data Source, the “currency" field of the pointed Data Source table will be utilized. For details, see https://pricefx.atlassian.net/wiki/spaces/KB/pages/22183992.

When the transaction data source points to Product Extensions, the currency is converted using the ExchangeRate PP. For details, see ExchangeRates PP.

Lookup

Transaction data lookups return aggregated data for the current and all children dependency levels and there is no fallback like other lookups. Transactions are records of anything being sold. If something has been sold in a city, it means that these transactions should also appear as being sold in the country.

If there is no dependency defined, e.g. a small company working only in a country, without changing their prices depending on the regions, it will grab all transactions.

Example:

Open

It collects everything from Germany and levels defined as children, and children's children, etc. In this example, Germany data = Germany + Berlin + Hamburg + Local store + Local store. It does not include nodes at the same level, which are France and Poland in this case.

Configuration

Set Module Status

Set the module status in the PriceSettingModules PP table whose module name is PSP_TRANSACTION_MODULE

Set Transaction Data Source

• For transaction data source, set it in the PriceSettingConfig PP at the key Transaction Source. For details, see Transaction Lookup (PriceSettingConfig).

• For transaction dependency mapping, set it in the DependencyMapping PP table at the key Transaction. Details can be found at DependencyMappingConfig PP.

Configure Forecast Calculation

• For forecast setting, set it in the PriceSettingConfig PP at the key Forecast. For details, see Forecast Config (PriceSettingConfig).

• For transaction dependency mapping, set it in the DependencyMapping PP table at the key Forecast. Details can be found at DependencyMappingConfig PP.

Configure Last Period Calculation

To configure the last period calculation, set it in the PriceSettingConfig PP at the key Last Period Transaction. For details, see Last Period Config (PriceSettingConfig).

Warning