Application Development 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
Showing results for 
Search instead for 
Did you mean: 

Runtime error RAISE_EXCEPTION has occurred

Former Member
0 Kudos

I am running BDC in background for PP03 and getting this error message "Error message: (00/341) Runtime error RAISE_EXCEPTION has occurred" but while running in foreground it is working fine.In mode E there is no error ie successfully executed but in background this exception

"Exception condition "CNTL_SYSTEM_ERROR" is raised......Please give details analysis of problem as i am new to ABAP-HR..

Pasting the dump also.

ABAP Gurus please dont adivice me to try with other alternates like BAPI etc.

As i am doN'T know about BAPI and i am bound to fix the problem by BDC only

Runtime Error RAISE_EXCEPTION

Occurred on 09.04.2009 at 10:24:10

-


Exception condition "CNTL_SYSTEM_ERROR" raised.

-


What happened?

-


The current ABAP/4 program encountered an unexpected

situation.

-


What can you do?

-


Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

-


Error analysis

-


A RAISE statement in the program "CL_GUI_SPLITTER_CONTAINER=====CP" raised the

exception

condition "CNTL_SYSTEM_ERROR".

Since the exception was not intercepted by a superior program

in the hierarchy, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

-

-


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:

-


"RAISE_EXCEPTION" C

"CL_GUI_SPLITTER_CONTAINER=====CP" or "CL_GUI_SPLITTER_CONTAINER=====CM003"

"CONSTRUCTOR"

-


or

"CL_GUI_SPLITTER_CONTAINER=====CP" "CNTL_SYSTEM_ERROR"

or

"SAPMH5A0 " "CNTL_SYSTEM_ERROR"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

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

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

-


System environment

-


SAP Release.............. "620"

Application server....... "saq2301"

Network address.......... "87.254.218.5"

Operating system......... "HP-UX"

Release.................. "B.11.23"

Hardware type............ "ia64"

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

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

Work process number...... 13

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

Database server.......... "saq2301"

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

Database name............ "F23"

Database owner........... "SAPR3"

Terminal................. " "

Character set............ "en_US.iso88591"

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

Created on............... "Nov 18 2008 20:45:55"

Created in............... "HP-UX B.11.23 U ia64"

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

Patch level.............. "260"

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

Supported environment....

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

10.2.0.."

SAP database version..... "640"

Operating system......... "HP-UX B.11"

-


User, transaction...

-


Client.............. 006

User................ "TESTPIMATHUR"

Language key........ "E"

Transaction......... "PP03 "

Program............. "CL_GUI_SPLITTER_CONTAINER=====CP"

Screen.............. "SAPMH5A0 2000"

Screen line......... 11

-


Information on where terminated

-


The termination occurred in the ABAP program "CL_GUI_SPLITTER_CONTAINER=====CP"

in "CONSTRUCTOR".

The main program was "SAPMH5A0 ".

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

program "CL_GUI_SPLITTER_CONTAINER=====CM003"

of the source code of program "CL_GUI_SPLITTER_CONTAINER=====CM003" (when

calling the editor 220).

The program "CL_GUI_SPLITTER_CONTAINER=====CP" was started as a background job.

Error occurred during batch input processing

-


Source code extract

-


000010

000020 METHOD CONSTRUCTOR .

000030 DATA: RETVAL TYPE SYMSGNO.

000040 DATA: CLSID(80), WINSYS(4),

000050 LEFT_PARAM TYPE I,

000060 TOP_PARAM TYPE I,

000070 WIDTH_PARAM TYPE I,

000080 HEIGHT_PARAM TYPE I.

000090 DATA: HANDLE TYPE CNTL_HANDLE.

000100 DATA: SHELLID TYPE I,

000110 GUIFLAG.

000120 DATA: CPLIST TYPE REF TO LCL_CONTAINER_PANE_LIST.

000130 * DATA: MY_PARENT TYPE REF TO CL_GUI_CONTAINER.

000140

000150 * Clsid

000160 IF not activex is initial.

000170 CLSID = 'SAPGUI.SplitterCtrl.1'.

000180 elseif not javabean is initial.

000190 CLSID = 'com.sap.platin.cet.GuiSplitterShell'.

000200 ENDIF.

000210 IF CLSID IS INITIAL.

-


> RAISE CNTL_SYSTEM_ERROR.

000230 ENDIF.

000240

000250 * Style

000260 IF SHELLSTYLE IS INITIAL.

000270 SHELLSTYLE = CL_GUI_CONTAINER=>WS_VISIBLE

000280 + CL_GUI_CONTAINER=>WS_CHILD.

000290 ENDIF.

000300

000310 * MY_PARENT = GET_DYNPRO_CONTAINER( CONTAINER = PARENT ).

000320

000330 * Call constructor of CL_GUI_CONTAINER

000340 CALL METHOD SUPER->CONSTRUCTOR

000350 EXPORTING

000360 CLSID = CLSID

000370 STYLE = SHELLSTYLE

000380 DYNNR = LINK_DYNNR

000390 REPID = LINK_REPID

000400 PARENT = PARENT

000410 NO_AUTODEF_PROGID_DYNNR = NO_AUTODEF_PROGID_DYNNR

6 REPLIES 6

Former Member
0 Kudos

Hi,

Please try to capture the Error message after using the function module in your BDC Program.

Uncomment the Exception parameters from the Function module used.

Some times it may be due to some package problems also. Meaning that you need to install packages up to date for your SAP System.

Best Regards,

Suresh

0 Kudos

I am not using any function module in BDC. Please tell some other way.

0 Kudos

Hi

That excption is raised for GUI problem, probably the trx PP03 doesn't support the BDC

Max

0 Kudos

Everthing is working fine in foreground but error is generated while I run session in background.So i do not think that trx MM03 is not supported by BDC...

Thanks

0 Kudos

Hi

It depends on which functionality of MM03 u're trying to simulate by BDC

Max

Former Member
0 Kudos

Duplicate post locked.