intercompany data exchange for uk electricity suppliers 1 · 2 intercompany data exchange for uk...

User Guide

Document Version: 1.0 – FinalDate: May 27, 2014

CUSTOMER

Intercompany data exchange for UK electricitysuppliers 1.0

User Guide Customer

Intercompany data exchange for UK electricity suppliers 1.0User Guide – Version: 1.0 – Final

May 27, 2014© 2014 SAP AG or an SAP affiliate company. All rights reserved. 2

Typographic Conventions

Type Style Description

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

Textual cross-references to other documents.

Example Emphasized words or expressions.

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

Example Output on the screen. This includes file and directory names and their paths, messages,names of variables and parameters, source text, and names of installation, upgrade anddatabase tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as theyappear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters withappropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

User Guide Customer



Document History

Version Status Date Change

1.0 Final 2014-05-27 First Documentation Release

User Guide Customer



Table of Contents

1 About This Document ....................................................................................................... 81.1 Assumptions ............................................................................................................................................... 81.2 Prerequisites ............................................................................................................................................... 81.3 Related Information ..................................................................................................................................... 9

1.3.1 Configuration and Customization .................................................................................................. 91.3.2 Important SAP Notes.................................................................................................................... 9

1.4 Glossary ................................................................................................................................................... 10

2 Intercompany data exchange for UK electricity suppliers.............................................. 302.1 Solution Overview ..................................................................................................................................... 30

3 Main Menu ...................................................................................................................... 313.1 Introduction ............................................................................................................................................... 31

4 Scenario: Change of Supplier for a Half-Hourly Metering Customer (Simple) .................. 334.1 Introduction ............................................................................................................................................... 334.2 Details and Execution................................................................................................................................ 334.3 Running the CoS Gain Process ................................................................................................................. 35

4.3.1 Trigger the CoS Gain Process .................................................................................................... 354.3.2 Step 120: Send the CoS Registration Request (D0055) ............................................................... 364.3.3 Step 130: Receive the CoS Registration Rejection (D0057) ......................................................... 384.3.4 Step 200: Receive the CoS Registration Confirmation (D0217) .................................................... 394.3.5 Step 210: Update the Registration Data (D0217) ......................................................................... 444.3.6 Step 230: Create the Objection Window ...................................................................................... 454.3.7 Step 260: Create the Services at MPAN ..................................................................................... 464.3.8 Step 870: Check for the Agent Appointment ................................................................................ 474.3.9 Step 1100/1110/1120: Trigger the Agent Appointment for MOP/DC/DA ....................................... 494.3.10 Step 220: Receive the Old Supplier's Registration Details (D0260) .............................................. 514.3.11 Step 1130/1140: Notification of the Change to Other Parties (D0148) .......................................... 524.3.12 Step 1410: Receive the Meter Technical Details (D0268) ............................................................ 554.3.13 Step 1420: Update the System Data with Meter Technical Details ............................................... 574.3.14 Step 9900: Complete the CoS Gain Process ............................................................................... 58

5 Scenario: Change of Supplier for a Half-Hourly Metering Customer withObjection ........................................................................................................................ 60

5.1 Introduction ............................................................................................................................................... 605.2 Details and Execution................................................................................................................................ 605.3 Running the CoS Gain Process with Objection ........................................................................................... 63

5.3.1 Starting Point for Handling the Objection ..................................................................................... 645.3.2 Step 600: Receive the Registration Objection (D0067) ................................................................ 655.3.3 Step 610: Set the Deadline for Objection Resolution ................................................................... 665.3.4 Step 810/820/830: Trigger the Agent De-Appointment for MOP/DC/DA ........................................ 675.3.5 Step 860: Update the Services at Supply Scenario ...................................................................... 705.3.6 Step 700: Receive the Registration Objection Removal (D0091) .................................................. 71

User Guide Customer



5.3.7 Step 870: Check for the Agent Appointment ................................................................................ 725.3.8 Step 1100/1110/1120: Trigger the Agent Appointment for MOP/DC/DA ....................................... 735.3.9 Finalize the CoS Gain Process with Objection ............................................................................. 76

User Guide Customer



Table of Figures

Figure 1: Customizing Activities for IDEX UK ......................................................................................................... 31

Figure 2: CoS Gain Process - Process Flow .......................................................................................................... 34

Figure 3: Process Trigger Method .......................................................................................................................... 35

Figure 4: Process Document (PDoc) ...................................................................................................................... 36

Figure 5: DATEX Reference .................................................................................................................................. 37

Figure 6: Monitoring of Data Exchange Tasks ........................................................................................................ 37

Figure 7: Step Data Container with Additional Data ................................................................................................ 37

Figure 8: Process Step No. 120 (repeated) ............................................................................................................ 38

Figure 9: Response Code Validation ...................................................................................................................... 39

Figure 10: Receive Registration Confirmation (D0217) ........................................................................................... 40

Figure 11: Step Data Container after IDoc Inbound Processing .............................................................................. 40

Figure 12: Display Validation Results ..................................................................................................................... 41

Figure 13: Master Data Comparison ...................................................................................................................... 42

Figure 14: Activity Monitor - Business Exception created ........................................................................................ 43

Figure 15: Exception Monitoring ............................................................................................................................ 43

Figure 16: Clarification Case ................................................................................................................................. 44

Figure 17: Process Step 210 to Update SAP IS-U .................................................................................................. 45

Figure 18: Deadline Monitoring .............................................................................................................................. 46

Figure 19: Create Services for MPAS and Distributor at MPAN ............................................................................... 47

Figure 20: Check for Agent Appointment................................................................................................................ 48

Figure 21: Agent Appointment Process Values ...................................................................................................... 48

Figure 22: Trigger Agent Appointment ................................................................................................................... 50

Figure 23: Display Associated Processes .............................................................................................................. 51

Figure 24: Receive Old Supplier's Registration Details ........................................................................................... 52

Figure 25: Step Type "Process Trigger" ................................................................................................................. 53

Figure 26: Child Process for D0148 Out Processing ............................................................................................... 54

Figure 27: Process Document (PDoc) for D0148 Processing .................................................................................. 55

Figure 28: Process Step 1410 to receive Meter Technical Details ........................................................................... 56

Figure 29: Master Data Comparison: Validate Meter Technical Details ................................................................... 57

Figure 30: Process Step 1420 to update Meter Technical Details in SAP IS-U ........................................................ 58

Figure 31: Complete Process Document ................................................................................................................ 59

Figure 32: CoS Gain Process with Objection - Process Flow .................................................................................. 62

Figure 33: Process Document (PDoc) .................................................................................................................... 65

Figure 34: Notification of an Objection to Change of Supplier Sent to the New Supplier ........................................... 66

Figure 35: Objection Resolution Window................................................................................................................ 67

Figure 36: Agent De-Appointment.......................................................................................................................... 68

User Guide Customer



Figure 37: Associated Agent De-Appointment PDocs ............................................................................................. 69

Figure 38: Agent Appointment PDocs are obsolete ................................................................................................ 69

Figure 39: Remove Supplier Agent Services from MPAN ....................................................................................... 70

Figure 40: Receive Registration Objection Removal ............................................................................................... 71

Figure 41: Check for Appointed Agents .................................................................................................................. 72

Figure 42: Process Values for Agent Appointment check ........................................................................................ 73

Figure 43: Trigger Agent Appointment after Objection Removal .............................................................................. 74

Figure 44: Associated PDocs for Agent Appointment.............................................................................................. 75

Figure 45: Agent De-Appointment PDocs with Obsolete Status .............................................................................. 75

Figure 46: CoS Gain PDoc with Completed Status ................................................................................................. 76

User Guide Customer



1 About This Document

1.1 Assumptions

This user guide is based on the assumption that you have some level of familiarity with the terminology and functionsassociated with the intercompany data exchange for UK electricity suppliers.

The aim of this user guide is to provide you with the information you need to navigate through and optimize theperformance of the intercompany data exchange for UK electricity suppliers.

We recommend that you refer to this user guide whenever necessary during the hands-on operation of theintercompany data exchange for UK electricity suppliers.

1.2 Prerequisites

Make sure that the following prerequisites are met before running the intercompany data exchange for UK electricitysuppliers:

You have completed the necessary configuration settings in Customizing for:

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

You need to maintain the standard settings that are required for running the SAP Utilities.

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

You need to maintain the standard settings that are required for running the Intercompany Data Exchange forSAP Utilities.

process and data-exchange framework for utilities under SAP Customizing Implementation Guide(transaction code SPRO) SAP Utilities Intercompany Data Exchange Process and Data-ExchangeFramework for Utilities

You need to maintain the settings that are required for running the process and data-exchange framework forutilities. For more information, see the Configuration Guide for process and data-exchange framework for utilities.

intercompany data exchange for UK electricity suppliers under SAP Customizing ImplementationGuide (transaction code SPRO) SAP Utilities Intercompany Data Exchange Intercompany DataExchange for UK Electricity Suppliers

You need to maintain the solution-specific settings that are required for running the intercompany data exchangefor UK electricity suppliers, for example:

o Creation of master data, such as point of delivery (PoD) and business partner

o Definition of service providers and data-exchange processes

For more information, see the Configuration Guide for intercompany data exchange for UK electricity suppliers.

User Guide Customer



1.3 Related Information

1.3.1 Configuration and Customization

You can find related information in the following resources:

Resource Quick Link on SAP Service Marketplace

Solution Manager Documentation for process anddata-exchange framework for utilities 1.0

http://service.sap.com/swdc

Installations and Upgrades (index "P")PROCESS/XCHG FRAMWORK UTIL PROCESS/XCHGFRAMWORK UTIL 1.0 Technical Documentation

Configuration Guide for process and data-exchangeframework for utilities 1.0

Configuration Guide for intercompany dataexchange for UK electricity suppliers 1.0


Installations and Upgrades (index "I") IDEX UK IDEX UK 1.0 Technical Documentation

1.3.2 Important SAP Notes

RecommendationMake sure that you read the SAP Notes before you start implementing the software. The SAP Notes containthe latest information about the installation as well as corrections to the installation information.

Also make sure that you have the up-to-date version of each SAP Note, which is available on SAP ServiceMarketplace at https://service.sap.com/notes.

SAP NoteNumber

Title Description

1685414 IDXPF 604: Installation on ERP6.0 EHP4/EHP5/EHP6/EHP7

See this note for information about the download path for thesoftware and documentation, the software installation, as wellas the activation of the BC sets among others.

2013933 Release Strategy for the ABAPAdd-on IDXUK

See this note for information about the download path for thesoftware and documentation, and the software installationamong others.



https://service.sap.com/notes

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=1685414&

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=DISPL_TXT&_NNUM=2013933&

User Guide Customer



1.4 Glossary

Term Abbreviation Definition

Advanced BusinessApplication Programming

ABAP The SAP programming language

Advanced BusinessApplication ProgrammingObject Oriented

ABAP OO ABAP objects component of the ABAP programming languagethat allows object-oriented programming on the basis of classesand interfaces.

Annualised Advance AA As defined in the Data Transfer Catalogue (DTC). For moreinformation, see the MRA site athttp://dtc.mrasco.com/Default.aspx.

Application for Registration An application by a supplier to be registered against supplynumber core data.

Application Link Enabling ALE The technology for setting up and operating distributedapplications.Application Link Enabling (ALE) facilitates the distributed, butintegrated, installation of SAP systems. This involves business-driven message exchange using consistent data across looselylinked SAP applications.Applications are integrated using synchronous andasynchronous communication, not by using a central database.ALE consists of the following layers:• Application services• Distribution services• Communication services

Associated Supplier The supplier registered to the metering point that has issued anotice of objection with respect to the initiating supplier’sregistration and in this circumstance is the old supplier.The supplier who is required to respond to a dispute over achange of supplier meter reading or an erroneous registrationnotification.

Balancing and SettlementCode

BSC Multilateral agreements for electricity.The document designated by the Secretary of State and adoptedby NGC as the BSC pursuant to Condition 7 [A] of theTransmission License, and as given contractual force by theBSC Framework Agreement.

Balancing and SettlementCode Procedure

BSCP

Business Add-In BAdI Business Add-Ins (BAdIs) are the basis for enhancements whereBAdI methods in object plug-ins can be called from ABAPprograms. By specifying filter values, the calling program controlswhich BAdI implementations are used. A BAdI consists of a BAdIinterface, a set of filters and some settings.

http://dtc.mrasco.com/Default.aspx

User Guide Customer




Business as Usual BAU

Business ObjectRepository

BOR The Business Object Repository (BOR) is the central accesspoint for the SAP business object types and their BAPIs. TheBOR was originally developed for SAP Business Workflow.Today, in addition to storing SAP business object types and theirBAPIs, the BOR is used for ArchiveLink, output control, andother generic object services.The BOR provides the following services in the BAPI context:• Allows an object-oriented view of all data and processes in anSAP systemArranging the various business object types according to thecomponent hierarchy. This enables you to find the requiredfunctions quickly and easily.• Contains all relevant informationThe BOR contains all the relevant information on the SAPbusiness object types, their key fields, and their BAPI methodsthat is needed to integrate the correct object type definitions andBAPI calls in an application program. This enables theintegration of middleware. such as the DCOM Connector,ActiveX Controls, CORBA Gateway, and so on.• Ensures BAPI interface stabilityAny interface changes carried out in the BOR are automaticallychecked for syntax compatibility against the associateddevelopment objects in the ABAP Dictionary.• Manages BAPIs in release updatesBAPI interface enhancements made by adding parameters arerecorded in the BOR. Previous interface versions can thus bereconstructed at any time. When a BAPI is created, the releaseversion of the new BAPI is recorded in the BOR. The sameapplies when any interface parameter is created.• Creates instances of SAP business objectsThe runtime environment of the BOR receives requests to createruntime objects from client applications and creates theappropriate object instances.

Business Partner BP A natural or legal person or a group of natural or legal persons,not part of the business organization but with whom a businessinterest exists.

Business ProcessException Management

BPEM Business Process Exception Management (BPEM) is used toanalyze and monitor mass activities and online transactions. TheBPEM process monitoring allows you to identify successful andincorrect processes at a glance. Problem messages that occurduring processes are added to a clarification work list, usingBPEM, and are distributed to the employees responsible.• Industry independent solution• Non-modifying standalone solution: can be implementedtogether with any SAP module

User Guide Customer




• Analyze application messages of any business process• Analyze and monitor executed business processes in SAP• Data reduction for huge logs by removal of irrelevant messages• Analyzed data stored as extracts• Instant access to the information• Direct navigation from message to business object embeddedas variable• Automatic or manual creation of cases for problems• Assignment of cases to a user group based on role resolution• Measure the performance of executed business processes inBWFor more information, see the SAP Library athttp://help.sap.com/saphelp_nw70/helpdata/EN/4e/91f6984f174730b0be192b3c9c5541/frameset.htm.

Central Meter RegistrationService

CMRS The service for the registration of CVA metering systems andassociated data as defined in the Balancing and SettlementCode (BSC).

Change of Occupier CoO See the definition provided for Change of Tenancy (CoT).

Change of Supplier CoS A scenario wherein a customer stops purchasing a utility fromone supplier and starts purchasing that utility from a differentsupplier.A registration, which has been confirmed by the relevant MeterPoint Administration Service (MPAS), in relation to a newsupplier undertaking responsibility for that metering point.

Change of Tenancy CoT A process which takes place based on the following specificswitch scenarios:1. Consumer A left the site (Move out) and Consumer B entersthe site (Move In) and both have same supplier Change ofbusiness partner in the system.2. Consumer left Site A (Move out) and enters Site B (Move In)staying with same supplier Business partner switchesbetween two supply points.

Complex Debt Indicator The field within the D0307 as defined in the DTC. For moreinformation, see the MRA site athttp://dtc.mrasco.com/Default.aspx.

COMPR function module COMPR A function module that processes all inbound messages anddetermines what needs to be done with the content of themessage.

Configuration The definition of parameters that an SAP program uses todetermine, for example, display modes, available functions andcomponents, network communication, and connection with otherprograms.

Connection Object A link between installation and postal regional structure.This is usually a building, but can also be a piece of property or

http://help.sap.com/saphelp_nw70/helpdata/EN/4e/91f6984f174730b0be192b3c9c5541/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/4e/91f6984f174730b0be192b3c9c5541/frameset.htm


User Guide Customer




other facility, such as a fountain or construction site. Theconnection object corresponds to the functional location in thePlant Maintenance (PM) application component.

Contract Account CA An account in which posting data for those contracts or contractitems are processed for which the same collection/paymentagreements apply.Contract accounts are managed on an open item basis withincontract accounts receivable and payable.

Contract VolumeAggregation

CVA

Custom DevelopmentProject

CDP

Customer Acquisition andValidation System

CAVS

Customer Descriptor The data item (J0559) defined in the DTC. For more information,see the MRA site at http://dtc.mrasco.com/Default.aspx.

Customer Enhancement An adjustment to the standard SAP system, requested by thecustomer.SAP designs empty modification modules at particular points inthe standard system where customer enhancements areanticipated. These modules, known as exits, can be filled withcustomer-specific logic.

Customer own Reading CoR A meter reading provided by a customer.

Customer ReferenceNumber

CRN As defined in the DTC, it is the customer’s own referencenumber. For more information, see the MRA site athttp://dtc.mrasco.com/Default.aspx.

Customer RequestedObjection

CRO An objection raised, pursuant to Condition 14.4(c) of theElectricity Supply License.

Customer Transfer Process CTP As defined in the DTC, it is a unique identifier for a Smart Cardcustomer. This includes Supplier Reference and CustomerReference Number. For more information, see the MRA site athttp://dtc.mrasco.com/Default.aspx.

Customizing Overall implementation procedure to set up one or more SAPsystems at a customer site. The procedure aims to:• Adjust the company-neutral and industry-specific deliveredfunctions to your company's business requirements• Enhance SAP functions in the company• Implement SAP functions in your company quickly, safely, andcost effectively

Data Aggregator DA The organization appointed to aggregate the meter-reading/settlement data received from the appointed DataCollectors (DC) and forward it to suppliers. A function of this




User Guide Customer




aggregation process is the comparison of registration dataprovided to it, in separate streams, from NHHDC and MPAS.

Data Collector DC The organization responsible for collecting, processing andvalidating the meter reading data, which then passes theinformation to the Data Aggregator (DA). The DA, for example,collects customer meter readings at a frequency determined bythe supplier.

Data exchange DATEX Process that monitors and controls, according to point ofdelivery, the transfer of messages within Intercompany DataExchange (IDEX).

Data Protection Act DPA Data Protection Act 1998

Data Transfer Catalogue ofMRA

DTC The Data Transfer Catalogue (DTC) accommodates the inter-operational exchange of information, enabling effective interfacebetween industry participants. For more information, see theMaster Registration Agreement (MRA) site athttp://dtc.mrasco.com/Default.aspx.

Data Transfer Network DTN

De-energisation In relation to any boundary point or systems connection point (orthe plant or apparatus connected to any system at such a point),the movement of any isolator, breaker or switch, or the removalof any fuse whereby no electricity can flow at such point to andfrom a system.

Device Info Record Contains devices that are maintained by or belong to othercompanies. A data record in the Utilities Industry (SAP IS-U)contains only devices in the SAP IS-U component.A record may contain the following types of devices:• Metering devices (meters)• Controlling devices (ripple control receivers)• Data processing devices (converters)• Devices that protect or adjust (pressure regulators)

Distribution Connectionand Use of SystemAgreement

DCUSA Multilateral agreements for electricity

Distribution SystemOperator/ Distributor

DSO Distribution Business (BSC Terminology is Distribution SystemOperator)

Distribution Use of System DUoS Charge for use of the distribution networks that are invoiced bythe distributor to the supplier.

Division Category Type of supply or service that is predefined in the UtilitiesIndustry (SAP IS-U) component.Examples of division categories are electricity, gas and water.

Drill Down To do a detailed navigation into a query result by expanding adimension into values for each of its members, and adding these


User Guide Customer




values to additional rows in the result.You can also drill across, where values for the selecteddimension are added to additional columns. This is alsocommonly referred to as drilling down.

Earliest Re-submissionDate

As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Electricity Central OnlineEnquiry Service

ECOES

End 2 End Diagram E2E

Enhancement An addition to an SAP standard program made at a user exit.An enhancement does not change R/3 Repository objects. Withthe ABAP Development Workbench, you can develop any R/3Repository Objects. Enhancements are not affected byupgrading to a new release.

Enhancement Package EhP A collection of new and improved business functions for SAPBusiness Suite and SAP ERP. Enhancement packagesrepresent a new SAP approach to accelerate the delivery ofinnovation to customers via optional packages. Rather thanengaging in large upgrade projects, customers can takeadvantage of ongoing business innovation while keeping theircore systems stable. These optional enhancement packages canbe configured in a completely modular fashion by “switching on”only the new features and functionalities those customers want.

Enterprise Service-Oriented Architecture

Enterprise SOA A software architecture that uses policies, practices, andframework to enable application functionality to be provided andconsumed as sets of services. These services are published at alevel of granularity relevant to service consumers.

Erroneous Transfer ET An Erroneous Transfer occurs where a customer is transferred toa supplier without a valid contract in place and the Application forRegistration is processed in the relevant MPAS RegistrationSystem (see MAP 10). The business process ErroneousTransfer is only used for residential customers. Instead, forbusiness customers, a bilateral agreement exists.

Estimated AnnualConsumption

EAC As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Estimated Total DebtOutstanding

As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Failed F Regarding validation of electricity meter reading, the non-validmeter reading is "failed".The opposite of “failed” is "valid".

Flow Management Solution A software which transforms the SAP IDoc data structure to theUnited Kingdom (UK) industry-specific data structure and vice




User Guide Customer




versa.

Grid Supply Point GSP A connection from the national grid to a distribution network, thatis, a systems connection point at which the transmission systemis connected to a distribution system. Currently there are 14 GSPGroups in the United Kingdom (UK).

Grid Supply Point Group GSP Group A distinct electrical system, consisting of:(i) The distribution system(s) that are connected to thetransmission system at (and only at) Grid Supply Point(s), whichfall within one Group of GSPs, and(ii) Any distribution system that: (1) is connected to a distributionsystem in paragraph (i), or to any other distribution system underthis paragraph (ii), (2) is not connected to the transmissionsystem at any Grid Supply Point and the total supply into whichis determined by metering for each half hour.

Guaranteed Standards GS

Half-Hourly DataAggregator

HHDA

Half-Hourly Data Collector HHDC

Half-Hourly Metering HH Sites with a peak load above 100kW are equipped with "halfhourly" primary meters. This means that total consumption isrecorded every half hour and this information is automaticallyretrieved from the meter and passed to the energy supplier.

Industrial & CommercialCustomers

I&C

Initial Allocation andReconciliation Agent

IARA Profiles supplier consumption into half-hour values to calculateenergy purchases. This is part of the settlement process.

Initiating Supplier The supplier who raises a dispute over a change of suppliermeter reading or raises an erroneous registration notification,whether such supplier is old or new supplier.

Installed Base IBase Technical master data combining connection object, device,register, premise and Point of Delivery (POD).

Intercompany DataExchange

IDEX An add-on to Utilities Industry (SAP IS-U) component. It supportsthe established industry processes as part of the energyderegulation for the energy supply of metered metering pointsand unmetered sites. IDEX UK also supports the correspondingmarket communication according to the British market rules forthe market roles.

Intermediate Document IDoc Standard SAP format for electronic data interchange betweensystems.Different message types, for example, delivery confirmations orpurchase orders, normally represent the different specificformats, known as IDoc types. Multiple message types with

User Guide Customer




related content can be assigned to one IDoc type.

Line Loss Factor LLF As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Market Agent MA

Market Domain Data MDD

Market Domain Data Agent MDDA

Market Participant ID MPID

Market Participant RoleCode

MPRC

Master Data MD The information that remains the same over a long period of timein the system. Master data contains information that is neededoften and in the same form.

Master Data Generator Program that uses the master data template to create masterdata.

Master RegistrationAgreement

MRA Multilateral agreements for electricity.

Master RegistrationAgreement ServiceCompany (Gemserv)

MRASCo

Measurement Class MC The measurement class of a metering system, for example,above 100kW, below 100kW, remains unmetered.

Meter Asset Provider MAP

Meter Operator MO(P) Responsible for the installation, removal and maintenance ofmeters installed on a customer’s premise.

Meter Point AdministrationDetails

MPAD Details assigned to a metering point.

Meter Point AdministrationNumber (Core)

MPAN (Core) A 13-digit number (the bottom line of the supply number) madeup of the distributor identifier (first two digits), the company thatprovides the distribution network for the supply address. It is ameter point unique reference (11-digit number), which is linked tothe supply address.

Meter Point AdministrationService

MPAS The Meter Point Administration Service (MPAS) maintains arecord of all properties within its geographic area includingdetails of supplier, agents and key registration data items. It canbe defined as a market role performed by a system.

Meter Point Number MPN This is Meter Point Administration Number (MPAN) for electricity.

Meter Point RegistrationSystem

MPRS The Meter Point Registration System (MPRS) is owned by thedistribution companies. It contains all the MPANs for that


User Guide Customer




distribution area. It can be defined as a market role performed bya system.

Meter Reading MR As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Meter Reading on Changeof Supplier

MRoCoS The meter reading issued (D0086) as the initial meter reading forthe new supplier and the final meter reading for the old supplieron a change of supplier.

Meter Serial Number /Meter ID

MSN A 9 or 10-digit alphanumeric reference used in the UnitedKingdom (UK) to identify an electricity meter.

Meter Technical Details MTD All technical details, including outstation channel mapping, of ametering system required to enable metered data to be collectedand correctly interpreted from that metering system. This is asreferred to in BSCP20, BSCP502 or (as the case may be)BSCP504.

Meter Timeswitch Code MTC As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Meter Type MT As defined in the DTC. Indicates the type of meter - Half-Hourlyor Non-Half-Hourly. For more information, see the MRA site athttp://dtc.mrasco.com/Default.aspx.

Metered Supply Point MSP Point at which the meter measuring a customer's consumption islocated.

Metering Point MP As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Metering PointAdministration ServiceAgent

MPAS Agent BSC Terminology is Supplier Meter Registration Agent – SMRA

Metering System MS

Modification Change made to R/3 Repository objects for a particularcustomer.In the event of changes made by SAP, modified R/3 Repositoryobjects must be reviewed and, where necessary, adapted.

Move In Depends on the context, Move In process takes place as follows:

UK Industry: Move In is a sub process of the Change of Occupier(CoO) process. This includes the receiving and processing ofcustomer details, and special needs, as well as managing ofmeter reading of move in date and providing that information tothe relevant market participants.SAP IS-U: Move In is defined as a function including mostactivities that are required to start providing a business partnerwith a utility service. Among those activities are creation/changeof existing business master data, allocation of a contract to an





User Guide Customer




installation, establishing whether a contract can be billed,triggering the charges levied at the commencement of a utilityservice and sending a welcome letter to the customer.

Non-Half-Hourly DataAggregator

NHHDA

Non-Half-Hourly DataCollector

NHHDC

Non-Half-Hourly DataRetriever

NHHDR

Non-Half-Hourly Metering NHH Sites that take a power supply less than 100kW. Refers to meterequipment or data that is for a time period other than half hourly,normally monthly or longer.

Notice of Objection As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Notification of Old SupplierInformation

NOSI A DTC message in which the old supplier notifies the newsupplier of existing billing information.

Notification of Terminationof Registration

As defined in MRA Schedule 3 and the DTC. For moreinformation, see the MRA site athttp://dtc.mrasco.com/Default.aspx.

Objection Raising Period The period from and including the time that the notification to theold Supplier pursuant to Clause 15.9 is sent from the MPASregistration system to the relevant MPAS provider’s gateway upto but not including 18:00 hours on the fifth working daythereafter.

Objection ResolutionPeriod

The period from and including the time that the Messageconfirming that the Notice of Objection has been Accepted issent from the MPAS Registration System to the relevant MPASProvider’s Gateway up to but not including 18:00 hours on thefifth Working Day thereafter.

Opening Meter ReadProvider

Party Service Lines (120) PSL120

Performance AssuranceReporting and MonitoringSystem

PARMS The system established inter alia for the purpose of recordingand monitoring compliance by suppliers with their obligationspursuant to the BSC.

Persistence The technical term for permanently storing data, so that it stillremains after being used within a program.

Point of Delivery POD De-regulated Point of Delivery. Representation within SAP of anindividual utility connection to which a utility service is supplied,or for which a utility service can be determined. The POD is used



User Guide Customer




as a communication basis within the industry.

Point of Sale PoS

Post Office AddressFormat (Number +Postcode)

PAF Data file available from Royal Mail.Every house and business in the United Kingdom (UK) is given apostal address by Royal Mail. This address is used as a routinginstruction by Royal Mail staff to sort and deliver mail quickly andaccurately. However, it is not always a geographically accuratedescription of where a property is located.• Organization: Organization Name(60), Department Name(60)• Premise: Sub Building Name(30), Building Name(50), BuildingNumber(4)• Thoroughfare: Dependent Thoroughfare Name(60), DependentThoroughfare Descriptor(20), Thoroughfare Name(60),Thoroughfare Descriptor(20)• Locality: Double Dependent Locality(35), DependentLocality(35), Post Town(30)• Postcode: Postcode (7)• PO Box: PO Box (6)

Premise Enclosed spatial unit that is supplied with energy, such as anapartment or factory.

Process Code The second name for a specific processing type, such as for afunction module or an SAP Business Workflow task.Typically, a specific IDoc type is assigned a specific processcode. If you want to change the processing type of this IDoctype, you must assign the corresponding process code to thenew processing type at one place. Without the process code, youwould have to assign this IDoc type to the new processing typedirectly in several places.There are four types of process codes that correspond to theIDoc interface processing types: outbound, inbound, statusprocessing, system process codes for exception handling.

Processability Describing the characteristic of a data value, for example, ameter reading. This can be processed without causingexceptions.

Profile Administrator

Profile Class PC As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Rejected Rej/RJ Regarding validation of gas meter reading, the non-valid meterreading is "rejected". The equivalent for electricity is "failed". Theopposite is "valid". The equivalent for electricity is "rejected".In relation to a message or file, to reject such message or file onthe grounds that it does not comply with the relevant MPASvalidation procedures and “Rejection” shall be construedaccordingly. For the avoidance of doubt, rejection shall not


User Guide Customer




involve any subjective judgment by the MPAS provider.

Related Metering Points Related MPAN The following cases are considered:(a) Two or more metering points (other than export meteringpoints and pseudo metering points) that supply to the samecustomer and are located at the same (or any part of the same)premises, or(b) Two or more metering points (other than export meteringpoints and pseudo metering points) relating to unmeteredsupplies. The supply numbers attributable to them are statedwithin a single unmetered supplies certificate issued by thedistribution business.In either case, in circumstances where the charges applied forelectricity supplied through those metering points are mutuallyconditional.

Remote Function Call RFC Call of a function module that runs in a different system(destination) from the calling program. Connections are possiblebetween different AS ABAP systems as well as between an ASABAP and a non-SAP systems. In non-SAP systems, instead offunction modules, special programmed functions are called,whose interface simulates a function module. A distinction ismade between synchronous, asynchronous, and transactionalfunction calls. The called system is accessed via the RFCinterface.

Reports, Interfaces,Conversions,Enhancements and Forms

RICEF

Revenue ProtectionService

RPS

Sales Order SO The following options are considered:Option 1:A customer request to the company for delivery of goods orservices at a certain time.The request is received by a sales area that is then responsiblefor fulfilling the contract.Option 2: (valid for SOA)An agreement between an organization and a customer, wherethe organization agrees to supply a defined amount of productsfor an agreed price by a specified date.

SAP Business Workflow You use SAP Business Workflow (WebFlow Engine) to definebusiness processes that are not yet mapped in the SAP system.These may be simple release or approval procedures, or morecomplex business processes such as creating a material masterand the associated coordination of the departments involved.SAP Business Workflow is particularly suitable for situations inwhich work processes have to be run through repeatedly, or

User Guide Customer




situations in which the business process requires theinvolvement of a large number of agents in a specific sequence.You can also use Business Workflow to respond to errors andexceptions in other existing business processes. You can start aworkflow when predefined events occur, for example, an eventcan be triggered if particular errors are found during an automaticcheck.SAP provides several workflows that map predefined businessprocesses. These workflows do not require much implementationeffort.The Workflow Engine is a logical system (system and client) inthe transport domain in which the transport workflow runs. TheWorkflow Engine operates as a server that provides your entiretransport domain with the transport workflow functions.For more information, see the SAP Library athttp://help.sap.com/saphelp_nw04s/helpdata/en/95/4b45b4b04211d2a5f80060087a79ea/frameset.htm.

SAP CustomerRelationship Management

SAP CRM A comprehensive solution for managing your customerrelationships. It supports all customer-focused business areas,from marketing to sales and service, as well as customerinteraction channels, such as the Interaction Center, the Internet,and mobile clients. SAP CRM is part of SAP Business Suite.SAP CRM includes features and functions to support corebusiness processes in the following areas:• Marketing• Sales• Service• Partner Channel Management• Interaction Center• Web ChannelFor more information, see:• SAP Library athttp://help.sap.com/saphelp_crm60/helpdata/en/1a/023d63b8387c4a8dfea6592f3a23a7/frameset.htm• SAP Service Marketplace at http://www.service.sap.com/crm

SAP Enterprise ResourcePlanning

SAP ERP Redefines enterprise resource planning – delivering role-basedaccess to crucial data, applications, and analytical tools. WithSAP ERP, you can efficiently deal with business challenges inthe following areas:• End-user service delivery• SAP ERP Financials• SAP ERP Human Capital Management• SAP ERP Operations• SAP ERP Corporate Services• Performance managementFor more information, see the SAP Service Marketplace athttp://www.service.sap.com/erp.

http://help.sap.com/saphelp_nw04s/helpdata/en/95/4b45b4b04211d2a5f80060087a79ea/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/95/4b45b4b04211d2a5f80060087a79ea/frameset.htm

http://help.sap.com/saphelp_crm60/helpdata/en/1a/023d63b8387c4a8dfea6592f3a23a7/frameset.htm

http://help.sap.com/saphelp_crm60/helpdata/en/1a/023d63b8387c4a8dfea6592f3a23a7/frameset.htm

http://www.service.sap.com/crm

http://www.service.sap.com/erp

User Guide Customer




SAP Industry Solution forUtilities

SAP IS-U The SAP IS-U component is a sales and information system thatsupports all business processes and utility services of a utilitycompany. You can use SAP IS-U for managing and billingresidential, commercial and industrial, and prospectivecustomers. This component also allows you to manage and billcustomers who receive services, purchase goods, or pay feesand taxes.The main functions of SAP IS-U are as follows:• Customer Care and Service (SAP IS-U-CCS) is a solution thatmeets the requirements of customer information and billing• Energy Data Management (SAP IS-U-EDM) is a solution thatmeets the requirements of interval reading, schedulemanagement, and the billing of interval energy consumption• Work Management combines various SAP components andenhances them to include industry-specific functions forplanning, calculating, executing, and billing work orders• Waste and Recycling (SAP IS-U-WA) is a comprehensivelogistics, billing, service, and customer service system thatcovers all the business processes required by a waste disposalcompany• Intercompany Data Exchange (SAP IS-U-IDE) is a solution thatcovers the requirements that have arisen from the deregulationof energy markets.For more information, see the SAP Library athttp://help.sap.com/erp2005_ehp_03/helpdata/EN/c6/4dce68eafc11d18a030000e829fbbd/frameset.htm.

SAP Industry Solution forUtilities, Customer Careand Service

SAP IS-U-CCS The Customer Care and Service (SAP IS-U-CCS) is a solutionthat meets the requirements of customer information and billing.The main functions are as follows:• Basic Functions: Manage addresses and regional structures, aswell as generating dates and schedules for meter readings,billings, and budget billings.• Master Data: Manage data that remains fixed for long periodsof time. In SAP IS-U, this data includes the business partners,contracts and contract accounts, connection objects (buildingsand real estate) and the premises, installations, and devicelocations contained therein.• SAP IS-U Billing component is used for billing the followingstandard divisions: electricity, gas, water/waste water, districtheating, and multimedia services, for example, cable TV.• SAP IS-U Invoicing component enables you to group servicesand invoice them on one bill. You can also use the component tocalculate and charge fees and taxes.• Customer Service: you can use the front office to display alldata and start frequently used business processes. In Internet-Self-Services your customers can send you new data or changesto their existing data via the Internet. For example, they can grant

http://help.sap.com/erp2005_ehp_03/helpdata/EN/c6/4dce68eafc11d18a030000e829fbbd/frameset.htm


User Guide Customer




you collection authorization or register a move-in.For more information, see the SAP Library athttp://help.sap.com/erp2005_ehp_03/helpdata/EN/c6/4dce68eafc11d18a030000e829fbbd/frameset.htm.

SAP Industry Solution forUtilities, Energy DataManagement

SAP IS-U-EDM The Energy Data Management is a solution that fulfillsrequirements by offering interval reading, settlement of energyquantities, scheduling, and billing of interval energy consumption.The Energy Data Management (SAP IS-U-EDM) component isfully integrated into the SAP IS-U system and can be installed inan existing SAP IS-U system as a new component. SAP IS-U-EDM is also integrated into Intercompany Data Exchange (SAPIS-U-IDE). This component allows for data exchange instandardized formats and enables the integration of cross-company business processes. SAP IS-U-EDM allows you to billprofiles in SAP for Utilities. Profiles are prepared in SAP IS-U-EDM and transferred to SAP for Utilities billing via an internalinterface. This allows you to bill new types of contracts, such asspot purchases.SAP IS-U-EDM also interfaces with automated meter readingsystems.For more information, see the SAP Library athttp://help.sap.com/saphelp_utilities472/helpdata/en/81/a0023b288dd720e10000000a114084/frameset.htm.

SAP Industry Solution forUtilities, Intercompany DataExchange

SAP IS-U-IDE The Intercompany Data Exchange is a solution that meets thedemands of deregulated energy markets with the following mainfeatures:• Administration of Deregulation Data: Deregulation data includespoints of delivery, grids, point of delivery services and serviceproviders.• Process Management: Process management allows you totrigger processes for inbound communication: simple processessuch as changes to business partner master data, as well as acomplex workflow for processing enrolment. Outboundcommunication does not usually require complex processmanagement. Many existing SAP for Utilities processes triggeroutbound communication. For this reason, communicationevents have been created in the standard SAP for Utilitiessystem. These trigger communication in accordance with theCustomizing settings.• Processing Data Exchange ProcessesFor more information, see the SAP Library athttp://help.sap.com/saphelp_utilities472/helpdata/en/f5/7ce4382763855ee10000000a114084/frameset.htm.

SAP NetWeaver SAP NW A web-based, open integration and application platform thatserves as the foundation for enterprise service-orientedarchitecture (enterprise SOA) and allows the integration andalignment of people, information, and business processes across



http://help.sap.com/saphelp_utilities472/helpdata/en/81/a0023b288dd720e10000000a114084/frameset.htm

http://help.sap.com/saphelp_utilities472/helpdata/en/81/a0023b288dd720e10000000a114084/frameset.htm

http://help.sap.com/saphelp_utilities472/helpdata/en/f5/7ce4382763855ee10000000a114084/frameset.htm

http://help.sap.com/saphelp_utilities472/helpdata/en/f5/7ce4382763855ee10000000a114084/frameset.htm

User Guide Customer




business and technology boundaries. It utilizes open standardsto enable integration with information and applications fromalmost any source or technology. SAP NetWeaver is thefoundation of SAP Business Suite and SAP Business ByDesign,and also powers partner solutions and customer custom-builtapplications.Components:• SAP NetWeaver Application Server• SAP NetWeaver Business Intelligence• SAP NetWeaver Business Process Management• SAP NetWeaver Exchange Infrastructure• SAP NetWeaver Master Data Management• SAP NetWeaver Mobile• SAP NetWeaver Portal• SAP Auto-ID Infrastructure• SAP NetWeaver Identity ManagementFor more information, see the SAP Community Network athttp://scn.sap.com/community/netweaver.

SAP NetWeaver BusinessIntelligence

SAP NW BI The reporting, analysis and interpretation of business data is ofcentral importance to a company in guaranteeing its competitiveedge, optimizing processes, and enabling it to react quickly andin line with the market. With Business Intelligence (BI), SAPNetWeaver provides data warehousing functionality, a businessintelligence platform, and a suite of business intelligence toolswith which an enterprise can attain these goals. Relevantbusiness information from productive SAP applications and allexternal data sources can be integrated, transformed, andconsolidated in BI with the toolset provided. BI provides flexiblereporting, analysis, and planning tools to support you inevaluating and interpreting data, as well as facilitating itsdistribution. Businesses are able to make well-founded decisionsand determine target-orientated activities on the basis of thisanalysis.For more information, see:• SAP Library athttp://help.sap.com/saphelp_nw70/helpdata/EN/e3/e60138fede083de10000009b38f8cf/frameset.htm• SAP Service Marketplace at http://www.service.sap.com/bi

SAP NetWeaver Portal The portal offers a single point of access to SAP and non-SAPinformation sources, enterprise applications, informationrepositories, databases and services in and outside yourorganization, all integrated into a single user experience. Itprovides you the tools to manage and analyze this knowledge,and to share and collaborate on the basis of it. With its role-based content, and personalization features, the portal enablesusers, from employees and customers to partners and suppliers,to focus exclusively on data relevant to daily decision-making

http://scn.sap.com/community/netweaver

http://help.sap.com/saphelp_nw70/helpdata/EN/e3/e60138fede083de10000009b38f8cf/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/e3/e60138fede083de10000009b38f8cf/frameset.htm

http://www.service.sap.com/bi

User Guide Customer




processes.The main features are as follows:• Knowledge Management offers capabilities that everyone canuse to distribute, access, and manage unstructured informationwithin an organization through a heterogeneous repositorylandscape.• Collaboration brings users, information, and applicationstogether to ensure successful cooperation.• Guided Procedures offers a set of functions that enables abusiness expert to create reusable components and modelpeople-centric business workflows with them.For more information, see the SAP Library athttp://help.sap.com/saphelp_nw70/helpdata/EN/a4/76bd3b57743b09e10000000a11402f/frameset.htm.

SAP NetWeaver ProcessIntegration

SAP NW PI SAP NetWeaver Process Integration is an open integration andapplication platform that provides tools that enable you to createa service-oriented architecture for business applications(enterprise SOA).SAP NW PI supports the following key capabilities:• Enterprise Services Repository & Registry• Functions for the design, configuration, and execution ofintegration processes (process automation)• BAM infrastructure for handling events from applicationsystems in integration processes• Service Bus for exchanging messages in a heterogeneoussystem landscape• Infrastructure Services of SAP NetWeaver Application Server(ABAP and Java) on which SAP NetWeaver PI applications runFor more information, see:• SAP Library athttp://help.sap.com/saphelp_nwpi71/helpdata/en/c0/3930405fa9e801e10000000a155106/frameset.htm• SAP Community Network at http://scn.sap.com/community/pi-and-soa-middleware

Search and Classification TREX Search and Classification (TREX) provides SAP applications withnumerous services for searching, classifying, and text-mining inlarge collections of documents (unstructured data) as well as forsearching in and aggregating business objects (structured data).TREX processes documents in a wide variety of formats and inmore than 30 languages.For more information, see the SAP Library athttp://help.sap.com/saphelp_nw70/helpdata/EN/70/0837ced133304eba452c45b6047c74/frameset.htm.

Service Provider SP Company that offers one or more of the following services(service types): energy generation, energy sales, energy supply,energy transmission, energy distribution, meter installation andmaintenance, meter reading.

http://help.sap.com/saphelp_nw70/helpdata/EN/a4/76bd3b57743b09e10000000a11402f/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/a4/76bd3b57743b09e10000000a11402f/frameset.htm

http://help.sap.com/saphelp_nwpi71/helpdata/en/c0/3930405fa9e801e10000000a155106/frameset.htm

http://help.sap.com/saphelp_nwpi71/helpdata/en/c0/3930405fa9e801e10000000a155106/frameset.htm

http://scn.sap.com/community/pi-and-soa-middleware

http://scn.sap.com/community/pi-and-soa-middleware

http://help.sap.com/saphelp_nw70/helpdata/EN/70/0837ced133304eba452c45b6047c74/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/70/0837ced133304eba452c45b6047c74/frameset.htm

User Guide Customer




A service provider is uniquely allocated to a service type.

Service Type User-defined version of the service category predefined by SAP.It is possible to allocate several service types to a servicecategory.

Settlement Depends on the context, settlement takes place as follows:SAP: Comparison of energy supplied and energy used. Thebalance is communicated to the corresponding settlementcoordinator. For example, the actual or forecast consumption ofall points of delivery in a settlement unit can be grouped togetherfor settlement purposes.United Kingdom (UK): The determination and settlement ofamounts payable in respect of trading charges (includingreconciliation charges) in accordance with the Code (includeswhere the context admits volume allocation).

Settlement Day SD

Site Visit Check Code SVCC

Skeleton Record The initial record on the MPAS registration system for a meteringpoint that contains:(i) Supply Number core data(ii) Data item 6 of Schedule 2 for the metering point(iii) Data item 9 of Schedule 2 for the metering point(iv) Data item 15 of Schedule 2 for the metering point(v) Data item 18 of Schedule 2 for the metering point, whereapplicable; where data item 6 of Schedule 2 for the meteringpoint may be a default value

Small & MidsizedEnterprises

SME Small and medium enterprises or SMEs, also called small andmedium-sized enterprises and small and medium-sizedbusinesses or small and medium businesses or SMBs, arecompanies whose headcount or turnover falls below certainlimits.

Service ProviderAgreement

SP Agreement The agreement made between two participating serviceproviders regarding the processes necessary to supply energy toa point of delivery.

Standard Address File(PAF + street name, housenumber, and others)

SAF SAF means the completion of data items 9 and 9A of Schedule 2as below:• Metering Point Address Line 1 = Free Text• Metering Point Address Line 2 = Sub-building Name/Number• Metering Point Address Line 3 = MRA Version 9. 8 27 BuildingName/ Number• Metering Point Address Line 4 = Dependent Thoroughfare;• Metering Point Address Line 5 = Thoroughfare;• Metering Point Address Line 6 = Double Dependent Locality;• Metering Point Address Line 7 = Dependent Locality;• Metering Point Address Line 8 = Locality (Post Town);

User Guide Customer




• Metering Point Address Line 9 = County;• Metering Point Postcode = Postcode

Standard SettlementConfiguration

SSC As defined in the DTC. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Supplier Meter RegistrationService

SMRS The Supplier Meter Registration Service (SMRS) has thefollowing functions:• Provides suppliers with information relating to their MSIDs• Provides (Non) Half Hourly data aggregators with MSIDinformation• Receives and processes supplier data• Makes bulk change of Non Half Hourly supplier agents• Receives and processes licensed distribution system operatordata• Receives and processes market domain data• Enables transfers of registrations between SMRS and CMRS• Enables new connections where the same metering equipmentat an exemptible generating plant is comprised in both a SupplierVolume Allocation (SVA) metering system and a ContractVolume Aggregation (CVA) metering system, where exportactive energy is traded in CVA and import active energy is tradedin SVA

Supplier Volume Allocation SVA Non Half Hourly: Profiled consumption for each half hourHalf Hourly: Actual consumption for each half hour

Supplier Volume AllocationAgent

SVAA The main functions of the SVAA are:• Calculation of daily profiles• Execution of volume allocation runs (VAR)• Management of market domain data• Re-calculation of AFYC and EAC values• Provision of national help desk

Supply End Date SED The last inclusive settlement date of a supplier's registration to ametering system.

Supply Scenario Scenario for energy supply implemented in the system.Note that there are different supply scenarios for electricity andgas.

Supply Services Area As defined in the SLC 53B of the Electricity Supply License.

Supply Start Date / SupplySwitch Date

SSD As defined in the MRA. For more information, see the MRA siteat http://dtc.mrasco.com/Default.aspx.

Switch Document The document which controls and documents the IDEXprocesses in the system.

Switch View The view from which the change of supplier process isconsidered.

Time Based Debt Recovery TBDR



User Guide Customer




Transaction Reference Includes, amongst other data items, Customer Descriptor(J0559), PAN Number (J0525), or Key Meter Supplier/CustomerID (J0582) as appropriate to the Meter Type (J0483).

Unmetered SuppliesOperator

UMSO

Unmetered Supply UMS Supply of electricity to a particular inventory of apparatus, inrespect of which a licensed distribution system operator hasissued an unmetered supply certificate.

Valid V Regarding validation of electricity meter reading, the valid meterreading is "valid".The opposite of “valid” is "failed".

User Guide Customer



2 Intercompany data exchange for UKelectricity suppliers

2.1 Solution Overview

The intercompany data exchange for UK electricity suppliers is a solution to manage the flow of intercompanymessages that are exchanged each day between the various companies operating in the complex, deregulated UKutility market. For instance, when a customer moves from one supplier to another UK based provider, managing acustomer's changeover to a new utility is complex for all market participants involved in the switch process. The oldprovider must supply a great deal of information about the customer to the new one, such as account data, meterreadings and type of meter installed, among many other things. This information is delivered in market messages thatcan take many forms such as e-mails and data flows.

The solution enables an electricity supplier to automate message handling and to manage message exchangeeffectively. The end result is a well-managed, accelerated business processes.

The solution provides accurate message processing by handling them in the right time and the right sequence. Thesoftware enables the missing messages to be identified and located, and then sequenced in a correct order. Itdetects the corrupt data which are then routed to the SAP's Business Processes Exception Management toolkit.

The solution covers more than 50 industry processes within the UK electricity market such as Change of Supplier Winand Change of Supplier Loss among many others. The solution supports both household and commercial customersas metered and unmetered sites.

The solution provides the components for:

Process definition for all regulatory required processes for electricity from the view point of supplier role

Validations for messages and exceptions handling

Deadline monitoring according to the regulatory rules

Message inbound and outbound handling, including mapping and message parsing

The intercompany data exchange for UK electricity suppliers solution is build based on the process and data-exchange framework for utilities which is a generic solution to manage intercompany data exchange processes. Formore information, see the Configuration Guide for process and data-exchange framework for utilities.

User Guide Customer



3 Main Menu

The intercompany data exchange for UK electricity suppliers solution is built based on the process and data-exchange framework for utilities. To access the main SAP Easy Access menu for the process and data-exchangeframework for utilities solution, use the transaction code /IDXPF/MAIN. For more information, see the ConfigurationGuide for process and data-exchange framework for utilities.

To access the available features for intercompany data exchange for UK electricity suppliers solution, go to theCustomizing (transaction code SPRO) for intercompany data exchange for UK electricity suppliers under SAP Utilities

Intercompany Data Exchange Intercompany Data Exchange for UK Electricity Suppliers.

3.1 Introduction

The SAP Customizing Implementation Guide (IMG) contains the following Customizing activities:

Figure 1: Customizing Activities for IDEX UK

BAdI: Data Access

Use this IMG activity to create and manage the BAdI enhancements for accessing master data.

BAdI: Activate/Deactivate Process Document Data

Use this IMG activity to activate or deactivate the BAdI implementation /IDXUK/BADI_PROCESS_DOC_DBfor the BAdI definition /IDXPF/BADI_PROCESS_DOC_DB.

Map External Market Roles to Service Types

Use this IMG activity to map the roles of the external service provider IDs to internal service types. Thismapping allows you to determine the corresponding internal service provider in the system based on theexternal role received within the market message.

User Guide Customer



Maintain Meter Reading Tolerance Values

Use this IMG activity to maintain the meter reading tolerance values. When an IDoc is received, the systemfirst validates it by comparing the meter reading value in the IDoc with the tolerance value set in this IMGactivity and raises an exception accordingly if the meter reading value in IDoc exceeds the defined tolerance.

Assign Process IDs to Meter Reading Types

Use this IMG activity to define the reading types which are relevant for a process. You also maintain thepriorities for the meter reading types in cases where the same meter reading type can be used for multipleprocesses.

User Guide Customer



4 Scenario: Change of Supplier for aHalf-Hourly Metering Customer(Simple)

4.1 Introduction

The Change of Supplier (CoS) for a Half-Hourly Metering (METERED_HH) Customer (Simple)scenario is used as an example in this User Guide to show the functionalities available to you when using the contentprovided by the solution.

4.2 Details and Execution

The example scenario represents a CoS Gain process where the new supplier triggers a registration request on aD0055 to the metering point administration service (MPAS). The MPAS can now either reject the registration requestby triggering a D0057 to return it to the new supplier or by sending a D0217 to confirm the registration.

In case the registration is rejected, the supplier may resend the registration request. Upon receipt of a registrationconfirmation, the new supplier triggers a master data validation, initiates the Agent Appointment process, andcalculates the objection window where a registration objection can be received. Due to a mismatch during the masterdata validation, the system triggers a master data update in SAP IS-U. For the CoS Gain process, the D0217 is alsofollowed by the D0260 which is received from the old supplier.

Once the meter operator (MOP) has accepted the agent appointment on a D0011, the MOP will send the metertechnical details via the D0268 to the new supplier. The new supplier then triggers a master data update in SAP IS-Uto install the meter details in the system. Once the meter is successfully installed, the CoS Gain process iscompleted.

The following figure depicts the process flow for the CoS Gain process. The overview and details of each processstep included in this scenario are provided with the step-by-step procedure in the following sub-chapters.

User Guide Customer



Figure 2: CoS Gain Process - Process Flow

User Guide Customer



4.3 Running the CoS Gain Process

4.3.1 Trigger the CoS Gain Process

4.3.1.1 Overview

To trigger the process from applications other than the SAP CRM, for example, SAP ERP Service Order, ExceptionResolution and so on, and to create the IDEX process document, the generic method START_PROCESS of the class/IDXPF/CL_PROCESS_TRIGGER is used.

Figure 3: Process Trigger Method

4.3.1.2 Details

The process step runs as follows:

1. As a starting point, a process document (PDoc) has been created.

2. The system creates the process step 100 to kick off the process.

3. The system creates the process step 110 to check the metered or unmetered scenario.

4. The system creates the process step 120 to send the outbound IDoc (D0055).

5. As a result, an IDoc (D0055) is created.

User Guide Customer



4.3.2 Step 120: Send the CoS Registration Request(D0055)

4.3.2.1 Overview

When the supplier sends a CoS registration request to a distribution system operator (DSO), this step waits for aresponse from the DSO.

4.3.2.2 Details

To send the CoS registration request, follow the procedure below:

1. Execute the transaction code /IDXPF/PDOCMON01.

2. Enter the ID of the PoD that has been created as part of the prerequisites described in the chapter 1.2.

3. Choose Execute.

The system displays the process document (PDoc) on your screen as follows:

Figure 4: Process Document (PDoc)

A CoS Gain PDoc for the process ID 1100 has been created. This PDoc displays the three process steps thatshow a successful outbound process flow D0055.

The last step (120 in the Figure 4 above) is an outbound step with an IDoc reference that is displayed in the Iconname column either as IMPORT or EXPORT icon as follows:

User Guide Customer



Figure 5: DATEX Reference

4. The IMPORT or EXPORT icon enables you to directly jump to the Monitoring of Data Exchange Tasks report(transaction code EDATEXMON01) which gives you an overview about the status of the outbound IDoc.

Figure 6: Monitoring of Data Exchange Tasks

5. Click on the Step No. 120 to navigate to the step data container.

Figure 7: Step Data Container with Additional Data

The step data container is filled with all relevant data that was used to create and fill the outbound IDoc. The datawithin the step data container is grouped. For each data group such as MPAN data or meter data, a specific tabpage is provided.

User Guide Customer



4.3.3 Step 130: Receive the CoS Registration Rejection(D0057)

4.3.3.1 Overview

A registration request rejection (D0057) by the metering point administration service (MPAS) is sent, it is received,but not accepted by the supplier. The process steps are repeated and the registration request (D0055) is sent again.

4.3.3.2 Details


1. As a starting point, an inbound IDoc (D0057) has been created.

2. The system creates the process step 120 to handle the inbound IDoc.

3. The system executes the response code validation.

4. The system triggers the registration request again.

The step data in the PDoc looks as follows:

Figure 8: Process Step No. 120 (repeated)

The step 120 is created for the second time which results in sending another registration request. The status ofthe previous steps 120 and 130 are set to obsolete/reversed.

User Guide Customer



5. Upon receipt of a registration rejection, the system performs a response code validation (rejection reason code:J0107). For certain response codes, for example, 98, the system automatically repeats the process step 120 tosend the registration request again.

Figure 9: Response Code Validation

4.3.4 Step 200: Receive the CoS RegistrationConfirmation (D0217)

4.3.4.1 Overview

A registration request confirmation (D0217) is received from the metering point administration service (MPAS) andaccepted by the new supplier. The process now moves on to execute the inbound validations for the data which hasbeen received.

User Guide Customer



4.3.4.2 Details


1. As a starting point, an inbound IDoc (D0217) has been received.


3. You look up the process document (PDoc) which you have created in the chapter 4.3.1 using the transactioncode /IDXPF/PDOCMON01.


Figure 10: Receive Registration Confirmation (D0217)

4. This PDoc displays a new process step 200. When an inbound message is received, the system removes themessage data and fills the step data container accordingly.

Figure 11: Step Data Container after IDoc Inbound Processing

5. Upon receipt of the D0217, the system performs the inbound validations where the data received is validatedagainst the data held in the system. The status of step No. 200 is shown as Completed with warnings whichindicates a data mismatch. The validations which have been performed during the inbound processing aredisplayed on the FRW: Check results tab page as follows:

User Guide Customer



Figure 12: Display Validation Results

6. For master data comparison a generic check ID /IDXPF/MTD is used (see the check No. 30 in the Figure 12above). This check No. validates the data received against the data held in the system. The data items whichhave been validated are shown in the FRW: MTD check results tab page as follows:

User Guide Customer



Figure 13: Master Data Comparison

7. The CompValue (master data compare value) column is filled with the data from the SAP IS-U tables. TheSrcValue (master data source value) column shows the data which has been received. As there is a mismatch,the Outcome Code is filled with ERROR_CONT and as a result the step status is updated to completed withwarnings (see the Activities tab page below).

Along with an Outcome Code, a Process Value is created which is used later on as a step trigger condition (seethe chapter 4.3.5). Due to the mismatch, the Excp. Code (exception code) column is also filled with PCmismatchand as a consequence the system creates a clarification case (BPEM) as follows:

User Guide Customer



Activities tab page:

Figure 14: Activity Monitor - Business Exception created

Exceptions tab page:

Figure 15: Exception Monitoring

8. The Exceptions tab page details the exceptions created during the PDoc processing. The Step No. indicates theprocess step for which the exception is created. The intercompany data exchange for UK electricity supplierssolution allows you to access the BPEM case for further processing from the PDoc. If you click on the number inthe Case column, the system navigates you directly to the clarification case attribute as follows:

User Guide Customer



Figure 16: Clarification Case

4.3.5 Step 210: Update the Registration Data (D0217)

4.3.5.1 Overview

A registration request confirmation (D0217) is received from the metering point administration service (MPAS) andthe inbound validations (master data comparison) have failed due to the data mismatch, and as a result the processvalue SYS_DATA_UPD is filled.

Due to this process value, the Cos Gain process now triggers a system data update in SAP IS-U to synchronize thedata with the MPAS.

4.3.5.2 Details


1. As a starting point, the CoS Gain registration confirmation (inbound IDoc) is received.

2. The system executes the master data comparison.

3. The system identifies the profile class mismatch.

4. The system fills the process value SYS_DATA_UPD.

5. As a result, the system creates the process step 210 to update the profile class.

User Guide Customer




Figure 17: Process Step 210 to Update SAP IS-U

4.3.6 Step 230: Create the Objection Window

4.3.6.1 Overview

Upon receipt of a registration request confirmation (D0217), this process calculates the objection window to receivean objection on the D0067. The objection raising window is determined based on the calculation formula “DeemedReceived Date + X days".

4.3.6.2 Details



2. The system creates the process step 230 to open the objection window.


User Guide Customer



Figure 18: Deadline Monitoring

The process step 230 sets a date in the Deadline column. That means that an objection (D0067) can be receivedwithin this period.

4.3.7 Step 260: Create the Services at MPAN

4.3.7.1 Overview

Upon receipt of a registration request confirmation (D0217), this process triggers an update in SAP IS-U to createservices for the metering point administration service (MPAS) and the distributor that start from the effective date.

4.3.7.2 Details



2. The system creates the process step 260 to open the objection window.


User Guide Customer



Figure 19: Create Services for MPAS and Distributor at MPAN

4.3.8 Step 870: Check for the Agent Appointment

4.3.8.1 Overview

After receiving a valid D0217, this process checks whether the agent appointment processes are required.

4.3.8.2 Details



2. The system creates the process step 870 to check if the agents are appointed.


User Guide Customer



Figure 20: Check for Agent Appointment

The process step 870 is configured as a check step. The purpose of this step is to make a decision whether theagent appointment is going to be triggered. Based on the check results, the system determines if the agentappointment is required.

Figure 21: Agent Appointment Process Values

User Guide Customer



4.3.9 Step 1100/1110/1120: Trigger the AgentAppointment for MOP/DC/DA

4.3.9.1 Overview

The process step 870 is used as a decision step to check whether the agent appointment is required. Since theprocess values for the step 870 have been filled with meter operator (MOP), data collector (DC) and data aggregator(DA), the CoS Gain process now triggers the agent appointment for all three agents by sending D0153 or D0155.

4.3.9.2 Details


1. As a starting point, the system checks whether the agent appointment has been executed.

2. The system fills the process values for agent appointment check with MOP, DC and DA.

3. The system creates the process steps 1100, 1110 and 1120 to trigger the agent appointment for MOP, DC andDA.

4. The system triggers the meter operator agent appointment (child process).

5. The system triggers the data collector agent appointment (child process).

6. The system triggers the data aggregator agent appointment (child process).


User Guide Customer



Figure 22: Trigger Agent Appointment

This PDoc displays the three new process steps used as triggering steps for the agent appointment processes.

To view the associated (child) processes, you can look up the Add. header data tab page under the Process linkssection.

User Guide Customer



Figure 23: Display Associated Processes

The Process links section shows the three new processes created for agent appointment. For each agent adistinct PDoc is created. By clicking the number in the Proc. Ref (process reference) column, you can navigate tothe corresponding PDoc directly.

All agent appointment related activities, for example, sending D0153 or D0155, receiving D0011 and so on, arehandled within the corresponding child PDocs rather than in the CoS Gain (parent) PDoc.

4.3.10 Step 220: Receive the Old Supplier's RegistrationDetails (D0260)

4.3.10.1 Overview

For the CoS Gain process, the D0217 is followed also by the D0260.

User Guide Customer



4.3.10.2 Details


2. The system receives the inbound IDoc (D0260).

3. The system creates the process step 220 for the inbound IDoc.


Figure 24: Receive Old Supplier's Registration Details

This PDoc displays a new process step 220 which represents the D0260 inbound message.

4.3.11 Step 1130/1140: Notification of the Change toOther Parties (D0148)

4.3.11.1 Overview

The receipt of the D0011 triggers the process for sending the D0148 to the meter operator (MOP) and the datacollector (DC).

User Guide Customer



4.3.11.2 Details


1. The system receives the D0011 for meter operator appointment.

2. The system receives the D0011 for data aggregator appointment.

3. The system receives the D0011 for data collector appointment.

4. A D0011 has been received for all the three agent appointment processes. As a result, the system creates theprocess step 1130.

5. The system creates the process step 1140 to trigger the D0148 flow to MOP and DC.

6. As a result, the system triggers the notification of change to other parties (child process).


Figure 25: Step Type "Process Trigger"

This PDoc displays the two new process steps 1130 and 1140. The process step 1130 is created because thesystem creates a D0011 for all the agent appointment processes. As a result the system has created the processstep 1140. This step is used to trigger the associated child processes. A new PDoc has been created for theD0148 outbound processing.

7. To view the new PDoc created, you look up the Add. header data tab page under the Process links section.

User Guide Customer



Figure 26: Child Process for D0148 Out Processing

8. By clicking the number in the Proc. Ref (process reference) column, you can navigate to the new D0148 PDoc asfollows:

User Guide Customer



Figure 27: Process Document (PDoc) for D0148 Processing

This PDoc is created as an associated PDoc for the CoS Gain process to handle all activities related to theD0148 outbound processing.

4.3.12 Step 1410: Receive the Meter Technical Details(D0268)

4.3.12.1 Overview

Once the meter operator (MOP) has accepted the agent appointment on the D0011, the MOP sends the metertechnical details on the D0268.

4.3.12.2 Details


1. As a starting point, the D0011 has been received for meter operator appointment.

2. The system creates an inbound IDoc (D0268).

3. As a result, the system creates the process step 1410 to handle the inbound IDoc.


User Guide Customer



Figure 28: Process Step 1410 to receive Meter Technical Details

This PDoc displays a new process step 1410 to handle the IDoc inbound processing. When the inboundmessage is received the system removes the message data and fills the step data container accordingly.

User Guide Customer



Figure 29: Master Data Comparison: Validate Meter Technical Details

Upon receipt of the D0268 the system performs the inbound validations where the meter technical detailsreceived are validated against the meter data installed in the system. The FRW: Check results tab page and theFRW: MTD check results tab page indicate which validations have been performed.

For the field OUTSTATION_TYPE, a mismatch has been identified (see the MD Source Value and the MDCompare Value columns) and as a consequence the process value SYS_DATA_UPD is raised. This processvalue is now used as a condition to trigger a system update in SAP IS-U.

4.3.13 Step 1420: Update the System Data with MeterTechnical Details

4.3.13.1 Overview

The meter technical details have been received from the meter operator (MOP) on the D0268 and then the systemtriggers an update to install the meter in SAP IS-U.

User Guide Customer



4.3.13.2 Details


1. As a starting point, the meter technical details (inbound IDoc D0268) have been received.

2. The system executes the master data comparison.

3. The system identifies the master data mismatch.

4. The system fills the process value SYS_DATA_UPD.

5. As a result, the system creates the process step 1420 to update the meter technical details.


Figure 30: Process Step 1420 to update Meter Technical Details in SAP IS-U

4.3.14 Step 9900: Complete the CoS Gain Process

4.3.14.1 Overview

Once the meter technical details are setup in the system and the corresponding process step is completed, thesystem completes the CoS Gain process by closing the process document (PDoc).

4.3.14.2 Details


1. As a starting point, the meter technical details have been installed.

User Guide Customer



2. There are no outstanding data flows in the system.

3. The system creates the process step 9900 to complete the PDoc.


Figure 31: Complete Process Document

The process is completed and the status of the PDoc is set to completed accordingly.

User Guide Customer



5 Scenario: Change of Supplier for aHalf-Hourly Metering Customer withObjection

5.1 Introduction

The Change of Supplier (CoS) for a Half-Hourly Metering (METERED_HH) Customer withObjection scenario is used as an example in this User Guide to show the functionalities available to you whenusing the content provided by the solution.

5.2 Details and Execution

The example scenario represents a CoS Gain process where the new supplier receives an objection from themetering point administration service (MPAS) after the registration request has been confirmed.

The new supplier triggers a registration request on a D0055 to the metering point administration service (MPAS). TheMPAS agent confirms the request by sending a D0217 back to the new supplier.

Upon receipt of the registration confirmation the new supplier triggers the agent appointment process to appoint thesupplier agents and calculates the objection window where a registration objection can be received. For the CoSGain process, the D0217 is also followed by the D0260 received from the old supplier.

There are a couple of reasons why an objection could be triggered. One of the reasons could be that there is still acontract between the old supplier and the customer, and therefore the old supplier initiates the objection process withthe metering point administration service (MPAS) and the MPAS triggers a D0067 to the new supplier. As aconsequence the objection raising window is closed and the process creates an objection resolution window. Withinthe objection resolution window the new supplier expects to receive either a D0091 for objection removal or a D0093to upheld objection. Along with creating the objection resolution window, the new supplier triggers the agent de-appointment processes for meter operator (MOP), data collector (DC) and data aggregator (DA).

Finally the objection is removed by receiving a D0091 from MPAS and the objection resolution window is closed.Since the objection is removed the new supplier triggers the agent appointment process again to appoint the supplieragents MOP, DC and DA.

Once the meter operator (MOP) has accepted the agent appointment on a D0011, the MOP will send the metertechnical details via the D0268 to the new supplier. The new supplier then triggers a master data update in SAP IS-Uto install meter details in the system. Once the meter is successfully installed, the CoS Gain process is completed.

User Guide Customer



The following figure depicts the process flow for the CoS Gain process with objection. The overview and details ofeach process step included in this scenario are provided with the step-by-step procedure in the following sub-chapters.

User Guide Customer



Figure 32: CoS Gain Process with Objection - Process Flow

User Guide Customer



5.3 Running the CoS Gain Process with Objection

This CoS Gain process focuses on the objection flow which may be received from the metering point administrationservice (MPAS), if the old supplier has objected to the change of supplier.

The following sub-chapters describe the functionalities available to receive an objection flow (D0067) as well as thestep-by-step procedures for how to handle the received objection.

The baseline for this CoS Gain process with objection is the CoS Gain process (simple) described in the chapter 4.3with the following process steps:

Trigger the CoS Gain Process

Send the CoS Registration Request

Receive the CoS Registration Rejection

Receive the CoS Registration Confirmation

Update the Registration Data

Create the Objection Window

Create the Services at MPAN

Check for the Agent Appointment

Trigger the Agent Appointment for MOP/DC/DA

Receive the Old Supplier's Registration Details

Notification of Change to Other Parties

Receive the Meter Technical Details

Update the System Data with Meter Technical Details

Complete the CoS Gain Process

For more information, see the chapter 4 Scenario: Change of Supplier for a Half-Hourly Metering Customer (Simple).

The figure for the CoS Gain process with objection (see the Figure 32) has the same process steps as the simpleCoS Gain process that are listed above. In addition there are seven new processes listed below (highlighted in bold)to handle the objection related activities:

Trigger the CoS Gain Process

Send the CoS Registration Request

Receive the CoS Registration Rejection

Receive the CoS Registration Confirmation

Update the Registration Data

Create the Objection Window

Create the Services at MPAN


Trigger the Agent Appointment for MOP/DC/DA

User Guide Customer



Receive the Old Supplier's Registration Details

Notification of Change to Other Parties

Receive the Registration ObjectionSet the Deadline for Objection Resolution

Trigger the Agent De-Appointment for MOP/DC/DA

Update the Services at Supply ScenarioReceive the Registration Objection Removal


Trigger the Agent Appointment for MOP/DC/DA Notification of Change to Other Parties




The process steps which are highlighted in bold above are the ones related to the objection management. Theoverview and details of these process steps are provided with the step-by-step procedure in the following sub-chapters.

5.3.1 Starting Point for Handling the Objection

5.3.1.1 Overview

The following process steps have been already performed as part of the (simple) CoS Gain process:

1. Trigger the CoS Gain Process

2. Send the CoS Registration Request

3. Receive the CoS Registration Confirmation

4. Update the Registration Data

5. Create the Objection Window

6. Create the Services at MPAN

7. Check for the Agent Appointment

8. Trigger the Agent Appointment for MOP/DC/DA

9. Receive the Old Supplier's Registration Details

10. Notification of Change to Other Parties

User Guide Customer



5.3.1.2 Details


Figure 33: Process Document (PDoc)

5.3.2 Step 600: Receive the Registration Objection(D0067)

5.3.2.1 Overview

There are several reasons why an objection could be triggered. One of the reasons could be that there is still acontract between the old supplier and the customer, and therefore the old supplier initiates the objection process withthe metering point administration service (MPAS). As a consequence the MPAS triggers a D0067 to the new supplier.

5.3.2.2 Details




User Guide Customer



3. The system closes the objection window.


Figure 34: Notification of an Objection to Change of Supplier Sent to the New Supplier

This PDoc displays a new process step 600 which represents the D0067 inbound message. With regard to theobjection window which is created when the registration request is triggered, the system has cancelled thecorresponding deadline (see the step No. 230 in the Figure 34 above) as the objection has been received.

5.3.3 Step 610: Set the Deadline for ObjectionResolution

5.3.3.1 Overview

Upon receipt of a registration objection (D0067) the process calculates the objection resolution window to receiveeither a D0091 or a D0093 that is to be used to upheld or reject the objection.

5.3.3.2 Details


User Guide Customer



1. The system receives the CoS Gain registration objection (inbound IDoc).

2. The system creates the process step 610 to calculate the objection resolution window.


Figure 35: Objection Resolution Window

This PDoc displays a new process step 610 which is a deadline step. The objection resolution window iscalculated based on the calculation formula “Deemed Received Date + X days".

5.3.4 Step 810/820/830: Trigger the Agent De-Appointment for MOP/DC/DA

5.3.4.1 Overview

Upon receipt of a registration objection (D0067) the CoS Gain process triggers the agent de-appointment for all thethree supplier agents by sending a D0151.

User Guide Customer



5.3.4.2 Details



2. The system creates the process steps 810, 820 and 830 to trigger the agent de-appointment for MOP, DC andDA.

3. The system triggers the meter operator agent de-appointment (child process).

4. The system triggers the data collector agent de-appointment (child process).

5. The system triggers the data aggregator agent de-appointment (child process).

6. The system updates the child process of meter operator agent appointment and sets the status to obsolete.

7. The system updates the child process of data collector agent appointment and sets the status to obsolete.

8. The system updates the child process of data aggregator agent appointment and sets the status to obsolete.


Figure 36: Agent De-Appointment

This PDoc displays the three new process steps used as triggering steps for the agent de-appointmentprocesses.

User Guide Customer



To view the associated processes, you can look up the Add. header data tab page under the Process linkssection.

Figure 37: Associated Agent De-Appointment PDocs

The Process links section shows the three new processes created for agent de-appointment. For each agent adistinct PDoc is created. By clicking the number in the Proc. Ref (process reference) column, you can navigate tothe corresponding process document directly.

Figure 38: Agent Appointment PDocs are obsolete

9. As a result, the agent appointment processes created previously during the registration confirmation flow havebeen cancelled.

User Guide Customer



5.3.5 Step 860: Update the Services at Supply Scenario

5.3.5.1 Overview

When the agent de-appointment is triggered as a result of a registration objection, the CoS Gain process updates theSAP IS-U to remove the supplier agents from the MPAN.

5.3.5.2 Details



2. The system triggers the agent de-appointment for all three supplier agents.

3. The system creates the process step 860 to update the services at supply scenario.


Figure 39: Remove Supplier Agent Services from MPAN

User Guide Customer



5.3.6 Step 700: Receive the Registration ObjectionRemoval (D0091)

5.3.6.1 Overview

The metering point administration service (MPAS) notifies the new supplier that the old supplier has removed theobjection and the change of Supplier (CoS) can move forward.

5.3.6.2 Details



2. The system opens the objection resolution window.


4. The system creates the process step 700 to handle the thee inbound IDocs.

5. The system closes the objection resolution window.


Figure 40: Receive Registration Objection Removal

User Guide Customer



5.3.7 Step 870: Check for the Agent Appointment

5.3.7.1 Overview

If the objection is removed within the objection resolution window by receiving a D0091 from the metering pointadministration service (MPAS), the system checks whether the supplier agents are required to be appointed.

5.3.7.2 Details


1. As a starting point, the CoS Gain registration objection (inbound IDoc) has been received.

2. The system receives the notification of removal for the registration objection (inbound IDoc).

3. The system creates the process step 870 to check if the agents are appointed.


Figure 41: Check for Appointed Agents

The process step 870 is configured as a check step. The purpose of this step is to make a decision whether theagent appointment is going to be triggered. Based on the check results, the system determines if the agentappointment is required.

User Guide Customer



Figure 42: Process Values for Agent Appointment check

5.3.8 Step 1100/1110/1120: Trigger the AgentAppointment for MOP/DC/DA

5.3.8.1 Overview

The process step 870 is used as a decision step which checks whether an agent appointment is required. Since theprocess values for the step 870 have been filled with meter operator (MOP), data collector (DC) and data aggregator(DA), the CoS Gain process now triggers the agent appointment for all three agents by sending a D0153 or D0155.

5.3.8.2 Details


User Guide Customer



1. As a starting point, the system checks whether the agent appointment has been executed.

2. The system fills the process values for agent appointment check with MOP, DC and DA.

3. The system creates the process steps 1100, 1110 and1120 to trigger the agent appointment for MOP, DC andDA.

4. The system triggers the meter operator agent appointment (child process).

5. The system triggers the data collector agent appointment (child process).

6. The system triggers the data aggregator agent appointment (child process).


Figure 43: Trigger Agent Appointment after Objection Removal

This PDoc displays the three new process steps used as triggering steps for the agent appointment processes.

To view the associated (child) processes, you look up the Add. header data tab page under the Process linkssection.

User Guide Customer



Figure 44: Associated PDocs for Agent Appointment

The Process links section shows the three new processes created for agent de-appointment. For each agent adistinct PDoc is created. By clicking the number in the Proc. Ref (process reference) column, you can navigate tothe corresponding process document directly.

As a result, the status of the agent de-appointment processes created during the objection handling has been setto obsolete.

Figure 45: Agent De-Appointment PDocs with Obsolete Status

User Guide Customer



5.3.9 Finalize the CoS Gain Process with Objection

5.3.9.1 Process Overview

The following process steps have been already performed:




5.3.9.2 Process Details


Figure 46: CoS Gain PDoc with Completed Status

intercompany data exchange for uk electricity suppliers 1 · 2 intercompany data exchange for uk...

Documents