Skip to Content
0
Former Member
Oct 27, 2009 at 01:50 PM

short dump Runtime Errors CALL_FUNCTION_CONFLICT_LENG

140 Views

we just move to ECC6 and we have this dump to day, caused by FBL5N, a i looked in the forum and i have found a case not too similar to mine (in that case someone have changed the sourcecode of a standard abap program)

here is the dump:

What happened?

Error in the ABAP Application Program

The current ABAP program "RFITEMAR" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

A function module was called incorrectly.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

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 "POS_TABLE_FILL" "(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 "ITEM_DERIVE_FIELDS" is incorrect:

In the function module interface, you can specify only

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

Although the currently specified field

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

i looked in sap notes and i ve found nothing convincing me,

thank you in advance.

Jamal.