The page describes the basics of Accelerator use and provides examples with screen captures.

In this section:

User Roles

To use the Rebate Manager Accelerator, you need to have the following Pricefx user roles:

If you don't want a user to manage Rebate Types, you need to remove the user role Administer RebateManager.

Define Rebate Type

Go to Rebates > Condition Types, add a new Rebate Type, and define its properties:

Name	Name of the Rebate Type
Label	Label of the Rebate Type
Pricing Logic	Should be "RebateLogic"
Condition Type Name	Maps your rebate logic with an existing Rebate Type template. Select here a suitable Rebate Type. Currently, there are more than 20 Rebate Types implemented. See their list at Rebate Types Reference (Rebate Management).
Target for	Maps your rebate logic with an existing Rebate Type template. Select one of these options: Payment Period – Gets sales for every period to compare and calculate the rebate. Annual – Gets sales for the whole year to compare and calculate the rebate.
Deposit Scheme	If 'Target for' is 'Annual', you need to define how to calculate the rebate value: Non-Cumulative – The rebate value is calculated for the current period based on cumulative sales, then divided by the number of periods (12 months or 4 quarters, 2 for semi-annually, 1 year). Cumulative – The same as with calculation of Non-Cumulative above, but the rebate value of the previous period is excluded.
Payment Period	Maps your rebate logic with existing Rebate Type templates. Select: "Monthly", "Quarterly", "Semi-Annually" or "Annually". If left empty, there is the "Payment Period" input in the rebate agreement with the same values.
Payout Days	Enter the number of days after the end date of the payment period when you want the payout. If left empty, it is set to 1 day.
Customer Selection Level	Options are: Header Level – Shows the customer group input in the header of a rebate agreement. At the line item level, the customer group input will be disabled and will inherit values from the header. Line Item Level – Shows the customer group input both for the rebate agreement header and line items. If users change the value of the customer group for each line item, it takes priority over the header input value.
Customer Filter Logic	Name of Customer Filter Logic (suggested: CustomerFilter_Logic). You can change the customer filter as needed in this logic, so that you get the customers you need in the rebate agreement.
Product Filter Logic	Name of Product Filter Logic (suggested: ProductFilter_Logic). You can change the product filter as needed in this logic, so that you get the products you need in the rebate agreement.
Source Type	Options are: DataMart – Rebate values will be calculated from Datamart. DataSource – Rebate values will be calculated from Data Source.
Rebate Base Source	Source name
Rebate Base Field Value	Baseline field name in the Data Source
Rebate Base Field Quantity	Quantity field name in the Data Source
Rebate Base Field Customer	Customer ID field name in the Data Source
Rebate Base Field Product	Product ID field name in the Data Source
Rebate Base Field Date	Pricing date field name in the Data Source

These are the default values of some of the attributes in Advanced Configuration, so that users do not need to define them from scratch in each Rebate Type:

{
  "sourceType": "DataMart",
  "sourceName": "SC_TransactionData",
  "baselineFieldName": "InvoicePrice",
  "quantityFieldName": "Quantity",
  "pricingDateFieldName": "PricingDate",
  "rebateFieldName": "Rebates",
  "customerIDFieldName": "CustomerId",
  "productIDFieldName": "ProductId",
  "payoutDays": 1,
  "paymentPeriod": "Quarterly",
  "targetFor": "Payment Period",
  "depositScheme": "Non-Cumulative",
  "customerFilterLogic": "CustomerFilter_Logic",
  "customerSelectionLevel": "Line Item Level"
}

Options:

paymentPeriod – By default empty, it will then be populated on the line item level.
Note: These attributes will be hidden in Rebate Types. If users define them in Rebate Types, these settings will be used, otherwise Advanced Configuration settings are used.
Pay To Input – It is based on Customer Selection and is also applied to Customer Filter Logic if this attribute is set.
- If CustomerSelectionLevel = “Header Level”, Pay To input will be disabled for all line items and will be inherited from the header.
- If CustomerSelectionLevel = “Line Item Level”, Pay To input will be in both on the Header level and Line Item level. If you have Pay To on the Header level in this case, line items will not inherit from this level. If you choose one Rebate Type with CustomerSelectionLevel = "Header Level”, Pay To will be disabled for line items for only this Rebate Type.
customerFilterLogic/productFilterLogic – If you want to set a filter for customers/products, you can use Customer Filter Logic or Product Filter Logic.
Go to Calculation Logic, choose ProductFilter_Logic or/and CustomerFilter_Logic, and the input data that you want to filter.
- Customer Filter Logic is set in Advanced Configuration.
- Product Filter Logic is set in a Rebate Type in the Product Filter Formula column for a specific Rebate Type.

Working with Rebate Manager

User Roles

Define Rebate Type