Rebates and Trade Promotions SuiteApp Limitations

• You can edit preferences for Rebates and Trade Promotions, but you can't delete them.

• Rebate Management features are only available in the Classic and Accounting Centers.

• You need to select UOM Criteria values first followed by UOM Calculation values. Changes made on UOM Calculation field do not have impact on the selection made in the UOM Criteria field.

• You can't create a rebate agreement and its agreement detail at the same time. Save the agreement first, then edit it to add the agreement details.

• All custom forms for sales and purchase transactions must have a Units field, where an item's Units of Measure (UoM) is indicated. The system requires the UoM field on the custom form to calculate rebates.

• After you upgrade the SuiteApp, permissions to the custom records are removed from a custom role. An Administrator needs to 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 need to save the transaction first, then refresh the page to populate the rebates.

• If you mark an item as a sub-item of another item, the item criteria screen displays only the sub-item in the agreement details, not both.

• You can't hide Rebate Transaction Record column on sales and purchase orders.

• If you clear a UoM from the UOM Calculation field, it won't automatically clear 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. The system recalculates only after you save the 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 need to specify the values for the Amount and Item Quantity.

• When you combine multiple purchase orders with future dates into a single bill, rebates copy over to bills and the bill date serves 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 only covers transaction creation (POST) calls.

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

• The system can only process a settlement with up to 75,000 transaction lines or if the CSV file size is 10 MB or less.

• Retroactive operations are not supported, which means, any changes to Rebate custom records will only affect transactions created after the change, but will not affect existing transactions or those created before the change.

• To support rebates, custom transaction forms should not hide fields associated with rebates. Hiding rebate transaction fields might result in inaccurate calculation of rebates or amount updates.

• Changes or any edit to Custom Segment records will not be reflected on the Custom Segment Preferences page; you should manually set the changes on the page.

• Custom segments of the type Multiple Select, and those that are inactive or locked, are not supported in rebate transactions and journal entries; these custom segments will not be displayed on the Custom Segment Preferences page

• In creating a Rebate Agreement, the Partner entity, even if saved as a multiple type record such as a customer or vendor, is not displayed in the Payer/Payee dropdown list. If you want to select a Partner entity in the Payer/Payee field, you can select it using the advanced search at the bottom of the dropdown list.

  If you use CSV import to create a Rebate Agreement, you cannot enter a Partner entity (even if it is a multiple type record) as a value for the Payer/Payee field.

• Rebates are not supported for items with negative quantities. You should exclude items with negative quantities in Rebate Agreement Details or do not select them or clear them in the Applicable Rebates popup window. Negative item quantities will result in invalid rebates that may have adverse impact on accruals and settlements.

  Likewise, price pass-through is not supported for transaction items with negative amounts or quantities. If price pass-through is applied to a negative amount, the rebate scripts will update the amount to zero (0).

• Rebates management features do not support custom segments of type "Internal". Internal custom segment types will not be grouped in accruals or settlements and their corresponding journal entries.

General Notices