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

User-exit F-02 to avoid program termination.

Former Member

‎2009 Mar 23 7:33 PM

0 Likes
672

Hi All.

We've written a small validation in user-exit ZXF48U01 of module function EXIT_SAPLF048_001 od enhacement F180A001.

At certain point, if data is not as requested a proper 'E' message is triggered but this is causing standard to trigger an 'A' message and abort the transaction causing all data to be lost.

message e208(11) with text-e01.

Could you give an alternate use of message to avoid program termination?

We're in 4.6C release, so, message 'E' display like 'S' variant doesn't apply.

Thanks & Regards.

Hi All.

We've written a small validation in user-exit ZXF48U01 of module function EXIT_SAPLF048_001 od enhacement F180A001.

At certain point, if data is not as requested a proper 'E' message is triggered but this is causing standard to trigger an 'A' message and abort the transaction causing all data to be lost.

message e208(11) with text-e01.

Could you give an alternate use of message to avoid program termination?

We're in 4.6C release, so, message 'E' display like 'S' variant doesn't apply.

Thanks & Regards.

Reply
2 REPLIES 2
Read only

Former Member

‎2009 Mar 23 7:39 PM

0 Likes
546

Hi,

Try giving information Message and than EXIT.

Message I208(11) with text-e01.

EXIT.

Read only

Former Member
In response to Former Member

‎2009 Mar 23 9:42 PM

0 Likes
546

Hi, i'm afraid that won't work. In fact, we've switch all message types, but it doesn't seems to work in the way we want.

What we are trying is to validate at item level sgtxt and zuonr field contents, if in certain conditions values don't match specific ones, don't let post the document but stand still in transaction to fix data.

For message type E (and obviously A), validations occurs, but program is terminated and all data entered discarded. For all others message types, we get the message displayed, but document is posted which is suppossed to be restricted.

To be more specific, after this exit finishes, it returns to form fcode_bearbeitung(MF05AFF0_FCODE_BEARBEITUNG) at 'BREAKDOWN_RELATION_FI_DOC' call function, after this, for any error message triggered standard will send an 'A' message, this is what were are trying to avoid.

Hope this helps to clarify scenary.