Community
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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Is it possible to catch a hard-coded message type 'E' or 'A' from calling program

Former Member

‎2013 Oct 02 5:36 AM

0 Likes
1,290

Hi,

We are running a SAP standard program which contains error messages hard-coded with type 'E' or 'A', such as -

message eNNN(XX).

When these statements are executed, the runtime system will simply stop the SAP standard program with an error message or a dump.

Is there a way to "catch" these errors and handle them according to our own logic? (perhaps using a wrapper Z program to call the SAP standard program)

Hi,

We are running a SAP standard program which contains error messages hard-coded with type 'E' or 'A', such as -

message eNNN(XX).

When these statements are executed, the runtime system will simply stop the SAP standard program with an error message or a dump.

Is there a way to "catch" these errors and handle them according to our own logic? (perhaps using a wrapper Z program to call the SAP standard program)

Reply
1 REPLY 1
Read only

alejandro_mejias
Active Participant

‎2013 Oct 02 2:37 PM

0 Likes
647

You can use a Z report with call transaction statement with the messages option, but even in this way you cannot avoid the abort of the transaction execution.

http://help.sap.com/saphelp_erp60_sp/helpdata/en/fa/09715a543b11d1898e0000e8322d00/content.htm

You can capture the error and perform something but the transaction will state cannot be recovered.

Best regards