Ansicht
Dokumentation
CRM_ABT_EXECUTION - Define Settings for Automated Budget Transfer
General Data in Customer Master ROGBILLS - Synchronize billing plansThis documentation is copyright by SAP AG.
In this Customizing activity, you specify that automated budget transfer execution calculates transfer amounts using new budget or available budget. Define the transaction types used for calculating new budget from the following budget posting types under the Assignment of Business Transaction folder:
- Budget updates (UPDATE)
- Budget transfers (TRANSFER)
- Automated budget transfers (ABTRANS)
After defining the transaction type, all new money entering the fund using this transaction type is considered as new budget.
- You have defined transaction types for budget updates, transfers, and automated budget transfer in the Customizing activity Define Transaction Types.
- You have specified the transaction types that are used for automated budget transfer for funds whose budget expires and does not expire in the Customizing activity Define Transaction Types for Automated Budget Transfer.
The New Budgetcheckbox is not selected. Automated budget transfer calculations are based on the available budget in the source fund.
In the standard system, do not enter the same transaction types for market development funds (MDF) and trade promotion management (TPM). If you enter transactions relevant for TPM, budget is not posted to the fund and the checkbook is not updated. Therefore, we recommend that you enter the following transactions for new budget:
- Budget update with expiration (BPUE)
- Budget transaction with expiration (BPTE)
- Specifying That Automated Budget Transfer Only Considers Available Budget
If you have previously specified that automated budget transfer execution considers new budget, you can later deselect the New Budgetcheckbox to use the default calculation logic for available budget only. The system checks for blocked budget postings. You must run the unblock report to unblock any blocked budget.
- Deleting Transaction Types
When you delete a transaction type, ensure that all budget postings of this transaction type are unblocked. Note that you are not be able to consume any blocked budget until the next automated budget transfer execution.
- Saving a Budget Posting Document
When you save a Budget Posting (BPO) document as Approved, the system verifies that the current transaction type is relevant for new budget and this budget is blocked for consumption. Additionally, the status of the BPO document is set to Blocked until the next automated budget transfer execution. Otherwise, the budget is directly booked to the fund.
- Unblocking Budget
When executing the automated budget transfer report, all blocked budget postings related to the specified channel partners are unblocked and the new budget is distributed according to the automated budget transfer rules. Note that you may also unblock budget without automated budget transfer execution: Run the automated budget transfer batch job and choose to release the blocked budget only.
- Using Multilevel Logic for Automated Budget Transfer
During automated budget transfer execution, the system may use multilevel logic for automated budget transfer. For example, assume that transaction types are defined for automated budget transfer for funds whose budget expires (BPAE) and does not expire (BPAT) in the Customizing activity Define Transaction Types for Automated Budget Transfer. If the funds in the channel partner hierarchy support expiration and the transaction type BPAE is also defined in the current Customizing activity as a transaction type used for calculating new budget, then the system uses multilevel logic for automated budget transfer. Budget is transferred to target funds using a single scheduled batch job. However, if no automated budget transfer transaction type is entered, then all rules are executed only once. Therefore, amounts credited to a source fund due to a rule in the current automated budget transfer execution are not considered for further distribution. Note that rules containing fixed transfer amounts are executed only once.
Assume that Fund 1 has USD 3000 to spend as follows:
| Amount | Expiration | |
|---|---|---|
| USD 1000 | January 2009 | |
| USD 2000 | February 2009 |
Assume that automated budget transfer rules have been setup as follows:
- 30% of Fund 1 total to Fund 2
.30 * USD 3000 = USD 900
- 20% of Fund 1 total to Fund 3
.20 * USD 3000 = USD 600
During automated budget transfer execution, all funds get a proportional share of the expiring budget. The system creates fund postings by calculating a transfer ratio where the specific transfer amount is divided by the total transfer amount of the source fund.
- Budget Expiring January 2009
(Transfer Amount / Total Transfer Amount) * Amount Expiring January 2009 = Amount Transferred
- Fund 1 to Fund 2
(USD 900 / USD 1500) * USD 1000 = USD 600
- Fund 1 to Fund 3
(USD 600 / USD 1500) * USD 1000 = USD 400
- Budget Expiring February 2009
Transfer Amount - Amount Transferred
- Fund 1 to Fund 2
USD 900 - USD 600 = USD 300
- Fund 1 to Fund 3
USD 600 - USD 400 = USD 200
Therefore, the total amount transferred between the funds is as follows:
- Fund 1 to Fund 2: USD 600 + USD 300 = USD 900
- Fund 1 to Fund 3: USD 400 + USD 200 = USD 600
PERFORM Short Reference BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 6967 Date: 20240523 Time: 154126 sap01-206 ( 122 ms )
