SAP ABAP IMG Activity PAY_DE_B2A_KK_650 (Communication Server DSRV (Immediate Notifications))
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_KK_650 Communication Server DSRV (Immediate Notifications)  
Transaction Code S_L4H_49002333   (empty) 
Created on 20110720    
Customizing Attributes PAY_DE_B2A_KK_010   Communication with PKCS#7 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PAY_DE_B2A_KK_650    

Use

Note:

It is absolutely necessary that you note the current adjustments for setting up the communication server for German Pension Insurance (DRV) in the SAP Note 1612331 (SI: Setting Up the DRV Communication Server (DEUEV Immediate Notifications)).

Setup of the HTTP Connection

General Information for HTTP from SAP Systems:

For general information about setting up the HTTP connection from the SAP system, see the documentation on SAP Help Portal by choosing the following links:

  • Basis 6.40
    http://help.sap.com/saphelp_nw04/helpdata/EN/0a/a7903febb15a7be10000000a11405a/frameset.htm
  • Basis 7.00
    http://help.sap.com/saphelp_nw70ehp1/helpdata/de/48/6360878c4a31cbe10000000a42189d/frameset.htm

If problems or error messages (ICM) occur when setting up the HTTP connection, you can also refer to SAP Note 634006 (Note on the preclarification of ICM messages).

Activities

  1. Check and, if required, update of the certificate list
    Use the report Test Report for Listing GKV Communication Settings (RPUSVHD0) to check whether the company number 66667777 already exists in your certificate list.
    ...
    66667777 CN=Roland Jaeger, OU=BN66667777, OU=Deutsche Rentenversicherung Bund ...
    ...
    If this is not the case, update the certificate list in the key files (PSE files) that you use, as follows:
    1. Downloading of the current certificate list from ITSG
      www.itsg.de -> Trust Center -> Öffentliche Schlüsselverzeichnisse der Datenannahmestellen -> Arbeitgeberverfahren für das PKCS#7-Verfahren.
      From there, download the file for the PKCS#7 procedure (PKCS#7-Verfahren) and save it to your local PC (example: annahme-pkcs_431.agv).
    2. Deletion of the old certificate from the PSE files used
      Start the report Utility Report for Management of Encryption PKCS#7 for HI Funds (RPUSVKD1) and enter the company number. You can find the company numbers you use along with the related PSE files in the view Administration CoNo Certificates E-Mail Procedure (V_T5D4X).
      Confirm the entry. The information (administrator, company name, PSE file) is thus read and displayed.
      In the group box Delete Certificate List, select the checkbox Delete List (All) and run the report (F8). The report displays the number of deleted entries.
    3. Import of the new certificate list
      Restart the report Utility Report for Management of Encryption PKCS#7 for HI Funds (RPUSVKD1), enter the company number and confirm the entry.
      In the group box Read Certificate List, select the checkbox Read List and confirm the entry so that the field Path/File Name is ready for input.
      Enter the path for the file with the current certificate list (example: C:\annahme-pkcs_431.agv).
      Run the report (F8). The report displays the number of read entries.
    4. Use the report Test Report for Listing GKV Communication Settings (RPUSVHD0) to check whether the company number 66667777 is listed in the certificate list of the PSE file you have just processed.
    5. If your system runs on different instances and if the encryption for the health insurance funds is activated in these instances, repeat the steps b-d for each instance.
    6. If you use more than one company as the sender (V_T5D4X), import the most recent certificate list for these company numbers as well (steps b-e).
  2. Create HTTP test connection in transaction SM59
    To create an HTTP test connection, proceed as follows:
    1. Start transaction SM59.
    2. Choose Create:
      Connection type: G
      RFC destination: HR_DE_DSRV_TEST
      Description: HTTP connection for immediate notification test
    3. Entries on the Technical Settings tab:
      Target host: itsg.eservicet-drv.de
      Service no.: 80
      Path prefix: /extra/rest

      HTTP proxy options:
      Enter your own proxy data, if required
    4. Choose Save.
    5. You can then test the connection. Return code 405 means that the connection has no technical issues.
      Background: The connection test calls the connection with HTTP-Get. However, the data is later transmitted by the HR application program using HTTP-Post. For this reason, the DRV communication server allows only Post and returns error 405 when Get is transmitted.
  3. Create HTTP live connection in transaction SM59
    To create an HTTP live connection, proceed as follows:
    1. Start transaction SM59.
    2. Choose Create:
      Connection type: G
      RFC destination: HR_DE_DSRV_PROD
      Description: HTTP connection for immediate notifications live
    3. Entries on the Technical Settings tab:
      Target host: itsg.eservice-drv.de
      Service no.: 80
      Path prefix: /extra/rest

      HTTP proxy options:
      Enter your own proxy data, if required
    4. Choose Save.
    5. You can then test the connection. Return code 400 should be returned. In the live environment, the DRV communication server returns this code for invalid data or an access type HTTP-Get that is not permitted.

General Comments/Additional Information

  • The decision as to whether a system is a test system or live system is made as follows:
    • Constant MODE is evaluated in table T50BK (SV/ODES). If the constant is not maintained (it usually is not), table T000 is evaluated. If the client is classified as P, this means the system is a live system. If not, then the system is a test system.
  • You can do further tests on the HTTP connection using the report Test Report for Listing GKV Communication Settings (RPUSVHD0). For the test URL and live URL, the DRV communication server should return the text #Error 200: Error reported: 200#" and HTTP code 200. (This is OK. You can ignore the error message because the test report cannot send any valid XML data.)
  • For more information on saving HTTP/HTTPS connections, see the following documentation on SAP Service Marketplace at https://service.sap.com/security -> SAP Security Guides -> SAP NetWeaver 7.0 Network Security.

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  20111121 
SAP Release Created in