SAP ABAP Message Class SEEF_BASE Message Number 146 (Function call through RFC connection &1 not successful &3)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-TOO-ENH (Application Component) Enhancement Tools
     ⤷ SEEF_BASE (Package) Enhancement Base Functionality

Attribute

Message class	SEEF_BASE
Short Description	Message Class for Package SEEF_BASE
Message Number	146
Documentation status		Space: object requires documentation
Authorization check Error Message	☐
Changed On	20130531

Message Text

Function call through RFC connection &1 not successful &3

Help Document

Diagnosis

Either you have created the BAdI implementation or you have explicitly called up a check for same-name BAdI implementations in other systems.

It was not possible to check the data in system GTS since no RFC link could be set up.

System Response

Since no link to the GTS system was possible, it could be that the implementation already exists under the same name in another system. But this should not happen.

Procedure

Call up the manual check, using the corresponding pushbutton, at a later time in order to make sure that the name has not been assigned twice.

Procedure for System Administration

History

Last changed on/by	20141121	SAP
SAP Release Created in	700