Create Technical Masterdata in SAP IS-U

Build a full IS-U masterdata chain from Connection Object to installed meter.

Introduction

30 Second Summary

Every time you flip a light switch or receive a utility bill, there is a system tracking exactly which meter sits at which address and who should be charged for the energy consumed. That system needs a carefully structured chain of data objects linking physical locations to billing accounts.

In this project, you will build a complete technical masterdata chain in SAP IS-U for a fictional residential electricity customer. You will create every object from the building-level Connection Object down to an installed meter that is ready for billing.

What You'll Build

You will create a full SAP IS-U technical masterdata hierarchy using SAP GUI transactions, linking a Connection Object, Premise, Installation, Device Location, and Device together through a Full Installation.

By the end of this project, you'll have:

A Connection Object and Premise representing a residential building and apartment unit in SAP IS-U.
A Utility Installation configured with billing class, rate category, and meter reading unit.
A Device fully installed at a Device Location and linked to the installation via Full Installation (transaction EG31).
Secret Mission: Create the entire technical masterdata chain in a single execution using the Master Data Template.

Are there any prerequisites?

You need access to an SAP IS-U system (such as an S/4HANA Utilities sandbox or an ECC system with the IS-U component) with authorization for transactions ES55, ES60, ES30, ES65, IQ01, and EG31. Basic SAP GUI navigation skills (running transactions, entering field values, saving) are also expected.

Navigate SAP IS-U and Understand the Data Hierarchy

Before creating any objects in SAP IS-U, you need to understand how its technical masterdata hierarchy works. Each object you create depends on the one above it, so building in the wrong order will fail.

In this step, you will confirm your transaction access, map out the hierarchy, and document the transaction codes you will use throughout the project.

In this step, get ready to:

Confirm your IS-U transaction authorizations using the EASY transaction.
Understand the technical masterdata hierarchy and how objects relate to each other.
Document the key transaction codes and verify each one is accessible.

Use transaction EASY to confirm your authorizations

The EASY transaction is a search tool that lets you find IS-U transaction codes and confirm your system authorizations are active.

In the SAP GUI command field (the text box at the top of the screen), type /nEASY and press Enter.
Search for ES55 in the search field.
Confirm the transaction appears in the results. If you see it listed, your authorization for Connection Object creation is active.
Repeat the search for ES60, ES30, ES65, IQ01, and EG31 to confirm all six are accessible.

Seeing an authorization error?

If any transaction shows an authorization error, contact your SAP Basis administrator to request the missing role assignment. You will need all six transactions to complete this project.

Help me understand SAP IS-U authorization errors and how to resolve them.

Review the IS-U technical masterdata hierarchy

The technical masterdata hierarchy in SAP IS-U models how a utility company tracks its physical infrastructure. Each level represents a real-world object.

Connection Object (top level): represents the physical building connected to the utility grid.
Premise: represents the specific unit within the building that receives utility service (e.g., an apartment).
Installation: the billing-relevant object linked to the premise. This is where billing class, rate category, and meter reading schedules are assigned.
Device Location: the physical spot where a meter is mounted (e.g., basement meter cabinet). Inherits address and maintenance plant from the Connection Object.
Device: the actual meter hardware (e.g., an electricity meter with registers that record consumption).

How does data flow through the hierarchy?

Address data inherits downward from the Connection Object. When you create a Premise under a Connection Object, it automatically picks up the address. The same applies to Device Locations.

Billing happens at the Installation level. The Installation is where the system connects physical meter readings to billing schedules and rate categories. Everything above it describes location. Everything below it describes measurement hardware.

Why does creation order matter?

You must create objects from top to bottom. A Premise requires a Connection Object number. An Installation requires a Premise number. A Device Location requires a Connection Object number. The Full Installation at the end ties Device, Device Location, and Installation together.

Document your transaction codes and verify access

Each object in the hierarchy has its own dedicated transaction code for creation. You will use these throughout the project, so keep them handy.

Note these transaction codes for the objects you will create:

ES55 = Create Connection Object (stored in table EHAUISU, field HAUS).
ES60 = Create Premise (stored in table EVBS, field VSTELLE).
ES30 = Create Installation (stored in tables EANL/EANLH, field ANLAGE).
ES65 = Create Device Location (stored in table EGPLT, field DEVLOC).
IQ01 = Create Device (stored in table EGERS, field GERAET).
EG31 = Full Installation (links device to device location and installation for billing).

Verify each transaction is accessible by typing it into the command field (e.g., /nES55) and confirming the creation screen loads without errors.
Press F3 (Back) to exit each transaction without saving. You will create real objects starting in Step 2.

What is the /n prefix?

Typing /n before a transaction code ends the current transaction and opens the new one in the same session. This is the standard way to navigate between transactions in SAP GUI.

✔️ All six transactions loaded successfully

You are ready to start creating objects. Keep your transaction code reference handy for the remaining steps.

ⓧ One or more transactions gave an error

If you see an authorization error on any transaction, you will not be able to complete the corresponding step. Contact your SAP Basis administrator and request the IS-U technical masterdata creation roles.

Provide the specific transaction codes that failed so the administrator can assign the correct authorization objects.

Your transaction access is confirmed and you have a clear map of the hierarchy. Next up, you will create your first object at the top of the chain: a Connection Object representing a residential building.

Create a Connection Object

Your SAP IS-U system is ready and you have confirmed access to all the transactions you need. Now it is time to start building.

The first object in the technical masterdata chain is the Connection Object. This represents the physical point where a building connects to the utility grid. Every other object in the hierarchy inherits its address data from the Connection Object, so getting this right is the foundation for everything that follows.

In this step, get ready to:

Execute transaction ES55 to create a Connection Object with address details.
Assign a maintenance plant and note the system-generated Connection Object number.
Verify the Connection Object by displaying it with transaction ES57.

Execute transaction ES55 and enter address details

The Connection Object stores the physical address of the building that connects to the utility network. You will create one using a fictional residential building address.

In the SAP GUI command field, type ES55 and press Enter.
The Create Connection Object screen opens.
Enter a street name in the Street field (e.g., Musterstrasse).
Enter a house number in the House number field (e.g., 12).
Enter a postal code in the Postal code field (e.g., 10115).
Enter a city in the City field (e.g., Berlin).
Select the appropriate regional structure values for your system. These fields control how the Connection Object maps to your system's geographic and organizational configuration.

What is a regional structure?

The regional structure defines how your system organizes geographic areas for utility services. The exact values you see depend on your system's Customizing (SPRO) configuration.

Select values that match a residential scenario in your system. If you are unsure which values to choose, check with your system administrator or trainer.

Assign the maintenance plant and note the Connection Object number

The maintenance plant links the Connection Object to your organization's plant maintenance structure. This is required before you can save.

In the Plant field, enter or select the maintenance plant appropriate for your system configuration.
Click the Save button (or press Ctrl+S).
Look at the status bar at the bottom of the screen. The system displays a confirmation message with the newly generated Connection Object number.
Write down this Connection Object number. You will need it in every subsequent step of this project.

Where is the Connection Object number stored?

The Connection Object number is stored in the HAUS field in table EHAUISU. This is a system-generated 30-character identifier that uniquely identifies your physical connection point.

Getting an error when saving?

If you see a message about missing required fields, check that the regional structure values are filled in. Some systems require all regional structure fields before saving.

If you see an authorization error, confirm that your user has access to transaction ES55 by running the EASY transaction search again.

Help me troubleshoot my Connection Object creation error in SAP IS-U.

Verify the Connection Object using ES57

Before moving on, confirm that the Connection Object was created correctly by displaying it in read-only mode.

In the SAP GUI command field, type ES57 and press Enter.
Enter the Connection Object number you noted in the previous substep.
Press Enter to display the Connection Object details.
Confirm that the street name, house number, postal code, city, and maintenance plant all match what you entered.

Keep your numbers handy

Open a text file or notepad and record your Connection Object number along with the transaction code used to create it. As you progress through this project, you will accumulate several object numbers that reference each other.

Your Connection Object is in place. Next up, you will create a Premise and a Utility Installation that sit beneath it in the hierarchy.

Create a Premise and Utility Installation

Your Connection Object represents the physical building connected to the utility grid. Now you need to model what actually receives the service inside that building.

In this step, you will create a Premise (the specific unit, like an apartment) and a Utility Installation (the billing-level object that controls how meter readings turn into invoices).

In this step, get ready to:

Create a Premise linked to your Connection Object.
Create a Utility Installation with division, billing class, rate category, and meter reading unit configured.
Verify the installation is correctly assigned to your Premise.

Create a Premise (ES60)

A Premise represents the spatial unit that actually receives utility service. In a residential building, each apartment is its own Premise. The Premise inherits its address from the Connection Object, so you do not need to re-enter it.

Open the SAP command field and enter transaction ES60.
Press Enter to execute the transaction.
In the Connection Object field, enter the Connection Object number you recorded in the previous step.
Press Enter. The address fields will populate automatically from your Connection Object.

Why does the address appear automatically?

In the IS-U hierarchy, address data inherits downward from the Connection Object. Every Premise, Installation, and Device Location beneath it shares the same physical address unless explicitly overridden.

Add premise-level details to distinguish this unit within the building. Enter a floor level (e.g., 2) and apartment number (e.g., 2A) in the relevant fields.
Click the Save button (or press Ctrl+S).
The system generates a Premise number. Note this number down. It is stored in the VSTELLE field in table EVBS. You will need it for the next substep.

Record your object numbers

Keep a running list of the system-generated numbers for each object you create (Connection Object, Premise, Installation). Each subsequent transaction requires the number from the previous object as input.

Not seeing the address populate?

Double-check that the Connection Object number you entered matches exactly what was generated in the previous step. Leading zeros matter in SAP.

If you see an authorization error, confirm your user has access to transaction ES60 by asking your system administrator.

Still stuck? Help me troubleshoot my ES60 Premise creation in SAP IS-U.

Create a Utility Installation (ES30)

The Utility Installation is where billing lives in IS-U. It ties together division, billing class, rate category, and meter reading schedule. All billing and meter-to-cash processes reference this object.

Open the SAP command field and enter transaction ES30.
Press Enter to execute the transaction.
In the Premise field, enter the Premise number you just recorded.
In the Division field, select the electricity division from the dropdown or matchcode.

What is a division?

A division represents the type of utility service (electricity, gas, water, etc.). Each Installation is tied to exactly one division. If a premise receives both electricity and gas, it would have two separate Installations.

In the Billing class field, select the residential billing class. This classifies the installation within its division for validation and statistics.
In the Rate category field, select the appropriate rate category for your system. The rate category works together with rate types to determine how consumption is priced.
In the MRU (Meter Reading Unit) field, assign a meter reading unit. The MRU controls when meter readings are scheduled and when billing runs.
Click Save (or press Ctrl+S).
The system generates an Installation number. Note this number down. It is stored in the ANLAGE field in tables EANL (master data) and EANLH (time-dependent data).

Why are there two tables for one Installation?

Table EANL holds the master record that does not change over time (like the division). Table EANLH holds time-dependent data (like rate category and billing class) that can change on specific dates without creating a new Installation.

Seeing a missing field error on save?

The specific values available for billing class, rate category, and MRU depend on your system's Customizing configuration (SPRO). If a field is marked as required but shows no values, ask your system administrator which values are configured for electricity residential installations.

Need help? Help me resolve a missing field error when creating a Utility Installation in ES30.

Verify the installation (ES32)

Before moving on, confirm that all the billing configuration is correctly saved on your Installation.

Open the SAP command field and enter transaction ES32.
Press Enter to execute the transaction.
Enter the Installation number you just recorded.
Confirm the following fields are correctly displayed:

Premise matches your Premise number.
Division shows electricity.
Billing class shows residential.
Rate category shows the value you assigned.
MRU shows the meter reading unit you assigned.

What should I see?

Transaction ES32 displays the Installation in read-only mode. You should see all five fields (Premise, division, billing class, rate category, MRU) populated with the values you entered during creation. If any field is blank or incorrect, go back to transaction ES31 (Change Installation) to correct it.

A field shows a different value than expected?

Some fields may display a code rather than a description text. Use the matchcode (F4) on the field in ES31 to verify the code maps to the intended value (e.g., residential billing class).

Need help? Help me verify my Utility Installation in SAP IS-U transaction ES32.

Your Premise and Installation are now in place. The billing side of your technical masterdata chain is configured. Next, you will create the physical locations and devices that connect meter hardware to this billing structure.

Create a Device Location and Device

Your Installation is configured and ready for billing. Now you need to model the physical meter itself and the spot where it sits in the building.

In SAP IS-U, the Device Location represents where a meter is physically mounted (e.g., a basement cabinet). The Device represents the meter hardware itself. Both must exist before you can perform a Full Installation in the next step.

In this step, get ready to:

Create a Device Location linked to your Connection Object using transaction ES65.
Create an electricity meter Device using transaction IQ01.
Verify the Device was created correctly using transaction EG43.

Create a Device Location (ES65)

A Device Location pinpoints the exact physical spot where a meter is mounted. It inherits the address and maintenance plant from the Connection Object automatically, so you only need to add location-specific details.

In the SAP command field, type ES65 and press Enter.
Enter your Connection Object number (the HAUS number you recorded in Step 2) in the Connection Object field.
Confirm that the address and maintenance plant fields are populated automatically from the Connection Object.
Add location-specific details in the description or location fields. For example, enter Basement meter cabinet to describe where the meter will sit in the building.
Click Save (or press Ctrl+S).
Note the system-generated Device Location number displayed in the status bar. This is the DEVLOC field value (stored in table EGPLT). Record it for later use.

Why does the Device Location inherit from the Connection Object?

The Connection Object represents the entire building connected to the utility grid. The Device Location sits within that building, so it makes sense to pull the address and maintenance plant from the parent object rather than requiring you to re-enter them.

This inheritance pattern keeps data consistent. If the building address changes, updates flow down to all child objects automatically.

Getting an authorization error on ES65?

Confirm your user role includes authorization for transaction ES65. Ask your system administrator to check the IS-U Device Management authorization objects assigned to your profile.

If the Connection Object number is not accepted, verify you are entering the exact number from Step 2 (check for leading zeros).

Help me troubleshoot my ES65 Device Location creation error

Create a Device (IQ01)

The Device represents your physical electricity meter. When you create a device in IS-U, the system also creates a corresponding PM equipment entry with the same serial number.

In the SAP command field, type IQ01 and press Enter.
Select the appropriate Device Category for an electricity meter from the dropdown or search help. The available categories depend on your system's Customizing configuration.
Enter a serial number in the Serial Number field (for example, EL-2024-00001).
Enter the manufacturer name in the Manufacturer field.
Complete any other mandatory fields highlighted by the system (these vary by device category).
Click Save (or press Ctrl+S).
Note the system-generated Device number displayed in the status bar. This is the GERAET field value (stored in table EGERS). Record it for the next step.

What does a device category control?

A device category groups devices with similar technical properties. It determines the register group (which registers the meter has), links the device to a material in Materials Management, and controls which fields appear during device creation.

For an electricity meter, the device category typically defines registers for consumption readings (e.g., peak, off-peak). The register group becomes important later during Full Installation when registers are linked to rate types for billing.

Not sure which device category to select?

Use the search help (F4) on the Device Category field to see all available options in your system. Look for a category name that references electricity or kWh meters.

If no suitable category exists, your system may not have electricity device categories configured in Customizing. Check with your system administrator or IS-U configuration team.

Help me find the right device category for my electricity meter

Verify the device with EG43

In the SAP command field, type EG43 and press Enter.
Enter the Device number you just recorded and press Enter.
Confirm the Device Category matches what you selected during creation.
Confirm the Register Group is populated (this was assigned automatically based on the device category).
Confirm the Serial Number matches what you entered.

If all three fields are correct, your Device is ready to be installed.

What does the device master record contain?

A device master record spans three areas: IS-U data (device number, category, registers, meter readings), Materials Management data (serial number, material, plant, storage location), and Plant Maintenance data (equipment number, status, maintenance plant).

This cross-module integration means creating a device in IS-U automatically creates the corresponding equipment and material references. You get a single source of truth for the physical meter across all SAP modules.

You now have all the building blocks in place. Your Device Location knows where the meter goes, and your Device represents the meter itself. Next up, you will link everything together with a Full Installation to make the chain billing-ready.

Perform a Full Installation

You now have all the individual pieces of your technical masterdata chain created: a Connection Object, Premise, Installation, Device Location, and Device. The final step is to link them together so the system knows which meter is installed where and which registers feed into billing.

A Full Installation (transaction EG31) performs two operations in one step. It links the device to the device location (the technical installation) and links the device registers to the installation for billing (the billing-related installation).

In this step, get ready to:

Execute a full installation using transaction EG31.
Confirm the system creates the installation structure linking registers to rate types.
Verify your complete technical masterdata chain is fully linked and billing-ready.

Execute transaction EG31

Transaction EG31 brings together your Installation, Device Location, and Device into a single linked structure. This is what makes your masterdata chain billing-ready.

Enter EG31 in the SAP command field and press Enter.
Enter your Installation number (ANLAGE) that you recorded from Step 3.
Enter your Device Location number (DEVLOC) that you recorded from Step 4.
Enter your Device number (GERAET) or serial number from Step 4.
Set the installation date to today's date.

What does a full installation do?

A full installation performs two things at once. The technical installation links the physical device to the device location, recording where the meter is physically mounted.

The billing-related installation links the device registers to the installation. This tells the system which meter readings feed into billing calculations using the rate types and rate category you configured earlier.

Keep your reference numbers handy

You need three numbers for this transaction: the Installation number from Step 3, the Device Location number from Step 4, and the Device number from Step 4. If you did not record them, you can look them up using transactions ES32, ES67, and EG43 respectively.

Confirm the installation details and save

Before saving, the system presents a summary of what will be linked. Review the details to make sure the correct objects are being connected.

Review the installation details displayed on screen. Confirm that the Installation number, Device Location number, and Device number all match what you created in previous steps.
Verify the installation date is correct.
Click the Save button (or press Ctrl+S) to execute the full installation.

The system creates the installation structure, linking registers to rate types within your installation. You should see a confirmation message indicating the full installation was performed successfully.

Seeing an error when saving?

If the system reports a missing or invalid Installation number, double-check that you entered the correct ANLAGE value from transaction ES32.
If you see an error about the device already being installed, the device may have been linked in a previous attempt. Use transaction EG43 to check the device status.
If you receive an authorization error, confirm your user has access to transaction EG31 by checking with your system administrator.

Help me troubleshoot my EG31 full installation error

Verify the full installation in ES32

The final verification confirms that all objects in your technical masterdata chain are properly linked and that the installation is billing-ready.

Enter ES32 in the SAP command field and press Enter.
Enter your Installation number (ANLAGE).
Navigate to the Installation Structure tab.
Confirm that your device, registers, and rate types are now linked to the installation.

What should I see?

The Installation Structure tab shows the complete linkage between your device, its registers, and the rate types configured for your installation. You should see your electricity meter's device number, the register(s) associated with it, and the rate type(s) that map to your rate category.

This structure is what the system uses during meter reading and billing. When a meter reading comes in, the system knows which register recorded it, which rate type applies, and therefore how to calculate the bill.

Your technical masterdata chain is now complete. You have a fully linked hierarchy from Connection Object down to an installed device that is ready for a move-in process.

Secret mission

Create Technical Masterdata Using MDT (EPRODCUST)

You just built the entire technical masterdata chain one transaction at a time. But in real SAP IS-U implementations, consultants use the Master Data Template to create everything in a single execution. Can you do the same?

Clean Up Your Resources

This project runs entirely within your existing SAP IS-U system, so there are no ongoing costs from the objects you created. Decide whether to keep your masterdata for future reference, or request deletion through your system administrator.

Resources you used:

Connection Object (created via ES55).
Premise (created via ES60).
Utility Installation (created via ES30).
Device Location (created via ES65).
Device (created via IQ01).
Full Installation linking (created via EG31).

Keep everything running

No action needed. Choose this if you want to keep your masterdata chain for future practice or as a reference for upcoming projects (such as creating business masterdata or performing a move-in).

Your technical masterdata objects remain in the system and do not incur any costs.
Note down your Connection Object number, Premise number, Installation number, Device Location number, and Device number for future reference.

Pause - I'll come back to this later

SAP IS-U masterdata objects persist in the system without any running processes to pause. There is nothing to shut down or stop.

Record your object numbers (Connection Object, Premise, Installation, Device Location, Device) in a document outside SAP so you can find them when you return.
Use transaction ES57 (Connection Object), ES62 (Premise), ES32 (Installation) to display your objects anytime you return.

Delete - I don't want to use this again

SAP IS-U masterdata cannot be directly deleted through a single transaction. Deletion requires flagging objects and processing them through system administration jobs.

If you are using a training sandbox, the system is typically reset periodically by your administrator. No action is needed from you.
If you are using a shared company system, contact your SAP Basis team or system administrator to request deletion of your test objects. Provide your Connection Object number as the top-level reference.
Objects must be removed in reverse dependency order: Full Installation first, then Device and Device Location, then Installation, then Premise, and finally Connection Object.

Why can't I just delete these myself?

SAP IS-U enforces referential integrity across the masterdata hierarchy. You cannot remove a Connection Object while a Premise still references it. Deletion flags and archiving runs are handled by administrators with specific authorizations.

Nice Work!

You have built a complete SAP IS-U technical masterdata chain from scratch. Your system now has a fully linked hierarchy from a physical building all the way down to a billing-ready installed meter.

You've learned how to:

Build a complete technical masterdata chain in SAP IS-U by creating a Connection Object (ES55), Premise (ES60), Installation (ES30), Device Location (ES65), and Device (IQ01).
Perform a Full Installation (EG31) linking a device to both the physical location and the billing installation, making the meter ready for move-in and meter reading.
Map each IS-U object to its transaction code, SAP table, and real-world equivalent, giving you a documented reference for future IS-U work.
Created the entire technical masterdata chain in a single execution using the Master Data Template (EPRODCUST) in the Secret Mission.

Ready to quiz yourself?