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

Introducing an error log into existing application

kerstin_hambrecht
Advisor
Advisor

‎2012 May 29 4:36 PM

0 Likes
607

Hi Experts,

I have an existing application that uses an engine. This engine (= function module) triggers messages of type S and E.

We now wanna offer a new UI (ABAP Dynpro) within that application, on this new UI all the messages from the engine shall be shown after a click at the "Error Log" button only.

Means I somehow have to force the system to not bring up a message directly on the UI, but to collect the message in an log (Apllication Log?).

I wanna do this without enhancing all the message statements in the engine!!

I found some information about a similar behavior during background processing:

    A message is not displayed, but instead is written as follows to the background processing log (Joblog) depending on the message type:

    • Messages of type "S" are written to the log and the program is continued.
    • Messages of type "I" and "W" are written to the log and the program is continued. The user input Enter, which is required to continue the program, is generated automatically.
    • Messages of type "E" and "A" are written to the log. A check is then performed and if applicable, the message is handled with error_message. If this is not the case, the message is also written to the log ....

Is there anybody having an idea how I could introduce such log?

Thanks!

Kerstin

Hi Experts,

I have an existing application that uses an engine. This engine (= function module) triggers messages of type S and E.

We now wanna offer a new UI (ABAP Dynpro) within that application, on this new UI all the messages from the engine shall be shown after a click at the "Error Log" button only.

Means I somehow have to force the system to not bring up a message directly on the UI, but to collect the message in an log (Apllication Log?).

I wanna do this without enhancing all the message statements in the engine!!

I found some information about a similar behavior during background processing:

    A message is not displayed, but instead is written as follows to the background processing log (Joblog) depending on the message type:

    • Messages of type "S" are written to the log and the program is continued.
    • Messages of type "I" and "W" are written to the log and the program is continued. The user input Enter, which is required to continue the program, is generated automatically.
    • Messages of type "E" and "A" are written to the log. A check is then performed and if applicable, the message is handled with error_message. If this is not the case, the message is also written to the log ....

Is there anybody having an idea how I could introduce such log?

Thanks!

Kerstin

Reply
2 REPLIES 2
Read only

Former Member

‎2012 May 29 4:50 PM

0 Likes
552 
Kerstin Hambrecht wrote:
Means I somehow have to force the system to not bring up a message directly on the UI, but to collect the message in an log (Apllication Log?). 
I wanna do this without enhancing all the message statements in the engine!!

I think you'll have to enhance the messaages so that they are not written, but collected instead.

Rob

Read only

Former Member

‎2012 May 29 5:06 PM

0 Likes
552

Hi Kerstin,

In most RFC's you have the return parameter, which will hold all the messages generated.

I am guessing you don't have that privilege. If the FM is trigerring the messages using MESSAGE keyword, then it will display this in the screen. You will have to disable this and add all the messages in a Return table as BAPIRET table.

Hope this helps.

Thanks,
Shambu