When setting up an RQ rate component, additional fields become available for you to define.
The following information will help you to set up your RQ rate components.
Select a Value Type of Unit Rate if the type of charge is an amount per some unit/quantity. In the rare situation where the amount of the charge is flat for the first X units, use the Value Type of Charge. This field will be gray when the rate component is referenced on another rate component.
Refer to Rate Component - Main Information for information about defining the Value Source.
The amount that you specified using the rate factor / value field was a rate per some unit of some thing. This thing must be identified using the Unit Of Measure, Time Of Use, and Rate Qty. Identifier fields.
Turn on Measures Peak Qty if you do not want this rate component to prorate.
Default note. The value of Measures Peak Qty is defaulted from the UOM table (if a UOM is specified).
Turn on GL Statistical Quantity if GL journal lines generated for this rate component should also contain the rate quantity amount as a statistical quantity. You would use this option if you keep track of both dollar amounts and consumption units in your general ledger.
When a bill segment is created, the system stores the statistical quantity on the journal line associated with the rate component's distribution code. If you book multiple UOM's to the same distribution code, you should only turn on GL Statistical Qty on one of the rate components. Otherwise, you will commingle different UOM's on a journal line's statistical quantity.
If the charge is only applicable to a quantity within some tier, indicate that the rate component is Stepped. When this option is turned on, you must indicate the Step Low Value and Step High Value that the charge is applicable to. When multiple tiers exist, the high value of the first tier is the low value of the second tier (and so on).
If the step boundaries are dynamic (i.e., they are calculated based on something that's only known at billing time), you can change the step boundaries using either of the following methods:
Use Step RC Sequence to indicate the sequence number of the rate component whose value will be multiplied by the step's boundaries to calculate the step boundaries to use at billing time.
Use Step Algorithm to indicate that an algorithm will be called to manipulate the step boundaries (note, this algorithm can manipulate the low and/or high boundaries). If you plan to use this method, you must set up this algorithm in the system. To do this:
Create a new algorithm (refer to Setting Up Algorithms).
On this algorithm, reference an Algorithm Type that manipulates a rate component's step boundaries. Click here to see the algorithm types available for this plug-in spot.
If you dynamically calculate step boundaries and the resultant high AND low values become zero, this signals the system that the rate component should be skipped (i.e., no bill line will be produced for the rate component).
Turn on Error if No Value if a bill error should be generated if the UOM / TOU / RQI specified on the rate component was not supplied at billing time.
Enter the verbiage to appear on the taxpayer's bill in Description On Bill and turn on the Print switch. Refer to How To Use Description on Bill for more information about these fields.
Move to the GL Distribution window to define how to book moneys associated with this rate component in the general ledger.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]