Application Development and Automation 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: 
Read only

Exception condition "CONVERSION_ERROR" raised.

Former Member
0 Likes
2,365

Hi,

We have been getting short dumps in our production system daily. I was unable to locate the problem by looking at the dump. The dump says that CONVERSION_ERROR raised.

Which application raised this exception? Again no clue on the same. Please find the text of the dump.

Short text

Exception condition "CONVERSION_ERROR" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

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

exception

condition "CONVERSION_ERROR".

Since the exception was not intercepted by a superior

program, 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

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"RAISE_EXCEPTION" " "

"CL_SWF_CNT_CONTAINER==========CP" or "CL_SWF_CNT_CONTAINER==========CM02J"

"IF_SWF_CNT_CONVERSION~TO_XML"

or

"CL_SWF_CNT_CONTAINER==========CP" "CONVERSION_ERROR"

or

"SAPMSSY1 " "CONVERSION_ERROR"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP-Release 700

Application server... "zacwtbsrv0

Network address...... "10.27.191.

Operating system..... "Windows NT

Release.............. "5.2"

Hardware type........ "4x AMD64 L

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 9

Shortdump setting.... "full"

Database server... "ZACWTBSRV063"

Database type..... "MSSQL"

Database name..... "EP1"

Database user ID.. "ep1"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Apr 21 2008 00:12:39"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "SQL_Server_8.00 "

Patch level. 157

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 16192

EM...... 8379680

Heap.... 0

Page.... 16384

MM Used. 8164576

MM Free. 212256

User and Transaction

Client.............. 100

User................ "WF-BATCH"

Language Key........ "E"

Transaction......... " "

Transactions ID..... "FB565CDDF6D0F1BFA292001E0B5D7336"

Program............. "CL_SWF_CNT_CONTAINER==========CP"

Screen.............. "SAPMSSY1 3004"

Screen Line......... 2

Information on caller of Remote Function Call (RFC):

System.............. "EP1"

Database Release.... 700

Kernel Release...... 700

Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "synchron and transactional (emode 0, imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........."0A1BBF4011A4488D408222BD"

Outbound Queue Name.." "

Client.............. 100

User................ "HPRETORIUS"

Transaction......... " "

Call Program........."SAPLERFC"

Function Module..... "ARFC_DEST_SHIP"

Call Destination.... "WORKFLOW_LOCAL_100"

Source Server....... "zacwtbsrv064_EP1_00"

Source IP Address... "10.27.191.64"

Additional information on RFC logon:

Trusted Relationship " "

Logon Return Code... 0

Trusted Return Code. 0

Note: For releases < 4.0, information on the RFC caller are often

only partially available.

Information on where terminated

Termination occurred in the ABAP program "CL_SWF_CNT_CONTAINER==========CP" -

in "IF_SWF_CNT_CONVERSION~TO_XML".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 67

of the (Include) program "CL_SWF_CNT_CONTAINER==========CM02J".

Source Code Extract

Line SourceCde

37 lv_xml_table_req = 'X'.

38 ENDIF.

39 IF xml_stream IS REQUESTED.

40 lv_xml_stream_req = 'X'.

41 ENDIF.

42

43 IF use_xslt NE space.

44

45 cl_swf_cnt_conversion_service=>to_xml_xslt(

46 EXPORTING

47 container = me

48 include_null_values = include_null_values

49 include_initial_values = include_initial_values

50 include_change_data = include_change_data

51 include_texts = include_texts

52 include_extension_elements = include_extension_elements

53 save_delta_handling_info = save_delta_handling_info

54 xml_dom_req = lv_xml_dom_req

55 xml_table_req = lv_xml_table_req

56 xml_stream_req = lv_xml_stream_req

57 IMPORTING

58 xml_dom = xml_dom

59 xml_table = xml_table

60 xml_stream = xml_stream

61 xml_rendered_size = xml_rendered_size

62 EXCEPTIONS

63 conversion_error = 1

64 OTHERS = 2

65 ).

66 IF sy-subrc <> 0.

>>>> RAISE conversion_error.

68 ENDIF.

69

70 ELSE.

71

72 cl_swf_cnt_conversion_service=>to_xml_ixml(

73 EXPORTING

74 container = me

75 include_null_values = include_null_values

76 include_initial_values = include_initial_values

77 include_typenames = include_typenames

78 include_change_data = include_change_data

79 include_texts = include_texts

Could you please help me out in resolving this issue?

Is there any need to apply any OSS notes?

Thanks in advance. And reward points will be given for the solution..

Thanks,

Ravikumar.

Hi,

We have been getting short dumps in our production system daily. I was unable to locate the problem by looking at the dump. The dump says that CONVERSION_ERROR raised.

Which application raised this exception? Again no clue on the same. Please find the text of the dump.

Short text

Exception condition "CONVERSION_ERROR" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

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

exception

condition "CONVERSION_ERROR".

Since the exception was not intercepted by a superior

program, 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

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"RAISE_EXCEPTION" " "

"CL_SWF_CNT_CONTAINER==========CP" or "CL_SWF_CNT_CONTAINER==========CM02J"

"IF_SWF_CNT_CONVERSION~TO_XML"

or

"CL_SWF_CNT_CONTAINER==========CP" "CONVERSION_ERROR"

or

"SAPMSSY1 " "CONVERSION_ERROR"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP-Release 700

Application server... "zacwtbsrv0

Network address...... "10.27.191.

Operating system..... "Windows NT

Release.............. "5.2"

Hardware type........ "4x AMD64 L

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 9

Shortdump setting.... "full"

Database server... "ZACWTBSRV063"

Database type..... "MSSQL"

Database name..... "EP1"

Database user ID.. "ep1"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Apr 21 2008 00:12:39"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "SQL_Server_8.00 "

Patch level. 157

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 16192

EM...... 8379680

Heap.... 0

Page.... 16384

MM Used. 8164576

MM Free. 212256

User and Transaction

Client.............. 100

User................ "WF-BATCH"

Language Key........ "E"

Transaction......... " "

Transactions ID..... "FB565CDDF6D0F1BFA292001E0B5D7336"

Program............. "CL_SWF_CNT_CONTAINER==========CP"

Screen.............. "SAPMSSY1 3004"

Screen Line......... 2

Information on caller of Remote Function Call (RFC):

System.............. "EP1"

Database Release.... 700

Kernel Release...... 700

Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "synchron and transactional (emode 0, imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........."0A1BBF4011A4488D408222BD"

Outbound Queue Name.." "

Client.............. 100

User................ "HPRETORIUS"

Transaction......... " "

Call Program........."SAPLERFC"

Function Module..... "ARFC_DEST_SHIP"

Call Destination.... "WORKFLOW_LOCAL_100"

Source Server....... "zacwtbsrv064_EP1_00"

Source IP Address... "10.27.191.64"

Additional information on RFC logon:

Trusted Relationship " "

Logon Return Code... 0

Trusted Return Code. 0

Note: For releases < 4.0, information on the RFC caller are often

only partially available.

Information on where terminated

Termination occurred in the ABAP program "CL_SWF_CNT_CONTAINER==========CP" -

in "IF_SWF_CNT_CONVERSION~TO_XML".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 67

of the (Include) program "CL_SWF_CNT_CONTAINER==========CM02J".

Source Code Extract

Line SourceCde

37 lv_xml_table_req = 'X'.

38 ENDIF.

39 IF xml_stream IS REQUESTED.

40 lv_xml_stream_req = 'X'.

41 ENDIF.

42

43 IF use_xslt NE space.

44

45 cl_swf_cnt_conversion_service=>to_xml_xslt(

46 EXPORTING

47 container = me

48 include_null_values = include_null_values

49 include_initial_values = include_initial_values

50 include_change_data = include_change_data

51 include_texts = include_texts

52 include_extension_elements = include_extension_elements

53 save_delta_handling_info = save_delta_handling_info

54 xml_dom_req = lv_xml_dom_req

55 xml_table_req = lv_xml_table_req

56 xml_stream_req = lv_xml_stream_req

57 IMPORTING

58 xml_dom = xml_dom

59 xml_table = xml_table

60 xml_stream = xml_stream

61 xml_rendered_size = xml_rendered_size

62 EXCEPTIONS

63 conversion_error = 1

64 OTHERS = 2

65 ).

66 IF sy-subrc <> 0.

>>>> RAISE conversion_error.

68 ENDIF.

69

70 ELSE.

71

72 cl_swf_cnt_conversion_service=>to_xml_ixml(

73 EXPORTING

74 container = me

75 include_null_values = include_null_values

76 include_initial_values = include_initial_values

77 include_typenames = include_typenames

78 include_change_data = include_change_data

79 include_texts = include_texts

Could you please help me out in resolving this issue?

Is there any need to apply any OSS notes?

Thanks in advance. And reward points will be given for the solution..

Thanks,

Ravikumar.

4 REPLIES 4
Read only

Former Member
0 Likes
1,616

Hi,

This dump occurs when you pass inappropriate data types to another data type where no conversion rule exists.

Check this link for more info:-

http://help.sap.com/saphelp_nw04/Helpdata/EN/fc/eb3427358411d1829f0000e829fbfe/content.htm

Best of luck,

Bhumika

Read only

vinod_vemuru2
Active Contributor
0 Likes
1,616

Hi,

U will receive this error when ever it is not possible to achieve runtime conversion.

i.e When u r passing the data from one type variable to another type if the conversion is not defined or not possible u will get this dump. Just analyze the dump in ST22.

Look at this simple example. Here i am trying to assign 101.23 to l_p for which length is not sufficient. So i will get dump. But if u do the same with character variable it will truncate the data.

DATA: l_p(2) TYPE P DECIMALS 2.

l_p = '103.23'.

WRITE l_p.

So check the place where u r getting the dump. It must be some assignment statement.

Hope it gave some idea on ur case.

Thanks,

Vinod.

Read only

Former Member
0 Likes
1,616

Hi Bhumika and Vinod,

Your information is most useful. But the exception was raised in standard SAP program. I don't have any clue which application is causing this dump. If I can know the application which is triggering the dump I can validate the values that are being passed and why this dump has been triggered.

I think there must be some conversion rules that should be applied along with SAP note.

Can anybody suggest on the same?

Thanks,

Ravikumar.

Read only

Former Member
0 Likes
1,616

Please check the Data types of the variables you are trying to transfer the data.

If that is fine, Check for the data u are passing. It should not exceed the total length it is allowed to do in Numc case.

Probably this can solve the issue.