topic Re: CALL_FUNCTION_NOT_FOUND in Application Development and Automation Discussions

CALL_FUNCTION_NOT_FOUND

Former Member — Tue, 17 Feb 2009 06:46:51 GMT

Hi,

I got this error when doin client copy from 000 client to 300 client on ECC5.0 with Oracle as DB.

Runtime Errors CALL_FUNCTION_NOT_FOUND

Except. CX_SY_DYN_CALL_ILLEGAL_FUNC

ShrtText

Function module "#" not found.

What happened?

The function module "#" was called, but cannot be

found in the Function Library.

Error in ABAP application program.

The current ABAP program "SAPLSCCM" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',

was neither

caught nor passed along using a RAISING clause, in the procedure

"SCCM_CHECK_NAMETAB" "(FUNCTION)"

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

The program "SAPLSCCM" contains a CALL FUNCTION statement. The name

of the function module to be called is "#".

No function module exists with the name "#".

All function modules are stored in the Function Library (SE37).

Possible reasons:

a) Wrong name specified. Particular attention should be paid

to upper/lower case and underscores ("_")

b) Transport error

c) If an enqueue/dequeue module has been used, the lock object

may not have been activated (ABAP Dictionary)

may not have been activated (ABAP Dictionary).

How to correct the error

Check the last transports to the R/3 System.

Is the program "SAPLSCCM" currently being changed?

If an enqueue/dequeue module is involved, is the activation

of the lock object missing in the ABAP/4 Dictionary?

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

"CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC

"SAPLSCCM" or "LSCCMU13"

"SCCM_CHECK_NAMETAB"

Please suggest me how to rectify this...

Thnx,

Kalyan

Re: CALL_FUNCTION_NOT_FOUND

Sm1tje — Tue, 17 Feb 2009 06:53:52 GMT

When does this occur? Obviously a function module (named '#') is not available which sounds logical since there is no FM called '#'. This is causing the short dump.

However, it kinda depends from where this dump is initiated. Is there some customizing involved, or are you for example calling this function module dynamically?

Re: CALL_FUNCTION_NOT_FOUND

Former Member — Tue, 17 Feb 2009 06:56:50 GMT

Hi,

Goto the Tcode SE37, give the Function module name SCCM_CHECK_NAMETAB click on the button Display

Check do u get any error message or displays the details of the Function module. If Error .. the Check some SAP NOTE to implement this FM. The FM is used for Parallel Client Copy

Re: CALL_FUNCTION_NOT_FOUND

Former Member — Tue, 17 Feb 2009 07:00:18 GMT

Check this SAP NOTE might be helpful 491022

Re: CALL_FUNCTION_NOT_FOUND

kamesh_g — Tue, 17 Feb 2009 07:05:22 GMT

May be the FM you are using is OBSOLETE try to find out FM for that .

Re: CALL_FUNCTION_NOT_FOUND

Former Member — Tue, 17 Feb 2009 07:08:46 GMT

Hi,

Got this error when doing Client Copy......

Tnx,

Kalyan

Re: CALL_FUNCTION_NOT_FOUND

Former Member — Tue, 17 Feb 2009 07:14:37 GMT

When i checked that function module ...it displayed no syntax errors found.

Regards,

Kalyan

Re: CALL_FUNCTION_NOT_FOUND

Sm1tje — Tue, 17 Feb 2009 07:20:36 GMT

I already thought it would be something like Client copy. Well, this could be quite a problem to solve by yourself. First, try and contact the people responsible for the client copy. Maybe somewhere in the log, an error has occurred resulting in NOT copying all the data to the new client.

Might be worth to start debugging and see, which function module should be called. Do this by debugging the new and the old client, and try to compare both.