Service Provider

转自：http://help.sap.com/saphelp_utilities472/helpdata/en/f1/5dcd3ba9567d78e10000000a11402f/content.htm

Service Provider 

Definition

The service provider has two main functions in IDE:

  1.  It represents the central communication object.

If communication occurs using IDocs, the logical transmission address of the recipient is determined from the relevant Customizing settings. Before you can do this, you must maintain partner profiles for partner type SP (IS-U Service Provider) under Tools ® Business Communication ® IDoc Basis ® IDoc ® Partner Profile.

Do not use purely numeric values as keys for service providers, since this leads to problems when maintaining partner profiles.

If you allocate a service provider to a business partner, you can use the business partner functions for non-electronic communication (for example, for address management, contact persons, and telephone numbers).

  2.  The service provider plays an important role in defining the deregulation scenario for a point of delivery. A service provider can be allocated to different objects in IS-U, such as services (billable and non-billable) and installations.

For a more detailed description, see Deregulation Data in IS-U Master Data.

You can allocate one service type to a service provider.

You can maintain the service provider data in the menu under Intercompany Data Exchange -> Service Provider.

Scenario 1: Service Provider Agreement Active

In Customizing for SAP Utilities under Basic Settings/Enterprise Structure ® Determine Deregulation Settings, the ServProv. Agreement field is selected under Dialog Control.

This indicator activates the Service Provider Agreement function (in a separate tab page) in theCreate/Change/Display Service Provider transactions (EEDMIDESERVPROV01/02/03 respectively) and in thePoint of Delivery Group in the point of delivery transactions (EEDM09, EEDM10, EEDM11).

If you select this field, the CA Aggr. Bill Payment field is hidden in the Hdr Data tab page of the service provider transactions. The G/L Accounts and Contract Accounts for Aggregated Bill Payment table is also hidden.

The Payment and Billing Data tab title is also hidden.

You can use the service provider agreement to define the hidden functions as control information for a specific process.

Selecting this field allows you to allocate point of delivery groups to the point of delivery in the point of delivery transaction.

Create service provider

Enter an ID for the service provider in the Service Prov. field, and a name for  the service provider in the SP namefield.

You can use a template to create a new service provider. To do this, enter the ID of the service provider that you want to use as a template in the Template field, and choose Enter. The template service provider is copied to the new service provider. The external number is however not copied. If you do not change the service type and the template service provider has defined data exchange processes, then these are copied (see Data Exchange Tab Page section).

Header Data Tab Page

The header data contains the following information for the service provider:

·  Business partner (mandatory field)

·  Service type (mandatory field)

You can only configure a service provider with a service type from category technical service provider once in the system.

·  Company code of service provider

Company code that the service provider is allocated to.

When allocating a service provider to a contract, the company code of the contract must be the same as the company code of the service provider. This ensures that all posting items that result from invoicing a contract for this service provider have this company code.

·  Vendor

This vendor number is used during payment with an external company if a payment is made using a vendor posting.

·  External number

The external number is used to identify the communication partner. It may only exist once in the system.

·  Second external number

The second external number is an additional external number that you can use if in the event that the first external number is not sufficient to uniquely identify a business partner.

·  Authorization group

·  Service providers in own system

All of your company’s own service providers that are managed in one client must be marked as service providers belonging to your own system. This means that you must flag the SP in Own System field for these service providers.

This information is vital for determining which service provider is the sender and which is the recipient of messages in communication control.

Historical Data Tab Page

You can record the information for the contract here that is agreed between the individual companies.

You can process the validity periods by specifying the from and to dates. You can also enter the corresponding contract reference number (contract ID).

The customer include for customer-specific enhancements (CI_ESERVPROVHIST) exists for the structure being used, for maintaining further historical data.

BAdI (ISU_EDMIDE_SERVPROVH) is available for checking the data entered in the fields of the customer include.

Tab Page Overview

You can use enhancement EIDESP01 (IDE Service Provider Integration Customer Subscreen) to collect and display service provider data on this tab page.

·  If data has been maintained, this tab page is displayed as the first active tab page.

·  If no data has been maintained, this tab page is hidden.

Change service provider

Note that the header data service type, company code, vendor and service provider in own system can no longer be changed.

If you did not enter the company code when you created the service provider, you have the opportunity to enter it now.

Agreements Tab Page

This is where you define the service provider agreements. A service provider agreement is an agreement between two participating service providers regarding the processes necessary to supply a point of delivery. Service provider agreements are defined from the view of the market partner.

You can only enter data in this tab page in change mode.

To create service provider agreements choose (create agreement). Alternatively, you can choose  (copy agreement) to use the agreements of another market partner as a template.

The individual fields have the following meanings:

·  Type of Service Provider Agreement

The type of service provider agreement that was defined in Customizing with reference to a deregulation process and to the service types of the participating service providers.

·  Documentation of the Process

The documentation for the corresponding deregulation process is displayed here. First, however, in Customizing for SAP Utilities under Tools ® System Modifications ® User-Defined Enhancements for IDE ® Define Deregulation Processes you must enter the ID of a previously created documentation object in theDocumentation Object field.

·  Processing Service Provider

The possible service types of the participating service providers (market partner and processing service provider) were already determined in Customizing for each type of service provider agreement. Therefore, the input help for this field only allows you to select service providers that have the service type required for this type of agreement.

·  Description of the Parameter Configuration

The parameters relate to a deregulation process. You define the parameter configuration in Customizing for SAP Utilities under Tools ® System Modifications ® User-Defined Enhancements for IDE ® Define Deregulation Processes. The deregulation process determines which parameters must be or can be maintained in the service provider agreement.

·  Description of the Supply Scenario

·  Description of the Point of Delivery Group

·  Day From and Day To

·  Contract Identification (Reference Number)

Choose  (View Sprov(Proc.)) to branch to the processing service provider view.

To go to the display view for the change documents, select a line from the list and choose  (Display Change Document).

Data Exchange Tab Page

All the relevant data exchange processes for this service provider are displayed here. The data exchange processes are only created at service provider level. If you want to define an alternative due date control for individual points of delivery, you can redefine the existing definition specifically for the point of delivery.

By clicking on a data exchange process, you go to the associated data exchange definition.

The individual fields have the following meanings:

Field ID	Description	Symbol
Import/export	Direction of data exchange process	Export process   Import process
Data exchange process	Data exchange process
ID of data exchange process
Sender/recipient	Description of sender or recipient in data exchange process	Recipient  Sender
Own service type	For export processes this is the service type of the message sender The service type of the message recipient for import processes
Own service provider	Own service provider
Name of service provider
Sender/recipient	Description of sender or recipient in data exchange process	Recipient  Sender
Third party service type	For export processes this is the service type of the message recipient  The service type of the message sender for import processes
Technical service provider	Service provider to which a service type from category technical service provider is allocated. This service category describes technical systems (such as automated meter reading systems).	Technical service provider
Third-party service provider	Third-party service provider
Name of service provider
Redefined definition	Redefined definition of data exchange definition at point of delivery level.  Data exchange definitions are determined at service provider level.	Redefined definition   Inherited by service provider
Not active	Data exchange process is not active for the point of delivery
Point of delivery ID
Valid from	Validity period of the data exchange definition
Valid to
No due date control	No due date control has been allocated to the data exchange process. This means that you cannot schedule the process actively. The due date of the execution cannot be monitored. Only the process execution and the data communication are logged.
ID of due date control
Data exchange format	For example MSCONS
ID of data exchange format

Delete Service Provider

A prerequisite for deleting a service provider is that it has not yet been allocated in IS-U (for example, to an installation or grid).

Navigation

The symbols have the following meaning:

Create service provider	Call up transaction in creation mode
Change service provider	Call up transaction in change mode
Display service provider	Call up transaction in display mode
Display <-> change service provider	Transaction switches between the change mode and display mode with the same service provider
Delete Service Provider	Deletes the service provider from the database. Prerequisite is that it has not yet been allocated in IS-U

By double-clicking on the Business partner field, you can branch to the Display business partner transaction.

Object Services

The generic object services are available for the service provider.

It is possible, for example to enter personal or general notes, attach documents, send objects and so on.

Authorization Object

Authorization object E_SERVPROV exists with authorization fields BEGRU and ISU_ACTIVT for the service provider.

Scenario 2: Service Provider Agreement Not Active

In Customizing for SAP Utilities under Basic Settings/Enterprise Structure ® Determine Deregulation Settings, the ServProv. Agreement field is not selected under Dialog Control.

This results in the following changes:

·  The CA Aggr. BillPayment (Contract Account for Aggregated Bill Payment) field is displayed on the Hdr Datatab page.

The contract account for aggregated bill payment is used for the aggregated posting of payments to the third party service provider in deregulated markets.

This posting takes place in addition to the receivables postings for individual customers, and is used primarily for tracking payments involving the third-party.

·  The G/L Accounts and Contract Accounts for Aggregated Bill Payment table is displayed.

Depending upon whether you have entered a vendor, you must enter one or more general ledger accounts from accounts payable accounting (FI-AP) or contract accounts aggregated bill payment from contract A/R &A/P (FI-CA)-

¡  If a vendor has been entered, you must enter the general ledger accounts.

¡  If no vendor has been entered, you must enter the contract accounts aggregated bill payment.

The contract account aggregated bill payment is used for the aggregated posting of payments to a third-party service provider in deregulated markets.

You can define more than one contract account for each service provider.

If you have entered several general ledger accounts or contract account aggregated bill payment, they must be easily identifiable by the bill category. This means that bill categories are used to distinguish between the aggregation accounts for the service provider.

For effective processing of payments in the deregulated market, the individual due amounts to be paid to a third-party service provider are aggregated.  Depending upon the settings for the service provider, this aggregated posting takes place to accounts payable accounting (FI-AP) or to contract A/R & A/P (FI-CA).

For different reasons, it can be necessary to post to separate accounts in FI-AP or in FI-CA. The bill category is used to determine the necessary account. This bill category must be allocated to an account when maintaining the accounts for a service provider.

Since the bill categories are developed company-specifically, the bill category is determined using the company’s own programming. The value SPACE is used as standard.

You define the necessary bill categories in Customizing under SAP Utilities ® Intercompany Data Exchange® Payment Control ® Define Bill Categories.

  Example

In a sole provider scenario, the supplier receives the grid usage bills from the distributor. Due to legal conditions, the supplier is obliged to post the tax portion of the bill separately and to transfer it separately.

Two types bill categories are defined:

A bill category for the bill amount before taxes, and a bill category for the tax amount.

Both amounts are listed separately in table EPAYTHP (Transfer Records for Payment to Third-Party) and the appropriate bill category is allocated (this takes place using the corresponding company-specific processing of the incoming bill).

When executing report RECTHP02 (program for generation of FI vendor posting), different bill categories and different accounts are found.

Note that the header data service type, company code, vendor and service provider in own system can no longer be changed once you have saved.

·  Payment and Billing Data tab page (payment frequency)

You can enter the payment frequency data here. A payment class may only be allocated once for each service provider.

You define the payment classes and payment frequency in Customizing under SAP Utilities ® Intercompany Data Exchange ® Payment Control.

For more information, see the Implementation Guide (IMG).