Streetlights can be managed and billed in different ways in ISU. Streetlights can be managed at Installation Facts level as an Operand or in the installation Structure as devices. There are multiple Variants available in ISU which can be used to perform billing of streetlights. We will be looking at the below variants. REFVAL01 - Valuate a Reference Value with a Price REFVAL02 - Convert a Reference Value to Demand REFVAL03 - Determine Consumption for Lighting Unit from Burning Hour Calendar REFVAL01 REFVAL01 has 2 input operands – (REFVALUE and TPRICE) and one output operand – AMOUNT. Create a Rate with Facts Permissibility and Insert variant REFVAL01. Provide the Input Operand 1 which will be maintained at the Installation facts, Input Operand 2 which will hold the price key, and Output Operand which will hold the amount. When creating the input operand for REFVAL01, verify "Rate type required" checkbox is selected. Price of $2.5 per month is configured. Maintain the Reference value Operand at the Installation level. Entry value – Installed value of device. Value to be billed – Can be a value other than Entry value. This value is used in consumption billing. If value to be billed is not entered, the value from “Entry value” is automatically copied. Rep. factor – Determines how many times the same type of reference value exists. Value to be billed is multiplied by repetition factor. For example, if there are 10 streetlights, we can create one reference value and provide repetition factor as 10. Bill The account. Since we selected Period control as “00 – To the day” at the rate level, price for 1 year is calculated first to get the per day price and then price for time portion is calculated. This can be changed to monthly by choosing PC as 01 or 02. Billing quantity = 10*20 = 200 (val.to be billed * rep. factor) Price for a year = 2.5 *12 = 30 Time portion = 31 (Number of days in the billing period) 30/365 = 0.08219 * 31 = 2.5479 (Price for 1 day) 2.5479 * 200 = 509.59 REFVAL02 REFVAL02 is used to convert a Reference value to demand and has one input operand – REFVALUE and one output operand – DEMAND. Create a Rate with Facts Permissibility and Insert variant REFVAL02. Provide the Input Operand 1 which will be maintained at the Installation facts and Output Operand which will hold the demand. Since REFVAL02 outputs Demand, we need to add one more Variant to calculate the amount. We will add DEMAND01 and provide the output operand of REFVAL02 as the input operand for DEMAND01 Price of $2 per month is configured. Maintain the Reference value Operand at the Installation level. Bill The account. Billing quantity = 20*3 = 60 (val.to be billed * rep. factor) Price for a year = 2*12 = 24 Time portion = 31 (Number of days in the billing period) 24/365 = 0.06575 * 31 = 2.03835 (Price for 1 day) 2.03835 * 60 = 122.30 REFVAL03 REFVAL03 is used when we are calculating the consumption using the burning hour calendar. REFVAL03 has 1 input operand – REFVALUE and 1 output operand – QUANT. We begin by configuring the Operation Types for Lighting and create an operation type. Operation Type defines the type of lightning being used. Navigate to the configuration path below: Contract Billing ➡️ Billing Master Data ➡️ Rate Structure ➡️ Operands ➡️ Lighting ➡️ Define Operation Types for Lighting. Navigate to the configuration path below to configure the Types of burning hour Calendar Maintenance: Contract Billing ➡️ Billing Master Data ➡️ Rate Structure ➡️ Operands ➡️ Lighting ➡️ Define Types of Burning Hour Calendar Maintenance Here we can choose whether Burning Hour is to be maintained on a Daily or monthly basis.  Navigate to IMG configuration path below to configure the Burning hour Calendar: Contract Billing ➡️ Billing Master Data ➡️ Rate Structure ➡️ Operands ➡️ Lighting ➡️ Maintain Burning Hour Calendar. The Burning Hour Calendar contains the total number of hours where the lightning unit was operational in the given period. Create a facts permissible Rate. Add variant REFVAL03 and provide the Input and Output Operands. The input operand should have the 'Rate type required' checkbox checked and ‘Reference value type’ selected as lightning. Since REFVAL03 outputs Quantity, we need to add one more Variant to calculate the amount. We will add QUANTI01 and provide the output operand of REFVAL03 as the input operand for QUANTI01. Create a Rate fact group and add price to the rate facts. Quantity can be set to ‘0’ and set the reference value as ‘Required value’. Add the Refval03 operand in the installation facts. Bill the account Value from Burning hour calendar for 01/01 to 01/31 = 200 200 x 10 (val. To be billed) = 2000 (Billing Quantity) 2000 * 10(price) = $20,000

Period Control is a calculation procedure used to calculate the length of Time Portions. The time portion is the billing period in days or months based on the period control used. The Proration of charges happens based on the Time portion. There are 3 standard methods that are commonly used to calculate the length of Time Portions. To the Day Monthly time portions dependent on a key date Monthly time portions dependent on an interval 1. To The Day (00). When we select Period control “00 – To the Day”, the exact days in the billing period are used to calculate the time portions. Here the charges are calculated on a per day basis. Period control is maintained at the Rate step level. Tcode: EA32 The Price is configured as $50 for 1 month. Tcode: EA91 We will perform Interim billing. Below we can see that the Time portion is the exact number of days that comes under the billing period and the amount is calculated accordingly. Billing Period: 05-01-2017 to 06-16-2017 (47 Days) Since the price is maintained on a per-month basis, to get the per-day price, the 50$ is multiplied by 12 (months) and then divided by 365(days). Price for 1 year = $50 (Price configured for 1 month) x 12 (Months) = $600 Time portion = 47 (Number of days in the billing period) 600/365 = 1.6438356164 (Price per day) 1.6438356164 x 47 = $77.26 (Price for 47 days) 2. Month-based using key date (01). When we select Period control “01 – Month-based using key date”, the Key date is used to calculate the time portions. Period control is maintained at the Rate step level. In the Rate Step, select the Period control “01” as shown below and save the Rate. The Key date is maintained inside the MRU. We will perform Interim billing. Here the billing period will cover from 15th of July till 15th of August. Since two Key dates are falling within the billing period, the amount should be calculated for 2 time portions. Billing Period : 07-01-2017 to 08-16-2017 In the billing document, we can see that the Time portion is shown as 2 and the amount is calculated accordingly. Price amount is $50 and Time portion is 2 so the Net amount is 50 x 2 = $100 . 3. Month based with interval. to the day Move I/O (02). When Period Control “02 – Month based using Interval” is selected, if the total number of days in a billing period falls within the Interval period specified inside the Portion, then the account is billed for one billing period. The period control is maintained at the Rate step level. The Interval days are maintained inside the Portion. We will perform Interim billing. Here the bill period is still within the interval date specified in the portion. Billing Period: 09-01-2017 to 10-04-2017 (34 Days) In the billing document, we can see that since the total number of days are within the interval days, it is calculated as 1 time portion. When the number of days in the billing period does not fall within the interval days, the time portions are first calculated for an exact number of days. Then these time portions in days can be converted to the standard month. In the below example, we can see that the billing period only has 24 days, so the time portion is calculated for 24 days and shown in months. Billing Period: 09-01-2017 to 09-24-2017 (24 Days) 24/30 = 0.8 Month We will also see how this Period control works in case of a Moveout. A Moveout was carried out and a Final bill is created. Billing period: 09-01-2017 to 10-04-2017 Here the billing period contains 34 days, and the time portion is calculated for 34 days on a “To the day” basis as configured in the Period Control. 34/365 = 0.0931506849315068 0.0931506849315068 x 12 = 1.117808219178082 4. Creating Custom Period Control. Based on business requirements, we can also create custom Period controls. Before creating the custom Period Control, we need to create a Category of enhanced interval procedure by going to Tcode SPRO . Path: SAP Utilities ➡ Contract Billing ➡ Billing Master Data ➡ Rate Structure ➡ Rate ➡ Period Control ➡ Basic Calculation Procedures ➡ Month-Based Calculation Using Interval Execute “Define Category for Enhanced Interval Procedure” Click on New Entries and create Interval Procedure Category as shown below. Go back to SPRO path and execute “Define Type for Enhanced Interval Procedure.” Click on New Entries and create Interval Procedure Type as shown below. Go back to the SPRO path and execute “Define Additional Values for Enhanced Interval Procedure.” Click on New Entries and define additional values as shown below. Go to Tcode E41C and add the “Cat. of Enhanced Interval Procedure” to the portion. Go to Tcode SPRO and open the path mentioned below: Path: SAP Utilities ➡ Contract Billing ➡ Billing Master Data ➡ Rate Structure ➡ Rate ➡ Period Control Click on the Execute button next to “Define Period Control.” Click on “New Entries” button to Create a new Period Control. Create a new Period Control by providing the Period control, Description, Period Procedure as 03, and the Cat. of Enhanced Interval Procedure as shown below. Using this method, when we have a new requirement and the standard Period control does not fulfill the requirement, we can create a custom Period Control and use it at the Rate Step.