Rebates and Trade Promotions Limitations and Best Practices

Rebates and Trade Promotions SuiteApp Limitations

You can edit preferences for Rebates and Trade Promotions, but you can’t delete them.
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 used for sales and purchase transactions must have a Units field to indicate the corresponding Units of Measure (UoM) of an item. The system requires UoM field in the custom form to calculate the 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.

Best Practices for Rebates and Trade Promotions SuiteApp

To avoid potential performance issues, please avoid adding more than 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 required in a system in-use with 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.
Don't make a rebate agreement Inactive from the List page to avoid issues in its related records.
If you update agreement details for an item, remove the item from the transaction line and add it again 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.
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 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, you can 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 you save, since the system recalculates rebates after you click the Save button.
Creation of Rebate Agreement, Rebate Agreement Detail, and Rebate tiers through CSV or web services is supported; however, they cannot be edited through CSV or web services.
Rebate calculation may take some time to complete. You should wait until the rebate calculation banner is not displayed anymore. Then, refresh the page to view the rebates and then proceed to edit or transform any transaction.
The following forms must not be used in creating transactions; and you should neither customize them nor apply workflows/scripts on them:
- RM Vendor Credit
- RM Vendor Bill Disbursement
- RM Credit Memo Disbursement
- RM Invoice Claim

Rebates and Trade Promotions SuiteApp Limitations

Best Practices for Rebates and Trade Promotions SuiteApp

Related Topics