‎2007 Aug 08 9:37 AM
Dear experts,
I have encountered the following problem. I am using a user exit or a BADI that consists the internal tables that I need to check and provide an error message so that the processing does NOT continue. But all the user exits that help me, reside in the COMMIT state of the program, so any error message after that ends in the above abap error. saying that the processing cannot be stopped there.
I tried to use the statement ROLLBACK work, after my error message, again the same short dump.
Is there any other way to achieve stopping the processing after commit?
Thank you in advance,
Roxani Athousaki
‎2007 Aug 08 9:46 AM
Within what transaction are you doing this and which User Exit/BADI.
‎2007 Aug 08 9:59 AM
Thank you for answering.
The badi I am using is IF_EX_WORKORDER_UPDATE~BEFORE_UPDATE.
and the tables I need to check are stat_new[] and stat_old[].
in program : SAPLCOBT.
thank you...
‎2007 Aug 08 9:53 AM
what BADI u are using ? , provide more details .
Regards
Peram
‎2007 Aug 08 10:06 AM
Hi Roxani,
1. Instead of giving the error message directly,
2. Just check in the BAdi whether there is a return structure / return itab,
to fill with error messages.
If that is there, then the main program calling the BADI,
will automatically handle this.
(We only need to pass the error information via the badi return structure/itab)
Regards,
Amit Mittal.
‎2007 Aug 08 10:21 AM
Dear Amit,
unfortunatelly no raise of error messages exist in the badi:
BADI is active -> call method at_save
CALL METHOD lp_badi_if->before_update
EXPORTING
it_header = caufv_bt[]
it_header_old = caufv_bt_old[]
it_item = afpo_bt[]
it_item_old = afpo_bt_old[]
it_sequence = affl_bt[]
it_sequence_old = affl_bt_old[]
it_operation = afvg_bt[]
it_operation_old_afvc = afvg_bt_old[]
it_operation_old_afvv = afvv_bt_old[]
it_operation_old_afvu = afvu_bt_old[]
it_component = resb_bt[]
it_component_old = resb_bt_old[]
.
.
.
it_pmpartner_old = ihpa_bt_old[]
it_piinstruction = afft_bt[]
it_piinstructionvalue = affv_bt[].
thank you,
Roxani
‎2007 Aug 08 11:24 AM
Dear experts,
Finally I found a user exit that stops the update before the ON-COMMIT phase and I solved the issue.
Thanks for your help.
Roxani
‎2009 May 13 9:15 AM
i have same problem too. Could you tell which user_exit it is?
Edited by: Aselsan IT Department on May 13, 2009 10:31 AM
‎2007 Oct 10 3:07 PM
Hi All,
How can this be handled. I have a similar requirement and I need to give a Popup in the components tab screen, but when I give a Popup the order component screen goes to a display mode but we need the user to change the values in the screen and hence the screen should be in display mode. Also when it has gone to display mode and i do any action on the screen it is giving a short dump as 'COMMIT Work interrupted' . Please provide a solution for the same.
Regards,
Prabaharan.G
‎2009 May 13 9:43 AM