Skip to Content

SOLMAN Transaction saving with CONDITION CHECK errors

Dear Folks,

Reqeust your assistance.

I followed the steps given in the blog Condition Check and was able to successfully implement custom condition checks in SOLMAN ChaRM process.
However, I have a small issue. Although I was able to display error on the UI based on the condition check, the transaction was still getting saved. Meaning, the UI shows 2 messages – one for the error from the condition check and second success message stating that the transaction is saved (standard message). Refer the image.

I do not want to save the transaction in case of any errors, so I did some analysis and found the there is a BADI called ORDER_SAVE where we can restrict the saving. Cool !!
However, when tested, I noticed that the BADI ORDER_SAVE gets called before the BADI SOCM_CHECK_CONDITION is called. Therefore I could not stop saving the transaction since by the time my condition checks are performed, the ORDER_SAVE BADI is already completed execution.

Hope you understand my situation here. Do you have any pointers on how I can restrict saving the transaction if there are any error during the condition checks?



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

0 Answers