SAP ABAP Data Element PREISZUS (Indicator: Price Summary)
Hierarchy
☛ IS-UT (Software Component) SAP Utilities/Telecommunication
   ⤷ IS-U-BI (Application Component) Contract Billing
     ⤷ EE20 (Package) IS-U: Billing
Basic Data
Data Element PREISZUS
Short Description Indicator: Price Summary  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type KENNZ4    
Data Type CHAR   Character String 
Length 4    
Decimal Places 0    
Output Length 4    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Price sum. 
Medium 15 Price summary 
Long 20 Price summary 
Heading 4 PSum 
Documentation

Definition

You can set the price summary indicator in the billing schema for steps that generate billing line items relevant to posting. Billing line items are then grouped together on the bill.

Example:

  • The schema contains a step in which consumption is valuated with an energy price. The price is $0.20/kWh.
  • The schema contains an additional step in which the same consumption is valuated with a quantity-based demand price. The price is $0.05/kWh.

Using the schema, you bill a device that has a consumption of 1000 kWh.

  • If you do not set a price summary indicator, the following two billing line items are shown on the bill:
    • Consumption 1000 kWh Price $0.20/kWh Amount $200.00
    • Consumption 1000 kWh Price $0.05/kWh Amount $ 50.00
  • However, if you set the same price summary indicator for both of the schema steps, only one billing line item with the total price is shown on the bill:
    • Consumption 1000 kWh Price $0.25/kWh Amount $250.00

The above example illustrates quantity-dependent grouping. Time-dependent grouping is also possible. In this case the values to be billed do not have to match.

In general, widely differing time-dependent billing line items need to be summarized. As a result they are displayed on a day basis and any reference to a billing value gets lost.

The following conditions must be met for a price summary of billing line items to occur:

  • Identical price summary indicators must be entered in the corresponding schema steps
  • The periods of the billing line items must match
  • The consumption must match (in the case of quantity-dependent summarization)
  • The billing line items must be taxed in the same way
  • The back-billing allocation indicator and the back-billing reversal indicator must match

You can freely choose the label for the price summary indicator. You can also group together steps for several groups.

Example:
Schema step no. Price summary
0001 AAA
0002 AAA
0003 1000
0004 1000
0005 1000

Information about the added prices is available in the ZAHL1 field in the billing line item. The original time basis is available in the ZAHL2 field.

When time-dependent prices with different billing quantities or different repetition factors are summarized, rounding differences may occur in the ZAHL1 field.

Example:

First the system checks if the summarization lines in the ABRMENGE, WDHFAKT and TIMBASIS fields in the price match. If they do, the summarization line is calculated as follows:

Individual lines:

-------------

$82.74 / 365 days * 1 device * 31 days = 7.02723 ==> $7.03

$1.26 / 365 days * 1 device * 31 days = 0.107 ==> $0.11

Summarized line:

------------

1. The price is summarized (=> $84, this is stored in ZAHL1 as before)

2. The amount is recalculated

$84 / 365 days * 1 device * 31 days = 7.1342 ==> $7.13

In this case the calculated amount of $7.13 deviates from the sum of the individual amounts which was $7.14. Therefore $0.01 has to be subtracted from the individual line with an amount of $0.11.

Correction

----------

$1.26 / 365 days * 1 device * 31 days = 0.107 ==> $0.10

The PRSBTR field contains the added price for one day.

If the ABRMENGE, WDHFAKT and TIMBASIS fields in the price do not tally, the following occurs: The price per day is calculated using the sum of of the individual amounts (7.14 / 31 days). In this case rounding cannot be balanced. The ZAHL1 and ZAHL2 fields are still filled, however.

History
Last changed by/on SAP  20050224 
SAP Release Created in