Phase 4: Device Management & AMI/EDM Preparation

Prerequisite Check: Phases 1–3 must be complete. We need: Company Code AEP1 with IS-U/EDM active (Phase 2), Plant AEP1 (Phase 3), Installation Types with EDM Relevance flag (Phase 3), Rate Categories for TOU billing (Phase 3), and verified Units of Measurement KWH/KW (Phase 1, Step 1.11). This phase builds the smart meter infrastructure, configures Business Partner and Contract Account master data, and establishes the EDM profiles for 15-minute interval TOU billing.

Section A: Business Master Data Foundation

Step 4.1 — Define Business Partner Roles

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — BP Roles: Table View

SAP displays existing BP roles (SAP delivers many standard roles).

2. Click New Entries.

Screen 3 — New Entry: BP Role Details

For each custom role, fill in:

3. Click Save (Ctrl+S).
4. Repeat New Entries for each additional role:

Complete Business Partner Roles

Why This Step

Business Partner (BP) is the universal customer master in S/4HANA. Unlike the legacy Customer Master (KNA1/KNB1), the BP is a single, role-based object that can simultaneously serve as a customer in FI-CA, a contract partner in IS-U, and a vendor in MM. Roles define what the BP can do:

• ISU001 (Contract Partner) is required to create a utility Contract — without this role, the ES25 Contract creation screen will not function.
• ISU003 (Meter Operator) identifies who manages the physical meter devices — critical for AMI device assignment.

Key Configuration Notes

• ⚠️ In S/4HANA, the BP transaction (BP) replaces legacy XD01/FD01. The Business Partner is integrated with the Customer/Vendor Integration (CVI) layer.
• BP Grouping (from Phase 2, Step 2.2.3) assigns the number range 01 to all partner roles.
• At runtime, create a new Business Partner via T-Code BP:
  • Screen 1: Select BP Role → Enter name/address → Save.
  • Screen 2: Navigate to IS-U Data tab → Assign Company Code AEP1 → Enter dunning data, payment method.

Step 4.2 — Define Contract Account Categories

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Contract Account Categories: Table View

2. Click New Entries.

Screen 3 — New Entry: CA Category — General Tab

Screen 4 — CA Category — Control Flags Tab

3. Click Save (Ctrl+S).
4. Repeat for each CA Category:

Complete Contract Account Categories

At runtime, Contract Accounts are created via T-Code CAA1: Screen 1: Enter Contract Account Category → Enter Business Partner number → Save.

Why This Step

The Contract Account is the financial container that groups all receivables for a customer at a specific Company Code. It sits between the Business Partner (who the customer is) and the Contract (what service they receive).

Step 4.3 — Define Contract Types

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Contract Types: Table View

2. Click New Entries.

Screen 3 — New Entry: Contract Type Details

3. Click Save (Ctrl+S).
4. Repeat for each contract type:

Complete Contract Types

At runtime, Contracts are created via T-Code ES25: Screen 1: Enter Installation number → Select Contract Type → Enter Contract Account → Assign rate → Save.

Why This Step

The Contract is the legal agreement between the utility and the customer for service delivery at a specific installation. It is the activating bridge — without a Contract, an Installation is “dark” (no billing, no service).

Section B: Device Management — AMI Smart Meters

Step 4.4 — Define Device Categories

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Device Categories: Table View

2. Click New Entries.

Screen 3 — New Entry: Device Category — General Tab

Screen 4 — Device Category — Control Flags Tab

⚠️ Critical AMI configuration flags:

3. Click Save (Ctrl+S).
4. Repeat for each device category:

Complete Device Categories

At runtime, devices are created via T-Code EG51 (Create Device): Screen 1: Enter Device Category → Serial Number → Save. Devices are installed at an installation via T-Code EG31I or through the Installation management screen.

Why This Step

The Device Category is the template for physical meter hardware. Every meter installed in the Columbus grid must be assigned to a Device Category. For an AMI-only utility:

• The Interval Data Capable flag is the most critical setting — it tells the system that this meter produces time-series data (not single scalar reads).
• Manual Read Relevant = unchecked ensures that no Meter Reading Order processes are triggered for these devices.

Step 4.5 — Define Register Groups (Interval Data Structure)

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Register Groups: Table View

2. Click New Entries.

Screen 3 — New Entry: Register Group Header

3. Click Save (Ctrl+S).
4. Double-click on the new register group to define individual registers.

Screen 4 — Register Group Details: Register Lines

5. Click New Entries to add registers within the group:

Registers for RG-AMI-R (Residential)

6. Click Save (Ctrl+S).
7. Repeat the entire process for each register group:

Registers for RG-AMI-C (Commercial)

Registers for RG-AMI-I (Industrial)

Registers for RG-AMI-N (Net Metering)

Why This Step

Register Groups define the data structure of what each meter records. In an AMI system, registers store 15-minute interval time series — this is a fundamentally different data model from traditional scalar cumulative reads.

Key Configuration Notes

• ⚠️ All registers use 15-minute intervals to align with PUCO reporting requirements and PJM Interconnection wholesale settlement periods.
• The Reactive Energy (KVARH) and Power Factor registers on commercial/industrial meters are required for power factor penalty calculations.
• Coincident Peak Demand (R06) on industrial meters is used for PJM capacity obligation cost allocation (the 4-CP or 5-CP method).

Step 4.6 — Define Device Number Ranges

SAP Screen Flow

Screen 1 — Number Range Maintenance: Initial Screen

When you execute EG30, SAP prompts:

1. Press Enter.

Screen 2 — Number Range Maintenance: Devices

2. Click Change Intervals (pencil icon 📝).

Screen 3 — Maintain Intervals

3. Click Insert Interval (➕):

4. Click Save (💾).

Why External Numbering?

Unlike other master data objects, meters use external numbering because each physical device arrives from the manufacturer with a pre-assigned serial number. The system must accept the manufacturer’s serial as the SAP device number to maintain traceability across the AMI head-end system, the warehouse, and the field workforce management system. Setting Ext = ✓ means the user (or integration) must supply the device number during creation rather than SAP auto-assigning one.

Section C: Energy Data Management (EDM) — The AMI Billing Engine

⚠️ This is the most architecturally significant section of the entire configuration. EDM is what makes AMI billing possible. Without EDM, 15-minute interval data has no path from the meter to the billing engine. Without EDM profiles, TOU billing is impossible.

Step 4.7 — Define EDM Profile Types

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — EDM Profile Types: Table View

2. Click New Entries.

Screen 3 — New Entry: Profile Type Details

For each profile type:

3. Click Save (Ctrl+S).
4. Repeat for all profile types:

Complete EDM Profile Types

Why This Step

EDM Profile Types are the classification templates for the time-series data managed by the Energy Data Management engine. Each profile type tells EDM:

• What kind of data to expect (consumption, demand, reactive, etc.)
• How to validate the incoming data
• Which replacement value procedures to apply when data is missing
• How to store the data in the time-series database

Step 4.8 — Define Time-of-Use (TOU) Period Definitions

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — TOU Rate Periods: Table View

2. Click New Entries.

Screen 3 — New Entry: TOU Period Definition

For each TOU period:

3. Click Save (Ctrl+S).
4. Repeat for all TOU periods:

Complete TOU Periods

Part B: Define Season Calendars

SPRO Path: SPRO → SAP Utilities → Energy Data Management → Profile Management → Time-of-Use → Define Season Calendar

5. Click New Entries.

6. Repeat for Winter:

7. Click Save (Ctrl+S).

Part C: Define Day Types

SPRO Path: SPRO → SAP Utilities → Energy Data Management → Profile Management → Time-of-Use → Define Day Types

8. Click New Entries and define:

9. Click Save (Ctrl+S).

Part D: Define Holiday Calendar

SPRO Path: SPRO → SAP Utilities → Energy Data Management → Profile Management → Time-of-Use → Define Holiday Calendar for TOU

10. Click New Entries.

11. Double-click on OH_PUCO to add individual holiday entries:

12. Click Save (Ctrl+S).

Part E: Define TOU Time Assignments (Period → Season → Day Type → Hours)

SPRO Path: SPRO → SAP Utilities → Energy Data Management → Profile Management → Time-of-Use → Define TOU Time Assignments

13. Click New Entries. This is the master mapping table that ties it all together:

14. Click Save (Ctrl+S).

Note: CRIT (Critical Peak) is not mapped to fixed time slots — it is activated as a dynamic overlay via event declaration. When AEP signals a Critical Peak event through the head-end system, EDM overrides the normal period assignment for the declared hours.

Why This Step

TOU periods are the heart of interval-based billing. EDM takes the raw 15-minute load profile data and overlays the TOU period definitions to produce time-bucketed consumption totals:

Raw Load Profile (96 intervals/day × 30 days = 2,880 data points)
    ↓ EDM TOU Processing
Bucketed Output:
    PEAK:  450 KWH
    OFFP:  820 KWH
    SOFF:  230 KWH
    CRIT:    0 KWH (no event declared)
    TOTAL: 1,500 KWH

The billing engine then applies different prices to each bucket:

PEAK:  450 KWH × $0.12/KWH = $54.00
OFFP:  820 KWH × $0.08/KWH = $65.60
SOFF:  230 KWH × $0.05/KWH = $11.50
Bill Total (Energy Charges):  $131.10

Step 4.9 — Define EDM Replacement Value Procedures

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Replacement Value Procedures: Table View

2. Click New Entries.

Screen 3 — New Entry: Procedure Details

3. Click Save (Ctrl+S).
4. Repeat for all procedures:

Complete Replacement Value Procedures

Part B: Define Validation Rules

SPRO Path: SPRO → SAP Utilities → Energy Data Management → Data Validation and Correction → Define Validation Rules

5. Click New Entries for each validation rule:

6. Click Save (Ctrl+S).

Why This Step

AMI systems are not perfect — communication failures, head-end outages, and meter malfunctions can create gaps in the 15-minute interval stream. EDM Replacement Value Procedures are the data quality safety net.

Key Configuration Notes

• ⚠️ PUCO regulations require that estimated readings be clearly identified on the customer’s bill. When a replacement procedure fills data, the billing document must carry an estimation indicator.
• The Spike Detection rule (V02) is critical for preventing billing complaints — a single anomalous 15-minute interval of 500 KWH (vs. a normal 0.5 KWH) could inflate a bill by thousands of dollars.

Step 4.10 — Define EDM Profile Allocation to Installations

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Profile Allocation Rules: Table View

2. Click New Entries.

Screen 3 — New Entry: Allocation Rule

For each combination of Installation Type and required EDM Profile:

3. Click Save (Ctrl+S).
4. Repeat for every Installation Type / Profile Type combination:

Profile Allocation Matrix

Why This Step

Profile Allocation is the critical linkage between the physical installation, its meter data, and the billing engine.

Without this allocation:

• The Load Profile data arriving from the AMI head-end would be stored but never processed into TOU buckets.
• The billing engine, when it processes a TOU Rate Category, would search for a TOU Profile, find nothing, and abort the billing order with error EDM 501 (“No EDM profile found for installation”).

Key Configuration Notes

• E1 (Residential Standard) gets only a LOAD profile because flat-rate customers do not need TOU bucketing — the billing engine simply sums all 15-minute intervals to get total KWH consumed.
• E2/E4/E5 (TOU variants) get LOAD + DEMA + TOU profiles because the billing engine needs:
  1. Raw interval data (LOAD) for audit trail
  2. Peak demand (DEMA) for demand charges
  3. Time-bucketed consumption (TOU) for time-differentiated energy charges
• Net Metering additionally gets a RECV profile to track solar export (energy flowing back to the grid).

Step 4.11 — Configure AMI Head-End Interface (Inbound Data Channel)

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Inbound Processing Configuration

2. Click New Entries.

Screen 3 — New Entry: Inbound Channel Details

3. Click Save (Ctrl+S).

Data Flow Architecture

AMI Head-End System (Itron/Landis+Gyr/Sensus)
    │
    │  15-minute interval data (MSCONS / XML)
    │  Frequency: Every 4 hours (96 intervals/batch per meter)
    ▼
SAP EDM Inbound Processor
    │
    ├── Validation Engine (V01–V05)
    │     ├── Pass → Store in LOAD Profile
    │     └── Fail → Exception Worklist (EDEX)
    │
    ├── Replacement Value Processor (LINT/HAVG/SYNT)
    │     └── Fill gaps in LOAD Profile
    │
    ├── TOU Processor
    │     └── Apply TOU Period Definitions → Generate TOU Profile
    │
    └── Demand Calculator
          └── Extract peak demand values → Generate DEMA Profile

Why This Step

This step defines how the raw 15-minute interval data physically enters SAP from the AMI head-end system. Without this configuration:

• There is no landing zone for meter data
• EDM profiles remain empty
• Billing has no consumption data to calculate against

Key Configuration Notes

• The actual middleware integration (SAP CPI / PI/PO / RFC) is a separate technical workstream, but the EDM inbound configuration must be defined first so that the middleware team knows which target structures to map to.
• Near real-time processing (every 4 hours) is the standard for billing-grade data. Real-time (per-interval) processing is reserved for operational use cases like outage detection and power quality monitoring.

Step 4.12 — Define Device/Register to Installation Assignment Rules

SAP Screen Flow

Screen 1 — IMG Navigation

1. Navigate to the SPRO path above → click Execute (⏩).

Screen 2 — Installation Rules: Table View

2. Click New Entries.

Screen 3 — New Entry: Compatibility Rule

3. Click Save (Ctrl+S).
4. Repeat for all combinations:

Complete Compatibility Matrix

Why This Step

This configuration ensures that when a field technician installs an AMI meter at a premise, the system automatically:

1. Validates that the meter type is compatible with the installation type
2. Assigns the correct register group to the device
3. Allocates the required EDM profiles for interval data processing
4. The installation is immediately ready for billing — no manual intervention required

Section D: End-to-End Process Validation

Step 4.13 — Verify the Complete Data Chain

This is not a configuration step but a validation exercise. Before declaring Phase 4 complete, trace the full data chain from meter to bill:

1. AMI Meter (EAMI-1P, Serial: 100001)
   └── Device Category: EAMI-1P
       └── Register Group: RG-AMI-R
           ├── R01: Total Active Energy (KWH, 15-min interval)
           ├── R02: Received Energy (KWH, 15-min interval)
           └── R03: Max Demand (KW, 15-min interval)

2. Installed at Installation (Type: E2 — Residential TOU)
   └── Premise (Type: 01 — Residential Unit)
       └── Connection Object (Type: 01 — Single Family)
           └── Address: 123 High St, Columbus, OH 43215

3. EDM Profile Allocation (auto-triggered on install):
   ├── LOAD Profile → receives raw 15-min KWH data
   ├── DEMA Profile → receives peak KW demand
   └── TOU Profile → receives time-bucketed consumption:
       ├── PEAK: Σ intervals during 3PM–7PM (Mon–Fri, Summer)
       ├── OFFP: Σ intervals during off-peak hours
       └── SOFF: Σ intervals during 11PM–5AM

4. Contract:
   └── Contract Type: E-RES
       └── Rate Category: RES-TOU
           └── Billing Schema: applies TOU prices to PEAK/OFFP/SOFF buckets

5. Contract Account (Category: 01 — Residential)
   └── Business Partner (Role: ISU001 — Contract Partner)
       └── Name: John Q. Customer
           └── BP Number: 0000000001

6. Billing Output:
   └── Invoice:
       ├── PEAK:  450 KWH × $0.12 = $54.00
       ├── OFFP:  820 KWH × $0.08 = $65.60
       ├── SOFF:  230 KWH × $0.05 = $11.50
       ├── Demand: 8.5 KW × $3.50 = $29.75
       ├── Customer Charge: $8.50
       └── TOTAL: $169.35
           └── Posted to FI-CA Subledger (Doc Type: ZI)
               └── Periodic G/L Transfer via Recon Key 0001 (T-Code: FPG1)
                   └── FI-GL Document (Doc Type: ZC, Number Range 19)
                       └── Debit: 1200000000 (AR)
                       └── Credit: 4100000000 (Revenue–Residential)

Runtime T-Code Quick Reference for Validation

Phase 4 — Completion Checklist

What Comes Next?

With Phases 1–4 complete, the utility’s system has:

✅ A fully functional FI/CO enterprise foundation
✅ An IS-U industry layer with FI-CA subledger integration
✅ A regional structure modeling the Columbus metropolitan grid
✅ AMI-ready device management with interval data register groups
✅ A complete EDM profile allocation for 15-minute TOU billing

Next Phases

🔗 Proceed to Phase 5: Billing & Tariff Foundation to build the billing engine.