Ansicht
Dokumentation

CRMV_UBB_USG_MAINT - Assign Usage Functions and Credit Overview

Fill RESBD Structure from EBP Component Structure   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

In this IMG activity, you define the settings for pricing in Usage-Based Billing.

Usage Functions

The usage function is a primary allocation attribute for pricing in Usage-Based Billing. You allocate the usage function to a counter. The standard delivery contains usage function 0BW4, for example, which indicates that a counter with this usage function counts black-and-white copies (on a copying machine, for example). You use additional keys to allocate the usage function to a condition function.

Usage Function Categories

In the standard delivery, usage function category 0PRE indicates that the condition represents prebilling of the usage quantity. Type 0GRO indicates the gross usage volume. The gross usage volume is the usage volume used to calculate the usage volume for billing. If you have not defined a usage function category in Customizing, the system assumes that a usage volume subtotal or condition based on a usage volume subtotal is involved.

Defining Categories for Gross/Accrual Volumes

In the standard delivery, usage function category 0GRO is defined as the category for the gross usage volume. The system always calculates the gross usage volume from the volume document. Category 0ACR is defined as the accrual usage volume. If you do not want to use the standard categories, you can enter alternate categories in this view.

Categories for Manual Credit Maintenance

You can enter manual credits in the credit overview. You have to allocate a usage function category to each credit. In this table, enter all the categories for which manual maintenance will be allowed. You can only enter usage function categories that you have already defined in the Usage Function Categories table.

If the table only contains one entry, the system proposes this category when you enter credits. If several entries are defined, you can select the required entry with the input help or through manual input.

Categories for Credits in Readings

When you enter readings, you can enter up to three credits in addition to the counter reading. You have to allocate a usage function category to the credits. Enter the usage functions that are valid for credits here. You can only enter usage function categories that you have already defined in the Usage Function Categories table.

Usage Function Groups

The usage function groups enable you use condition functions and usage functions differently within the different groups. The usage function group is part of the control data in the contract. You cannot edit it manually in the contract because it is contained in the respective service product.

Allocating Usage Functions

You assign a usage function and a usage function category to a combination of condition function and transaction category, dependent on the usage function group. The condition function is an attribute of the condition type. You edit the condition function for a condition type in Customizing for Usage-Based Billing under Pricing -> Settings for Pricing -> Condition Types. You maintain the transaction category in the billing plan type; it is then allocated to the billing request items from this billing plan. The condition function is an attribute of the condition type. The system uses this allocation to determine which usage volume from the volume document (or credit from the credit overview) it has to pass on to which condition.

If you do not enter a usage function category for a key combination, that combination represents a volume subtotal.

To simplify Customizing and reduce the number of entries, you can also use a wildcard entry, "*", for the transaction category. The system first tries a fully qualified key (condition function and transaction category). If it cannot locate an entry for this key, it uses the generic entry for the transaction category to find a table entry.

Creating Credits in the Credit Overview

When prebilling a contract and during contract inception, the system checks whether a credit should be created in the credit overview for each condition function and other keys in this view.

If you enter a credit, the system creates a credit with the specified usage function category and the credit category (C or P). You can also specify that the system should only create credits when the credit is positive or negative.

As in the Allocate Usage Function table, you can also use the wildcard entry (*) for the transaction category here.

Using Credits from the Credit Overview

During prebilling, credits can be used from the credit overview (that is, precalculated usage volumes). In this view, you configure which condition function (in combination with other key fields) can use which usage volumes in the credit overview. You can also configure whether a condition function should only use positive credits or only negative ones. This is particularly important for configuring pool prebilling. A condition type can create and use a credit at the same time.

Like in the Allocate Usage Function table, you can also use the wildcard entry (*) for the transaction category here.

Usage Function Dependencies

In this view, you can allocate combinations of usage functions and usage function categories to another usage function. You can also specify an operator (+/-) to determine whether the usage volume / value will be added or subtracted. In the 'Factor' column, you can enter a positive or negative factor (maximum of three decimal places), with which the current quantity / value is multiplied before the quantity / value is added or subtracted.

This allocation models the so-called "logical counters". Logical counters do not exist physically in a device, but instead are calculated by adding to or subtracting from other counters (which in turn can be other logical or physical counters). The table is analyzed recursively. You can calculate pricing based on the logical counters. To avoid calculation errors, you can indicate for each entry whether or not the usage volume from the allocated usage function has to be present during calculation. If this usage volume is missing, an error message is output during pricing.
The system analyzes the table recursively. If the table contains entries that result in an endless program loop, the program terminates with a short dump. If you attempt to define an incorrect entry in the Customizing table, the system detects this and rejects the entry. Always use the Customizing activity to make entries in the table.

Example

A copying machine has two counters: counter 1 only counts black-and-white copies, while counter 2 only counts color copies. A single price for the grand total of both counters is defined in the contract. Create a new usage function (such as TOTL) for this. You allocate the usage functions for b/w and color copies, as well as the usage function categories for the gross usage volume, to the new usage function TOTL. Enter the target usage function (TOTL in this case) in the first column. As the operator, enter "+" in both lines as a sequential number with any desired ascending order (this is used for sorting within customizing views). In the "Factor" column, enter "2" for the lines with the usage function for color copies. With this setting, the system will add the two gross usage volumes before pricing, and pricing can now take place based on the new usage function.

If you use accrual volumes, you have to use the same entries with the usage function category for the accrual volumes in order to calculate a sensible accrual value.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 9568 Date: 20240523 Time: 170631     sap01-206 ( 216 ms )