SAP ABAP IMG Activity PAY_DE_B2A_FIN_120 (Set Up Connections)
Hierarchy
☛ SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR
   ⤷ PY-DE (Application Component) Germany
     ⤷ PC01 (Package) HR Payroll: Germany
IMG Activity
ID PAY_DE_B2A_FIN_120 Set Up Connections  
Transaction Code S_PL0_86000093   (empty) 
Created on 20040301    
Customizing Attributes PAY_DE_B2A_FIN_000   Data Exchange with Financial Administration 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PAY_DE_B2A_FIN_120    

Set Up Connection


It is possible to use the XI platform or the Business Connector for the technical connection between the SAP system and the clearing house. Depending on your choice, perform the configuration steps listed under "Using XI Platform" or "Using the Business Connector".

Using the Business Connector

The Business Connector (BC) is a server that is freely available to SAP customers to realize various data exchange scenarios between SAP systems and/or external systems of service providers and authorities.

Install the BC in your system landscape so that data can be exchanged between the SAP system, the BC, and the Internet (HTTP POST). To do so, you may have to maintain the <Object>Proxy Server in the Business Connector. For more information about activating the required IP addresses, services, and so on, see SAP Note 717218 (B2A: Technical details employment tax statement).

For information about installation and administration, see the documentation available on SAP Service Marketplace, under the quick link Connectors.

HR-specific steps to configure the transfer of the employment tax data to the tax authorities' clearing houses

  • Applying the ELSTER package on the Business Connector
    • To download the package for the Business Connector, go to SAP Service Marketplace, choose quick link hrde then the menu item Elster@SAP (http://service.sap.com/HRDE).
    • Copy the file to the .../replicate/inbound directory on the BC.
    • Log on to the Business Connector. Choose Packages -> Management -> Install Inbound Releases and select the file. Install the package by choosing Install Release.
    • Choose Packages -> Management and check in the overview of packages that the ELSTER package is enabled and loaded.
  • Setting up the SAP system
    • The SAP system has to be created on the Business Connector for communication between the SAP system and the BC.
      • To define the system, choose SAP -> SAP Servers -> Add SAP Server.
      Maintain the System, Login Defaults, and Server Logon blocks. An RFC user (category C) is sufficient as the user for the server definition.
    • Choose Test Connection. It must be possible to log on to the defined SAP system.
  • Setting up the listener for the created SAP system

    To establish the connection between the RFC connection created in the SAP system and the SAP system defined previously on the BC, you create a "listener".

    • The defined systems are listed in the overview in the BC, under SAP -> SAP Server. In the row of the relevant system, click on the number in the Listeners column to display the defined listeners. To create a new listener, choose Add Listeners.
    • As the Program ID, enter the label used in the RFC definition, ELSTER_XML_<system name>.
      • Example: ELSTER_XML_H01
      Select Yes for autostart. This means that the listener is automatically reactivated after the BC is restarted.
      Unicode note: If the listener is created for a Unicode SAP system, you have to set the Unicode option for the listener and the RFC connection.
    • Check in the overview that the listener is started. If so, the Started? field is displayed in green.
    • Check the connection between the SAP system and the BC by testing the RFC connection created previously in the SAP system. You may have to reregister the connection in the SAP system.
  • Setting the maps to the created listener

    Before you can set maps, the RFC connection must be created and tested in the SAP system. The SAP system must be defined on the BC and a listener must be set up for the RFC connection.

    In addition to the listener, you have to create maps as a connection between the function modules in the SAP system and the services executed on the BC.

    • From the menu, choose SAP -> Lookup and under RFC Lookup enter the server name of the SAP system. Under Function Search, enter HR_DE_B2A_ELSTER* in the Function Name field, and choose Search.

      All function modules with names beginning HR_DE_B2A_ELSTER* in the SAP system are then displayed.

    • Create a map for each of the following function modules:
      • HR_DE_B2A_ELSTER_GZIP
      HR_DE_B2A_ELSTER_TRANSHTTP
      HR_DE_B2A_ELSTER_UNGZIP
      To do so, click on the name of the function module. The direction of the connection is SAP -> SAP BC. Choose Define New Map.
    • On the subsequent screen, assign the R/3 function module to the service in the ELSTER package.
    • Enter the following data for each of the above-mentioned function modules:

    Field     Content

    Generate for Listener     ELSTER_XML_<system name>

    Package     ELSTER

    ACL     <None>

    Remote Server Alias     (local)

    Folder     LSTB

    Service     see below

    Scope     Session

Enter the following services for each of the function modules:

    Function Module     Service

    HR_DE_B2A_ELSTER_GZIP     GZIP

    HR_DE_B2A_ELSTER_TRANSHTTP     TRANSHTTP

    HR_DE_B2A_ELSTER_UNGZIP     UNGZIP

  • Check the maps.
    • To do so, choose SAP -> SAP Servers -> RFC Function Maps for <name of SAP system>.
    You can also access the function by choosing the blue M in the overview of SAP servers.
    The Function Map List should now contain the following maps:

Function Module     Type     Folder    Service

HR_DE_B2A_ELSTER_GZIP     SAP->SAP BC     LSTB     GZIP

HR_DE_B2A_ELSTER_TRANSHTTP     SAP->SAP BC     LSTB     TRANSHTTP

HR_DE_B2A_ELSTER_UNGZIP     SAP->SAP BC     LSTB     UNGZIP

  • You can use the RPUTX7D0 report (test report for checking the RFC connection to the Business Connector) to test the entire connection between the SAP system and the BC.

Setting up authentication for the Business Connector

  1. Requesting the code for the authentication

    A software certificate is used as the code for the application implemented by SAP. Meaning that the code for the authentication is in a file. (Support for ELSTER stick and signature card is not planned)
    For more information, see https://www.elsteronline.de/eportal/

Comments for requesting the necessary certificate:

You request the certificate in the ELSTER online portal at https://www.elsteronline.de/eportal/.

The request must be completed and submitted in sufficient time before the fiscal year change.

The options provided by the clearing houses are listed under "Registration".
Three variants are provided:

  1. ElsterBasis: The certificate is in a file (software certificate)
  2. ElsterSpezial: The certificate is on a USB stick
  3. ElsterPlus: The certificate is on a signature card


    The SAP application uses a software certificate. When requesting the certificate, select ElsterBasis.

    In the subsequent registration you can choose between "Personal Certificate" and a "Non-Personal Certificate (Organizational Certificate)".

    If you use the signature for the ETNotif. and ETStmt, it is useful to use an organizational certificate.

    It is sufficient to request a single certificate for the organization (tax number) of the data communicator.
    After you have successfully requested a certificate, you should receive a password-protected file (Musterzert.pfx). This is required for the following steps.

    Business Connector

  1. Download and apply CoreFix (4.7 and 4.8) as well as Service Release 8 (4.7) for the Business Connector

Version 4.7:
For CoreFix 9, see SAP Service Marketplace and choose the alias Connectors under SAP Business Connector -> Tools & Services -> Software Updates. Install the CoreFix as described in the related readme.txt file or SAP Note 657153.
Restart the Business Connector. Check whether the CoreFix is listed under "About"Updates and Build Number.
Service Release 8:
Check whether the Service Release is already installed on the Business Connector. Under Adapters -> SAP... About, Version "4.7 SR8" should be listed in the block version. Service Release 8 is the prerequisite for the functions below BC 4.7.
For Service Release 8, see SAP Service Marketplace and choose the alias Connectors under SAP Business Connector -> Tools & Services -> Software Updates. If required, install the Service Release as described there.
Version 4.8:
For CoreFix 1, see SAP Service Marketplace and choose the alias Connectors under SAP Business Connector -> Tools & Services -> Software Updates.
Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20050801 
SAP Release Created in 500