Maximum Price Limitation

1. Maximum Price Limitation
Well, as the title says this post is on Maximum Price Limitation which is a form of Best Rate
Billing (probably will post later on this) with 2 alternatives.
The main variant used for this UTILIT02, probably one look at the documentation should clear what it
does and how it functions. My intention here is to show a demo on its functionality as per my
understanding.
UTILIT02 takes in 2 operands of amount type for comparing and gives out 2 operands as outputs :
Amount(determined value) and an Integer which tells which amount got selected.
The variant control for this operand gives flexibility to delete the billing line items of the amount failing
the comparison. Also the value of integer can be used to trigger specific line items (use IF-ELSE) based on
which amount got selected. If only one line item needs to be triggered specific to the selection after the
execution of this variant then this happens automatically.(demo shall show this)
Now for the demo. I have defined 2 rates.
• Rate MPL001 takes in the consumption multiplies to with the price and gives the amount. Also it
takes a rental price and adds it to the amount.
• Rate MPL002 changes the price used in MPL001 by multiplying with a factor ,use this price for
the consumption. UTILIT02 then compares the 2 amounts obtained from above and passes one
amount according to the variant control and also the integer value. based on the integer value the
next rate steps works. If its 01 then it executes rate step 006 if its 02 it executes rate step 007.
Rate steps for Maximum Price Limitation
Now for the facts of the rate.

2. Rate Steps Facts
Just to show the USERDEF operand. Make sure for the block titled 'Values for USERDEF' select the same
value for the USERDEF operands.
USERDEF_Operand Keep a note for the Values for USERDEF
So lets the execution start.
1st run:

3. 1st Run
Here we are comparing to get the highest amount and also deleting the billing line items of the lower
amount.
1st Run_rate steps
So the highest amount (Rate MPL002) gets into the billing line items and also the installation fact is
updated with the second value.
2nd Run:

4. 2nd Run
Here we are comparing to get the lower amount and also deleting the billing line items of the higher
amount.
2nd run_rate steps
So the lower amount (Rate MPL001) gets into the billing line items and also the installation fact is
updated with the first value.
3rd Run:

5. 3rd Run
Here we are comparing to get the lower amount but not deleting the billing line items of the higher
amount.
3rd Run_rate steps
So both the amounts (Rate MPL001 and MPL002) gets into the billing line items and also the
installation fact is updated with the first value. But this doesn't seem a good idea as we are not sure on
which amount is taken except for the fact that the Installation was updated with the First Rate value.
Anyways...
4th Run:

6. 4th Run
Here we are comparing to get the higher amount but not deleting the billing line items of the lower
amount.
4th Run_rate steps
So both the amounts (Rate MPL001 and MPL002) gets into the billing line items and also the
installation fact is updated with the second value.
There are other UTILITXX variants which actually do almost a similar function but with more operands.
Hope this short demo was up to the standards of the last posts. :)
Cheers!!
PS: I could have changed the layout of the billing line items to show the amount but then laziness is more
tempting. ;)
Blog: http://sapisurdg.wordpress.com/