Intercompany data exchange for Swiss electric and … data exchange for Swiss electric and ... The...

Application Help (English)Document version: 1.1 – 2015-10-16

Intercompany data exchange for Swiss electric and gas utilities 1.0

CUSTOMER

Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. You can find the

latest version at the following location: support.sap.com/swdc

The following table provides an overview of the most important document changes.

Table 1

Version Date Description

1.1 2015-10-16 Reviewed for SP01 (no major changes)

1.0 2015-09-30 Initial Release

2

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved.

Intercompany data exchange for Swiss electric and gas utilities 1.0Document History

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc

Content

1 Intercompany data exchange for Swiss electric and gas utilities . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Main Menu and Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Metered Data Exchange Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1 Exchange of Validated Metered Data (E66) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.2 Exchange of Aggregated Metered Data (E31) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.3 Sending Assignment List (C02) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.4 Reports for Metering Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Trigger Metering Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Monitor Metering Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Switching Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.1 Change of Supplier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2 Move-In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.3 Move-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.4 End of Supply (Drop) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.5 Basic Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.6 Invalidation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.7 Cancellation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.8 Reports for Switching Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Configure Data Exchange Processes for Service Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

5 Operations Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.1 Monitor Process Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.2 Schedule Background Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.3 Monitor Data Exchange Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.4 Monitor IDocs (ALE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Intercompany data exchange for Swiss electric and gas utilities 1.0Content

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.

All rights reserved. 3

4

CUSTOMER© Copyright 2015 SAP SE or an SAP affiliate company.All rights reserved. Intercompany data exchange for Swiss electric and gas utilities 1.0

1 Intercompany data exchange for Swiss electric and gas utilities

Product Information

Table 2

Product intercompany data exchange for Swiss electric and gas utilities

Release 1.0 SP01

Based On SAP ERP 6.0 EHP6 or higher (with SAP IS-U)

process and data-exchange framework for utilities

Documentation Published October 2015

Use

The deregulation of energy markets has led to dramatic changes in utility companies' customer-oriented business processes. In the utilities industry, it is common for business processes to cross multiple systems within an organization and across companies with various market participants.

For example, when a residential customer decides to change the energy supplier, the agent at the new supplier company would enter the information into the SAP system and run a change of supplier (CoS) process. This creates various communications across multiple systems within the new supplier company. It also initiates communications with an intermediary energy distribution provider and with the current supplier company which the customer is leaving, in order to ensure that the change happens smoothly.

This entire process and the formats for data exchange are defined by the legal authorities, such as Swiss Federal Office of Energy (SFOE) in the case of the Swiss utilities industry and are binding for all market participants.

The intercompany data exchange for Swiss electric and gas utilities is an SAP application which enables the automatic data exchanges among the market participants in the Swiss deregulated energy market to ensure the reliable supply of energy to customers and it is also fully enhanced to comply with the requirements of the Swiss Federal Electricity Supply Act ( “StromVG” ).

Furthermore, the intercompany data exchange for Swiss electric and gas utilities application has been enhanced technically to be fully compatible with the SAP IS-U Intercompany Data Exchange (IDE) infrastructure add-on solution process and data-exchange framework for utilities in which data exchange processes are controlled and monitored based on the process documents with processes and their steps, as compared to means of workflow as the previously used technology base.

Integration

As depicted in the diagram below, the intercompany data exchange for Swiss electric and gas utilities 1.0 application is based on and fully integrated with:

● SAP ERP 6.0 EHP6 or higher (with SAP IS-U)

Intercompany data exchange for Swiss electric and gas utilities 1.0Intercompany data exchange for Swiss electric and gas utilities



● Intercompany Data Exchange (SAP IS-U-IDE) infrastructure add-on solution process and data-exchange framework for utilities 1.0

Figure 1: Integration Overview for intercompany data exchange for Swiss electric and gas utilities

As for the communication technology side of the integration, data is exchanged using intermediate documents (IDocs) in the SAP for Utilities IDE framework (SAP IS-U IDE). If you want to send data to another market participant, an IDoc (in the format predefined in the data exchange definition) is created from the data. If a third party system/client is involved, you can send the data using the SAP NetWeaver Process Integration (SAP PI). The SAP PI can create an XML file from the IDoc that can be sent to the appropriate recipient via an e-mail. It can also receive an XML file from another market participant with a third party system/client and convert it to an IDoc so that it can be processed as a data exchange process in SAP IS-U.

CautionNo SAP PI content is included in the scope of intercompany data exchange for Swiss electric and gas utilities . In addition, the application generally works with or without SAP CRM integration. However, any development or adaptation of SAP PI or SAP CRM is out of scope for the intercompany data exchange for Swiss electric and gas utilities application, but it must be realized as part of the implementation project as required.

Prerequisites

Make sure that the following solutions have been installed and the required configuration and Customizing settings have been completed before running the intercompany data exchange for Swiss electric and gas utilities application:

● SAP ERP 6.0 EHP6 or higher (with SAP IS-U)

Choose SAP Customizing Implementation Guide (transaction SPRO ) under SAP Utilities

6



● Intercompany Data Exchange

Choose SAP Customizing Implementation Guide (transaction SPRO ) under SAP Utilities Intercompany Data Exchange

● process and data-exchange framework for utilities

Choose SAP Customizing Implementation Guide (transaction SPRO ) under SAP Utilities Intercompany Data Exchange Process and Data-Exchange Framework for Utilities

● intercompany data exchange for Swiss electric and gas utilities

Choose SAP Customizing Implementation Guide (transaction SPRO ) under SAP Utilities Intercompany Data Exchange Intercompany Data Exchange for Swiss Electric and Gas Utilities

Features

The table below shows a list of main topics which are explained in the subsequent chapters that also correspond to the main features delivered as part of intercompany data exchange for Swiss electric and gas utilities .

Table 3

Functional Area Topics

Metered Data Exchange Processes [page 11] ● Validated Metered Data (E66) [page 12]

● Aggregated Metered Data (E31) [page 13]

● Assignment List (C02) [page 15]

● Reports for Metering Processes [page 16]

Switching Processes [page 20] ● Change of Supplier [page 21]

● Move-In [page 22]

● Move-Out [page 24]

● End of Supply (Drop) [page 25]

● Basic Supply [page 26]

● Invalidation [page 28]

● Cancellation [page 29]

● Reports for Switching Processes [page 30]

Operations Information [page 33] ● Monitor Process Documents [page 33]

● Schedule Background Jobs [page 35]

● Monitor Data Exchange Tasks [page 35]

● Monitor IDocs (ALE) [page 36]

More Information

For more information, see the following documents:

● SAP Utilities as Part of SAP ERP 6.0 (EHP6 or higher)

See SAP Library for SAP Utilities . Go to SAP Help portal at help.sap.com and choose Enterprise Management SAP ERP (select a relevant release with an EHP number, for example) 6.0 EHP6 SAP Utilities .




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com

● process and data-exchange framework for utilities

See the configuration guide and user guide for process and data-exchange framework for utilities 1.0 . Go to

SAP Support Portal Software Download Center at support.sap.com/swdc and choose Installations and Upgrades Alphabetical List of my Products (index "P") PROCESS/XCHG FRAMWORK UTIL PROCESS/XCHG FRAMWORK UTIL 1.0 Technical Documentation .

● intercompany data exchange for Swiss electric and gas utilities

See the configuration guide for intercompany data exchange for Swiss electric and gas utilities 1.0 . Go to SAP

Support Portal Software Download Center at support.sap.com/swdc and choose Installations and Upgrades Alphabetical List of my Products (index "D") DATA XCHANGE SWISS UTILITY DATA XCHANGE SWISS UTILITY 1.0 Technical Documentation .

8





2 Main Menu and Transactions

To access the SAP Easy Access menu for the intercompany data exchange for Swiss electric and gas utilities application, execute the transaction /IDXCH2/MENU .

The following table lists the menu and the corresponding transaction that are provided under the main menu for intercompany data exchange for Swiss electric and gas utilities .

Table 4

Area Class Menu/Transaction

General Settings Define Business Role Codes ( /IDXCH2/BSR_CD )

Define Business Domains ( /IDXCH2/BUDOM )

Define Document Types ( /IDXCH2/DOCTYP )

Define Business Reason Codes ( /IDXCH2/BUSRSN )

Configure Additional Process Document Data ( /IDXCH2/PDOC_A )

Map Internal Message Codes to Message Types ( /IDXCH2/MTYP_M )

Define Business Sector Codes ( /IDXCH2/SEC_CD )

Assign Business Sector Codes to Divisions ( /IDXCH2/SEC_DV )

Maintain Rejection Codes ( /IDXCH2/REJCOD )

Define Fix Values ( /IDXCH2/FIXVAL )

Metering Processes Trigger Metering Processes ( /IDXCH2/MET_TRIGGER )

Monitor Metering Communications ( /IDXCH2/MET_MON )

General Metering Settings Define Product Details ( /IDXCH2/PROD )

General Metering Settings Define Metering Parameter Values ( /IDXCH2/METPAR )

E66 Process Configuration Data Import Define E66 Profile Roles( /IDXCH2/E66ROL )

E66 Process Configuration Data Export Define In- and Out-

Areas ( /IDXCH2/IOAREA )

E31 Process Configuration Define E31 Profile Roles ( /IDXCH2/E31ROL )

Profile Value Status Map External Profile Value Status to Internal

Status ( /IDXCH2/PVST_I )

Intercompany data exchange for Swiss electric and gas utilities 1.0Main Menu and Transactions



Profile Value Status Map Internal Profile Value Status to External

Status ( /IDXCH2/PVST_E )

Switching Processes Maintain Periods for Switching Process ( /IDXCH2/SWT_PERIOD )

Maintain Switching Supply Scenarios ( /IDXCH2/SWT_SCENARIO )

Maintain Switching Balance Responsible Parties ( /IDXCH2/SWT_BAL_RESP )

Maintain Switching Basic Suppliers ( /IDXCH2/SWT_BAS_SUP )

Maintain Switching Matching Processes ( /IDXCH2/SWT_MATCHING )

Maintain Switching Conflict Processes ( /IDXCH2/SWT_CONFLICT )

Configure DEx Processes for Service Providers ( /IDXCH2/SWT_DATEX )

Monitoring of Process Documents ( /IDXCH2/PDOCMON01 )

More Information

You can access the Customizing for intercompany data exchange for Swiss electric and gas utilities in SAP Customizing Implementation Guide (transaction SPRO ) under SAP Utilities Intercompany Data ExchangeIntercompany Data Exchange for Swiss Electric and Gas Utilities .

You can find more information about the required Customizing and configuration settings for intercompany data exchange for Swiss electric and gas utilities in the following documents:

● Configuration Guide for intercompany data exchange for Swiss electric and gas utilities 1.0

10


Intercompany data exchange for Swiss electric and gas utilities 1.0Main Menu and Transactions

3 Metered Data Exchange Processes

The metered data exchange processes for intercompany data exchange for Swiss electric and gas utilities take place automatically based on the standard Intercompany Data Exchange functions provided within SAP for Utilities (SAP IS-U) as well as on the infrastructure add-on process and data-exchange framework for utilities solution.

As such, basically no actual user operations are involved in the data exchange processes, or in other words in sending of messages, except for error handling and monitoring. Therefore, the most significant part of the metered data exchange processes lies in how to make the relevant Customizing and configuration settings to realize the required automatic data exchanges.

Prerequisites

The installation and configuration settings of the following solutions have been completed:

Table 5

Solution Path to Customizing Structure

SAP ERP 6.0 EHP6 or higher (with SAP IS-U) SAP Customizing Implementation Guide (transaction SPRO )

SAP Utilities

Intercompany Data Exchange (SAP IS-U IDE) SAP Customizing Implementation Guide (transaction SPRO )

SAP Utilities Intercompany Data Exchange

process and data-exchange framework for utilities SAP Customizing Implementation Guide (transaction SPRO )

SAP Utilities Intercompany Data Exchange Process and

Data-Exchange Framework for Utilities

intercompany data exchange for Swiss electric and gas utilities

SAP Customizing Implementation Guide (transaction SPRO )

SAP Utilities Intercompany Data ExchangeIntercompany Data Exchange for Swiss Electric and Gas

Utilities

NoteThe Customizing activities under General Settings and Metering Processes have been completed.

Process

The following metered data exchange processes are supported as part of intercompany data exchange for Swiss electric and gas utilities :

● Validated Metered Data (E66) [page 12]

● Aggregated Metered Data (E31) [page 13]

Intercompany data exchange for Swiss electric and gas utilities 1.0Metered Data Exchange Processes



● Assignment List (C02) [page 15]

More Information

For more information, see the followings:


● Configuration Guide for process and data-exchange framework for utilities 1.0

3.1 Exchange of Validated Metered Data (E66)

Each “E66” message is related to a specific point of delivery (PoD). These messages contain load profiles for consumption and production, or active and reactive energy.

Process

Supported Sub-scenarios for Document Type E66

The E66 scenario further branches to the following sub-scenarios based on the business reason code:

Continuous measured data for energy cost and forecasting

Table 6

Business Reason Code E88 (Billing Energy)

Source DSO

Destination Supplier/Producer

Continuous measured data between grids

Table 7

Business Reason Code E44 (Imbalance Settlement)

Source DSO

Destination Neighboring Distributor

Continuous measured data used for productions (pump and machine)

Table 8

Business Reason Code C12 (Cost rollup/cost rollup from grid operator to the other operators that follow)

Source DSO


12



Continuous measured data for GOR (Sending to Green Certificate Responsible)Table 9

Business Reason Code E0D (Green Certificate Responsible)

Source DSO

Destination GOR (Green Certificate Responsible

Exchanging and Monitoring of Validated Metered Data (E66)

The following two new reports are developed for exchanging and monitoring of Validated Metered Data (E66) :

● Metering Process Trigger Report

You can use this report to send metered data to the associated service providers.

For more information, see Trigger Metering Processes [page 16] .

● Metering Communication Monitor

You can use this report to monitor metered data processes from sending and receiving perspective.

For more information, see Monitor Metering Communications [page 18] .

For more information about monitoring, see the relevant topics under Operations Information [page 33] .

More Information

For more information about related Customizing and configuration settings, see the Configuration Guide for intercompany data exchange for Swiss electric and gas utilities 1.0 .

This document is downloadable from SAP Support Portal Software Download Center at support.sap.com/swdc

under Installations and Upgrades Alphabetical List of my Products (index "D") DATA XCHANGE SWISS UTILITY DATA XCHANGE SWISS UTILITY 1.0 Technical Documentation

3.2 Exchange of Aggregated Metered Data (E31)

Each “E31” message is related to a specific grid or settlement unit. These messages contain aggregated metered data.

Process

Supported Sub-scenarios for Document Type E31

The E31 scenario further branches to the following sub-scenarios based on the business reason code:

Aggregated continuous measured data for grid costsTable 10

Business Reason Code C12 (Cost rollup/cost rollup from grid operator to the other operators that follow)

Source DSO





Destination Upstream System Operators

Aggregated continuous measured data for TGO grid costsTable 11

Business Reason Code C11 (Cost allocation (system service)/cost allocation of the transmission system operator to all distribution system operators)

Source DSO

Destination TSOs

Supplier/generation company aggregations to supplier/generation company - E31 (A)Table 12


Source DSO

Destination Supplier Level

Supplier/generation company to BGR - E31 (B)Table 13


Source DSO

Destination Supplier Level

Aggregations of load profile per balance group to BGR - E31 (C)Table 14


Source DSO

Destination Balance Group Level

Load profiles aggregations per BG to TGO - E31 (D)Table 15


Source DSO


Load profiles aggregations per BG to OSTRAL - E31 (O)Table 16


Source DSO


14



Exchanging and Monitoring of Aggregated Metered Data (E31)

The following two new reports are developed for exchanging and monitoring of Aggregated Metered Data (E31) :





You can use this report to monitor metered data processes from sending and receiving perspective.

For more information, see Monitor Metering Communications [page 18] .


More Information




3.3 Sending Assignment List (C02)

Using “C02” messages, the PoD assignment list is sent from the distributor (DSO) to the relevant supplier or producer.

Process

Supported Scenario for Document Type C02

No business reason code is involved with the document type C02.

Assignment listTable 17

Business Reason Code N/A

Source DSO


Exchanging of Assignment List (C02)

The following new report is developed for exchanging of Assignment List (C02) :








For more information, see the relevant topics under Operations Information [page 33] .

More Information




3.4 Reports for Metering Processes

The following two new reports are developed for the metering processes:



3.4.1 Trigger Metering Processes

You use this report to send metered data to the associated service provider. This metered data exchange process ensures that consistent metered data exists across different service providers.

This report provides the following features:

● One report to support the three document types (E66, E31 and C02)

● Simple and easy-to-use interface that is tailored for the Swiss market

● Resend data option is provided

● Apply all business rules for data selection

● Results are displayed in ALV (SAP List Viewer)

● One report to support both manual sending and batch job sending

● Enabled to trigger the generation of process documents by fully integrated with the process and data-exchange framework for utilities solution

Activities

To access this report, execute the transaction /IDXCH2/MENU to open the SAP Easy Access menu for intercompany data exchange for Swiss electric and gas utilities first, and then choose Metering ProcessesTrigger Metering Processes .

You can also execute the transaction /IDXCH2/MET_TRIGGER to call up this report directly.

Selection

The following selection criteria can be specified, as required:

16




● Metering Process

Select one of the following main metering processes:

○ Validated Metered Data (E66)

○ Aggregated metered Data (E31)

○ Assignment List (C02)

● Cycle Type

Select one of the following metering process cycle types:

○ Daily

○ Monthly

○ Last 5 Days

○ Last 10 Days

NoteThe cycle types displayed on the selection screen depend on the cycle types maintained for the selected metering type in the corresponding Customizing setting. For more information, see the Customizing for Intercompany Data Exchange for Swiss Electric and Gas Utilities under General Settings Map Internal Message Codes to Message Types .

For assignment list (C02), only the cycle type Monthly is applicable. When the Assignment List (C02) is selected in the Metering Process section above, the checkbox for Monthly is automatically selected and it is not editable.

● Selection Criteria

Depending on the metering process selected, the Selection Criteria displayed change dynamically as follows:

○ Process ID

○ Alternative Process ID

○ Own Service Provider

○ Third Party Service Provider

○ Grid (displayed only for E31 and C02)

○ Settlement Unit (displayed only for E31)

○ Point of Delivery ID (displayed only for E66)

○ From Date

○ To Date

○ Resend Data (checkbox) (displayed only for E66 and E31)

○ Message Package Size (displayed only for C02)

Output

When you execute this report, a process reference document is created. The list output displays the following fields:

● PDoc (process document) Creation Status

The value can be either (Newly Created) , (Already Existing) , or (Error) .

● Process-Reference

If a new one is created, it refers to the new process reference. When the document has already existed, in this case, it is the existing process reference.




NoteBy clicking the reference number, you can jump to the Display Process Document screen where end-to-end process document information can be viewed.

More Information

To run this report automatically in batch mode, you need to schedule background jobs. For more information, see Schedule Background Jobs [page 35] under Operations Information [page 33] .

3.4.2 Monitor Metering Communications

You use this report to monitor metered data processes from sending and receiving perspective.

This report provides the following features:

● One report to support the two document types (E66 and E31)

● Simple and easy-to-use interface that is tailored for the Swiss market

● Apply all business rules for data selection

● Results are displayed in ALV (SAP List Viewer)

● Enabled to trigger the generation of process documents by fully integrated with the process and data-exchange framework for utilities solution

Activities

To access this report, execute the transaction /IDXCH2/MENU to open the SAP Easy Access menu for intercompany data exchange for Swiss electric and gas utilities first, and then choose Metering ProcessesMonitor Metering Communications .

You can also execute the transaction /IDXCH2/MET_MON to call up this report directly.

Selection

The following selection criteria can be specified, as required:

● Metering Process

Select one of the following main metering processes:

○ Validated Metered Data (E66)

○ Aggregated metered Data (E31)

● Direction

Select one of the following directions:

○ Receiving Side

○ Sending Side

● Selection Criteria

Depending on the metering process selected, the Selection Criteria displayed change dynamically as follows:

18



○ Process ID




○ Grid (displayed only for E31)

○ Settlement Unit (displayed only for E31)

○ Point of Delivery ID (displayed only for E66)

○ Reference Date From

○ Reference Date To

○ Metering Process Communication Status

Output

When you execute this report, the list output displays the following fields that show the status of each metered data process:

● Metering Sending/Receiving Status

The value can be as follows:

○ On the Sender side:

(Sent/Confirmed) , (Not Sent) , or (Rejected) .

○ On the Receiver side:

(Confirmed) , (Received) , or (Not Received/Rejected)

● Process-Reference

If a new one is created, it refers to the new process reference. When the document has already existed, in this case, it is the existing process reference.

NoteBy clicking the reference number, you can jump to the Display Process Document screen where end-to-end process document information can be viewed.

More Information





4 Switching Processes

The intercompany data exchange for Swiss electric and gas utilities application offers a set of switching processes in order to fulfill the requirements of the Swiss energy market.

Prerequisites

The installation and configuration settings of the following solutions have been completed:

Table 18

Solution Path to Customizing Structure

SAP ERP 6.0 EHP6 or higher (with SAP IS-U) SAP Customizing Implementation Guide (transaction SPRO )

SAP Utilities

Intercompany Data Exchange (SAP IS-U IDE) SAP Customizing Implementation Guide (transaction SPRO )

SAP Utilities Intercompany Data Exchange

process and data-exchange framework for utilities SAP Customizing Implementation Guide (transaction SPRO )

SAP Utilities Intercompany Data Exchange Process and

Data-Exchange Framework for Utilities

intercompany data exchange for Swiss electric and gas utilities

SAP Customizing Implementation Guide (transaction SPRO )

SAP Utilities Intercompany Data ExchangeIntercompany Data Exchange for Swiss Electric and Gas

Utilities

NoteThe Customizing activities under General Settings and Switching Processes have been completed.

General assumptions for the switching processes

The following assumptions are applicable to all the switching processes that are listed below.

● The process can be started from either SAP IS-U or SAP CRM.

NoteHowever, the integration with SAP CRM is out of scope for the intercompany data exchange for Swiss electric and gas utilities application.

● The checks executed in the validation depend on the related Customizing settings. For more information about the available checks and related Customizing settings, see the Configuration Guide for intercompany data exchange for Swiss electric and gas utilities 1.0.

20


Intercompany data exchange for Swiss electric and gas utilities 1.0Switching Processes

Process

The following switching processes are supported as part of intercompany data exchange for Swiss electric and gas utilities :

● Change of Supplier [page 21]

● Move-In [page 22]

● Move-Out [page 24]

● End of Supply (Drop) [page 25]

● Basic Supply [page 26]

● Invalidation [page 28]

● Cancellation [page 29]

More Information

For more information, see the followings:



4.1 Change of Supplier

The change of supplier process is used when an end customer wants to change the supplier.

Process

This section explains about how the change of supplier process proceeds by describing the process steps that are technically enhanced to fulfill the specific requirements of the Swiss utilities market.

Figure 2: Change of Supplier Process

The change of supplier process involves the following market participants:

● New supplier

● Current supplier

● Distributor




As depicted in the diagram above, while various process steps are executed in the system, the change of supplier (CoS) process can be summarized in the following three main steps which correspond to the numbers mentioned in the diagram.

The change of supplier process proceeds as follows:

1. New supplier sends a change request to the distributor (Message Type: 392)

○ First, the end customer requests for the change of supplier.

○ Then the operator of the new supplier initiates the CoS process upon which the system automatically creates and sends the CoS request message to the distributor.

2. Distributor sends a confirmation or a rejection to the new supplier (Message Type: 414)

○ The reception of the request message leads to the automatic creation of a new process document in the distribution system.

○ The distributor validates the CoS request.

The system checks whether the CoS request has been received by the deadline defined as well as existence and eligibility of the data, such as PoD, sending service provider and so on.

○ Based on the result of the checks, the response message, either confirmation or rejection, will be sent back to the new supplier.

○ In case of an error with any of the checks that requires a user decision, the system creates a BPEM (business process exception management) case or directly sends a rejection message to the new supplier.

○ After the response for confirmation is sent to the new supplier, the new supplier will wait until the cancellation period has expired. After the expiry of the defined time period, the change of supplier process will be finalized and the system will determine the target supply scenario accordingly.

3. Distributor notifies the current supplier about the change (Message Type: E44)

○ When the distributor sends the confirmation to the new supplier (step 2 above), by sending an information message about CoS, the distributor notifies the current (old) supplier about the change at the same time.

○ Upon receiving the information message in the current supplier side, the system creates a new process document.

○ After the validation, if all checks are completed successfully, the current supplier will wait until the cancellation period has expired. After the expiry of the defined time period, the change of supplier process will be finalized and the system will determine the target supply scenario accordingly.

○ In case of an error for which a user decision is required, the system creates a BPEM case.

4.2 Move-In

The move-in process is used when an end customer moves in the new premise, either a home or a place of business.

Process

This section explains about how the move-in process proceeds by describing the process steps that are technically enhanced to fulfill the specific requirements of the Swiss utilities market.

22



Figure 3: Move-In Process

The move-in process involves the following market participants:

● New supplier

● Distributor

As depicted in the diagram above, while various process steps are executed inside the system, the move-in (MI) process can be summarized in the following two main steps which correspond to the numbers mentioned in the diagram.

The move-in process proceeds as follows:

1. New supplier notifies the distributor about the move-in (Message Type: 392)

○ First, the end customer requests for the move-in (or change of end customer).

○ Then the operator of the new supplier initiates the move-in (MI) process upon which the system automatically creates and sends the MI request message to the distributor.

2. Distributor sends a confirmation or a rejection to the new supplier (Message Type: 414)


○ The distributor validates the MI request.

The system checks whether the MI request has been received by the deadline defined as well as existence and eligibility of the data, such as PoD, sending service provider and so on.

The system also checks whether the new supplier is already assigned to the relevant PoD.


○ In case of an error with any of the checks that requires a user decision, the system creates a BPEM (business process exception management) case or directly sends a rejection message to the new supplier based on the underlying configuration settings made.

○ After the response for confirmation is sent to the new supplier, the new supplier will wait until the cancellation period has expired. After the expiry of the defined time period, the MI process will be finalized and the system will determine the target supply scenario accordingly.




4.3 Move-Out

The move-out process is used when an end customer moves out from the premise, either a home or a place of business.

Process

This section explains about how the move-out process proceeds by describing the process steps that are technically enhanced to fulfill the specific requirements of the Swiss utilities market.

Figure 4: Move-Out Process

The move-out process involves the following market participants:


● Distributor

As depicted in the diagram above, while various process steps are executed inside the system, the move-out (MO) process can be summarized in the following two main steps which correspond to the numbers mentioned in the diagram.

The move-out process proceeds as follows:

1. Current supplier notifies the distributor about the move-out (Message Type: 392)

○ First, the end customer requests for the move-out.

○ Then the operator of the current supplier initiates the move-out (MO) process upon which the system automatically creates and sends the MO request message to the distributor.

2. Distributor sends a confirmation or a rejection to the current supplier (Message Type: 414)


○ The distributor validates the MO request.

The system checks whether the MO request has been received by the deadline defined as well as existence and eligibility of the data, such as PoD, sending service provider and so on.

24



The system also checks whether the current supplier is still assigned to the relevant PoD

○ Based on the result of the checks, the response message, either confirmation or rejection, will be sent back to the current supplier.

○ In case of an error with any of the checks that requires a user decision, the system creates a BPEM (business process exception management) case or directly sends a rejection message to the current supplier based on the underlying configuration settings made.

○ After the response for confirmation is sent to the current supplier, the current supplier will wait until the cancellation period has expired. After the expiry of the defined time period, the MO process will be finalized and the system will determine the target supply scenario accordingly.

4.4 End of Supply (Drop)

The end of supply process is used when an end customer requests a termination of electricity supply for the premise, either a home or a place of business. This process is also referred as “drop” process.

Process

This section explains about how the end of supply process proceeds by describing the process steps that are technically enhanced to fulfill the specific requirements of the Swiss utilities market.

Figure 5: End of Supply Process

The end of supply process involves the following market participants:


● Distributor

As depicted in the diagram above, while various process steps are executed inside the system, the end of supply (EoS) can be summarized in the following two main steps which correspond to the numbers mentioned in the diagram.




The end of supply process proceeds as follows:

1. Current supplier notifies the distributor about the end of supply (Message Type: 392)

○ First, the end customer requests for the end of supply.

○ Then the operator of the current supplier initiates the end of supply (EoS) process upon which the system automatically creates and sends the EoS request message to the distributor.

2. Distributor sends a confirmation or a rejection to the current supplier (Message Type: 414)


○ The distributor validates the EoS request.

The system checks whether the EoS request has been received by the deadline defined as well as existence and eligibility of the data, such as PoD, sending service provider and so on.

At this point, the system also checks if a new supplier exists with the end customer. If no new supplier exists, then the Basic Supply [page 26] process will be triggered.


○ In case of an error with any of the checks that requires a user decision, the system creates a BPEM (business process exception management) case or directly sends a rejection message to the supplier.

○ After the response for confirmation is sent to the supplier, the supplier will wait until the cancellation period has expired. After the expiry of the defined time period, the EoS process will be finalized and the system will determine the target supply scenario accordingly.

4.5 Basic Supply

The basic supply process is used when an end customer requests the end of supply (drop) process without having a new supplier. This process is also referred as “backup supply” process.

Process

This section explains about how the basic supply process proceeds by describing the process steps that are technically enhanced to fulfill the specific requirements of the Swiss utilities market.

26



Figure 6: Basic Supply

The basic supply process involves the following market participants:

● Distributor

● Basic supplier

As depicted in the diagram above, while various process steps are executed inside the system, the basic supply (BS) process can be summarized in the following one main step which correspond to the number mentioned in the diagram.

The basic supply process proceeds as follows:

1. Distributor sends a basic supply message to the basic supplier (Message Type: E44)

○ First, this process is automatically triggered by the End of Supply [page 25] process, if the end customer has requested the termination of supply without having a new supplier. This is to make sure the backup of the electricity supply to the end customer.

In the Distributor side:

○ Then the operator of the distributor performs the change of master data and the system will determine the target supply scenario accordingly.

In the Basic Supplier side:

○ The reception of the basic supply request message is followed by the validation.

○ In case of an error with any of the checks that requires a user decision, the system creates a BPEM (business process exception management) case.

○ Based on the result of the checks, the user action needs to be taken to inform the end customer about the basic supply. The end customer can not reject it.

○ After informing the end customer, the BS process will be finalized and the system will determine the target supply scenario accordingly.




4.6 Invalidation

The invalidation process is used when an initiator, usually the new supplier, wants to invalidate the process, for example a change of supplier request, that has already been sent to a participant, which is usually the distributor.

The invalidation process should not be confused with the Cancellation [page 29] process. An invalidation request can be raised only if the response message has not been received yet. Otherwise, a cancellation request needs to be raised.

Process

This section explains about how the invalidation process proceeds by describing the process steps that are technically enhanced to fulfill the specific requirements of the Swiss utilities market.

Figure 7: Invalidation Process

The invalidation process involves the following market participants:

● Initiator (usually Supplier)

● Participant (usually Distributor)

As depicted in the diagram above, while various process steps are executed inside the system, the invalidation process can be summarized in the following one main step which corresponds to the number mentioned in the diagram.

The invalidation process proceeds as follows:

1. Initiator sends an invalidation request to the participant (Message Types: C02, E44, or 414)

○ First, the initiator (usually supplier) starts the invalidation process.

○ The existing process document which was created for the original request will be used for triggering the invalidation process upon which the system automatically creates and sends the invalidation request message to the participant (usually distributor).

○ In the participant side, the reception of the request message leads to the automatic identification of the process message to be invalidated based on the message ID of the original request message.

○ The distributor validates the invalidation request.

28



The system checks whether the invalidation request has been received by the deadline defined as well as existence and validity of the data, such as the original process, sending service provider and so on.

○ In case of an error with any of the checks that requires a user decision, the system creates a BPEM (business process exception management) case.

○ In case all of the checks pass, the invalidation process will be completed with an update of the status to Cancelled .

Note● From the supplier point of view, it is not possible to send an invalidation message, if the process, for

example change of supplier, has already been confirmed or rejected. In this case, a cancellation process has to be triggered by the supplier.

● From the distributor point of view, an invalidation request will be ignored, if the distributor has already confirmed or rejected the process, for example change of supplier. In this case, a cancellation process has to be triggered by the supplier.

4.7 Cancellation

The cancellation process is used when an end customer wants to cancel the process, such as change of supplier, that has been already requested.

The cancellation process should not be confused with the Invalidation [page 28] process. The cancellation process needs to be executed if the response message has already been received. Otherwise, an invalidation request can be raised.

Process

This section explains about how the cancellation process proceeds by describing the process steps that are technically enhanced to fulfill the specific requirements of the Swiss utilities market.

Figure 8: Cancellation Process

The cancellation process involves the following market participants:

● Initiator (usually New supplier)

● Participant (usually Current supplier)

● Distributor




As depicted in the diagram above, while various process steps are executed inside the system, the cancellation process can be summarized in the following three main steps which correspond to the numbers mentioned in the diagram.

The cancellation process proceeds as follows:

1. Initiator sends a cancellation request to the distributor (Message Type: E67)

○ First, the end customer requests for the cancellation.

○ Then the operator of the initiator (usually new supplier) starts the cancellation process.

○ The existing process document which was created for the original request will be used for triggering the cancellation process upon which the system automatically creates and sends the cancellation request message to the distributor.

2. Distributor sends a confirmation or a rejection to the initiator (Message Type: E68)

○ The reception of the cancellation request message leads to the automatic identification of the process message to be cancelled based on the external process reference of the original request message.

○ The distributor validates the cancellation request.

The system checks whether the cancellation request has been received by the deadline defined as well as existence and validity of the data, such as the original process, sending service provider (supplier) and so on.

○ Based on the result of the checks, the response message, either confirmation or rejection, will be sent back to the initiator.

○ In case of an error with any of the checks that requires a user decision, the system creates a BPEM (business process exception management) case or directly sends a rejection message to the new supplier based on the underlying configuration settings made.

In the distributor side, the cancellation process will be terminated with an update of the status to Rejected and the original process will continue.

○ After the response for confirmation is sent to the new supplier, the cancellation process will be terminated with an update of the status to OK and the original process will be terminated in both distributor and supplier sides.

3. Distributor notifies the participant about the cancellation (Message Type: E44)

○ In case of a change of supply (CoS) process, the distributor notifies the participant (usually current supplier) about the cancellation.

4.8 Reports for Switching Processes

The following new report is developed for the switching processes:

● Configure DEx Processes for Service Providers

4.8.1 Configure Data Exchange Processes for Service Providers

You use this report to create or delete the following data exchange process information for multiple service providers:

30



● Data exchange definitions

● Partner profiles for service providers for outbound messages

● Parameter configuration assignment to the deregulation process IDXCH2_IDE within service provider agreements

Activities

To access this report, execute the transaction /IDXCH2/MENU to open the SAP Easy Access menu for intercompany data exchange for Swiss electric and gas utilities first, and then choose Switching ProcessesConfigure DEx Processes for Service Providers .

You can also execute the transaction /IDXCH2/SWT_DATEX to call up this report directly.

Selection

To create data exchange process information for the selected service providers, you enter the relevant information in the following screen areas:

● General Selection Criteria

When you execute the report, you must enter a service provider or a range of service providers. In addition, you enter a validity period for the data exchange process information you want to create.

If you select the Only Extern. Service Providers checkbox, the system ignores internal service providers, and only creates data for data exchange processes of external service providers.

● Data Exchange Definitions

You enter the following values or value ranges:

○ Data exchange processes

○ Data exchange format

If you select the Assign Data Exchange Processes checkbox, the system assigns the selected data exchange processes to all relevant service providers, and creates the corresponding data exchange definitions.

● Partner Profiles

For outbound messages, you enter the output mode and receiver port.

If you select the Create ALE Partner Profiles checkbox, the system creates an Application Link Enabling (ALE) partner profile for the receiving service provider in the partner type SP (service provider). The created partner profiles can be displayed in transaction Partner Profiles ( WE20 ).

● Service Provider Agreements

You select a parameter configuration for the relevant service provider agreements.

If you select the Assign Parameter Configuration checkbox, the system assigns the selected parameter configuration to the deregulation process IDXCH2_IDE in the service provider definition.

● Working Mode

You can insert new and delete existing data exchange process entries by selecting the relevant radio buttons. Changes to the database are only carried out if you deselect the Simulation Mode checkbox.

Output

When you execute this report, the list output displays the following fields with corresponding number of data entries that have been maintained:

● Data Exchange Entries [Insert]




● Partner Profiles [Insert]

● Parameter Configuration Entries [Insert]

● Data Exchange Entries [Delete]

● Partner Profiles [Delete]

● Parameter Configuration Entries [Delete]

More Information


32



5 Operations Information

Certain administrative activities are required for the proper functioning of the intercompany data exchange for Swiss electric and gas utilities application.

The intercompany data exchange for Swiss electric and gas utilities uses the existing infrastructure provided by the standard component Intercompany Data Exchange within SAP for Utilities.

Therefore, the administrative activities to ensure a stable application operation can be achieved by following the corresponding guidelines for SAP for Utilities, specifically, the topics provided for Intercompany Data Exchange.

For more information, see SAP Library for SAP for Utilities in SAP Help Portal at help.sap.com under SAP Utilities Intercompany Data Exchange .

Activities

The following monitoring activities are covered in this application help, since they are particularly important and applicable to the intercompany data exchange for Swiss electric and gas utilities :

Table 19

Operations Activity Report/Transaction to be used

Monitor metered data communication Metering Communication Monitor (Transaction /IDXCH2/MET_MON )

See Monitor Metering Communications [page 18] .

To use this report for batch job sending, see Schedule Background Jobs [page 35] .

Monitor end-to-end status of process documents Monitoring of Process Documents (Transaction /IDXCH2/PDOCMON01 )

See Monitor Process Documents [page 33] .

Monitor data exchange tasks using the standard SAP IS-U IDE report

See Monitor Data Exchange Tasks [page 35] .

Monitor IDocs (ALE) using the standard SAP transactions See Monitor IDocs (ALE) [page 36] .

5.1 Monitor Process Documents

You use this report to display all the process documents that are currently available in your system.

Intercompany data exchange for Swiss electric and gas utilities 1.0Operations Information




Prerequisites

The process and data-exchange framework for utilities 1.0 (infrastructure add-on solution to SAP IS-U IDE) has been installed.

Activities

To access this report, execute the transaction /IDXCH2/MENU to open the SAP Easy Access menu for intercompany data exchange for Swiss electric and gas utilities first, and then choose Switching ProcessesMonitoring of Process Documents .

You can also execute the transaction /IDXCH2/PDOCMON01 to call up this report directly.

Selection

To select process documents, the following selection criteria can be specified, as required:

● Main Criteria

○ Process-Reference

○ Process ID


○ Process Class

○ Process Key Date

○ Point of Delivery ID

● Additional Criteria

○ Associated Process Documents (checkbox)

If this checkbox is selected, in addition to the process documents selected, the system also displays the related process documents that are linked to the selected ones.

○ Process View

For example, Distributor View, Supplier View - New Supplier, Supplier View - Old Supplier

○ Process Status

For example, OK, No/Error, Reversed, Obsolete, Terminated, Warning, Incomplete

○ Process Type

For example, Change of Supplier, End of Supply, Start of Supply, Cancellation, Move-In, Move-Out

○ Created On

○ Business Partner

○ IDoc Number

○ Current Supplier

○ New Supplier

○ Distributor



In addition, the following criteria can be specified on the message level:

○ Business Process ID

○ Document ID

34



○ Internal Message Code

Output

The result will be displayed as follows:

● If the system does not find any process document, the following error message is displayed:

“Process document cannot be found with given criteria”

● If the system finds more than one process document, all process documents found are displayed in an SAP List Viewer (ALV).

● If the system only finds a single process document, the system displays all the details of the process document found and skips the display in ALV.

5.2 Schedule Background Jobs

You need to schedule jobs with the reports that should run automatically in the background.

Activities

To define scheduled jobs, proceed as follows:

1. Execute transaction SM36 ( Define Background Job ).

2. Create a periodical job to run at a desired frequency in batch mode.

ExampleSuppose you want to send metered data to the associated service provider every day.

You can schedule a background job as follows in transaction SM36 ( Define Background Job ):

Table 20

Relevant Report Metering Process Trigger Report (program: /IDXCH2/RP_MET_TRIGGERING )


Frequency Daily

5.3 Monitor Data Exchange Tasks

In the operation of intercompany data exchange for Swiss electric and gas utilities , every data exchange is executed through, so called “data exchange tasks” .

A task references the switch document for which it is connected to, as well as the IDoc (intermediate document) that is sent or that leads to create the relevant task.

The transaction to monitor the data exchange tasks is EDATEXMON01 .




Each data exchange task has a status assigned, which can be used to filter only those having an error ( Data Exchange Process Status = ERROR ).

More Information

For more information, see SAP Library for SAP for Utilities in SAP Help Portal at help.sap.com under Intercompany Data Exchange Deregulation Functions Processing Data Exchange Data Exchange Data

Exchange Tasks Monitoring .

5.4 Monitor IDocs (ALE)

IDocs are used to realize the connection between the intercompany data exchange for Swiss electric and gas utilities application and the outside world. The ALE (Application Link Enabling) layer provides the environment for sending and receiving IDocs.

The following are the standard SAP transactions that can be used for the monitoring purposes:

● To monitor the IDoc (ALE message) status, use transaction BD87 ( Select IDocs )

● To display IDocs, use transaction WE02 ( IDoc List )

● In case of errors in the transactional RFCs with which the IDocs are sent, use transaction SM58 ( Asynchronous RFC Error Log )

More Information

The following are the standard SAP transactions that can be used for the IDoc (ALE) configuration purposes:

● WE30 ( Develop IDoc Types )

● WE57 ( Assign FM to Logical Messages and IDoc Types )

● WE42 ( Maintain Inbound Process Codes and Logical Messages )

● WE20 ( Maintain Partner Profiles )

For more information about IDocs, see SAP Library for SAP NetWeaver Enterprise Search in SAP Help Portal at

help.sap.com . Search the related topics with the search term “IDoc Interface/ALE” .

36





6 References

More Information

You can find more information about intercompany data exchange for Swiss electric and gas utilities in the following references:

● SAP Notes 1685414 (IDXPF 604: Installation on ERP 6.0 EHP4/EHP5/EHP6/EHP7)

● SAP Notes 2202027 (Release strategy for the ABAP add-on IDXCH2)



● Main Menu and Transactions [page 9] for intercompany data exchange for Swiss electric and gas utilities 1.0

● VSE (Verband Schweizerischer Elektrizitätsunternehmen or Association of Swiss Electricity Companies)

Website at www.strom.ch/de/verband/ueber-den-vse.html

● ENTSOG (European Network of Transmission System Operators for Gas) Website at www.entsog.eu/

Intercompany data exchange for Swiss electric and gas utilities 1.0References



http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D1685414%26_NLANG%3Den%26_NVERS%3D0


http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.strom.ch%2Fde%2Fverband%2Fueber-den-vse.html

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.entsog.eu%2F

Typographic Conventions

Table 21

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name> ”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

38


Intercompany data exchange for Swiss electric and gas utilities 1.0Typographic Conventions

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com



www.sap.com

© Copyright 2015 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company.SAP 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. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

http://www.sap.com

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

Intercompany data exchange for Swiss electric and … data exchange for Swiss electric and ... The...

Documents

Transcript of Intercompany data exchange for Swiss electric and … data exchange for Swiss electric and ... The...