topic Re: CALL_METHOD_CONFLICT_TYPE Error in Application Development and Automation Discussions

CALL_METHOD_CONFLICT_TYPE Error

Former Member — Wed, 27 Aug 2008 00:05:25 GMT

There is a program that calls a series of LSMW projects and runs them in the background. The program uses SUBMIT to run /SAPDMC/SAP_LSMW_INTERFACE.

The file that the LSMW projects use is in a folder in app server. It is a plain text, CSV file which gets uploaded to the app server using CG3Z.

The program runs fine in DEV and QA. The file in the app server is read and the LSMW projects run successfully. However, when the program gets into production, it is giving the error --

CALL_METHOD_CONFLICT_TYPE

which has the following description:

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 "CHECK_FOR_BOM" "(METHOD)", 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 of the method "CONSTRUCTOR" of the class "CX_SY_FILE_OPEN" is

incorrect. It was tried

to transfer a non-compatible variable to the formal parameter "FILENAME".

Can anyone please give me insights on how to resolve this? It is quite hard for me to debug since it only errors in production and I do not have much access to the program when it's there.

Any ideas will be appreciated.

Thanks.

Re: CALL_METHOD_CONFLICT_TYPE Error

Former Member — Wed, 27 Aug 2008 02:27:40 GMT

when you are submitting the program /SAPDMC/SAP_LSMW_INTERFACE

filename should be of type /SAPDMC/LS_FILENAME

show how you declared filename and submitted.

Re: CALL_METHOD_CONFLICT_TYPE Error

Former Member — Wed, 27 Aug 2008 16:37:22 GMT

This is how I submitted the the program:

SUBMIT /sapdmc/sap_lsmw_interface

USING SELECTION-SET jobvar

AND RETURN.

where jobvar is a variant with default parameters because the LSMW uses direct processing.

In the program where the SUBMIT is, the filename is declared as:

in_file(100) VALUE '/usr/sap/tmp/myfile.csv'

But I am not sure if the way I declared the filename will directly affect the SUBMIT above because the SUBMIT will run LSMW and LSMW will read the file itself.

Re: CALL_METHOD_CONFLICT_TYPE Error

Former Member — Wed, 27 Aug 2008 17:27:27 GMT

did you run the program with the same varaiant with out using submit (i mean direct execution).

check it once.

Re: CALL_METHOD_CONFLICT_TYPE Error

Former Member — Thu, 28 Aug 2008 11:33:51 GMT

Yes, I ran the program with the same variant without using SUBMIT.

It works from there.

Re: CALL_METHOD_CONFLICT_TYPE Error

Former Member — Thu, 28 Aug 2008 11:48:19 GMT

You can try with the Option

WITH selection parameters instead of jobvariant.

some thing like this..

submit /sapdmc/sap_lsmw_interface

with file = '/usr/tmp/etc/...'