Date Rule for Billing Dataset Generation This function is used to generate billing datasets for online items using defined calculation periods.
It is part of document processing.
The system performs the function automatically when the item data is confirmed if you have made the relevant settings in Customizing.
During revenue recognition, billing datasets can be posted by periods.
See also : Revenue Recognition by Periods
Several billing datasets are to be generated for an online item so that revenues can be posted by period and more than one invoice created during the posting period.
You have defined a date rule and determination of these rules in Customizing:
Activity |
Menu path |
|---|---|
Define date rule |
|
Define date rule determination |
If a factory calendar is to be used to define the date rule, you have created a factory calendar for billing dataset generation in Customizing.
Activity |
Menu path |
|---|---|
Define factory calendar |
|
If customers require invoices more frequently than the standard period for your organization, you have recorded an individual factory calendar for these customers in their master data (
Billing Schedule
field on the
Billing in Sales and Distribution
tab page).
To generate several billing datasets for an online item, you must define a date rule in Customizing.
This date rule controls the way in which the system determines calculation periods for billing datasets.
Date rules can be defined using a factory calendar or a number of days. If the date rule is defined using a factory calendar and a number of days, the system uses the factory calendar to determine calculation periods.
Recommendation
When creating date rules, you should ensure that the frequency of billing datasets generation is suitable for the customers invoice requirements.
If you have defined all days on which calculation periods are to end as weekdays in a special factory calendar, the system generates billing datasets as follows:
Starting from the earliest publication date, the system determines the next weekday in the calendar:
If this weekday is earlier than the latest publication date, the system creates a billing dataset whose service date start corresponds to the earliest publication date and service date end corresponds to the weekday from the calendar. The next billing dataset is created using a similar procedure in which the system starts a day after the service date end for the preceding billing dataset.
If the latest publication date is earlier than the next weekday from the calendar, the final billing dataset ends with the latest publication date.
Example
Posting periods in your organization start on the first day of the month and end on the last day. Create a factory calendar in which the last day of each month is defined as a weekday.
A customer books online advertising for the period from November 10 th to December 8 th .
The system generates a billing dataset for the period between November 10 th and November 30 th and another for the period between December 1 st and December 8 th .
If you have specified a number of days in Customizing, the system generates billing datasets as follows:
Starting from the earliest publication date, the system combines the number of days specified as a range. The final range ends on the latest publication date.
Example
You have specified a range that contains 7 days.
A customer books online advertising for the period from November 10 th to December 8 th .
The system generates a billing dataset for the period between November 10 th and November 16 th , one for the period between November 17 th and November 23 rd , one for the period between November 24 th and November 30 th, one for the period between December 1 st and December 7 th and one for December 8 th .
The sales area and the factory calendar for the advertiser are used to access entries in the
Define
Date Rule Determination
Customizing table and determine the date rule. If no entry is found for the advertiser’s sales area and factory calendar, the system attempts to access this table using the sales area.
The access sequence ensures that the more detailed date rule is only determined if a customer requests an invoice more frequently than billing datasets are usually generated in your organization.
Customer exit
EXIT_SAPLJHGA_018
in enhancement
JHGA0012
is used to influence date rule determination.
Planned gross impressions can be specified in the master data for each content component in an online basic booking unit or each target group in these content components.
If actual gross impressions are used for settlement, they are defined by the system from the associated schedule lines.
If target gross impressions are to be used for settlement and several billing datasets are generated for a booking unit/content component assignment, the target gross impressions have to be distributed amongst specific billing datasets. A distribution rule is required to do so. These rules are proposed by the system and specified by the user when the date rule is defined.
The
Percentage due to planned gross impressions
and
Distributed absolutely equally
distribution rules are available in the system.
The
Percentage due to planned gross impressions
distribution rule can only be used if planned gross impressions have been defined in the online booking unit master data.
The example below shows how target gross impressions can be distributed between billing dataset if you have chosen one of these distribution rules.
A customer books 100 target impressions between January 1 st and January 7 th .
The date rule has been defined so that two billing datasets are generated for this item: One for the period between January 1 st and January 3 rd (3 days) and one for January 4 th (1 day).
Planned gross impressions that have been recorded in the system change with effect from January 3 rd .
Date |
Plan GI |
Bill.dataset |
Abs. equally |
Perc.pld GI |
|---|---|---|---|---|
January |
10 |
1 |
15 |
10 |
January |
10 |
1 |
15 |
10 |
January |
20 |
1 |
15 |
20 |
January |
20 |
2 |
15 |
20 |
Total |
60 |
60 |
60 |
Target gross impressions for the item are divided between these billing datasets as follows:
Billing dataset |
Abs. equally |
Perc.due to planned gross imps |
|---|---|---|
1 |
45 |
40 |
2 |
15 |
20 |