Dump CALL_FUNCTION_CONFLICT_TYPE

[shwetha_hs]

Hi,

I am coming across a strange dump. My code is like this.

*****************************************

Function A.

*"----

---

*" CHANGING

*" REFERENCE(par1) TYPE bus_ei.

*"----

---

call function B

changing par1 = par1.

*****************************************

Function B.

*"----

---

*" CHANGING

*" REFERENCE(par1) TYPE bus_ei.

*"----

---

The call to FM B from FM A is dumping with the ablve text which says that The field "par1" specified here is a different

field type. CALL_FUNCTION_CONFLICT_TYPE CX_SY_DYN_CALL_ILLEGAL_TYPE.

But their types are same ie bus_ei. So why should there be a dump? Could any of you have an idea..

Thanks,

Shwetha

[Former Member]

Maybe it's not the call from A to B that dumps but the call to A?

Anyway, showing the real program codes might prove useful.

-

---

Please hug me!

[shwetha_hs]

No. Call to B from A is dumping.

[Former Member]

show us your code, and maybe even the start of the dump, please.

[shwetha_hs]

function bupa_outbound_transmit_bp.

*"----

---

""Local Interface:

*" CHANGING

*" REFERENCE(CT_BP) TYPE BUS_EI_MAIN

call function 'MDS_BUPA_OUTBOUND'

changing

ct_bp = ct_bp.

-

---

function mds_bupa_outbound.

*"----

---

""Local Interface:

*" CHANGING

*" REFERENCE(CT_BP) TYPE BUS_EI_MAIN

*"----

---

.

.

.

The Call call function 'MDS_BUPA_OUTBOUND'

dumps.

Dump text is here:

Runtime Errors CALL_FUNCTION_CONFLICT_TYPE

Except. CX_SY_DYN_CALL_ILLEGAL_TYPE

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLBUPA_INTERFACE_OUTBOUND" 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 "BUPA_OUTBOUND_TRANSMIT_BP" "(FUNCTION)", 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 "MDS_BUPA_OUTBOUND" is incorrect:

The function module interface allows you to specify only

fields of a particular type under "CT_BP".

The field "CT_BP" specified here is a different

field type

.

It refers to the same line.. which is call function 'MDS_BUPA_OUTBOUND'

[Former Member]

Couldn't find anything strange, so i'm a bit amazed as well. Maybe raise an OSS message for this one.

-

---

Please hug me!

[Former Member]

Thats WICKED.

On first sight i dont see any problems and i agree to you, this SHOULD work.

All i can see so far is that BUS_EI_MAIN is a deep structure containing two tables.

If i can remeber it right there are issues with CHANGING parameters and deep structures.

try making an import an an export parameter out of it. I sens this is the Problem.

Edited by: Florian Kemmer on Nov 11, 2010 12:18 PM

[Former Member]

Hi,

Just checjk if the import parameters typed in tab are the same as in function module.

That might be causing the problem.

rohit.

[Former Member]

Hi Swetha

We are Also facing same dump.

How did you solve this issue?

Regards,

Sushma.