Master Configuration

The Rate Engine Configuration master configuration can be used to define the behavior of the Rate Schedule portals used when creating rate schedules.

To edit this master configuration, select Admin > Master Configuration, and click the edit icon for the Rate Engine Configuration.

The Rate Engine Implementation dropdown list defines which rate engine(s) will be used by your organization.

  • Calculation-Rule Based indicates that your implementation uses calculation rule-based rates, which require the configuration of rate schedules with calculation groups and calculation rules.
  • Component-Based indicates that your implementation uses component-based rates, which require the configuration of rate versions with rate components, and rate schedules with SQ and register rules.
  • Both indicates that your implementation uses both rate engines. If this applies to you, then the system will use this option to ease navigation as follows:
    • Select Menu > Rates > Rate Schedule > Add to launch the page to add a new rate schedule. (A hyperlink is included to take the user to the component-based rate schedule maintenance page, if necessary.)
    • Select Menu > Rates > Rate Schedule > Search to launch the Rate Schedule Query portal.
    • The query results attempt to highlight component-based rates by appending “(Component-Based)” to the rate schedule's description.
    • Once a rate schedule is selected from the result set, the system navigates the user to either the calculation rule-based Rate Schedule portal or the component-based Rate Schedule page.

The External Communication section is used when the rate engine needs to communicate with an external system. For example, service quantities are needed to test a rate on the Rate Check portal. These service quantities may be entered on the portal, retrieved from an existing bill segment, or (in the case of a service agreement that requires bill determinants) request service quantities from Oracle Utilities Meter Data Management.

  • Request Type identifies the various data requests that can be made to an external system. Request types are defined in the RATE_​EXT_​REQ_​TYPE_​FLG lookup field. To introduce additional request types, add appropriate lookup values to this lookup field for each request type you wish to support.

    The base package includes the following business objects to be defined on the outbound message types created for such requests:

    • Rate Check Usage: C1-UsageRequestOutMsg (used to request bill determinants from MDM on the rate check portal)

  • External System and Outbound Message Type are used when creating the outbound message for the data request.