How To Fix HRPAYDEB2A652 - Use of a URL address (SHI) that is outdated or no longer permitted

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYDEB2A - Business to Administration: Germany

• Message number: 652

• Message text: Use of a URL address (SHI) that is outdated or no longer permitted

What causes this issue?

In August 2017, the deactivation of old URLs was announced on the
website of the SHI communications server.
Until the end of February 2018, either the old
(kommunikationsserver.itsg.de) or the new URL
(verarbeitung.gkv-kommunikationsserver.de) can be used in as the target
host in the RFC destination.
From March onwards, only the new URL is permitted.

System Response

The check of RFC destination <ZH>&v1&</> showed that the old URL
(kommunikationsserver.itsg.de) is still used as the target host. Grouped
according to the time remaining until the old URLs are deactivated in
the period
a warning message in the period from September 1 to February 18, 2018
or an error message in the period from February 19 to February 28, 2018
(therefore, in the last 10 days before the deadline has passed).
You can see the notifications in the log of test report
<DS:TRAN.PC00_M01_RPUSVHD0>RPUSVHD0</> and in the log of collection
report <DS:TRAN.PC00_M01_RPCSVPD0>RPCSVPD0</>. In the case of a warning,
inbound files are still collected from the SHI communications server in
the collection report. If there is an error, however, they are not
collected.

How to fix this error?

Please note the information on the SHI communications server website:
https://www.gkv-kommunikationsserver.de/aktuelles/

Procedure for System Administrators

As described in SAP Note 2484878, use transaction <DS:TRAN.SM59>SM59</>
to change the URL of the target host in RFC destination <ZH>&v1&</>
from '<ZH>kommunikationsserver.itsg.de</>' to '<ZH>
verarbeitung.gkv-kommunikationsserver.de</>'.
Check the RFC connections in your system using test program
<DS:TRAN.PC00_M01_RPUSVHD0>RPUSVHD0</>. If you encounter problems with
this, you should also check the settings of your proxy server or
firewall. You may have to release the new URL there.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

If it is not possible to change the URL at short notice, you can
deactivate the check using an implicit enhancement in method <AB>
CL_HR_B2A_DE_PKCS7_GKV=>CHECK_DEST_URL</>, suppressing the warning or
error message. (For example, using ABAP command <AB> <DS:ABAP.RETURN>
RETURN</></> at the start of the method.) This adjustment allows the
transfer via the SHI communications server, but only until the old URL
is deactivated.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAYDEB2A652 - Use of a URL address (SHI) that is outdated or no longer permitted ?

  The SAP error message HRPAYDEB2A652 indicates that there is an issue with the use of a URL address (SHI) that is either outdated or no longer permitted. This error typically arises in the context of SAP HR (Human Resources) payroll processing, particularly when the system is trying to access a URL that is no longer valid or has been deprecated.
  Cause:
  
  Outdated URL: The URL being referenced in the payroll process may have been changed or removed in a recent update or configuration change.
  Configuration Issues: The system configuration may not be aligned with the current standards or requirements for accessing external resources.
  System Updates: Recent updates to the SAP system or related components may have altered the way URLs are handled or accessed.
  Access Permissions: The URL may require specific permissions that are not currently granted to the user or the system.
  
  Solution:
  
  Check URL Validity: Verify the URL being used in the payroll process. Ensure that it is still valid and accessible. If it has changed, update it in the relevant configuration settings.
  Update Configuration: If the URL is part of a configuration setting, navigate to the relevant configuration area in SAP and update the URL to the current one.
  Consult Documentation: Review SAP documentation or release notes for any changes related to the URL or the specific functionality you are using. This may provide insights into what has changed and how to adapt.
  Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP support for assistance. They may have additional insights or patches available to address the problem.
  Check User Permissions: Ensure that the user or system has the necessary permissions to access the URL. This may involve checking user roles and authorizations in SAP.
  
  Related Information:
  
  SAP Notes: Look for SAP Notes related to this error message. SAP frequently publishes notes that address specific issues, including error messages and their resolutions.
  System Logs: Check the system logs for any additional error messages or warnings that may provide more context about the issue.
  Community Forums: Engage with SAP community forums or user groups. Other users may have encountered similar issues and can share their solutions or workarounds.
  Testing: If possible, test the changes in a development or test environment before applying them to the production system to avoid disruptions.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.