Conversion Design Document

[Connection Object]
Version 0.3
 Version Number 0.3
Draft
In Review
Document Status
Final
Update After Final
Document Approver(s)

Document Owner(s) Jim Rainear, Sunny Wong

Date Approved

Date Last Modified 06/19/2022

Document Link

Revision History
Versio Date Description Author
n
0.1 2/26/2019 Technical data map created based on Jonathan Chandy
initial sprint
0.2 7/12/2019 Updates made to complete draft Sunny Wong
document
0.3 3/27/2020 Catch up requirement updates to end of Sunny Wong
PT1

Duke Energy Proprietary – Internal Use OnlyPage 2 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
Table of Contents

1. EXECUTIVE SUMMARY..............................................................................................................5

2. SOURCE SYSTEM ANALYSIS......................................................................................................7

2.1. FRONT-END (LEGACY SYSTEM SCREENS)..............................................................................................................7

2.2. BACK-END (LEGACY SYSTEM TABLES)................................................................................................................12

3. TARGET SYSTEM ANALYSIS.....................................................................................................14

3.1. FRONT-END (SAP SYSTEM SCREENS)................................................................................................................14

3.2. BACK-END (SAP SYSTEM TABLES)....................................................................................................................15

4. CONVERSION SCOPE & CONSIDERATIONS.............................................................................16

4.1. SCOPE.........................................................................................................................................................16

4.2. CONVERSION REQUIREMENTS AND CONSIDERATIONS...........................................................................................16

4.3. DATA SCENARIOS..........................................................................................................................................19

4.4. MANUAL CONVERSION...................................................................................................................................19

4.5. DATA CLEANSING ITEMS.................................................................................................................................19

4.6. OPEN ITEMS.................................................................................................................................................20

5. TECHNICAL REQUIREMENTS - EXTRACT.................................................................................22

5.1. EXTRACT APPROACH......................................................................................................................................22

5.2. RELEVANT TABLES TO EXTRACT FROM...............................................................................................................22

5.3. SQL SELECTION RULE....................................................................................................................................23

6. TECHNICAL REQUIREMENTS - TRANSFORM...........................................................................24

6.1. TRANSFORM APPROACH.................................................................................................................................24

6.2. DATA MAPPING RULES...................................................................................................................................24

Duke Energy Proprietary – Internal Use OnlyPage 3 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
 6.3. STAGING TABLES...........................................................................................................................................24

6.4. CROSS REFERENCE TABLES..............................................................................................................................25

6.5. LEGACY TO SAP KEYS.....................................................................................................................................25

7. TECHNICAL REQUIREMENTS - LOAD......................................................................................26

7.1. LOAD APPROACH...........................................................................................................................................26

7.2. RELEVANT TABLES TO LOAD INTO.....................................................................................................................26

7.3. LOAD PROGRAM STRUCTURES.........................................................................................................................26

7.4. LOAD DEPENDENCIES.....................................................................................................................................27

8. UNIT TEST SCENARIOS............................................................................................................28

8.1. UNIT TEST CONDITIONS..................................................................................................................................28

8.2. APPLICABLE GO-LIVE CONVERSION CONTROLS....................................................................................................28

Duke Energy Proprietary – Internal Use OnlyPage 4 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
1. Executive Summary

RICEFW Overview
RICEFW Name CONV_TMD_Connection_Object
RICEFW Description Convert Connection Objects
RICEFW Complexity Medium
Data Object Definition Connection Objects are the starting point for the SAP
IS-U technical master data “house”. They represent a
building where service is provided independent of
how many services/meters/accounts are at the
building (i.e. an apartment building would represent 1
Connection Object). Generally, a Connection Object
can be imagined as a street address number without
any extensions such as floor, apt, unit, etc.

Connection Objects are the parent to Premises.

While most buildings in a service territory are
residential homes, and therefore maintain a 1 to 1
relationship between Connection Object and
Premise, several types of structures will have a one
to many relationship between CO and Premise (i.e.
office buildings (where a floor could be a Premise),
apartment complexes (where apartments could be a
Premise) etc…).

Scope and Extract

Extract for Record Creation CIS (CSS, CBIS, CIM, CMS)
Other source systems needed GIS, OneSource
Scope Statement Create connection objects for every serviced premise
in Duke's jurisdiction. Since the legacy systems
(other than CSS) do not have a "building" entity, we
will need to group premises with matching house
address together to form connection objects during
conversion.
Estimate of Record Volume 8 mil

Duke Energy Proprietary – Internal Use OnlyPage 5 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
 Load Program
Target System SAP ISU
Load Program Type EMIGALL
Load Program Name CONNOBJ
Target Tables EHAUISU, IFLOT, ILOA, ADRC
Pre-Requisite Object NONE – CONNOBJ is the first object in the TMD
stream

Functional Owner
Program Release Release 5
Functional Team Device Management
Functional Design/Process 2.1 - Create/Maintain Technical Master Data
BPO

Duke Energy Proprietary – Internal Use OnlyPage 6 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
 2. Source System Analysis

2.1. Front-end (Legacy System Screens)

The concept of the Connection Object/Premise relationship does not exist in CMS,
CBIS, CIM(it exists in CSS). Rather, there is simply an inventory of Service Addresses
(only these will be considered for CONNOBJ and PREMISE conversion).

Because the concept of the Connection Object/Premise relationship does not exist in
any of the legacy systems (excluding CSS), logic will be developed to group multiple
Service Address Locations into individual Connection Objects, if applicable. This logical
grouping of multiple Locations into a single Connection Object is referred to as Premise
(or Service Address) Consolidation. The logic will be applied across the three legacy
systems (Identical/Eligible Addresses from all systems will be combined into one
Connection Object where possible).

The following illustration is an example of the end result of a Service Address

Consolidation effort to support Connection Object and Premise creation in SAP. Notice
that we are grouping multiple Locations into a single SAP Connection Object if the
House Number, Street, City, State and Zip are the same.

SAP
House Street Apartment Connection
Legacy System Number Name City State Zip Floor Suite # Object SAP Premise

The following below is a CBIS example of the current legacy system screen for the connection
object

Duke Energy Proprietary – Internal Use OnlyPage 7 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
The following below is a CSS example of the current legacy system screen for the connection
object

The following below is a CMS example of the current legacy system screen for the connection
object

Duke Energy Proprietary – Internal Use OnlyPage 8 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
The following below is a CIM example of the current legacy system screen for the connection
object

2.2. Back-end (Legacy System Tables)

Legacy System Table Usage Keys

Duke Energy Proprietary – Internal Use OnlyPage 9 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
Duke Energy Proprietary – Internal Use OnlyPage 10 of 24
<< SharePoint link pending >>
Accenture Confidential and Proprietary
3. Target System Analysis

3.1. Front-end (SAP System Screens)

 A Connection Object is defined in SAP IS-U as “A link between installation and

postal regional structure.”
 The SAP documentation also states “This is usually a building, but can also be a
piece of property or other facility, such as a fountain or construction site. The
connection object corresponds to the functional location in the Plant Maintenance
(PM) application component.”
 Connection Objects are most commonly thought of as “Buildings” potentially
containing multiple Premises (apartments/suites/etc…).
 All Connection Objects that pass through cleansing and consolidation rules will
be loaded into SAP IS-U via the EMIGALL transaction code.

Connection Objects are displayed via t-code ES57.

<SCREENSHOT FROM SAP FOR CONNOBJ>

. Main fields include:

 Street
 House Number
 Postal Code
 City
 Country
 State
 Time Zone
 Tax Jurisdiction Code

3.2. Back-end (SAP System Tables)

Table Description Usage

ADRC Address table Contains the service address
for each connection object

Duke Energy Proprietary – Internal Use OnlyPage 11 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
 IFLOT Functional Location (Table)
ILOA PM Object Location and Account
Assignment
EHAUISU Connection Object Header

Duke Energy Proprietary – Internal Use OnlyPage 12 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
4. Conversion Scope & Considerations

4.1. Scope

# Selection Rule Include Reason Estimate

or Volume
Exclude
1 Create a connection Include
object for every inscope
premise (see PREMISE
design document).
Apply consolidation
rules as needed.

4.2. Conversion Requirements and Considerations

# Conversion Requirement Business Impact

General
1 Convert a Connection Object for every unique None
physical building or service address that Duke
Energy is servicing.
2 CSS has a “building” data entity already. Convert None
Connection Objects as a 1-to-1 from buildings.
3 CMS/CBIS/CIM do not have a “building” data entity. None
Apply consolidation rules to recognize premises that
share the same service address and create one
single connection object for each grouping. “Same
service address” is defined as premises having the
same house number, street, first 5 digits of zip code,
city, and region. Data cleansing will be done to
streamline this consolidation process.
4 Convert a Connection Object for lighting and May change how we count and

Duke Energy Proprietary – Internal Use OnlyPage 13 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
 unmetered installations, even if they do not have a reconcile legacy vs SAP premise
single physical premise location (E.g. a municipality counts.
of traffic signals). At a minimum we can convert 1
SAP Connection Object for every individual legacy
unmetered premise, however if one legacy premise
spans across multiple SAP tax jurisdiction codes
then we will need to split and create multiple SAP
Connection Objects accordingly.
5 Convert a Connection Object for directional None
addresses, even if they do not have a full traditional
street address.
6 SAP will auto-generate a new Connection Object None
number. No legacy identifiers will be retained.
7 Some fields will require making a SAP real-time None
function call to GIS The function takes in a service
address and returns the desired values for SAP. To
streamline the conversion process and reduce job
times, we will not invoke the function for each
premise individually. Instead, the GIS team will write
the data into the Hub (by premise) as a pre-cutover
activity and we will lookup these data attributes from
the Hub.
8 The Tax Jurisdiction field will require making a None
function call to OneSource. The function takes in a
specific set of address-related parameters, and
returns the desired tax jurisdiction code which we will
convert into SAP. To streamline the conversion
process and reduce job times, we will not invoke the
function for each premise individually. Instead the
Duke Tax Department Team will provide a full file as
a pre-cutover activity, and this file will be used in the
automated conversion process.
9 Real-time DQM (data quality management) will be None
turned off in SAP during the conversion loads, as it
will significantly slow down the conversion runtimes
otherwise.
10 Data cleansing should be done on the legacy service None
addresses to standardize and conform them to a
common format.
For target structure EHAUISU
11 Subdivision – Convert the subdivision if available. None
12 Lot Number – Convert the lot number if available. None
13 School District Code – Convert the school district None
code from OneSource.
14 Electric Area – Convert the Electric Area code None
(Operation Center Boundaries) from GIS.
15 Electric Sub Area – Convert the Electric (Distribution) None
Sub Area from GIS.

Duke Energy Proprietary – Internal Use OnlyPage 14 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
 16 Gas Area – Convert the Gas Area from GIS. None
17 Gas Sub Area – Convert the Gas Sub Area from None
GIS.
18 Vegetation Area – Convert the Vegetation Area None
(Distribution Right of Way) from GIS.
19 Gas Vegetation Area – Convert the Vegetation Sub None
Area (Gas Right of Way) from GIS.
20 In/Out City Limits – Convert the In/Out City indicator None
flag from OneSource.
26 Convert the County Code. None
27 Convert the Services Offered based on the types of Noen
services this connection object offers (E, G, or B for
both).
28 Convert the Company Code based on the numeric None
version of its jurisdiction (e.g. 2000 for DEC, 4000 for
DEO).

For target structure ADRC

21 Every Connection Object must have a service None
address converted, which includes these fields:

- House Number
- Street Name (which contains Prefix, Street
Name, Suffix, Direction all concatenated
together. For example 123 Main St NW).
- Zip Code
- City
- State Code
- County Code
- Country Code

22 Connection Objects created for Directional None

Addresses and Unmetered Installations may miss
some of the service address components (for
example, directional address may not have a House
Number).
23 Every Connection Object must have a Zip+4 None
populated as it is a mandatory value for the Tax
Jurisdiction determination process. Data
cleansing/enrichment needs to be done if the legacy
system is missing the +4 code.
24 Time Zone – All connection objects will have the time None
zone defaulted to ‘EST’, even for ones physically
residing in a CST district. This is because all
premises will be billed in EST, regardless of service
territory.
25 Tax Jurisdiction Code – All connection objects must None
have a Tax Jurisdiction Code populated. This is
Duke Energy Proprietary – Internal Use OnlyPage 15 of 24
<< SharePoint link pending >>
Accenture Confidential and Proprietary
 converted by passing location parameters to
OneSource and having OneSource return a tax
jurisdiction result.

* See Section 6.2 for detailed field by field technical mapping rules.

4.3. Data Scenarios

# Scenario Specific Items to Check fo

1 Verify that the attributes of the Find a single-premise house
connection object are populated
correctly as per data mapping rules.

2 Ensure that any consolidation that Find a building with multiple premises
occurred adheres to the consolidation inside, all with identical street
rules (in this case: one connection object addresses. 
should be created and all proper
Premises exist under the appropriate
Connection Object).

3 Connection Object with a Directional

Address
4 Connection Object with an Unmetered
Installation

4.4. Manual Conversion

# Manual Reason Point of Contact Estimate

Duke Energy Proprietary – Internal Use OnlyPage 16 of 24
<< SharePoint link pending >>
Accenture Confidential and Proprietary
 Conversion Item Volume
1 MAC (Major Account The way Unsure
Customer) – manually each
populated after jurisdiction
deployment classifies,
stores, and
manages
MAC is
inconsistent.

4.5. Data Cleansing Items

# Data Cleansing How to Point of Contact Estimate

Item cleanse Volume
1 Legacy Systems Create logic
(except CSS) do not to have a
have the concept of a Premise
Connection Object. As Consolidation
such, an effort to Table
consolidate individual
addresses into an
individual Connection
Object will likely be
necessary. Data
cleansing may be
required to standardize
specific address fields
in order to
systematically and
accurately consolidate.
2 Zip +4 is not tracked for
some premises (some
legacy systems don’t
have a field to store the
full zip+4).
3 Data Cleansing Team
will cleanse and
standardize all legacy
service addresses into
a common format, and
provide that cleansed
address file to the
Conversion Team to

Duke Energy Proprietary – Internal Use OnlyPage 17 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
 use.

4.6. Open Items

# Open Item Point of Contact Status

Duke Energy Proprietary – Internal Use OnlyPage 18 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
5. Technical Requirements - Extract

5.1. Extract Approach

Source System Database Extract Approach Point of

Type Contact

5.2. Relevant Tables to Extract From

Source Table Relevance to conversion

System program

5.3. SQL Selection Rule

The primary record creation rule is to select all connection objects:

Duke Energy Proprietary – Internal Use OnlyPage 19 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
6. Technical Requirements - Transform

6.1. Transform Approach

Transform Tool Staging Output

SAP Data Services (aka HANA staging Flat file for SAP EMIGALL load
BODS) database – CH1 program

6.2. Data Mapping Rules

Detailed technical field rules in the attached data map:

6.3. Staging Tables

Staging Table Usage

INSCOPE_PREM Staging table that determines which
premises are in scope for conversion and
how to group them into Connection
Objects.
CONNOBJ_EHAUD_STG2 Screen Fields: Connection Object
CONNOBJ_ADDR_DATA_STG2 Address Data for Connection Objects
CONNOBJ_STG3 A merge of all Stg2 tables with fields
concatenated and reformatted for the
SAP output file

Duke Energy Proprietary – Internal Use OnlyPage 20 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
6.4. Cross Reference Tables

LKP Table Usage Functional Point of Contact

6.5. Legacy to SAP Keys

Legacy Identifier SAP Identifier Comments

Duke Energy Proprietary – Internal Use OnlyPage 21 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
7. Technical Requirements - Load

7.1. Load Approach

Method of Load Load Program Description

Name
EMIGALL CONNOBJ We will be loading Connection
Objects into SAP IS-U via the
EMIGALL object CONNOBJ.

7.2. Relevant Tables to Load Into

Table Usage
EHAUISU Connection Object header information

ADRC Overall address table, which includes the Connection Object

service addresses.
IFLOT Functional Location table, which includes Connection
Objects (and Device Locations).

7.3. Load Program Structures

Target Structure Structure description Usage

(e.g. header or repeating-
structure)
Header – maps directly into SAP
EHAUD Header
EHAUISU, IFLOT, and ILOA tables.

Duke Energy Proprietary – Internal Use OnlyPage 22 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
 Target Structure Structure description Usage
(e.g. header or repeating-
structure)
Address – maps directly into SAP
ADDR_DATA Header
ADRC table.

7.4. Load Dependencies

Pre-Requisite Description
Object
NONE Connection Object is the starting point of all TMD and
has no pre-requisites.

Duke Energy Proprietary – Internal Use OnlyPage 23 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary
8. Unit Test Scenarios

8.1. Unit Test Conditions

# Test Scenario Specific Items to Check fo

1 Verify that the attributes of the Find a single-premise house
connection object are populated
correctly as per data mapping rules.

2 Ensure that any consolidation that Find a building with multiple premises
occurred adheres to the consolidation inside, all with identical street
rules (in this case: one connection addresses. 
object should be created and all proper
Premises exist under the appropriate
Connection Object).

3
4

8.2. Applicable Go-Live Conversion Controls

# Control Type Description BPO Owner

1 Completeness CONNOBJ ADDR_DATA –
compares the expected vs
actual row count of service
addresses.
2 Completeness CONNOBJ EHAUD –
compares the expected vs
actual row count of connection
objects.

Duke Energy Proprietary – Internal Use OnlyPage 24 of 24

<< SharePoint link pending >>
Accenture Confidential and Proprietary