E-Commerce create order runtime error because of user-exit

Question

Hi all,
we face the following problem in our e-Commerce 5.0 R3 B2B application:
In our R3 system, we have implemented the userexit_save_document_prepare when creating sales order (VA01) because we do not want an order to be created (saving is cancelled) if some conditions are not met. If this happens, the systems throws an error message that users can see at the status bar and the order creation is cancelled (but the user still is on the VA01 transaction).
Now, we are implementing SAP e-Commerce solution and we can create orders when these messages are not thrown (the order is saved without any message because all conditions are met). If one of these error messages (in user-exit) are thrown (the user has exceeded some limit, for instance), then e-Commerce application does not show the message but shows a runtime error and crashes (user has to log in again and so on...). I include the error trace below.
Is it not possible to show these error messages (which have information for user) on our B2B application?
com.sap.isa.businessobject.BORuntimeException: order create not possible
     at com.sap.isa.businessobject.BusinessObjectHelper.splitException(BusinessObjectHelper.java:78)
     at com.sap.isa.businessobject.order.Order.saveAndCommit(Order.java:393)
     at com.sap.isa.isacore.action.order.MaintainBasketSimulationSendAction.basketPerform(MaintainBasketSimulationSendAction.java:122)
     at com.sap.isa.isacore.action.order.MaintainBasketBaseAction.isaPerform(MaintainBasketBaseAction.java:998)
     at com.sap.isa.isacore.action.IsaCoreBaseAction.ecomPerform(IsaCoreBaseAction.java:343)
     at com.sap.isa.isacore.action.EComBaseAction.doPerform(EComBaseAction.java:353)
     at com.sap.isa.core.BaseAction.execute(BaseAction.java:211)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:674)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
     at com.tealeaf.capture.LiteFilter.doFilter(Unknown Source)
     at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61)
     at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Thanks in advance.

Answer 1

Hi Jolly,
thanks for your quick response. The user-exist is not java-based but ABAP-based. User-exit is included in program: MV45AFZZ. Routine: USEREXIT_SAVE_DOCUMENT_PREPARE.
If we do not want to let the user save the order we use:
MESSAGE eXXX....
Thanks.