Customizing the RTP Interface

The RTP interface is built from the header data, result parameters and RTP components. In order to customize an RTP interface, these building blocks must be developed. The following slides give you the information needed to build and customize an RTP interface.

• Set up Season, Day and TOU Groups (the component structure). This takes place outside RTP Customizing by means of the following menu path: Utilities Industry→Energy Data Management→Basic Settings..
• Determine RTP interface to be used. If the desired RTP interface does not exist, you can create it in Customizing: SAP Utilities→Energy Data Management→Interface to RTP Billing→Defining RTP Components→Define RTP Interface.
• Determine RTP components to be used. If the desired RTP component does not exist, you can create it in Customizing. SAP Utilities→Energy Data Management→Interface to RTP Billing→Defining RTP Components
• Determine formula to be used. If the desired formula does not exist, you can create it in Customizing. SAP Utilities→Tools→System Modifications→User-Defined Enhancements for Energy Data Management→Formulas(for further information, see the Formula Profiles unit of IUT225)
• Allocate RTP header data
• Allocate result parameters
• Allocate RTP components
• Allocate input and output parameters to each component

You can make the settings listed on the slide for the RTP interface. The following settings are dealt with in this unit:

• Define RTP component
• Define RTP interface
• Define result functions

• RTP component structure is comprised of a unique combination of season groups, day groups and TOU groups.
• When an RTP component is customized the following information is entered:
  • RTP component ID
  • RTP description
  • Season, day or TOU groups as defined by the requirements (not all have to be chosen)
• When a new RTP component is created, the day, season or TOU groups are allocated to the RTP component.
• In the above example, there are 3 RTP components
  • On-Off which is comprised of just a TOU Group
  • Season On-Off which is made up of both a season group and a TOU group
  • Peak which contains no time periods at all
• Customizing path: SAP Utilities→Energy Data Management→Interface to RTP Billing→Defining RTP Components.
• By allocating these groups to the RTP component in the RTP interface, it signals billing to be carried out according to these defined time periods.
• After the RTP component is created, it must be generated before it can be used. Once the RTP component has been generated, no changes can be made.

• Result functions define how profile values for a certain period are analyzed and used to calculate a single value such as a sum, minimum or maximum value.
• Result functions are defined with a description and a function module that performs the calculation. Results from result functions are currently used as input values in billing. This links the RTP interface to IS-U billing.
• Those provided by SAP are:
  • Function Description Function Module.
  • MINIMUM: Minimum Profile Value ISU_EDM_RESULT_0003.
  • PEAK: Maximum Profile ValueISU_EDM_RESULT_0002.
  • SUM: Total of Profile Values ISU_EDM_RESULT_0001.
  • Result function modules can be created at the customer site and implemented in this customizing process.

The following data must be entered to start the creation of the RTP interface:

• RTP Interface Code and Description: Identifies the RTP interface
• Header data: Formula, Interval Length, Division

To create result parameters, the following information must be entered: Result number, result parameter description, operand category, result function, unit of measurement (use the Copy button to insert the information into the RTP interface).

• RTP components: Activation, input parameters, output parameters and possibly template parameters should be defined for each RTP component, depending on the requirements.
  Note

  The activation type and priority should be defined.
• In the Activation tab:
  • Choose an RTP component. For each RTP component, choose one of the activation types.
  • For each RTP component, enter a priority. Enter a period in the From/To Date and From/To Time fields. (Choose the Copy function to insert the data below.)

• Recall that the structure of the RTP component is determined by the season, day and TOU groups allocated to the RTP Component.
• In the above examples:
  • RTP component 1 contains TOU periods On and Off.
  • RTP component 2 contains no time periods.

• Individual RTP components such as a specific agreement for a customer are defined in the installation.
• The RTP components can be activated in various ways:
  • Generally
  • Individually
• The activation and prioritization determine which RTP component will be executed in the RTP interface.

• On the Input Parameter tab, input parameters are the assigned a profile.
• Enter the period (From and To Date/Time) in which a profile is allocated to the input parameter of the RTP component. This enables allocation of different profiles to the same parameter (time slicing).
• Choose the profile OR role to be allocated to the parameter (Once you have entered this data, insert the information using the Copy function).

The above example displays how different profiles can be assigned to one input parameter based on the validity dates of the profile assignment.

• When an RTP component has the activation type Use and Activate Individually or Use Individually and Activate Generally, it is possible to define input parameters as template parameters. The advantage of template parameters is that they allow the user to define input parameters via the installation. This means that profiles or roles can only be allocated to input parameters at the installation.
• In order to assign the profile to the parameter template, go to the installation [NES31]. Choose the RTP interface button. Within this transaction, it is possible to assign the profile to the template parameter. This is typically used for short term agreements such as a SPOT pricing limit.

• In the Result number field, choose a result parameters that you want to allocate to the output parameter (Once you have entered this data, insert the information using the Copy function).
• Defined result parameters can be found under the Result Parameters tab.

After these steps below have been performed, the RTP interface has been created:

• Header data
• Result parameters
• RTP component activation and prioritization
• Input and output parameters

Before the RTP interface can be used, it must be allocated to a rate. This allocation is only possible for rates that have selected the Permitted for Interval Meters option. Within the RTP rate facts, individual rate step input operands can be allocated to result parameters of the RTP interface. This means that the appropriate operands are provided with result parameter values from the RTP interface during billing.

It is only possible to allocate result parameters to operands in the rate facts if the RTP operands have been defined. The operand category must also be defined. This is the operand category in which the RTP rate values in the RTP rate are to be processed. The operand category must match the category of the RTP operand.

The permissibility for interval meters is assigned within the rate.

• Within the rate facts, the operands coming from the RTP interface are indicated with the RTP operand symbol.
• The operands are tied to a result parameter number from the RTP interface.