cancel
Showing results for 
Search instead for 
Did you mean: 

CALL_FUNCTION_CONFLICT_TYPE Error in R/3

Former Member
0 Kudos

Hi Friends

My 0FI_AR and 0FI_AP loads have ran succesfully till yesterday and the same loads failed today due to the error 'CALL_FUNCTION_CONFLICT_TYPE' in R/3 and the loads have been cancelled.

Why the loads have failed and what should be done to resolve it?

Regards,

Chama.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

seems like there is a inconsistency between a parameter of the calling program and the called function. Look at the short dump and you will get the information which parameter is causing the error. In case it is a custum fm correct it, otherwise open a error message at http://www.service.sap.com

regards

Siggi

Former Member
0 Kudos

Hi Chandu

I am also facing a similar issue. We ran one job some 2 or 3 times on the same day but it is getting cancelled now due dump error ABAP/4 processor: CALL_FUNCTION_CONFLICT_TYPE. This dump is coming due to parameter incompatibity in the function module JOB_CLOSE.

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 "SUBMIT_JOB" "(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 "JOB_CLOSE" is incorrect:

The function module interface allows you to specify only

fields of a particular type under "TARGETSERVER".

The field "MYNAME" specified here is a different

field type.

CALL FUNCTION 'JOB_CLOSE'

EXPORTING

jobname = jobname

jobcount = jobcount

  • strtimmed = 'X'.

strtimmed = 'X'

  • TARGETSYSTEM = SY-HOST.

  • targetsystem = sy-host

targetserver = myname

EXCEPTIONS "QIZK001068

cant_start_immediate = 1 "QIZK001068

invalid_startdate = 2 "QIZK001068

jobname_missing = 3 "QIZK001068

job_close_failed = 4 "QIZK001068

job_nosteps = 5 "QIZK001068

job_notex = 6 "QIZK001068

lock_failed = 7 "QIZK001068

OTHERS = 8.

DATA myname LIKE msxxlist-name.

Structure MSXXLIST Active

NAME MSNAME2 CHAR 40 0 Application Server Name

Function module JOB_CLOSE Active

TARGETSERVER LIKE BTCTGTSRVR-SRVNSPACE

Structure BTCTGTSRVR Active

SRVNAME BTCSRVNAME CHAR 20 0 Server name

My question is why is this dump coming now after running the same job again, as earlier it got run successfully. Also, do i need to fix this this.

Answers (0)