How To Fix PSSC_CONTR025 - SwitchGroupID and SwitchValueID for bgRFC inbound destination missing

PSSC_CONTR025 - Overview

• Message type: E = Error

• Message class: PSSC_CONTR - Messages for application controller

• Message number: 025

• Message text: SwitchGroupID and SwitchValueID for bgRFC inbound destination missing

Hi Translators -Content is very similar to PSSC_CONTR030 & PSSC_CONTR031

What causes this issue?

The initial net calculation is done asynchronously in the background
using background RFC (bgRFC) technology. The required inbound
destination for bgRFC processing is missing.

System Response

Net calculation is not triggered.

How to fix this error?

Contact your system administrator.

Procedure for System Administrators

Execute the report <DS><DS:TRAN.PSSC00_NETCALC>Net Calculation Execution
</></> to run the missing net calculation.
Check the net calculation result carefully as the sequence of processing
is very important to prevent multiple gross payment items.
Create the queue prefix for bgRFC processing in Customizing for
<LS>Public Sector Management</> under <LS>Social Services -> Net
Calculation -> </><DS><DS:SIMG.PSSC_BGRFC>Define Background RFC Inbound
Destination</></><LS>.</>
The inbound bgRFC destination must be maintained for the SwitchGroupID
'NETCALC' and SwitchValID 'BGRFC_DEST' in Customizing for <LS>Public
Sector Management</> under <LS>Social Services -> Net Calculation -> </>
<DS> <DS:SIMG.PSSCC_SWITCH_NETCALC>Define Control Parameters for Net
Calculation</></><LS>.</>

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PSSC_CONTR025 - SwitchGroupID and SwitchValueID for bgRFC inbound destination missing ?

  The SAP error message PSSC_CONTR025 indicates that there is a problem with the configuration of the bgRFC (background Remote Function Call) inbound destination. Specifically, it points out that the SwitchGroupID and SwitchValueID are missing for the bgRFC inbound destination. This can occur in scenarios where the system is trying to process background RFC calls but cannot find the necessary configuration.
  Cause
  The error typically arises due to one of the following reasons:
  
  Missing Configuration: The bgRFC destination has not been properly configured in the system.
  Transport Issues: If the configuration was recently transported from another system, it may not have been set up correctly.
  System Settings: The system settings for bgRFC may not be correctly defined, leading to missing identifiers.
  
  Solution
  To resolve the error, you can follow these steps:
  
  
  Check bgRFC Configuration:
  
  Go to transaction SM58 (Transactional RFC) and check for any errors related to bgRFC.
  Use transaction SLG1 to check the application log for more details on the