Kontakt

Ansicht
Dokumentation

RPUSVHD0 - Test Report for Listing the Settings for Communication GKV (Obsolete)

RPUSVHD0 - Test Report for Listing the Settings for Communication GKV (Obsolete)

Vendor Master (General Section)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Obsolete.

This report is no longer supported and has been replaced with Test Report for Communication with the GKV and DSRV (RPUSVHD1).

Purpose

The purpose of this report is to read the technical customizing to use the PKCS#7 encryption for health insurance funds and pension insurance.
We recommend attaching the output of the report as a file (attachment) for problem notifications to SAP, which are related to the application.

Listed Values

  • Input Parameter
Inbound parameter of selection screen
  • Table T000
    Classification of the clients
  • Profile Paramters
    List of the SSF parameters relevant for encryption with the SAPCryptolib.
  • User Parameters
List of all possible user parameters and all user parameters used
  • Environment Variables
  • Version SAPCryptolib
    Installed version of SAPCryptolib
  • Last HRSP of SAP_HR
  • System/Kernel Information
  • Content of Table T50BA
Contains the transfer formats and classes that are permitted
  • Content of Table T50BB
Contains the standard transfer formats
  • Customizing of Table T50BC
    Contains the used encryption procedure
  • Customizing of Table T50BFC
    Contains the called classes and methods
  • Customizing in Table T50BK
    Contains technical constants for communication with the health insurance funds for PKCS#7
  • Number Range for B2A Manager (GLBID)
  • Customizing of Transaction File
    List of the mapping for logical file name/path to physical file name/path
  • SFF Customizing (Transaction SSFA)
  • Customizing in Table T5D4X
    Contains the mapping between the company number and the certificate used for it
  • Certificate of the Employer
    List of the certificates for each company number
  • SSL Client Certificates (SI* or DE SI')
    List of SSL Client Certificates in System
  • SO50 (E-Mail Inbox)
  • Query Virus Scan Profile
  • Programm Header RPUSVHD0
  • Programm Header RPCSVPD0
  • Programm Header RPCSVPD0_IN

Comments

  1. If the Print Table Content T50B* checkbox is not selected, the content of tablesT50BA, T50BB, T50BC, T50BFC, and T50BK is not displayed in the results log when running this report.
  2. The package size is limited to 20MB as the SHI communications server is only capable of processing messages that are this size or smaller and the communication channel keeps up to 180 seconds free for data transfer. If the report is run in the background (batch), the report ignores the package size that has been entered so and only a test without data volume is carried out.

HTTP Test

In the optional HTTP test, all RFC connections (communication using communication server) and logical ports (communication using web service) that are used for the SI notification procedure due to the settings in table T50BK are tested. If there are valid entries for a company number in table T5D4X, for which there is no valid entry in table T50BK, a HTTP test is also carried out. Using constants HTTPD and RHTTP, the Prefix of the name of the data connection is defined for each SI notification procedure. If no value is entered, the relevant standard prefix is automatically used. For example, for document type DEUV, if there is no value entered in constant HTTPD, this is the same as prefix HR_DE_GKV.

Depending on the SI notification procedure, there are different communication servers with two or three different RFC connections or logical ports that are all tested individually. The suffix of the name of the data connection is different for each of these: either TEST and PROD (DRSV / DSVV / rvBEA) or MELDUNG, ANFRAGE, and QUITTUNG (SHI).

For the tests, all (according to view V_T5D4X) currently valid data providers are tested individually. The name of the RFC connection consists of a combination of the prefix, possibly the company number of the data provider, and the suffix, for example, HR_DE_GKV_12345678_MELDUNG or HR_DE_GKV_MELDUNG. The name of the logical port consists of a combination of the prefix, the company number of the data provider, and the suffix, for example, HR_DE_RVBEA_12345678_TEST or HR_DE_RVBEA_12345678_PROD.

For each individual test, the company number of the data provider, the properties of the RFC connection or logical port, and the test result are logged.

Then a summary of each individual test sorted according to the name of the RFC connection or logical port follows. Each test is summarized in a table row.

  • From a technical point of view, green lines are acceptable.
  • Yellow Lines mean that an RFC connection or logical port is missing. According to the settings in view V_T50BK, at least one SI procedure uses this RFC connection or logical port. If you do not use the SI procedure, you can ignore this warning. Otherwise, you must set up the RFC connection or the logical port.
  • Red Lines are errors and may occur for several different reasons.
  • One cause is if there is no SSL client certificate suitable for the data provider. Create the certificate in transaction STRUST or remove the data provider from view Sicht V_T5D4X.

  • An error message from the communication server may be another cause. In this case, examine the response, check and, if necessary, correct the RFC connection in transaction SM59.

  • A further cause can be the use of a proxy with a user and password. In this case you need an RFC connection for each data provider of type <Prefix>_<Company Number>_<Suffix>.

  • Gray lines indicate that there are RFC connections that are available but not required. According to the settings in view V_T50BK, these connections are not used by any SI notification procedure at the moment.

The properties in the lines of the summary have the following significance:

  • T5D4X: According to view V_T5D4X,t here is currently a valid entry available for the company number (data provider) (value = X).
  • SM59: The name of the RFC connection is derived from the setup (view V_T50BK) of the relevant SI procedure. If a corresponding RFC connection or logical port was found (value = X), it can be used to transfer data. If not (value = empty), then the corresponding SI procedure (for example, DEUEV Immediate Notifications) may not be used.
  • SSL: In the RFC connection or configuration of the logical port, the property SSL is either active (value = X) for HTTPS or inactive (value = empty) for HTTP.
  • STRUST: The name of the SSL Client Certificate stored in the Trust Manager (transaction STRUST) for this company number.
  • B2A: SI outbound notifications that are transferred using an RFC connection or logical port, give an indication for the use of this RFC connection or logical port. If these kinds of outbound messages can be found in table P01SV_B2ATRNS for the last 1.3 years, this is indicated in this column (value = X).





Addresses (Business Address Services)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 8912 Date: 20240520 Time: 141715     sap01-206 ( 139 ms )