Pricefx Classic UI is no longer supported. It has been replaced by Pricefx Unity UI.

 

How to Set up Rebate Calculations


Aim of this articleExplains how to create and configure rebate calculations. There are two main ways of determining which Rebate Records are to be calculated by such a task:
  1. Using a static filter on the Rebate Record set.
  2. Using a so called feeder logic which is a sort of algorithmic filter.
Related sections

Rebate Calculations (Reference Manual)

Steps:

  1. Go to Rebates > Rebate Calculations.
  2. Create a new calculation task.
  3. Decide whether to use a static filter (Step 2 Rebate Records) or a feeder logic (Step 3 Calculation).

    1. When using a static filter, configure it in Step 2 Rebate Records.
      In this example, the calculation is for all VolumeDollar (Rebate Type) Rebate Records in the 1st quarter of 2016, and only if the Rebate Agreement was approved.
    2. When using a feeder logic, set it in Step 3 Calculation. When a feeder is used, any filter set in Step 2 Rebate Records is ignored.
      A feeder can have inputs just like any other logic, but in this example all the inputs are provided by the logic.

      A feeder can be used where a static Rebate Record filter falls short, for example if you want to: parametrize the Rebate Record-selection (using feeder inputs), implement an incremental calculation mechanism, perform multi-step filtering logic (first find relevant agreements, then Rebate Records within those agreement), etc.

      (warning) The Calculation section also allows you to specify a 'logic', which would then be used to calculate the Rebate Records (instead of the logic set on the Rebate Type). This is an option in advanced simulation scenarios where the Rebate Record calculation logic deviates too much from the regular accruals calculation logic.

      Feeders are created under the Price Setting Calculation Logic header – the reason for this is that they do not (always) implement specific Rebates logic and can be used for multiple purposes, not just in a Rebates or Analytics calculation.

      In this case, though, the only application is in a Rebate Record calculation. A feeder that finds all Rebate Records in draft agreements, not re-calculated since a modification was made to those agreement can be implement liked this (feeder JSON example attached):
  4. Save the calculation and run it (Run now icon at the top) and/or schedule it.

Found an issue in documentation? Write to us.

Â