Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

CALL_METHOD_CONFLICT_GEN_TYPE dump.

Former Member

‎2011 Sep 02 3:22 PM

0 Likes
606

I'm implementing the user exit for BW extraction and this function module receives a tables parameter of type ANY. Now I want to pass this table to a method so I created a changing parameter type ANY TABLE.

When trying to pass the data I receive a CALL_METHOD_CONFLICT_GEN_TYPE dump.

Is there any simple solution to overcome this problem?

Best regards

Sharad

I'm implementing the user exit for BW extraction and this function module receives a tables parameter of type ANY. Now I want to pass this table to a method so I created a changing parameter type ANY TABLE.

When trying to pass the data I receive a CALL_METHOD_CONFLICT_GEN_TYPE dump.

Is there any simple solution to overcome this problem?

Best regards

Sharad

Reply
2 REPLIES 2
Read only

Sandra_Rossi
Active Contributor

‎2011 Sep 03 12:04 AM

0 Likes
499

Hi,

This is probably because you passed the header line instead of the internal table body: TABLES keyword (in FORM, FUNCTION) automatically defines a header line. Use square brackets like this:

CALL METHOD yourmeth CHANGING itab = funcitab[].

Sandra

Read only

matt
Active Contributor
In response to Sandra_Rossi

‎2011 Sep 05 6:01 AM

0 Likes
499

I keep getting caught by this. There are two places where tables with header lines - incompatible with ABAP objects - linger; in function module TABLES parameters, and SELECT-OPTIONS.