Message_type_x error in a custom program

[Former Member]

Hi,

I am getting Message_type_x error in the program

" The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X)."

I am getting this error message only for a particular project rest of the projects are working fine i mean in the ALV output a particular project is not displayed and giving this dump,

But the same project in ALV is working correctly in different client.

Could you please suggest the reason and solution for the same.

[former_member195698]

Can you send the details of the Dump?

[Former Member]

Please do this...

go to st22....get your details of the dump ....that will be helpful to give a solution to you...

[Former Member]

Hi,

I have already gone through the dump but didnt find any solution i tried so many OSS Notes also but that were not useful.

Could you please suggest something.

this the dump which is coming:

The current application triggered a termination with a short dump.

What happened?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

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

Short text of error message:

Control Framework : Error processing control

Information on where terminated

The termination occurred in the ABAP program "SAPLOLEA" in "AC_SYSTEM

The main program was "Z_PS_COST_FOLLOW_UP ".

The termination occurred in line 29 of the source code of the (Includ

program "LOLEAU02"

of the source code of program "LOLEAU02" (when calling the editor 290

Source code extract

000010 FUNCTION AC_SYSTEM_FLUSH .

000020 *"

000030 ""Lokale Schnittstelle:

000040 *" IMPORTING

000050 *" VALUE(CALLED_BY_SYSTEM) TYPE C OPTIONAL

000060 *" EXCEPTIONS

000070 *" CNTL_SYSTEM_ERROR

000080 *" CNTL_ERROR

000090 *"

000100 data: sysubrc like sy-subrc.

000110

000120 CALL FUNCTION 'AC_FLUSH_CALL'

000130 EXPORTING

000140 SYSTEM_FLUSH = 'X'

000150 CALLED_BY_SYSTEM = CALLED_BY_SYSTEM

000160 IMPORTING

000170 MESSAGE_NR = sysubrc

000180 MESSAGE_TEXT = SY-MSGLI.

000190

000220 CASE SY-SUBRC.

000230 WHEN 0.

000240 WHEN 1.

000250 * system_error

000260 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 007 RAISING CNTL_SYSTEM_ERROR.

000270 WHEN 2.

000280 * method_call_error

> MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.

000300 WHEN 3.

000310 * property_set_error

000320 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.

000330 WHEN 4.

000340 * property_get_error

000350 MESSAGE ID 'CNDP' TYPE 'X' NUMBER 006 RAISING CNTL_ERROR.

000360 WHEN OTHERS.

000370 RAISE CNTL_ERROR.

000380 ENDCASE.

000390

000400 ENDFUNCTION.

And the main thing is that this dump is coming only for a particular project in ALV.