Access controls for Operands

www.sapisurdg.wordpress.com http://wp.me/p1Ci5j-hL
Access controls for Operands
This post is related to Operands, specifically to Operand access. Generally we go with
the default setting which is ‘All Operand Values’. The access control defines how
historical values of the operand are accessed during billing and refers only to values
stored in the Facts. Access control does not affect the processing of meter reading
results for a register operand.
All Operand Values
Here I have maintained a Factor Operand in the facts to get multiplied by the Quant
Operand having the meter reading for the billing period. Currently the value maintained
is 1. The billing period is 01/01/2012 to 02/01/2012(mm/dd/yyyy). The Meter reading is
320 units.

Factor Value maintained
So Factor (1) * Quant (320 units) gives 320 multiplied by price ($10) gives $3200.
Billing Document_1
The above was a simple example with no proration happening cause of operand access.
Now we shall look into specific scenarios. The following access controls are defined in
the system:
00 – All values are considered
This is the standard setting where all historical changes in the period to be billed are
imported.
Now the access control setting is the same ‘All Operand Values’. The Factor has a value
change in the middle of the billing period.

Factor Value Changed
When Billing is executed the proration happens as expected. 320 units is prorated as
Billing period length is 32 days. So per day consumption is 10 units.
1st
Period: Consumption for 01/01/2012 to 01/15/2012 is 10*15 days =150 units
2nd
Period: Consumption for 01/16/2012 to 02/01/2012 is 10*17days = 170 units
Now Consumption to be billed is 150*1(fact for 1st
Period) + 170*2(fact for 2nd
Period) =
150+340 = 490 units.
Amount is 490 * $10 = $4900.
Billing Document_2
01 – The value at the end of the rate period is valid
This setting causes the changes in the billing period to be disregarded.

End Rate Period
The facts are maintained as in the previous example. Here as it’s the end of the rate
period so the fact which is maintained at the end of the period is taken for billing.
Proration doesn’t happen. Here that’s ‘2’ so 320 units *2 * $10 gives $6400.
Billing Document_3
02 – The value on the key date is valid
Here only the values valid on the key date (maintained in the Meter Reading Unit) are
imported. Select this setting only in connection with billing on a monthly basis and

dependent on a key date. If operand values have been changed during the billing period,
these changes result in proration at the end of the month.
Key Date
Key date is the 10th of the month.
Key Date is 10th

Factor ‘1’ is selected because this value is valid on the key date (10th
) of the month.
320 units * 1 (Factor maintained before the key date) * $10 = $3200.
Billing Document_1
If I change the key date to 20th
of the month.
Key Date is 20th
Factor ‘2’ is selected because this value is valid on the key date (20th
) of the month.
320 units * 2 (Factor maintained before the key date) * $10 = $6400.
Billing Document_3
03 – The value at the end of the billing period is valid

This setting is chosen if the value maintained at the end of the billing period is to be
selected. This is different from value “01” as the end of the rate period may not always
be identical to the end of the billing period. Generally, they are identical.
End Billing Period
Here the fact which is maintained at the end of the billing period is selected. If the facts
are maintained in the rate category facts and the operand value is not found at the end
of the billing period, the system continues to search for this value in the other rate
category facts. Consumption of 320 units multiplied by 2 (Factor maintained at the end
of the period) * $10 gives $6400.

Billing Document_3
04 – All values in the month-based billing period
Here changes are only taken into account if they occur in a month for which the key date
falls in the billing period (or, more precisely, the rate period).
Values Month Based
Key date is the 20th of the month
Key Date is 20th
I have changed the values for the factor operand.

Factor Values Changed
Here the change after the key date is not considered. In this context, also note the
meaning of the period control in the rate step, and the control of the month-based
proration of tax changes in the rate category. Per day consumption is 10 units.
1st
Period: Consumption for 01/01/2012 to 01/15/2012 is 10*15 days =150 units
2nd
Period: Consumption for 01/16/2012 to 02/01/2012 is 10*17days = 170 units
Now Consumption to be billed is 150*1(fact for 1st
Period) + 170*2(fact for 2nd
Period) =
150+340 = 490 units.
Amount is 490 * $10 = $4900.

Billing Document_2
05 – The value at the start of the billing period is valid
This setting is chosen if the value which occurs at the start of the billing period is to be
only considered.
Start of Billing Period
This is opposite to the access control ‘03’. Here the facts which is maintained at the
beginning of the billing period is selected. If the facts are maintained in the rate category
facts and the operand value is not found at the start of the billing period, the system
continues to search for this value in the other rate category facts. Consumption of 320
units multiplied by 1 (Factor maintained at the start of the period) * $10 gives $3200.

Billing Document_1
06 – The value for the user-defined access date is valid
This setting is to be chosen if changes during the billing period are to be ignored and we
want to determine the access date flexibly during billing. To use this access control, you
must implement and activate the BAdi: ISU_BI_SELCONTROL. This BAdI determines
the date used to access the operands during runtime. So I have maintained the code to
get the average (not the weighted average) of the values and use it across the whole
period.
For Customer Date
My factor values are maintained as

Factor Value Changed
Billing Document_4
The average of the factor values during the billing period is 1.5 (average of 1 and 2)
Consumption to be billed is 320 units * 1.5 = 480 units multiplied by $10 gives $4200.
Any custom logic can be implemented in the BADI to get the desired output but
scenarios of move-in and move-out etc. needs to be tested if the values need to be
fetched outside of the billing period.
:)

Access controls for Operands

Recommended

More Related Content

What's hot (20)

Viewers also liked (9)

Similar to Access controls for Operands (20)

More from Rakesh Dasgupta (9)

Recently uploaded (20)

Access controls for Operands