process and data- exchange solution for utilities and data-exchange solution for utilities white...
TRANSCRIPT
Process and Data-
Exchange Solution for
Utilities
White Paper
May 2012
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 2 of 21
Table of Contents
Version .................................................................................................................................................... 3
Glossary of Terms.................................................................................................................................... 3
Acknowledgements ................................................................................................................................. 3
Target Audience ...................................................................................................................................... 4
Executive Summary ................................................................................................................................. 5
Background ......................................................................................................................................... 5
General Issues for market communication ......................................................................................... 5
SAP’s Answer ....................................................................................................................................... 5
Current Solution Overview ..................................................................................................................... 6
Architecture: Process and Data-Exchange Framework ....................................................................... 8
Components: Process and Data-Exchange Framework ...................................................................... 9
Evolution ............................................................................................................................................... 12
Flexibility ............................................................................................................................................... 13
Customizing ....................................................................................................................................... 13
Business Add-Ins ............................................................................................................................... 14
Benefits ................................................................................................................................................. 17
Implementation Steps ........................................................................................................................... 17
Future Enhancements ........................................................................................................................... 18
Contact Details ...................................................................................................................................... 19
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 3 of 21
Version
Author Date Version Comment
Mohan Gupta 21.05.2012 0.1 Draft Initial Draft
Mohan Gupta 22.05.2012 0.2 Draft Update following Peer
review
Mike Prentice 07.06.2012 0.3 Draft Update following Peer
review
Mohan Gupta 03.07.2012 0.5 Draft Update following
review
Glossary of Terms
Terms Description
RCS This is a “Repeatable Custom Solution” that has been developed previously
and is intended as the foundation to support unique business requirements
EAI This is the “Enterprise Application Interface”, or “Enterprise Application
Integration”. This is the use of one or more software components to enable
communication across the architectural landscape. Ie SAP PI
PI This is the EAI component of SAP netweaver. “Process Integration (PI)
BPEM This is a tool for managing exceptions. The Business Process Exception
Management (BPEM) tool
CDP A Custom Development Program (CDP) is a unique custom solution tailored
for a specific customers requirements.
Acknowledgements
Author Document
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 4 of 21
SAP
Custom
Developm
ent
IDEX Infrastructure ‘High Level Solution Proposal ‘
https://documents.wdf.sap.corp/share/page/site/IDXPF/documentlibrary#filter=path%
7C/Documentation&page=1
Target Audience
This document is intended for the following audience:
Consultants
Business Analysts
Technical Architects
Sales
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 5 of 21
Executive Summary
This White Paper describes current SAP solution: ‘Process and Data-Exchange for Utilities’,
its implementation approach based on generic requirements for Utilities Energy industry
and evolution of the solution in its current form based on past projects.
Background
In many countries, the utilities industry is experiencing massive transformation due to
deregulation. Deregulation has resulted in incumbent utility companies becoming separate
independent entities covering only parts of the total value chain from power generation
through distribution to end-user sales and service. This transformation has significant
impact both in terms of managing business processes for each independent entity and also
exchange of data across companies
General Issues for market communication
Process Logic distributed across several entities
Basic Process infrastructure needed to build, execute and monitor end-to-end process
Inbound/Outbound message communication rules need to be transparent and flexible
Robust change mechanism for adjustments needed in case of regulatory changes
Need for standardized Error handling and manual data correction
SAP’s Answer
SAP ‘Process and Data-Exchange for Utilities’ solution provides mechanism of market
communication for Intercompany processes in deregulated utilities markets which includes:
Market format implementation
Market Process modelling and choreography that can result in creation/change of
master/transaction data and exchange of information with other market
participants.
Exception management
Process Monitoring cockpit
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 6 of 21
Current Solution Overview
An implementation of SAP ‘Process and Data exchange’ solution consists of following:-
Installation of SAP Custom Development RCS solution: ‘Process and Data Exchange
Framework’
(If exists) Installation of ‘Country specific’ SAP Custom Development RCS solution
with generic business content
Implementation of individual customer specific business requirements to make the
solution complete and operate in desired manner
This flexible, configurable approach allows you to react to both ‘must have’ and ‘value add’
requirements and enables a customer-specific implementation.
Figure 1: Solution Installation base hierarchy
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 7 of 21
The following diagram shows high level interaction across various technical components for
Message Exchange (E2E)
ISU
Deregulation Process Execution
Me
ssa
ge
Pro
ce
sso
r
PI
SAP Converter
Market Partner
Data Exchange
Message Processor
IDocs
Data Exchange
items
Master Data
Service Processor
DE UK
DE UK
3rd Party
Converter
3rd Party
Converter
R
DE UK
DE UK
Idoc
Processor
Register CoS
Master Data Change
Asset work processes
...
Process Data
Market Message
as SOA Service
Market Message
as IDoc
Process Data Exchange
Task & internal view on
message data
Figure 2: Message Exchange (E2E) view
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 8 of 21
Architecture: Process and Data-Exchange Framework
The process and data-exchange framework for utilities is a generic software solution to
manage intercompany data-exchange processes as required by energy deregulation for the
energy supply of metered metering points and unmetered sites and the corresponding
market communication.
For communication between solution in the ISU system and the EAI system, IDocs or web-
services can be used.
The following picture provides an overview of the architectural elements of the Process and
Data-Exchange infrastructure
Figure 3: Architectural view of the Process and Data-Exchange Framework for Utilities
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 9 of 21
The light yellow and green coloured boxes are elements of the Process and Data
Exchange Framework
The light yellow boxes in particular describe those elements of the Process and Data-Exchange Framework which most likely could be affected by regulatory or customer imposed changes to the message or process flow.
The dark gray box on the left represents the EAI (Enterprise Application Interface) system, for example SAP PI. This system is, among others, responsible for the technical message handling to the different market partners
The light gray boxes reflect the standard IDE Data Exchange framework which will
still be used in the Process and Data-Exchange Framework Solution Process and Data-Exchange Framework for Utilities
Release 1.0
SAP Enhancement Package Enhancement Packages 4,5 and 6
Based On SAP Utilities
BI Content-Release Not applicable
Components: Process and Data-Exchange Framework
Main components are:
Process Configuration Layer
A process is by definition a directed (oriented) graph consisting of nodes and arrows. The set
of nodes is represented by the set of elementary process steps. Each process consists of a
number of process steps which correspond to market messages or activities which have
occurred within the processes (and which should trigger a further processing). Process steps
can be executed automatically by the Process Engine when determining the next possible
steps or if it’s a manual step then it will be executed externally without Process engine.
Process arrows link all process steps of a process such that the process becomes an oriented
graph. Process arrows will also link the process step of one process step of another process
for inter process linkage.
Process Execution Layer
When the Process Engine is called it will check for processes that are ready to be processed and triggers them. This layer also contains the process instances represented by their associated configuration layer (process classes and their associated process steps
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 10 of 21
represented by process step classes). Once a process is triggered by the Process Engine it will determine and execute all process steps that are ready to be processed. Per each (successfully) executed process step the process instance will again determine and execute all process steps that are ready to be processed. Thus the process instances will traverse the process graph until all process steps currently available for processing have been executed
Process UI Layer
The standard Switch Document has been enhanced to become more generic Process
Document. The user can see:
Current status of the overall process
Relevant information depending on type of process
All activities
Messages that have been sent and received
Data content of the messages depending on type of message
Errors that have occurred and exceptions that have been created
Process steps which have been executed and their individual status
Linked processes either as parent/link or associated link.
Check Framework
The check framework is an enhancement of the standard SAP Intercompany Data Exchange
(IDE)check framework with following additional features:
Definition and allocation of check groups to check applications, allowing for adding
and deleting checks through customizing
Ability to be called from anywhere
Flexible interface definition allowing the implementation Project to define their own
checks
Period Framework
This is a framework to ensure that all scheduled process steps are carried out at the appropriate time. Since no SAP Business Workflow will be used, a new deadline monitoring report will be made available. The definition of deadlines is based on the standard SAP/IDE period management
Exception Framework
Any kind of errors or exceptions will be handled through the standard BPEM tool. This can also be called from other systems, like SAP PI. For easier use the framework provides additional functionality:
Customizing to define exception codes and the corresponding BPEM case category
Default implementation of a BADI reading and interpreting the customizing and for creation of a BPEM case
Predefined exception resolution possibilities (handling alternatives), including
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 11 of 21
Reprocessing of process step Set inbound message to obsolete and act as if it has not been received;
continue waiting for the same message Resend outbound message again with new message data collection Resend outbound message again as is (technical resend) End processing of current process
Intercompany Data Exchange (IDE) Layer
This component describes the processing of sending and receiving messages. It is based on the standard IDE Infrastructure with an additional Message Mapping Framework:
Adding predefined metadata structures
Predefined architecture of OO objects (class hierarchy) for uniform and easy to maintain development of required mappings
For further details on architecture, refer to ‘High Level Solution Proposal’ document for IDEX infrastructure from SAP Custom Development. You can find contact persons in Contact details section.
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 12 of 21
Evolution
‘Process and Data-Exchange Solution’ in its current form (RCS: Framework + RCS: Country
specific solution (if exists) + Customer specific implementation) is a result of evolution
through various IDEX Custom Development projects in Europe/Asia over past 6 years.
The significant improvements up to now are:
Workflow replaced with efficient Process modelling tool
Central Process Engine with segregation of process steps into basic categories and
corresponding methods/interfaces
Improved flexible UI interface
The following chart shows evolution of the solution from one Custom Development Project
to next. This chart only shows CDPs which had significant impact on development of
‘Process and Data-Exchange Solution’ as it is now.
Figure 4: Evolution chart
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 13 of 21
Evolutionary Benefits
This section highlights those areas of change through out the lifecycle of the IDEX solution and
explains how the change has benefited the solution.
Area Benefit of Change
Workflow Initially the IDEX solution was a workflow based solution, over the
lifetime of the solution the use of SAP standard workflow was reduced
to a limited use for the npower solution and finally removed with the
Iberdrola Scottish Power implementation.
The benefit this has brought is that whilst it is possible to have a specific
version of a process all changes made to the configuration of that
process are actioned in real time meaning that all in flight processes are
working on the same platform. With the SAP workflow approach it was
likely that industry lead processes were not working to the same
industry or business current requirement.
Switch Document The first IDEX solutions centred on Data Exchange to support switching
processes (Customer Loss and Gain). With the npower solution the
switch document was further enhanced to support other
Supplier/Retailer industry processes such as Device exchange, Device
inspections etc. This gave the first UI representation of a business
industry process in an easy to read step format. With the Iberdrola
Scottish Power implementation this was further enhanced to support
other market roles such as Data Collector and Meter Asset Manager.
Flexibility
Customizing
The following list provides a short overview of the available customizing options:
Process Configuration/ Monitoring
Process Configuration Scenario
Period type configuration for Hour/Minute/Second
Process Monitoring configuration
Check Framework configuration
Configuration of Response Codes
Master data configuration with corresponding Outcomes
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 14 of 21
Inbound/Outbound Message Handling Configuration
Assign Parser Class for Inbound Message Processing
Assign Parser Class for Outbound Message Processing
IDoc Mapping Configuration
Transformation between External and Internal codes
Map External Market roles to Service types
Exception Code configuration
Tools
Configure Process Status
Configure Process Step Status
Define Scenario ID
For further configuration and customizing information, see the Process and Data Exchange
Framework for Utilities Configuration Guide in the SAP Service Marketplace at
http://service.sap.com/instguides
Business Add-Ins
The following table provides short overview of the available BAdIs:
BAdI Description BAdI Interface Method
BAdI: Exception
Framework
/IDXPF/IF_BADI_EXCEPTION CLOSE_EXCEPTION
CREATE_EXCEPTION
REASSIGN_STEP
REPEAT_STEP
REPROCESS_STEP
BAdI: Data Access
(/IDXPF/)
BAdI containing all
/IDXPF/ (that is,
Framework) data access
methods.
/IDXPF/IF_BADI_DATA_ACCESS GET_ADDRESS
GET_CUSTOMER_DETAIL
GET_METER_DETAILS
GET_METER_READING
SET_ADDRESS
SET_CUSTOMER_DETAIL
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 15 of 21
SET_METER_DETAILS
SET_METER_READING
VALIDATE_ADDRESS
GET_AGENT_DETAILS
GET_CONSUMPTION_DATA
GET_GROUP_MPXN
GET_POD_TECH_DATA
GET_SITE_OCCUPIED_STATUS
SET_CONSUMPTION_DATA
SET_INSPECTION_DATE
SET_POD_TECH_DATA
GET_ACTION_DETAILS
BAdI: Process Document
Data Enhancements
/IDXPF/IF_BADI_PROCESS_DOC
_DB
SELECT_MSG_MASS
SELECT_PDOC_MASS
UPDATE_DB_PROCESS_DATA
UPDATE_DB_PROCESS_STEP_
DATA
BAdI: Process
Filter based BAdI, multiple
implementations possible
/IDXPF /IF_BADI_PROCESS
BAdI: Process Step
Filter based BAdI, multiple
implementations possible
/IDXPF/IF_BADI_PROCESS_STEP
BAdI: Process Log
Framework
Filter based BAdI, multiple
implementations possible
/IDXPF /IF_BADI_PROCESS_LOG
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 16 of 21
BAdI: Process Specific
PDoc Display
Filter based BAdI, multiple
implementations possible
/IDXPF/IF_BADI_PDOC_DISPLAY
BAdI: CRM Mapping
Framework
/IDXPF /IF_BADI_CRM_PDOC MAP_CRM_DATA_TO_PROCES
S
MAP_PDOC_DISP_TO_CRM_D
ATA
MAP_PROCESS_TO_CRM_DAT
A
BAdI: Check Framework
/IDXPF /IF_BADI_CHECK DEFINE_CHECK_GROUP_RESU
LT
DETERMINE_CHECK_EXECUTI
ON_MODE
DETERMINE_MTD_DATA_SOU
RCE
DETERMINE_OVERRULE_CHEC
K
PREPARE_MTD_DATA
BAdI: Further Utility
Methods
/IDXPF/IF_BADI_UTILITY GET_PROCESS_REF_FROM_EX
T
BAdI: Message Processing /IDXPF/IF_BADI_MSG_PROCESSI
NG
ADJUST_IDOC_DATA
DET_BULK_PROCESSING
DET_UNIQUE_PROCESS_FOR_
MSG
HANDLE_BULK_PROCESSING
HANDLE_NONUNIQUE_PROCE
SS
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 17 of 21
For more information about BAdI enhancements and the default implementation, see the
documentation for individual activities in Customizing for Process and Data-Exchange
Framework for Utilities under System Preparation-> Create Enhancements
Benefits
The benefits of ‘Process and Data-Exchange solution’ are the following:
Same modelling for all kinds of processes within the Framework
Centralised and easy to maintain inbound and outbound processing
Future enhancements to delivered processes will be based on configuration and therefore
relatively easy to implement
High performance on Process Execution
Minimal impact of regulatory changes since the different layers are independent from each
other
Proven concepts derived from 12+ projects in Europe and worldwide
Implementation Steps
Following steps are necessary to implement the solution based on business specific needs:
1. Setup a SAP for Utilities Solution
2. Install the SAP RCS: ‘Process and Data-Exchange Framework’ solution
3. Configure standard SAP IS-U/IDE
4. Configure the ‘Process and Data-Exchange’ solution customizing as per business
requirements
5. Implement the BAdIs according to business requirements
6. Optional: Data migration from Legacy system
7. Go-Live
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 18 of 21
Future Enhancements
As detailed in Evolution how the solution has gradually evolved in last few years to its
current state, further enhancements are still on-going and there are new functionalities
lined up for future releases. Some of the key features in various phases (conception, design,
development) are highlighted below:
Graphical representation of current process state in the Process Document UI
‘Edit mode’ in Process Document UI
Simulation of Process step and Check execution in Process Document UI
Advanced ‘Authorization objects’ for Process document display/change and Process
execution
Web Service enablement (both synchronous and asynchronous) and integration
Non-disruptive delivery of configuration changes/enhancements into customer
systems
Testing Cockpit (Regression test reports + Analytical reports)
Disclaimer: Above features are not guaranteed to be part of future releases.
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 19 of 21
Contact Details
Name Organisation Email ID
Mike Prentice SAP Consulting UK [email protected]
Mohan Gupta SAP Consulting UK [email protected]
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 20 of 21
DISCLAIMER
© 2012 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
White Paper
© 2011 SAP AG Dietmar-Hopp-Allee 16
D-69190 Walldorf Page 21 of 21
These materials are subject to change without notice. These materials are provided by SAP AG and
its affiliated companies ("SAP Group") for informational purposes only, without representation or
warranty of any kind, and
SAP Group shall not be liable for errors or omissions with respect to the materials. The only
warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.