Point of Delivery (PoD) 

Definition

Point to which a utility service is supplied, or for which a utility service can be determined.

Use

A point of delivery can be identified by a unique key, called the point of delivery ID. This key is used for communication with external systems. It ensures that, for example, misunderstandings and incorrect data allocations can be avoided, even if a customer switches utility companies.

Structure

Communication Types

There are two communication types:

·        Communication in the deregulated energy market

This refers to communication between different utilities in a deregulated energy market. For example a distributor may exchange consumption information with a supplier.

A distributor has measured the consumption of a point of delivery (customer’s consumption in a given installation) and uses the point of delivery ID to send this information to the customer’s supplier. The supplier then bills the customer based on the consumption data.

·        Technical Communication

Refers to communication with an automated meter reading system (AMR), for example. This type of communication is used in the Energy Data Management component (IS-U-EDM) for importing profile values.

An AMR sends information on the measured load shape using the point of delivery ID (and the register code of the register) to IS-U-EDM.

Point of Delivery Roles

When you define a point of delivery, you can assign it one of the following roles:

·        Deregulation point of delivery

When you create an installation, the system automatically creates a deregulation point of delivery, to which you can allocate a point of delivery ID.

If you require a point of delivery for communication in a deregulated energy market then you must define it as a deregulation PoD. You can allocate a deregulation point of delivery to one or two installations. If you allocate two installations (dual contract model), ensure that the same devices (registers and so on) have been installed for billing purposes in both installations. A deregulation point of delivery can be allocated to one installation only. However, several technical points of delivery can be allocated to the same installation.

·        Technical point of delivery

You require a technical point of delivery in the following cases:

¡        You require a point of delivery for technical communication with systems that do not use the point of delivery ID common to the respective market.

¡        You require a point of delivery for technical communication with systems whose measurement systems do not conform to market requirements, such as a device that measure several points of delivery.

You can allocate logical registers or installations to a technical point of delivery. If you do this, the allocation applies to all the registers contained in the installation.

A technical point of delivery distinguishes between the following point of delivery categories:

§         Normal point of delivery category

§         Virtual point of delivery category

A virtual point of delivery category is a summary of several normal point of delivery categories. For example, the virtual point of delivery category can summarize the consumption of the normal point of delivery categories.

In Customizing, you define point of delivery types  and allocate these to the SAP predefined point of delivery categories.

Integration

The graphic below depicts the integration of the point of delivery in the IS-U data model.

The data model for the point of delivery is integrated in the following tables:

The individual tables have the following functions:

Table	Function
EUIHEAD	Definition of the point of delivery
EUITRANS	Link between point of delivery and point of delivery ID
EUIGRID	Link between point of delivery and grid
EEDMUISETTLUNIT	Link between point of delivery and settlement unit
EUILZW	Required for technical points of delivery Link between point of delivery and register
EUIINSTLN	Required for deregulation points of delivery Link between point of delivery and installation

For more information on the role of the point of delivery in Intercompany Data Exchange (IDE), see  point of delivery.

Application Examples

The following examples use selected processes to indicate when you must use a deregulation point of delivery and a technical point of delivery.

·        Example 1: Installation with Load Shape Measurement for Watt-Hour and Reactive Consumption

·        Example 2: Installation with Load Shape Measurement for Watt-Hour and Reactive Consumption, as well as Check Reading for Watt-Hour Consumption

Point of Delivery Transaction

You find the point of delivery transactions Create/Change/Display in the Easy Access Menu under Technical Master Data ® Point of Delivery.

The following information describes the individual fields and tab strips.

Group Box for PoD Description

The individual fields have the following functions:

Field/Symbol	Function
History	Enables you to display different histories
Header data	Enables you to return from times slice display to the normal view
New time slice	You cannot enter data in the To field. To restrict the validity of the point of delivery ID, insert a new time slice. To do this, choose New Time Slice. In the From Day field, enter the date and time at which you want the new time slice to become valid. The previous time slice finishes on the start date of the new time slice.
Default value	If you use the Metering Code structure category, you can generate a consecutive number for the point of delivery ID. To do this, choose the Default Value entry in the Consecutive Number field.
Valid to	Validity period for the PoD ID
Structure category	The system automatically proposes the structure category defined in Customizing as the default value (Master Data ® Point of Delivery ® Define Structure of Point of Delivery ID).
Fields of the PoD ID	Various fields are shown depending on the structure category you selected

Header Tab Strip

Field	Function
PoD Description	Text that describes the point of delivery
Point of delivery type	Enables you to select one of the point of delivery types defined in Customizing. You define point of delivery types in the IMG under SAP Utilities ® Master Data ® Point of Delivery Define Point of Delivery Type.
PoD role Technical PoD Deregulation PoD	See the Point of Delivery Roles unit

Grid tab strip

Field/Symbol	Function
Date From	Period for which the grid is allocated to the point of delivery
Date To
Date	You can restrict the period for which the grid is allocated to the point of delivery
Grid	Grid that you create beforehand in the Intercompany Data Exchange menu
Distributor	The system automatically displays the distributor allocated to the grid, provided you have allocated a distributor in the Intercompany Data Exchange menu under Grid.
Copy	Choose Copy to copy your entries to the list

Origin tab strip

The Origin tabstrip is for information purposes only. The entries you make here have no effect on the function.

You can define source systems and number ranges for sources systems in Customizing under Tools   System Modifications User-Defined Functions for Energy Data Management Source Systems.

Allocation tab strip

Field/Symbol	Function
Valid to	Validity period for allocation
Date	You can restrict the validity period for the allocation.

Register and Installation tabstrips

To allocate the point delivery to a register, choose Register and enter a device, material, register, or piece of equipment.

You can also allocate the point of delivery to an installation. This allocation applies to all the registers allocated to the installation. To do this, choose the Installation tabstrip and enter the installation to which you want to allocate the point of delivery.

Settlement tab strip

On this tab strip, the settlement units are displayed. These automatically originate from the combination of services for the point of delivery.

However, you can also manually allocate the point of delivery to a settlement unit. To do this, choose   Allocate Sett. Unit Manually. A dialog box appears in which you can use the F4 help to enter the required settlement unit in the Settlement Unit field.

In the list on the tab strip you can recognize the settlement units to which the point of delivery was manually allocated by the Manual field.

To delete a manual allocation, choose    Delete Sett. Unit Manually..

To change the settlement relevance, choose Sie    Change Settlement Relevance. A dialog box appears in which you can change the date and select or deselect the Settle field. If the field is selected, the consumption for the current point of delivery is taken into account when the settlement unit is settlement for the given period.

In the list on the tab strip, you can establish the settlement relevance of the point of delivery using the Settlement field.

PoD Service tab strip

Once a move-in has taken place for the installation, to which this POD is allocated, all the services for this POD are displayed.

You must have defined the default mechanisms in the IDE menu under Services.

Service on the Basis of the Operational Area or Services on the Basis of Service Provider Relationships.

You define the default mechanism to be used in Customizing under SAP Utilities ® Intercompany Data Exchange ® Basic Settings Define Control Parameters.

The service can have various statuses, which can be identified using the following icons:

	Service exists or is created when you save
	Optional service exits Is not created if you remove the data from the Service provider field and save
	Optional service is proposed Is created if the Service Provider field contains an entry If the entry is remove from the field, no service is created
	Service exists but conflicts with the service proposed by the system Service either no longer exists in Customizing or is not proposed in the current circumstances because, for example a contract (billable service) already exists for the same service type

Data Exchange tabstrip

Contains all the data exchange processes relevant to the current point of delivery. The data exchange processes are only created at service provider level. If you want to define a different due date control for individual points of delivery then you can redefine the current definition for the given PoD.

If you click on a data exchange process the data exchange definition appears.

To redefine a data exchange definition at point of delivery level, choose    Redefine DATEX Definition. The definition appears.

In the list on the tabstrip you can recognize the redefinition by the    symbol in the Redefinition column. The    symbol means that the data exchange definitionwas imparted to the point of delivery by the service provider.

To undo a redefinition, choose   Undo Redefine DATEX definition.

If you do not want a data exchange process to be active for the current point of delivery then you must first redefine it. The definition appears. Select the Inactive field and leave the dialog box.

In the list on the tab strip you can see whether a data exchange process is active by the Inactive field.

To synchronize scheduled data exchange tasks, choose  Synchronize. For more information on synchronization see Synchronization of Scheduled Data Exchange Tasks.

The individual fields have the following functions:

Field	Function	Symbol
Import/export	Direction of DATEX process	Export process   Import process
Data exchange process	Data exchange process
Description of data exchange process
Sender/recipient	Identifies sender and recipient in DATEX process	Recipient   Sender
Own service type	In export processes, the service type comes from the sender of the messages In import processes, the service type comes from the recipient of the messages
Own service provider	Own service provider
Name of service provider
Sender/recipient	Identifies sender and recipient in DATEX process	Recipient   Sender
External service type	In export processes, the service type comes from the recipient of the messages In import processes, the service type comes from the sender of the messages
Technical ServProv	Service provider to which a service type from the technical service category has been allocated. This service category described technical systems, such as automated meter reading systems.	Technical service provider
External ServProv	External service provider
Name of service provider
Redefinition	Redefinition	Redefinition   Impart by service provider
Inactive	Data exchange process inactive for PoD
Point of delivery
Valid from	Validity period for data exchange definition
Valid to
No Due Date Control	No due date control is allocated to the data exchange process, meaning you cannot actively schedule the process. The due date of process execution cannot be maintained. Only process execution data communication are logged.
Text for Due Date Control
Data Exchange Format	z. B. MSCONS
Text for DATEX format	Description of data exchange format

Migration of Points of Delivery

For more information, see Migration of points of delivery.