Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U (Application Component) SAP Utilities⤷
EE80 (Package) IS-U: Customizing
IMG Activity
| ID | _ISUEDMRTP_000007 | General Information on the RTP Interface |
| Transaction Code | S_SK4_99000014 | (empty) |
| Created on | 20000823 | |
| Customizing Attributes | _ISUEDMRTP_000007 | General Information on the RTP Interface |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _ISUEDMRTP_000007 |
The RTP interface is a data object that links the Energy Data Management (IS-U-EDM) and Contract Billing (IS-U-BI) components.
The RTP interface enables you to use the profiles maintained in IS-U-EDM in IS-U billing. In order to this, you allocate the RTP interface to the rate used for billing an interval meter.
In the RTP interface you can execute billing-relevant processing steps carried out based on profiles. For example, you can process billing agreements for periods as small as 15 minutes. The results from such processing steps are then transferred to the rate steps in the rate. Billing lines can then be created from the rate steps.
The most important features of the RTP interface are:
Formulas
Formulas define the calculations that take place when an RTP interface is executed. You allocate a formula to an RTP interface. When you choose a formula, you define input parameters to be supplied to the interface as well as the output parameters available.
Input and output parameters always refer to those of the formulas allocated to the RTP interface.
RTP components
RTP components allow you to model the individual calculations in RTP billing. You can group together parameter allocations within an RTP component for later use.
You define RTP components for RTP interfaces. These components are then used when the interface is executed.
You can activate components of an RTP interface separately. When you activate an RTP component, the parameters allocated to the component are used when the interface is executed.
When you allocate RTP components to the interface, you can
- Distinguish between different activation types
The different activation types allow you implement RTP interfaces in a flexible way.
- For example, you can bill customer-specific agreements by individually allocating and activating an RTP component. This means that you would allocate the components only to those installations that you want to bill with these components. You define the valid periods for the agreement at the RTP interface level. You only have to define these periods once.
- Limit the activation of RTP components to certain times
This allows you to define parameter allocations in such a way that they are only used when needed, that is, in certain activation periods.
- Define a priority for each RTP component
This allows you to define which RTP component is used if there is more than one RTP component in one activation period.
Input parameters
You can allocate profiles to an input parameter. The values from these profiles are used in formula execution. You can allocate profiles to the input parameter according to the structure defined for the RTP component. This means you can allocate the input parameter a different profile for every combination of season type, day type and time-of-use type. When the RTP interface is executed, the system creates a profile from these profiles that is transferred to the input parameter for execution of the formula.
You can allocate different profiles to one input parameter in different RTP components. These profiles are then used according to the priority defined for the RTP component and its corresponding activation periods.
You can also allocate profiles to input parameters indirectly via roles. In this case, the input parameter is supplied with profile values when the RTP interface is executed. These profile values are from a profile with a specified role and allocated to the interval meter to be billed.
This allows you to provide an input parameter only with those profile values that correspond to the load shape of the interval meter to be billed.
In the case of RTP components with activation type Allocate and activate individually or Allocate individually and activate generally, you can assign profiles or roles to the input parameters at the installation level. To do this you must first define the appropriate parameter templates. Parameter templates are proposed automatically during maintenance at the installation level.
Output parameters
You can allocate result parameters to an output parameter. Result parameters describe the results of RTP interface execution. Result parameter values are defined via result functions.
You allocate result parameters to output parameters in accordance with the Structure defined for the RTP component. This means you can allocate the output parameter different result parameters for each possible combination of season type, day type and time-of-use type. When the RTP interface is executed, a profile is created for every result parameter at runtime. The profile is the result of the profile values of the corresponding output parameter. This means that the profile values of one output parameter can be transferred to more than one result parameter. Alternatively, one result parameter can be supplied with values from more than one output parameter. The result function allocated to the result parameter is then executed on the profile values transferred to the result parameter.
You can allocate different result parameters to one output parameter in different RTP components. These result parameters are then processed according to priority of the RTP component and corresponding activation periods.
Use of the RTP interface in the RTP rate
To use the RTP interface for billing, you have to allocate the interface to a rate. This allocation is only possible for rates for which you have selected the Permitted for interval meters field. You can allocate individual input operands for rate steps to result parameters of the RTP interface in the RTP rate facts. This means that the appropriate operands are provided with result parameter values from the RTP interface during billing.
You can only allocate result parameters to operands in the rate facts if you have defined RTP operands. You also have to define the operand category in which the RTP rate values in the RTP rate are to be processed further. The operand category you define must match the category of the RTP operand.
Example
RTP interface ONOFFPEAK is used to determine the following billing values from a measured consumption profile (15-minute interval):
- On-peak consumption
The total consumption in a period from 06:00:00 to 21:59:59 hours. - Off-peak consumption
The total consumption in a period from 22:00:00 to 05:59:59 hours. - Maximum demand value
Define the following result parameters in the RTP interface:
No. Description Function Operand category
001 On-peak consum. SUM QUANT
002 Off-peak consum. SUM QUANT
003 Maximum demand measured PEAK DEMAND
You allocate formula COPY01 to the RTP interface. This formula has an input parameter with profile category quantity. The formula has two output parameters, one with profile category quantity, in which the values of the input parameter are copied, and another with profile category demand, in which the values of the input parameter are converted to demand values.
In addition, the following RTP components are required:
RTP comp Descript. Prior. Activation type
ONOFF Calculation of on-/off-peak consumpt. 1 General
MAX Determination of max. demand 2 General
The ONOFF component divides the load shape into on- and off-peak consumption. You define the component with reference to an appropriate time-of-use group.
The MAX component controls determination of the maximum demand measured. In this case you do not have to define the component with reference to a season group, day group, or time-of-use group.
In the ONOFF component, you allocate the role "measured consumption" to the input parameter for the entire period. This corresponds to the load shape of the interval meter in the billing period. You allocate the first output parameter result parameter 001 for the on-peak period and 002 for the off-peak period.
Note that three levels are available for parameter allocation for the RTP component ONOFF in the RTP interface: one for on-peak allocations, one for off-peak allocations, and one for allocations valid for the whole period.
In the MAX component you also allocate the role "measured consumption" to the input parameter because the load shape also provides the basis for determining maximum
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | _ISUEDMRTP_000007 | 0 | I500000200 | Energy Data Management |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20000823 |
| SAP Release Created in | 462 |
