Was this page helpful to you?
Do you have any additional feedback?
Interaction of Rebate Agreements with SAP ERP
When you use rebate agreements in trade promotions, all relevant data from the Marketing key capability of SAP Customer Relationship Management (SAP CRM) is transferred to SAP ERP Central Component (SAP ERP) for subsequent processing. SAP ERP tracks all receipts (invoices, credit memos, and debit memos) relevant for rebate processing and automatically posts accruals so that accounting in FI-CO has an overview of the cumulative value of the rebate agreements.
For rebate agreements to interact between SAP CRM and SAP ERP, you must make the appropriate Customizing settings to enable communication between the two systems. For more information, see SAP Solution Manager.
First Transfer from SAP CRM to SAP ERP
If you save the trade promotion after generating the conditions, the system transfers the conditions and rebate agreements from SAP CRM to SAP ERP. At this point, you can only post manual accruals and manual payments for the rebate agreement in SAP ERP.
Settlement of Rebate Agreements in SAP ERP
You cannot settle rebate agreements directly in SAP CRM. There are two ways of carrying out rebate settlements:
Set the status of the trade promotion to Completed.
When saving the trade promotion, the system automatically sets the status of the rebate agreement to To Be Settled in SAP ECC.
For more information, see Status Management.
In Planning in SAP CRM, click Release for Settlement.
In doing so, you can trigger the settlement of individual rebate agreements in SAP ERP manually.
As soon as rebate agreements are released for settlement in SAP ERP, you can no longer change rebate agreements and rebate conditions in SAP CRM. You can however partly or fully settle the rebate agreement in SAP ERP. If you change the status of the rebate agreement in SAP ERP, the system transfers the rebate agreement back to SAP CRM.
If you want to change a rebate agreement or a rebate condition at this point, you must first reset the status of all rebate agreements for the trade promotion. The rebate agreement can therefore no longer be settled in SAP ERP. You can however make changes again in SAP CRM.
Analyzing Data Integrity with the Data Integrity Manager (DIMa)
The Data Integrity Manager (transaction SDIMA) can be used to detect inconsistencies between rebate agreements in SAP CRM and SAP ERP. It checks for the following points:
Data that differs
Data that is only available in SAP CRM
Data that is only available in SAP ERP
If inconsistencies are found, an error message indicates the required steps.
For mass data, use the following procedure:
Run a detailed comparison.
Trigger a request to upload of all inconsistent agreements.
Run the detailed comparison again.
Trigger a request to download for all inconsistent agreements.
Rebate Agreement Status
You can process or settle the rebate agreement depending on the status of the rebate agreement in SAP CRM and in SAP ERP.
You can control the status using the Agreement Type and the field Minimum Value of the Rebate Agreement for Final Settlement (ECC: T6B1-BOSTA_MIN, SAP CRM: /BON/AG_STATUS_MIN_SETTLE). You do this in SAP ERP in Customizing for Sales and Distribution under .
The following options are available to you:
If the agreement does not have the minimum required status of Blank = Open, or B = Agreement Released for Settlement, you can process the rebate agreement in SAP CRM but not in SAP ERP.
Exceptions to this processing in SAP CRM only include when you make a manual payment or process a manual accrual.End of the note.
The system transfers all changes to rebate agreements and conditions after the trade promotion has been saved from SAP CRM to SAP ERP. The following fields can no longer be changed after conditions and rebate agreements have been generated:
Type, if this entails a change to the condition generation type
Products, as long as the trade promotion is set to Released
If the agreement has the minimum required status, you can process the rebate agreement in SAP ERP but not in SAP CRM
In SAP ERP manual payments, manual accruals and final settlements are possible. Since the rebate agreement can no longer be processed in SAP CRM, you cannot delete the trade promotion and you can no longer change the following:
Fields under Planning
Rebate agreement periods
The rebate agreement's products
Trade spends (here you are allowed to make additions)
Retroactive Processing of Rebate Agreements and Conditions
If the system updates billings in rebate processing, a new price determination is run but not a new campaign determination. This has the following effects:
It is possible to create or change rebate conditions within existing trade promotions (for example, a period or an amount).
The changes are then incorporated during a subsequent update run.
However, it is not possible to reverse a retroactively created or backdated trade promotion.
Consequently, you cannot apply a sales-dependent rebate at a later point.
This function does not apply to account planning because account planning does not use campaign determination conditions.
Deleting a Rebate Agreement
If you delete existing rebate agreements, it may be that manual payments have already been made in SAP ERP. For these cases, define how the system should proceed with these payments:
If you do not want to cancel manual payments for the final settlement in SAP ERP, mark the condition records as deleted in SAP ERP.
If you want to cancel manual payments for the final settlement in SAP ERP, set the condition amount to 0 in SAP ERP.
In doing so, note that in SAP ERP, there is no way of showing whether this rebate agreement is a deleted agreement, or an agreement that has been manually set to 0.
Archiving a Trade Promotion
You can only archive a trade promotion if all rebate agreements have the status Finally Settled in ECC.
For more information on the Customizing settings for rebate processing, see Customizing for Rebate Processing in SAP Solution Manager.
The following content is not part of SAP product documentation. For more information, see the following disclaimer .