on 09-24-2013 2:54 PM
We have a requirement to exit out of EXIT_SAPLV56U_004 without saving under certain circumstances. However, there is not an exception defined for FM EXIT_SAPLV56U_004. We have tested out adding an exception to the FM and it does give us the functionality we need, but has anyone else tried to do this and encountered any issues we should be aware of before we adopt this as our final solution? We have simply modified EXIT_SAPLV56U_004 to have the exception OTHERS and then added the RAISE OTHERS command in the userexit code.
We appreciate any feedback from anyone who has either successfully implemented this same modification, or who has encountered issues after doing so.
Hi Erin,
Instead of adding an exception to the EXIT, would it not be better to instead move your code inside the Exit between an IF..ELSE..ENDIF block and add your specific logic to either the IF or the ELSE part.
Regards,
Shashi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shashi,
Thank you for your reply. However, we did try a number of different ways of generating an error message within the userexit code. We found that, while it did send an error message, it would not stop the changes made to the order from actually saving as it progressed through the code past the call to the userexit. The only way we found to actually stop the save functionality and still have the transaction end cleanly was to add the exception.
Erin
Also, I should say that we are fine with having made the modification to enable the exception, we were just concerned about any potential negative impacts to doing so. But it does appear to be working for our requirements, so if no one responds saying they encountered issues attempting to do the same, then we are happy.
User | Count |
---|---|
107 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.