Skip to end of metadata
Go to start of metadata

Purpose

Introduce Deregulation Infrastructure.

Overview

The deregulation of the energy market has lead to the development of new business processes that require data to be exchanged between companies (supplier and distributor for example).

Data Exchange Basic Processes

The following basic processes are delivered by SAP:
CHCD_OUT: Send Changes to Business Partner Data
EXPPROFILE: Export Profile Values
EXPPROFOF: Export Profile Values with Offset (delivered with 602)
EXPREMADV: Sending Payment Advice Note Data
EXPREQSWT: Send Request for Change of Supplier/Start of Supply/End of Supply
EXPRESSWT: Send Response to Request for Change of Supplier/Start of Supply/End of Supply
EXPSETTLPA: Export Settlement Results (Profiles) for Document
EXPUSAGE: Send Consumption Data (from Billing)
INV_OUT: Send Invoicing Document (Creation/Reversal)
RES_DROP: Confirmation/Rejection of Termination Notification
RES_ENROLL: Confirmation/Rejection of Registration Notification
OUTBOUNIDE: General Logging of IDE Events (Outbound)
IMPINVOICE: Receive Invoicing Document (Create/Reverse)
IMPPROFILE: Importing Profile Values
IMPUSAGE: Receiving Consumption Data (Discrete Values)
REQ_CHANGE: Request for Changes to Business Partner Data
REQ_DROP: Request for End of Service
REQ_ENROLL: Request for Change of Supplier
INBOUNDIDE: General Logging of IDE Events (Inbound)

Data Exchange Processes

You can define the data exchange processes that you require for the implemented data exchange basis processes in Customizing. You do this by specifying the type of sender and the type of recipient exchanging the data.
Senders and recipients are recorded as service providers. The service types of the sender and the recipient are defined in the data exchange process.

Data Exchange Definition

You can create data exchange definitions on the basis of data exchange processes. A data exchange definition describes which due date is used and in which format the messages are exchanged between the two service providers. This is determined at service provider level. It is however possible to maintain this data at point of delivery level in exceptional cases (see Change Data Exchange Definition for the Point of Delivery). Each data exchange definition can be prorated historically. You can create a corresponding data exchange definition for service providers (of the corresponding service types) in reference to a data exchange process.

Data Exchange Task

A data exchange task is generated when a data exchange process is executed. A data exchange task always refers to a single point of delivery. This means that data is exchanged based on point of delivery.

The exchange of data from the individual point of delivery is controlled by the corresponding service provider’s data exchange definition.
You can also redefine data exchange definitions for individual points of delivery. This means that you can define a due date control for an individual point of delivery that differs from the data exchange definition of the corresponding service provider.

You can schedule the execution of data exchange processes according to the type of the data exchange basic process. As a result, the appropriate data exchange tasks are generated beforehand. Depending on the planned due date, you can then execute and monitor the data exchange processes (mass processing). You can also define data exchange processes for the exchange of data using technical systems (by means of a service type from category Technical Service Provider).

Related Content

Related Documents

Related SAP Notes/KBAs

  • No labels