Extend valid combinations for sales history transactions

The default interface service for defining valid combinations is extended to consider combinations from SC_SALES_HIST_TRX when it is configured as the main source table for sales history. Where exclusively using Sales History Transactions (SALES_HIST_TRX), such as in the LN-SCP integration for Demand, this is considered for setting valid combinations and a weighted spread for Demand.

The DPLS - SCV - Import Demand Valid Combinations interface service is updated.

SC_SALES_HIST_TRX is considered by the interface service where the dpls_sales_hist_to_use application variable has the SC_SALES_HIST_TRX value. The default value for the application variable remains SC_SALES_HIST_AGGR, maintaining existing behavior on upgrade.

Note: This feature is available after loading the demand (dpls.zip) template for this release. You are not required a new role or privilege access to use this feature.