Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Short Dump: CALL_FUNCTION_CONFLICT_LENG appearing in our ECC6 System

Hi All

I have started to notice a short dump appearing in our ECC6 system sice it has been connected to Solution Manager. The information included in the short dump seems to refer to a a potential modification of a program (SAPCNVE). I have checked this program in SE38 and checked the version, which is 09.09.2004 14:36:10 by SAP.

I have run a search for this on OSS and have come up with very little, so if anyone has help or pointers that would be great.

Thanks

Phil

The short dump is:

Runtime Errors CALL_FUNCTION_CONFLICT_LENG

Exception CX_SY_DYN_CALL_ILLEGAL_TYPE

Date and Time 17.06.2011 07:52:21

What happened?

Error in the ABAP Application Program

The current ABAP program "/SSA/ABO" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

A function module was called incorrectly.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was

not caught in

procedure "GET_TOP_OBJECTS" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

The call to the function module "MSS_GET_TABLE_SIZE_INFO" is incorrect:

In the function module interface, you can specify only

fields of a specific type and length under "TABLE_SIZEINFO".

Although the currently specified field

"LS_MSSTAB" is the correct type, its length is incorrect.

How to correct the error

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

If the error occurs in the program SAPCNVE, it could be for any of

the following reasons:

1. The field <INPUT> conflicts with a function module called

"..._INPUT" or the field <OUTPUT> with "..._OUTPUT".

This is probably due to an error in the definition of the

function module interface. For the relevant

parameters, you should not specify any reference field.

2. The field <INPUT> conflicts with a function module called

"..._OUTPUT.

It may be that the GPA mechanism was used to read a value from the

SAP memory with an incorrect length. The

material number conversion MATN1, for example, expects

a material number 18 characters long in ABAP/4 internal terms. If,

instead, MAT contains a value only 1 character long, the program

terminates.

To view the current contents of the SAP memory, go into "Debugging"

and select Goto -> System -> System areas. View area SMEM.

A GPA value may be the wrong length for any of the following reasons:

a) The user master record contains a value with an incorrect length.

b) In the current transaction, an incorrect parameter ID was

chosen for the field with this conversion.

c) In one of the screens for a previously executed transaction, a

field was assigned an incorrect parameter ID.

d) In a previously executed ABAP/4 program, a

SET-PARAMETER statement has a value with an incorrect length, e.g.

SET PARAMETER ID 'MAT' FIELD '1'.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"CALL_FUNCTION_CONFLICT_LENG" "CX_SY_DYN_CALL_ILLEGAL_TYPE"

"/SSA/ABO" or "/SSA/ABO"

"GET_TOP_OBJECTS"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

The exception must either be prevented, caught within proedure

"GET_TOP_OBJECTS" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Former Member
Not what you were looking for? View more on this topic or Ask a question