Account Defaults for Trade Promotions 
This function allows you to set defaults for account-specific information in trade promotions so that the information is entered automatically for all relevant trade promotions or deals. You can create defaults for:
Default dates
Buying patterns
You have defined:
Date ranges with which you want to work in Customizing for Customer Relationship Management by choosing .
You can define up to five date ranges.
If you define a date range that has a specific meaning, for example, pre-dip or post-dip, you need to select the corresponding period type in this activity. These could be dates for the buying period, the “dip” period before buying begins (pre-dip), the “dip” period after buying ends (post-dip), or any other date. This is used to trigger validation of the dates in SAP CRM and in SAP NetWeaver Business Intelligence (SAP NetWeaver BI).
At least one buying pattern type in Customizing for Customer Relationship Management by choosing
Under Account Data, you can select the Account Type and Account for which you are going to set your defaults. Under Organizational Data, you can enter the relevant sales area data for this account.
If you enter a target group as your account, defaults are not maintained for each individual combination of target group, campaign type, and sales area. They are maintained for all target groups for a particular campaign type and sales area.
Under Default Dates, you can enter defaults for all of the relevant dates in a trade promotion.
You enter the mandatory data for the trade promotion and then specify the following information for the additional date ranges that you have defined in Customizing, under Periods in the following fields:
Start Date for the start of this additional date range, for example, if it is before the start of the trade promotion
Start Date Offset, for example, if it is two weeks before the start of the trade promotion
End Date for the end of this additional date range
End Date Offset
Caution
Only the planned start and finish dates are supported as reference dates. You cannot maintain dependencies between different date ranges from the additional date ranges.
You can define the buying period to start four weeks before the trade promotion takes place, and finish two weeks before the end of the trade promotion. You define the buying period as a date range in Customizing and then you can enter the actual dates here. A buying pattern can be defined for each combination of marketing project type, buying pattern type and duration.
Under Buying Pattern, you can define buying patterns, for example, for various different buying pattern types such as confectionery, drinks, and so on. The buying pattern defined in Account Defaults is used to calculate trade promotion planning. To enter a buying pattern:
Enter the marketing project type again.
Select the particular buying pattern type you wish to make settings for.
Enter a duration for the buying pattern.
The duration that you have defined for the buying pattern determines how many buying percentage fields are available. For example, if you specify a buying pattern of two weeks, there will be two fields available for the buying percentages. For example, you can then plan that the retailer (planning account) purchases 20% of the goods in the first week and 80% in the second. Any other combination that adds up to 100% is permitted. The aim of the buying pattern is to increase the accuracy of the planned increase in sales before sending the values over to Demand Planning.
Note
If no other buying pattern is assigned in a trade promotion, the system defaults to an equal distribution. In this two week example, that would be 50% and 50%. If the trade promotion starts on any day other than a Monday, the distribution may differ.
Note
A Business Add-In (BAdI) allows you to implement additional checks and actions on the Account Defaults screen, by allowing you to implement additional rules for the dates that you set up under Default Dates.
For example, you can set up a rule so that there are no gaps between two dates or you could set up a rule so that one date starts directly after another.
For more information, see the documentation on the BAdI interface.