cancel
Showing results for 
Search instead for 
Did you mean: 

CALL_FUNCTION_CONFLICT_TYPE Standard Data loading

Former Member
0 Kudos

Hi,

I am facing a data loading problem using Business content on CPS_DATE infocube (0PS_DAT_MLS datasource).

The R/3 extraction processes without any error, but the problem occurs in the update rules while updating the milestone date. Please find hereunder the log from the ST22.

The real weird thing is that the process works perfectly in development environment and not in integration one (the patch levels are strongly the same: BW 3.5 Patch #16).

I apologise for the long message below... this is a part of the system log.

For information the routine_0004 is a standard one.

Thanks a lot in advanced!

Cheers.

CALL_FUNCTION_CONFLICT_TYPE

Except. CX_SY_DYN_CALL_ILLEGAL_TYPE

Symptoms. Type conflict when calling a function module

Causes Error in ABAP application program.

The current ABAP program "GP420EQ35FHFOCVEBCR6RWPVQBR" had to be terminated because one of the statements could not be executed.

This is probably due to an error in the ABAP program.

A function module was called incorrectly.

Errors analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was neither caught nor passed along using a RAISING clause, in the procedure "ROUTINE_0004"

"(FORM)" .

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated. The reason for the exception is:

The call to the function module "RS_BCT_TIMCONV_PS_CONV" is incorrect:

The function module interface allows you to specify only fields of a particular type under "E_FISCPER".

The field "RESULT" specified here is a different field type.

How to correct the error.

You may able to find an interim solution to the problem in the SAP note system. If you have access to the note system yourself, use the following search criteria:

-

-


"CALL_FUNCTION_CONFLICT_TYPE" CX_SY_DYN_CALL_ILLEGAL_TYPEC

"GP420EQ35FHFOCVEBCR6RWPVQBR" or "GP420EQ35FHFOCVEBCR6RWPVQBR"

"ROUTINE_0004"

-

-


-

-


If you cannot solve the problem yourself and you wish to send

an error message to SAP, include the following documents:

1. A printout of the problem description (short dump)

To obtain this, select in the current display "System->List->

Save->Local File (unconverted)". 2. A suitable printout of the system log To obtain this, call the system log through transaction SM21. Limit the time interval to 10 minutes before and 5 minutes after the short dump. In the display, then select the function

"System->List->Save->Local File (unconverted)".

3. If the programs are your own programs or modified SAP programs, supply the source code.

To do this, select the Editor function "Further Utilities-> Upload/Download->Download".

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

The exception must either be prevented, caught within the procedure

"ROUTINE_0004"

"(FORM)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Environment system SAP Release.............. "640"

Operating system......... "SunOS" Release.................. "5.9"

Hardware type............ "sun4u"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 2

Short dump setting....... "full"

Database type............ "ORACLE"

Database name............ "BWI"

Database owner........... "SAPTB1"

Character set............ "fr"

SAP kernel............... "640"

Created on............... "Jan 15 2006 21:42:36" Created in............... "SunOS 5.8 Generic_108528-16 sun4u"

Database version......... "OCI_920 "

Patch level.............. "109"

Patch text............... " "

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version..... "640"

Operating system......... "SunOS 5.8, SunOS 5.9, SunOS 5.10"

SAP Release.............. "640"

The termination occurred in the ABAP program "GP420EQ35FHFOCVEBCR6RWPVQBR" in

"ROUTINE_0004".

The main program was "RSMO1_RSM2 ".

The termination occurred in line 702 of the source code of the (Include)

program "GP420EQ35FHFOCVEBCR6RWPVQBR"

of the source code of program "GP420EQ35FHFOCVEBCR6RWPVQBR" (when calling the editor 7020).

Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_TYPE" occurred in the procedure "ROUTINE_0004" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.

The procedure is in the program "GP420EQ35FHFOCVEBCR6RWPVQBR ". Its source code starts in line 685 of the (Include) program "GP420EQ35FHFOCVEBCR6RWPVQBR ".

672 'ROUTINE_0003' g_s_is-recno

673 rs_c_false rs_c_false g_s_is-recno

674 changing c_abort.

675 catch cx_foev_error_in_function.

676 perform error_message using 'RSAU' 'E' '510'

677 'ROUTINE_0003' g_s_is-recno

678 rs_c_false rs_c_false g_s_is-recno

679 changing c_abort.

680 endtry.

681 endform.

682 ************************************************************************

683 * routine no.: 0004

684 ************************************************************************

685 form routine_0004

686 changing

687 result type g_s_hashed_cube-FISCPER3

688 returncode like sy-subrc

689 c_t_idocstate type rsarr_t_idocstate

690 c_subrc like sy-subrc

691 c_abort like sy-subrc. "#EC *

692 data:

693 l_t_rsmondata like rsmonview occurs 0 with header line. "#EC *

694

695 try.

696 * init

variables

697 move-corresponding g_s_is to comm_structure.

698

699 * fill the internal table "MONITOR", to make monitor entries

700

701 * result value of the routine

>>>> CALL FUNCTION 'RS_BCT_TIMCONV_PS_CONV'

703 EXPORTING

704 I_TIMNM_FROM = '0CALDAY'

705 I_TIMNM_TO = '0FISCPER'

706 I_TIMVL = COMM_STRUCTURE-CALDAY

707 I_FISCVARNT = gd_fiscvarnt

708 IMPORTING

709 E_FISCPER = RESULT.

710 * if the returncode is not equal zero, the result will not be updated

711 RETURNCODE = 0.

712 * if abort is not equal zero, the update process will be canceled

713 ABORT = 0.

714

715 catch cx_sy_conversion_error

716 cx_sy_arithmetic_error.

717 perform error_message using 'RSAU' 'E' '507'

718 'ROUTINE_0004' g_s_is-recno

719 rs_c_false rs_c_false g_s_is-recno

720 changing c_abort.

721 catch cx_foev_error_in_function.

System zones content

Name Val.

SY-SUBRC 0

SY-INDEX 2

SY-TABIX 0

SY-DBCNT 0

SY-FDPOS 65

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY 0400

SY-UCOMM OK

SY-TITLE Moniteur - Atelier d'administration

SY-MSGTY E

SY-MSGID RSAU

SY-MSGNO 583

SY-MSGV1 BATVC 0000000000

SY-MSGV2 0PROJECT

SY-MSGV3

SY-MSGV4

Selected variables

Nº 23 Tpe FORM

Name ROUTINE_0004

GD_FISCVARNT

22

00 RS_C_INFO I

4

9

COMM_STRUCTURE-CALDAY

20060303

33333333

20060303

SYST-REPID GP420EQ35FHFOCVEBCR6RWPVQBR 4533345334444454445355555452222222222222 704205135686F365232627061220000000000000

RESULT

000

333

00

%

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

You have an update routine in which youar callin FM 'RS_BCT_TIMCONV_PS_CONV'. Parameter e_fiscper must be the same that type of the variable you use (you can see the data tyoe in FM definition, transaction se37). You should do somethin like the following.

DATA: var type <the same that e_fiscper in FM definition>

CALL FUNCTION 'RS_BCT_TIMCONV_PS_CONV'

EXPORTING

I_TIMNM_FROM = '0CALDAY'

I_TIMNM_TO = '0FISCPER'

I_TIMVL = COMM_STRUCTURE-CALDAY

I_FISCVARNT = gd_fiscvarnt

IMPORTING

E_FISCPER = var.

result = var.

--- ASSIGN POINTS IS USEFUL.

Former Member
0 Kudos

Hi,

I guess you have incorrect datefield. look at this from your dump:

<i>COMM_STRUCTURE-CALDAY

20060303

33333333

20060303</i>

the 2nd date (33333333) seem2 wrong and system cannot derive a fisc.period, correct this record in psa.

/manfred