Utilities · SAP IS-U

SAP IS-U test data for utilities

Billing, dunning and move-in tests in SAP IS-U need whole chains of master data: business partner, contract account, contract, installation, premise and meter readings. Synthesized copies those chains into test systems with every customer masked, bank details and consumption data included.

Book a health check

The data model

Available on SAP Store

Move-in test case · maskedExample

Business partner

Masked name, address and IBAN

BUT000

Contract account

Payment terms and dunning

FKKVKP

Contract and installation

Billing-relevant, linked

EVER · EANL

Meter readings

Consumption kept, person removed

EABL

Chains kept whole

Results measured in live deployments outside SAP

30%

faster testing and development cycles

Global bank · self-service test data

20bn

rows masked and subsetted in hours

Digital health platform · replaced a legacy TDM tool · Read the case study

28M

production rows protected, 100% referential integrity

Global specialty insurer · 40+ core applications · Read the case study

200×

more test data, from 100K to 20M entries

Telecom operator · masking and synthetic generation

On SAP, we measure results on your own data in a 10-day validation.

Why utilities need it

Four things that make IS-U test data hard

Millions of customersEvery household is a business partner with a contract account, bank details and a payment history.

Consumption is personalMeter readings and load profiles show when people are at home. Treat them as personal data in test too.

Long chainsA billing test needs the contract, installation, device and readings to match, or it fails before it starts.

Constant changeTariffs, regulatory changes and smart-meter rollouts mean regression testing never stops.

The data model

From business partner to meter reading, kept whole

Business partnerBUT000

Contract accountFKKVKP

ContractEVER

InstallationEANL

PremiseEVBS

Open itemsDFKKOP

Billing documentsERCH

Meter readingsEABL

Synthesized masks each customer once and keeps every link, so billing, dunning and move-in tests run end to end

SAP IS-U master data and documents

The IS-U chain from business partner to premise, with the documents tests depend on. Table names are a starting point; check them against your release.

Object	Main tables	Personal data to mask
Business partner	BUT000, BUT020, ADRC	Names, addresses, phone numbers and email
Bank details	BUT0BK	IBANs and account holders
Contract account	FKKVKP	Payment methods, dunning and correspondence data
Meter readings	EABL	Consumption linked to a household
Billing and print documents	ERCH, ERDK	Amounts and addresses on customer documents
Open items	DFKKOP	Payment history

A starting point. Check the tables against your release and your own extensions.

NIS2

Utilities are essential entities under NIS2

NIS2 lists energy and water among its highly critical sectors, and national laws now apply its cybersecurity rules to electricity, gas, district heating and water operators.

NIS2 · Article 21

Risk-management measures

Including security in how network and information systems are developed and maintained.

Test environments

Fewer copies of real customers

Masked test systems shrink what an incident in non-production could expose.

Supply chain

Partners and offshore teams

Testers at suppliers work on masked data, not on copies of your customers.

Not legal advice. National implementations differ; check the law that applies to you.

Read the source: Directive (EU) 2022/2555 (NIS2) on EUR-Lex

We've got you covered

Questions about SAP IS-U test data

What is SAP IS-U?

SAP's industry solution for utilities, covering customer service, billing and invoicing, device management and contract accounting (FI-CA). On S/4HANA it continues as SAP S/4HANA Utilities.

Which IS-U tables hold personal data?

Business partner tables such as BUT000 and ADRC, bank details in BUT0BK, contract accounts in FKKVKP, and documents that carry names and addresses. Meter readings in EABL are personal once linked to a household.

Can you subset IS-U by region or company code?

Yes. Choose company codes, regional structures or a sample of premises, and the chain from business partner to meter readings comes with each one.

Does masking break billing?

No. Masking replaces names, addresses and bank details but keeps consumption, tariffs and amounts, so billing and dunning runs behave as they do in production.

How does this help with NIS2?

NIS2 asks for cybersecurity risk management, including how systems are developed and maintained. Keeping real customers out of test systems reduces what a breach in non-production could expose. Your security team decides how it fits your measures.

Next step

See an IS-U refresh on your system

We refresh one IS-U test client with masked, complete chains for a region you choose.

Runs in your environmentNothing installed in SAPRead-only access to SAPSecurity and deployment

Book a health check

Security and deployment

Related SAP pages

BillingSAP BRIM test data for high-volume billingSAP BRIM

CapabilitySAP data masking and scramblingData masking

ComplianceSAP GDPR compliance for test dataGDPR test data

Updated October 2026

SAP, S/4HANA, SAP HANA, SuccessFactors, Ariba, Concur and other SAP products and services mentioned herein, as well as their respective logos, are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.