Fields Definition
Ration Types
Ratio Types and formulas used (by default) to calculate the output measure.
|
Field |
Formula |
|---|---|
|
Gross Margin % |
Gross Margin / Invoice Price |
|
Price Leakage % |
(Local List Price – Net Price) / Local List Price |
|
Price Realization % |
Invoice Price / Global List Price |
|
Incentive % |
Net Sales Column / Local List Price Column |
|
Average Price Per Unit |
Invoice Price / Quantity |
|
Average Profit Per Unit |
Gross Margin / Quantity |
|
Custom |
Input values are provided manually as numerator and denominator in the formula. |
Actual Period
|
Field |
Formula |
|---|---|
|
Start |
(Final Interval) – ((Number Of Intervals) * Interval Size) |
|
End |
Calendar unit defined by Final Interval. |
Comparison Period
|
Field |
Formula |
|---|---|
|
Start |
(Final Interval – Offset of Comparison Period) – ((Number Of Intervals) * Interval Size) |
|
End |
Calendar unit defined by (Final Interval – Offset of Comparison Period). |
Used Advanced Configuration Fields
Path
Administration > Configuration > System Configuration > Advanced Configuration Options
List of Advanced Configuration Fields
-
datamartName -
pricingDate -
productId -
customerId -
grossMargin -
quantity -
invoicePrice -
firstDayOfWeek– Defines the day which is considered a starting day of a week (typically Sunday or Monday). -
localListPrice -
globalListPrice -
netPrice -
pricingDateDay(optional) -
pricingDateWeek(optional) -
pricingDateMonth(optional) -
pricingDateQuadWeek(optional) -
pricingDateQuarter(optional) -
pricingDateYear(optional)
Example
|
Name |
Value |
|---|---|
|
|
JSON
|
Increase Query Performance
Increase query performance by using configurable fields. When the query data Interval Size must be recalculated (CONCAT) for each result row (e.g. With Interval Size = Day, extracted the date 13/11/2023 into 2023-D312), there can be performance issues due to large data.
To avoid this issue, there are new fields that can be configured optionally during deployment via PlatformManager, such as:
-
pricingDateDay -
pricingDateWeek -
pricingDateMonth -
pricingDateQuadWeek -
pricingDateQuarter -
pricingDateYear
These fields can be optionally mapped to the Datamart fields of the same names through the configuration SIP_AdvancedConfiguration.
As this configuration step is optional, it may happen that the fields do not exist in the Datamart or have not been mapped in SIP_AdvancedConfiguration. In such case, the old way (extracting pricingDate into the corresponding Interval Size for each result row) will be used.