Installing Technical Master Data

Objective

After completing this lesson, you will be able to describe the purpose and usage of the installation object.

Installation – Introduction

Illustration depicting the interconnected processes of utility installation, including customer data, scheduling, billing, technical setup, and regional coordination.
  • Scheduling

    The meter reading unit in the installation allocates the object to scheduling. This means that dates for periodic meter readings are determined via the meter reading unit and billing dates are determined via the portion.

  • Billing master data

    The assigned rate category defines the billing rule for the installation. The billing schema and the rate are determined via the rate category. The billing class is used for statistics and allows for validations for scheduling and rate categories.

  • Installation facts

    All individual agreements with customers, such as prices or special rate conditions are maintained in the installation facts. Flat-rate installations may also contain the rate type, which is used for rate determination along with the rate category. Installation facts can serve many other location/customer specific purposes, usually for billing.

Conceptual representation of organization and utility, highlighting systematic grouping for efficient billing, illustrated by tools in a container symbolizing functionality and order.
  • The utility installation groups together all devices, registers and flat-rate billing values that are allocated to the same premise, belong to the same division and are therefore to be billed together.
  • In the installation, you maintain the following links to other SAP S/4HANA Utilities components:
    • The rate category for the rate determination control in consumption billing
    • The meter reading unit for determining the meter reading dates
    • The premise for the spatial allocation of the installation (linked to central address management by the address of the connection object)
Diagram illustrating key components and relationships involved in a utility installation, emphasizing data, regulation, devices, and operational processes for resource management.
  • Each installation must be allocated to a premise.
  • The Current contract and Current bus. partner fields are only displayed if a business partner has been allocated to the installation in move-in processing.
  • Individual rate category data and facts enable you to adjust standard rates for a particular installation (that is, for a particular customer) (for nonresidential customers, for example). By allocating reference values, you can also model flat-rate installations in which no consumption entry devices are installed (for example, streetlights, or flat-rate heating installations).
  • RTP interface: Customer-specific agreements such as quantity limits, service limits or price profiles can be recorded in interval-related billing. When you define the RTP interface, these values must be defined as parameter templates.
  • Load profile: Synthetic profile whose values are generated based on predefined periods (defined using blocks of days and seasons) and the allocated day or annual profiles. Synthetic profiles are used in cases where interval reading does not take place. They are used to classify the consumption patterns of different customer groups. Customers that have similar consumption patterns are assigned the same synthetic profile.
Illustration of the billing process flow, highlighting data inputs, rate determination, price calculations, and procedural execution steps required to generate billing results.
  • The rates upon which a bill is to be based are determined from the rate category in the utility installation. The rate category can be stored at device or point of delivery level, or in the installation facts.
  • The rates determine prices via facts.
  • The rates that apply to a utility installation's bill are summarized in a billing schema. The billing schema is entered in the rate category when the billing rules are modeled.
Overview of billing data processes, including periods, documents, master data, and meter readings, paired with a line graph reflecting trends or analysis insights.
  • You can display both the billing document (billing results) and the print document (invoicing results). All data from the previous billing is available.
  • You can display the billing order if the installation has been prepared for billing.
Explains how time-sensitive data adjustments impact billing processes, requiring specific time segments for changes; illustrated by a clock symbolizing time management.
  • The billing class classifies contracts in the same division, for example, residential contract, nonresidential contract.
  • In the rate category, the criteria that control billing for the different types of rates are specified. These might include the control of the period-end billing or budget billing calculation.
  • The industry classifies companies according to their main area of economic activity. An industry can be allocated to business partners of the category organization. The industry serves as information only and is not relevant to billing.
  • Temperature areas group together parts of a service territory that have roughly the same air temperature. They are used for weighting of degree days and for thermal gas billing.
  • The Franchise contract defines the relationship between the utility company and the municipality regarding the franchise fee which will be charged. You set the Exempt from franchise fee indicator if no franchise fee is to be levied for the installation.
  • The meter reading unit groups together installations and their devices and registers according to regional criteria for the purposes of meter reading and device management. The meter reading unit forms the basis for the meter reader's worklist.
A timeline overview of installation status and associated contract changes, emphasizing transitions and highlighting the active contract as the current stage in the process.
  • The installation is always allocated to one contract only (or to no contract).
  • The installation is managed historically; this means that the installation can have several time slices.
  • In contrast to the installation, the contract is not maintained historically and therefore has no time slices. Only the start and end dates of the contract are maintained at the contract level.
  • You can display the time slices in the data environment of the installation.
Graphic explaining load profile management, highlighting energy consumption classification, data handling, profile creation, consumption factors, and automated billing calculations.
  • Load profile

    The load profile provides a form of standardized consumption patterns. This reduces the number of superfluous readings and also provides a basis for energy production planning.

  • You can allocate a consumption factor to each load profile historically. The values of the load profile are then multiplied by the value of the consumption factor. In the case of synthetic profiles managed using Energy Data Management (EDM), the system determines the consumption factor automatically.
  • To identify load profiles that you want to allocate without using Energy Data Management, use table maintenance for the table ELPROF.
Explains key considerations for energy meter reading, control, and energy return to the grid, with a focus on operational guidelines and troubleshooting.
  • The Purchase indicator shows that an installation or contract is used by the utility company to purchase utility services. As the utility company usually supplies customers with utility services, this indicator is not usually set. This is only an informative field. When billing small power producers, you can reverse the +/- sign for the consumption measured.
  • You use the base period category to define whether the previous period or period of previous year is to be used as the basis for extrapolating energy consumption.
  • In the Meter reading control field, you can override the number of customer meter readings or the number of estimations that have been predefined in the meter reading unit. You may wish to do this, for example, if a particular installation must never be read by the customer.
  • In the blocking reason, you indicate why the object in question has been temporarily blocked for meter reading. If a blocking reason has been defined, no meter reading orders will be generated for that meter reading unit during meter reading order creation.
A graphic emphasizes regional configuration, supply reliability for critical premises like doctor's offices, and device replacement tracking, supporting effective infrastructure management.

The installation type and voltage level fields, which also appear on the installation screen, are for information only and can be used for statistical evaluations if required.

Device Installation and Installation Structure

Conceptual graphic illustrating the relationship between device categories and individual devices, supported by text explaining device identification and management in system processes.
  • An equipment master record of a specified equipment category is created for each SAP S/4HANA Utilities device in the standard Plant Maintenance (PM) component. You must mark the corresponding equipment category as an SAP S/4HANA Utilities equipment category so that the data relevant to SAP S/4HANA Utilities is entered in the equipment when it is created.
  • This means that when you create equipment from this category, the system requests the data for consistent definition of a device.
  • If the device category is defined as AMI-relevant, then the device will contain AMI settings. Examples of AMI-related device data include the following: AMI device status, AMI active/inactive status, Advanced Meter Service provider, and Advanced Meter capabilities.
A central Device connects data sources like maintenance, processes, and attributes from PM and CR&B systems, highlighting integration for streamlined equipment management.
Overview of device records emphasizing their role in billing, technical setup, and installation processes to ensure accurate data management and compatibility with billing systems.
  • Device information records can be created with a future date. You can also install, remove, or replace device information records using future dates for billing purposes. The function must be activated in Customizing. Use the following path to make the appropriate settings in Customizing: SAP Fiori App, on Home pageUser Profile iconApp FinderSAP MenuSearch in SAP MenuCustomizing – Execute Project (enter)SAP UtilitiesDevice ManagementInstallationBasic SettingsDefine System Parameters for Installation/Removal/Replacement.
  • Device Info Records are used mainly in deregulated scenarios for utility companies operating as retailers.
Diagram illustrating the integration of billing and technical aspects of device installation, emphasizing connections between premises, devices, and functional locations.
  • The three procedures described above are supported during device installation. Depending on how the utility company is structured, technical installation can be carried out by a technician only, for example. Other departments are then responsible for rates and billing-related installation. However, full installation makes more sense if one department handles both technical and billing-related installations.

  • Once the billing-related installation has been carried out, it is then possible to maintain rate data at the register or device level within the installation structure.

Diagram illustrating relationships between installation, premise, and connection objects in regional and billing-related contexts, emphasizing device information and functional locations.
  • In the device installation, you can automatically create the device info record using the billing-related installation. If you do this, you do not install the device in a device location. Using the billing-related device installation, you can maintain rate data at installation structure level for points of delivery or devices.
  • When a device info record is removed from the last installation in which it was installed for billing purposes, its validity period is limited. You can now extend the validity of a limited device info record to 12/31/9999. This means the device info record can be reinstalled in an installation for billing purposes.
Visual representation of utility installation and billing processes, emphasizing data allocation, regional structures, device configuration, and categorized billing control mechanisms.

In addition to the rate data of the installation structure, you can also maintain device allocations at this level. For example, you can allocate an audio frequency ripple control receiver (ARCR) to a device. Any dependent registers or serial switching (primary or secondary meters) are maintained via the register relationships.

Facts and Reference Values

Overview of billing facts with examples, emphasizing their role in providing fixed values for calculations and processes, paired with a clipboard icon symbolizing documentation.
Illustrates a process for defining and customizing rate categories, emphasizing flexibility for special agreements and constraints on rate type usage based on predefined indicators.

You will learn in detail how to create and determine rates in the Billing/Invoicing training course. In this course, you will simply be shown how to override, at the installation level, data that controls billing.

Illustrates the hierarchy of facts, showing that installation facts take precedence over rate category facts, which in turn take precedence over rate facts.

Installation facts are the most specific form and thus are always used if available.

Summary of reference values used for non-measurement-based charges, including examples like energy, streetlights, and heating, paired with a symbolic stoplight for emphasis.
Overview of key billing data concepts, emphasizing entry values, indicators, repetition for similar items like streetlights, and rate classifications tied to operational usage patterns.
  • The entry value corresponds to the installed value. It can deviate from the value to be billed.
  • The repetition factor indicates how many reference values of the same type (for example, streetlights) exist. These reference values do not have to be created individually. However, you must create each reference value individually if you wish to enter detailed information (such as the address of the streetlights). The value entered in the Value to be billed field is multiplied by the repetition factor.
  • You will learn about the rate type, rate fact group, and burning hour calendar in the training course Billing/Invoicing.