Ansicht
Dokumentation
CRM_BTX_BF_FAPGRUP01 - Define Groupings of Billing Request Items
RFUMSV00 - Advance Return for Tax on Sales/Purchases SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3upThis documentation is copyright by SAP AG.
Use
In this activity you can define groupings of billing request items or billing request lines in billing plans that contain a large number of these items/lines. If items/lines with identical prices and conditions are grouped, the system does not need to call the pricing engine or trigger pricing and periodic billing for every single item/line in a plan. This substantially improves system performance for billing plans. In the BAdI you define the conditions under which you wish to group the billing request items/lines.
The groupings that you define in this activity are used as filter values of the following Business Add-Ins, depending on whether you are using billing request items or lines:
- Billing request items: Grouping of Billing Request Items
- Billing request lines:Grouping of Billing Request Lines
The grouping 02 (grouping according to period length) is predefined in the standard system. If you choose this grouping, the system groups all the lines with the same period length. However, as soon as the period is shorter or longer than the first line in the group, the system stops grouping and uses the next line as its new reference line. Any lines that do not fit into groups are billed individually.
This grouping is only relevant for billing plans in service contracts.
A BAdI implementation is provided for this grouping.
If you define a new grouping, you assign it to a billing plan type in the activity Define Billing Plan Types.
The following example illustrates how the grouping could work if you grouped billing request items according to period length, in this case, a month. The contract period runs from January 15 until July 15.
| Bill. Req. Item No. | Date Range |
|---|---|
| 00000010 | Jan 15 - Jan 31 |
| 00000020 | Feb 1 - Feb 28 |
| 00000030 | Mar 1 - Mar 31 |
| 00000040 | Apr 1 - Apr 30 |
| 00000050 | May 1 - May 31 |
| 00000060 | Jun 1 - Jun 30 |
| 00000070 | Jul 1 - Jul 15 |
The system notes that item 00000010 only has 15 days and does not therefore correspond to a month so it cannot be used as a reference item and is billed separately. Item 00000020 does correspond to a month and the system uses it as the next reference item. For item 0000030 the system copies the data from item 00000020 because they are identical and continues to use item 00000020 as its reference item for all the items up until July, in other words, it groups items 00000030 to 00000060. However as item 00000070 is for a period of only 15 days, the system creates a new billing item, in this case, for 15 days.
General Material Data General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 3779 Date: 20240523 Time: 171226 sap01-206 ( 92 ms )
