Rebates and Trade Promotions Limitations and Best Practices

Rebates and Trade Promotions SuiteApp Limitations

• Preferences for Rebates and Trade Promotions can be edited but not deleted.

• The values for UOM Criteria must be selected first followed by the values for UOM Calculation. Changes made on UOM Calculation field do not have impact on the selection made in the UOM Criteria field.

• A rebate agreement and its agreement detail cannot be created at the same time. A rebate agreement record must be saved first then edited to add the agreement details.

• All custom forms used for sales and purchase transactions must have a Units field to indicate the corresponding Units of Measure (UoM) of an item. The system does not calculate rebates if a custom form does not have a field for a UoM.

• Permissions to the custom records are removed from a custom role after the SuiteApp is upgraded. An Administrator must edit the custom roles and add any missing permissions for the custom records.

• Rebates are not shown immediately for item groups that you add on the transaction line. You must save the transaction first, then refresh the page to populate the rebates.

• If an item is marked as a sub-item of another item, the item criteria screen does not show both the item and sub-item in the selection drop down. The item criteria displays only the sub-item in the agreement details.

• The Rebate Transaction Record column cannot be hidden on sales and purchase orders.

• Deselecting a UoM from UOM Calculation field does not automatically clear the related UoMs from the UOM Criteria field.

• If an item does not have a UoM, the Adjusted Unit Cost value is shown as blank.

• Changing the transaction date and customer or vendor on a transaction may impact the rebate recalculation. Recalculations are triggered only after you save a transaction.

  The recalculation relative to the change in the transaction date or the customer is applicable when you modify the item quantity or amount, or when you add a new line to the transaction.

• When you transform an invoice created through SOAP to a return authorization, which contains price pass through, you must specify the value for the Amount and Item Quantity.

• When you transform multiple purchase orders with future dates into a single bill, rebates are copied to bills and the bill date serve as transaction date.

• Multi-currency conversion is not supported for the rebate amount you set in the agreement details. For more information, see the example of flat amount calculation in Examples of Rebate Calculations.

• Partial fulfillment for SOAP transactions is currently not supported.

• REST support is only for transaction creation(POST) calls.

• Custom multi-select fields for item and customer are not supported.

Best Practices for Rebates and Trade Promotions SuiteApp

• To avoid potential performance issues, please avoid adding more that 50 agreement detail lines per rebate agreement.

• Set the Classification preferences for Class, Department, and Location on the Accounting Preferences page before creating sales transactions. If the Class, Department and Location are changed to mandatory in an in-use system with already existing transactions, the accruals for those transactions will fail.

• Set the Classification Preferences by checking the Allow Per-line Classes and Allow Per-line Departments before creating transactions. If you set the preferences after creating a transaction, the rebate accruals for the existing transactions will fail.

• Ensure that the accounting period contains years, quarters, or months based on your preferred settlement frequency. The system encounters an error if it does not find the relevant period for posting transactions, creating accruals, and generating settlements.

• You must not make a rebate agreement Inactive from the List page to avoid issues in its related records.

• If you update the agreement details for an item, you must remove the item on the transaction line and re-enter it for the changes to reflect.

• When you add a new line item on a transaction by clicking the Copy Previous button, make sure you edit the Quantity, Unit, Rate, or Amount fields to show the values on the rebate columns.

• You must disable the Multiple Calendars feature to avoid Map/Reduce scripts from failing. To disable the feature, go to Set Up > Company > Enable Features and clear the box for Multiple Calendars box under the Accounting subtab.

• Click Refresh on the pro forma, claim, and disbursement records if the CSV file does not load immediately.

• If the Calculate Rebates at Real-Time preference box is cleared, verify rebate calculations by checking the Applicable Rebates popup window after saving a sales or purchase transaction.

• You must not modify the payload when you transform transactions using SOAP.

• Verify the rebates on the transactions after save as the system recalculates rebates after you click the Save button.

Related Topics