SAP ABAP IMG Activity _ISUBIBDRS_000067 (Define Dynamic Backbilling Groups)
Hierarchy
☛ IS-UT (Software Component) SAP Utilities/Telecommunication
   ⤷ IS-U (Application Component) SAP Utilities
     ⤷ EE80 (Package) IS-U: Customizing
IMG Activity
ID _ISUBIBDRS_000067 Define Dynamic Backbilling Groups  
Transaction Code S_KK4_82000402   (empty) 
Created on 20000802    
Customizing Attributes _ISUBIBDRS_000067   Define Dynamic Backbilling Groups 
Customizing Activity _ISUBIBDRS_000067   Define Dynamic Backbilling Groups 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _ISUBIBDRS_000067    

In this IMG activity you define the dynamic backbilling groups. These groups are needed when you want to perform backbilling in a schema with dynamic period control.

You can use these dynamic backbilling groups to group rate steps together for dynamic period control.

To suppress automatic line grouping, set field No line grouping.

Structure of a billing schema with dynamic period control

This section describes a simplified schema structure that illustrates the special features of dynamic period control. It also describes the settings of the various Customizing tables that are involved in dynamic period control.

You define that a schema will be used for dynamic period control in the header of that billing schema. In this case, the schema can only be used in rate categories that have also been classified for dynamic period control in the rate category header.

You maintain the following information in the steps of the billing schema:

  • A time slice generator. It determines the periods for which the schema step is set up, dependent on the category of the current billing period. If you use a schema with dynamic period control, you have to enter a time slice generator in every schema step. SAP provides 0000 as the default value, which is proposed for all steps when you create the schema. You have to assign the periods to set up for this standard value in the table of periods to set up for your schema. If you have a schema with dynamic period control, for example, that you always use to bill the current periodic billing period, you have to explicitly specify the periodic billing period. Information on how to control the periods for billing is available in Customizing for contract billing, under Information for dynamic period control.
  • The conditions that will result in backbilling. Normally, backbilling is triggered whenever an actual meter reading result is recorded. You also have to use variant DYNBI01 to trigger dynamic backbilling in the schema. However, you can use the various IF variants to suppress the dynamic backbilling after an actual meter reading result. For example, variant IF09 prevents dynamic backbilling when a move-in has taken place.
  • The schema steps that are affected by dynamic backbilling.

    Assign a dynamic backbilling group to the affected schema steps. This group forms the parentheses for dynamic backbilling.

    Schema steps can:

    • Be set up for different periods
      • You can define that a schema step will be set up for different periods, depending on the category of the current periodic billing period. We currently differentiate between four different basic categories of periods to set up (see example below).
    • Trigger dynamic backbilling
      • (only possible using variants from variant category 14). To do this, enter a dynamic backbilling group in field Execute dynamic period control. This group defines the schema steps for which the bill line items from the correction periods are cancelled, and which schema steps are executed again in the correction periods.
    • Be backbilled
      • To do this, enter a dynamic backbilling group in field Schema step for execution in dynamic period control. It determines the backbilling that is used for the schema step in the correction periods. This schema step is then performed in the correction periods when backbilling is triggered for the dynamic backbilling group.
    • Be cancelled
      • To do this, enter a dynamic backbilling group in field Schema steps for cancellation in dynamic period control. It determines the backbilling that is used to cancel the bill line items from the correction periods (for the schema step). The bill line items are cancelled when backbilling is triggered for the dynamic backbilling group.

Restrictions

See the documentation on dynamic period control

Example

In the example below, a consumption and a flat-rate charge are billed each month. The consumption is only a preliminary estimate when based on estimated meter readings. The consumption between the last actual meter reading and the current actual meter reading is revaluated when an actual meter reading result is entered. The preliminary bill line items for consumption have to be cancelled in this case. The flat-rate charge should be incurred normally for the last month.

You want to bill the following periods:

T1 T2 T3 T4

|------------------|------------------|------------------|

Actual Estimation Estimation Actual

The schema steps are set up for the individual billing periods:

Curr. period T1 to T2
|------------------| Consumption
|------------------| Flat rate

Curr. period T2 to T3
|------------------| Consumption
|------------------| Flat rate

Curr. period T3 to T4
|---------------------------------------------------------| Consumption
|-------------------| Flat rate

The corresponding schema DYNPER has the following structure:

CSNO    Variant    TimeSlcGen    Dyn.per.exec    Exec.step.    Canc.step

1    QUANTI01    CONS        NVB1    NVB1   

2    LUMSUM01    0000               

3    DYNBI01     0000    NVB1   

The following settings are required in the Customizing tables:

  1. Table Check table of periods to set up

Period to set up    Text    Basic period category

T    Per.bill.period    4

E    Complete period    3

  1. Table Periods to set up

Schema    Category    TimeSlcGen    Periods to set up

DYNPER    1000    CONS    T

DYNPER    1000    0000    T

DYNPER    2000    CONS    T

DYNPER    2000    0000    T

DYNPER    3000    CONS    E

DYNPER    3000    0000    T

DYNPER    4000    CONS    E or T

DYNPER    4000    0000    T

Note: Maintenance of this table will be integrated in schema maintenance in a later release.

Interpretation of schema step identification and the table Customizing

When the current meter reading result is an estimate (category 1000 or 2000), both time slice generators point to period to set up T with basic period category 4, which means variants QUANTI01, LUMSUM01, and DYNBI01 are each set up for the current periodic billing period. When an actual meter reading result is entered (category 3000 or 4000), time slice generator 0000 points to period to set up T, but CONS points to E, which has basic period category 3. In this case, variants LUMSUM01 and DYNBI01 are set up for the current periodic billing period. Variant QUANTI01 is set up for the period between the last and current actual meter reading results.

The start of each period to set up (with the exception of the current periodic billing period) is taken from table ERCHP. This table is a supplemental table of the billing document, ERCH.

  • When a move-in is involved, the move-in date is the start date.
  • When an actual meter reading result is billed, the start date is equal to the end of the current billing period plus one day.
  • When a periodic bill for an estimated billing document is involved, the start date is not changed - the start date of the previous document is used.

Schema steps

Periods T1 to T2 and T2 to T3: All three variants are executed for the current periodic billing period. However, variant DYNBI01 does not perform any actions, because it only affects steps outside the current periodic billing period.

Period T3 to T4: Variant LUMSUM01 calculates the flat-rate charge for the current periodic billing period. Variant DYNBI01 triggers backbilling for the QUANTI01 that has been set up for period T1 to T4 (trigger: backbilling group NBV1 in DYNBI01 and execution group NBV1 in QUANTI01). It also triggers the cancellation of&#

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG _ISUBIBDRS_000067 0 I110004842 Rate Structure 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
TE659 S - Table (with text table) SM30 Define Dynamic Backbilling Groups 
History
Last changed by/on SAP  20010419 
SAP Release Created in 462