CALL_FUNCTION_SNC_NAME_NOT_FND SAP ABAP Runtime Error call function snc name not fnd

CALL_FUNCTION_SNC_NAME_NOT_FND is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: I - Internal Kernel Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

CALL_FUNCTION_SNC_NAME_NOT_FND ABAP Runtime Error

You must make a corresponding entry (including SNC name and system ID of the source system) in table SNCSYSACL of the target system and then mark it for use with RFC. An error occurred while making a Remote Function Call. Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.

A Remote Function Call was made and the SNC connection (Secure Network Communications) was used. In this case, a check is performed in the target system to see whether an entry with the SNC name, SNC ID and the RFC type of the original system exists in the table SNCSYSACL and if this entry is activated for RFC.
This was not the case.

The following information was used to search SNCSYSACL: Type..... (Field SNC-TYP)....><runtime parameter><
System ID.(Field SNC-SID)....><runtime parameter><
SNC name..(Field SNC-PNAME)..><runtime parameter>< Sysid <runtime parameter> in target system in table SNCSYSACL is not allowed. SNC name=<runtime parameter>