Kontakt

Ansicht
Dokumentation

PAY_DE_B2A_FIN_120 - Set Up Connections

PAY_DE_B2A_FIN_120 - Set Up Connections

Addresses (Business Address Services)   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

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

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_
Package                 ELSTER
ACL                    
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 .
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. Install the CoreFix as described in the related readme.txt file or SAP Note 1260891.
Restart the Business Connector. Check whether the CoreFix is listed under "About"Updates and Build Number.
Applying the ELSTER_EXT Package to the Business Connector
To download the ELSTER_EXT package (at least Version 2.0) for the Business Connector, go to the HR pages of SAP Service Marketplace and choose quick link HRDE under Elster@SAP (http://service.sap.com/HRDE).
There are two different packages for Versions 4.7 and 4.8 of the Business Connector:
- BC 4.7: ELSTER_EXT for SAP BC 4.7
- BC 4.8: ELSTER_EXT for SAP BC 4.8
Note:
The "Package Elster for SAP BC(as of 4.6C)" contains the previous ELSTER function. That is, the ELSTER function already located and installed on your Business Connector.
Copy the file ELSTER_EXT_47_....zip or ELSTER_EXT_48...zip to the .../replicate/inbound installation 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_EXT package is enabled and loaded.
  1. Setting the map to the created listener
From the menu, choose SAP -> Lookup and under RFC Lookup enter the server name of the SAP system for which you want to set up the signature.
Under Function Search, enter HR_DE_B2A_ELSTER_BBOX in the Function Name field, and choose Search. The function module is then displayed. 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 service in the ELSTER_EXT package to the function module. Enter the following data:
Field Content
Generate for Listener
Package Default
ACL
Remote Server Alias (local)
Folder sap.elster
Service send
Scope Session


Check the created map.
To do so, choose SAP -> SAP Servers -> RFC Function Maps for .
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 for ELSTER:
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
HR_DE_B2A_ELSTER_BBOX SAP->SAP BC sap.elster send

(The maps for ...GZIP, ...TRANSHTTP, and ...UNGZIP already existed and were used by the existing ELSTER functions for transfer. The maps are case-sensitive).
  1. Applying the necessary certificates for the signature and encoding

    Applying your own key pair:
    You have previously requested your own key pair (file extension pfx) in the portal for the clearing house.
    To apply the key pair, choose Adapters -> Elster and enter the pfx file with your own key pair under Load SSL Profile.
    The pushbutton in the "Set as default" column must be used to set a key as the default for encoding with ELSTER.

    Applying the clearing house’s public key:
    For the public key for the clearing house, see SAP Service Marketplace under the quick link HRDE under Elster@SAP (http://service.sap.com/HRDE).
    To apply this public key, choose Adapters -> Elster and enter the file with the clearing house’s public key under Load Recipient Certificate.
    The pushbutton in the "Set as default" column must be used to set a key as the default for encoding with ELSTER.
  • Customizing in HR
    • The signature is activated by constant SIGSW in table T50BK (view V_T50BK).
    1. In transaction SM30, select the view V_T50BK.
    2. Select the country grouping 01 (Germany) and confirm your entry.
    3. Choose Position, enter the value ST (tax) in the Area field, and confirm your entry.
    4. Enter the value of the required value for the constants ST/LSTA/SIGSW and ST/LSTB/SIGSW.
    Example:
    Area DocCat Constant CVal.
    ST LSTA SIGSW 200901
    ST LSTB SIGSW 200901

    Comment:
    The signature remains optional for the transfer of the employment tax notification (ETNotif.). Meaning that in the future no value/initial will be permitted for constant ST/LSTA/SIGSW.
    As of 2009, authentication is mandatory for employment tax statements (ETStmt). Meaning that the constant must be set to 200901 or a previous period, for example, 200812.
    To test in the development or test system, set the constant to 200801, for example, to test before 2009. If you now create an employment tax statement for an employee for 2008 or an employment tax notification for a month in 2008, this is authenticated and transferred to the clearing house. The use of authentication is visible in the B2A Manager log.

    Using XI Platform

    You need to make the adjustments for using XI in the XI system and in the SAP system (HR Customizing). For up-to-date information on configuring the XI-specific part, see consulting note 966583.

    XI 3.0

    1. XI - Deployment XI Content
    Get the current version of the XI content from SAP Service Marketplace (http://service.sap.com/swdc), software component "XI CONTENT ELSTER 1.0" with the current SP and Patch status (at least SP 02, Patch 1), and upload this to the Integration Repository (see SAP Note 705541).
    XI - System Landscape Directory (SLD)
    Use the System Landscape Directory (SLD) to connect the SAP system to the XI system. The SAP system must first be created as a technical system in the SLD. You then define a business system that references the previously created technical system.
    XI - Integration Directory
    The following lists the configuration steps in the Integration Directory. Note 966583 contains file HCM_Elster_XI_Inst_01.pdf as an attachment. The attachment contains screenshots for the individual steps, which you can use as a template/example for the configuration. Replace the settings with your system-specific values as required.
    1. Create New Scenario
    Create a new scenario for LSTA/LSTB.
    1. Create Communication Channel Sender and Recipient
    Under communication channel, enter an RFC channel for the sender and for the recipient under the business system created for your system. Select RFC as the adapter type.
    1. Create Sender Agreement
    Create a sender agreement for each of the RFC modules (interface) HR_DE_B2A_ELSTER_GZIP and HR_DE_B2A_ELSTER_UNGZIP. Choose the "sender" communication channel you defined in b) as the "Communication Channel of Sender" for both.
    Create Interface Determination
    - Create an interface determination for your service and interface HR_DE_B2A_ELSTER_GZIP. The inbound interface is HR_DE_B2A_ELSTER_GZIP_D and the interface mapping IM_GZIP.

    - Create an interface determination for your service and interface HR_DE_B2A_ELSTER_UNGZIP. The inbound interface is HR_DE_B2A_ELSTER_UNGZIP_D and the interface mapping IM_UNGZIP.
    1. Create Recipient Determination
      - Create a recipient determination for your service and interface HR_DE_B2A_ELSTER_GZIP. The recipient is HR_DE_B2A_ELSTER_GZIP_D and the interface mapping IM_GZIP. (The system adds the recipient agreement automatically later on).

      - Create a recipient determination for your service and interface HR_DE_B2A_ELSTER_UNGZIP. The recipient is HR_DE_B2A_ELSTER_UNGZIP_D and the interface mapping IM_UNGZIP. (The system adds the recipient agreement automatically later on).
    2. Create Recipient Agreement
      - Create a recipient agreement for your service and interface HR_DE_B2A_ELSTER_GZIP_D. Select the "recipient" communication channel you defined in b) as the "Communication Channel of Recipient".

      - Create a recipient agreement for your service and interface HR_DE_B2A_ELSTER_UNGZIP_D. Select the "recipient" communication channel you defined in b) as the "Communication Channel of Recipient".

    You can use report RPUTX7D0 to check the connection between the SAP system and XI system.

    1. XI 7.0

    1. XI - Deployment XI Content
    Get the current version of the XI content from SAP Service Marketplace (http://service.sap.com/swdc), software component "XI CONTENT ELSTER 1.0" with the current SP and Patch status (at least SP 02, Patch 1), and upload this to the Integration Repository (see SAP Note 705541).

    1. XI - System Landscape Directory (SLD)
    Use the System Landscape Directory (SLD) to connect the SAP system to the XI system. The SAP system must first be created as a technical system in the SLD. You then define a business system that references the previously created technical system.

    1. XI - Integration Directory
    See Integration Directory for XI 3.0 above.

    You can use report RPUTX7D0 to check the connection between the SAP system and XI system.






    RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
    This documentation is copyright by SAP AG.

    Length: 29924 Date: 20240523 Time: 202927     sap01-206 ( 289 ms )