Show TOC

  Service Provider Locate this document in the navigation structure

Definition

Describes a company that provides a service.

Use

This object has two main functions:

  1. It forms the central communication object.

    If IDocs are used for communication, 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   .

    Note Note

    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).

    End of the note.

  2. It plays an important role in defining the deregulation scenario for a point of delivery.

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

  • Create Service Provider

  • Change Service Provider

  • 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

    Symbol

    Function

    ( ) 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 (see Delete service provider section)

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

Structure

The object consists of the following data groups:

Header Data Tab Page

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

  • Business partner (mandatory field)

  • Service type (mandatory field)

    Caution Caution

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

    End of the caution.

  • 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.

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.

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 ExchangeTab 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 a different due date control for individual points of delivery then you can redefine the current definition for the given PoD.

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

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 is available, this tab page is displayed as the first active tab page.

  • If no data exists, this tab page is hidden.

The structure of the object depends on the deregulation settings for dialog control in Customizing.

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 tab page in the Service Provider transactions and in the Point of Delivery Group tab page in the point of delivery transactions.

If you select this field, the following functions are also hidden in the service provider transactions:

  • On the Header Data tab page:

    • The CA Aggr. Bill Posting field (contract account for aggregated bill posting)

    • The G/L Accounts and Contract Accounts for Aggregated Bill Payment table

  • The Payment and Billing Data tab page

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

Scenario 2: Service Provider Agreement Not Active

If the ServProv. Agreement field is not selected, the following functions are displayed in the service provider transactions:

  • On the Header Data tab page:

    • The CA Aggr. Bill Posting field (contract account for aggregated bill posting)

      The contract account for aggregated bill posting is used for the aggregated posting of receivables to a 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

  • The Payment and Billing Data (Payment Frequency) tab page

    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).

Object Services

The generic object servicesare 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.

Integration

You can allocate a service provider to different objects in IS-U, such as services (billable and non-billable), and installations.

A service provider is assigned one service type.