ABAP Runtime Errors

CALL_FUNCTION_CONFLICT_LENG SAP ABAP Runtime Error call function conflict leng







CALL_FUNCTION_CONFLICT_LENG 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: A - ABAP Programming 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_CONFLICT_LENG ABAP Runtime Error

Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

If the error occurs in program SAPCNVE, one of the following situations might have arisen:

1. The field is referenced by a function module called "..._INPUT", or the field is referenced by a function module called "..._OUTPUT". This is probably due to an error in the definition of the function module interface. No reference field should be specified for the corresponding parameters.

2. The field is referenced by a function module called "..._OUTPUT.
The GPA mechanism might have been used to read a value from the SAP memory with an incorrect length. In ABAP, the material number conversion MATN1 expects a material number with length 18. If a value with length 1 is found under the ID MAT instead, this termination occurs.
To view the current contents of the SAP memory, open Debugging and choose Goto -> System -> System Areas. View Area SMEM. There are a number of explanations for a GPA value having the wrong length:

a) The user master record contains a value with the wrong 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 program, a SET-PARAMETER statement has a value with the wrong length, e.g. SET PARAMETER ID 'MAT' FIELD '1'. Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Please see funcparm error for more details about the possible cause of this runtime error and how it could be avoided.

Type conflict during a function module call (field length). Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

The call to function module <runtime parameter> is incorrect:

In the function module interface, it was stipulated that only fields of a specific type and length can be specified under <runtime parameter>. The currently specified field )<runtime parameter>) has the right type, but its length is incorrect. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

A function module was called incorrectly.