Temporary Exception Message Not Showing Up in Workflow Log

[Mark Pyc]

G'day Loren,

An oldie, but a goldie!!

SAP has some wonderful code that says if the message number is initial,
don't include it in the log. Oh but wait, message 000 is a valid message
number.... Too bad. Pick a different number.

If you change to message ZWF_MSG 001 it'll work a treat.

Have fun,
Mark



On 11 December 2013 05:41, Bratzler, Loren <loren.bratzler at nscorp.com>wrote:

> I feel like I’m asking an awful lot of questions here lately!  But here is
> another issue I am facing.  I spoke with Sue about this at TechEd and I
> have scoured SCN and the internet trying to find an answer but no luck so
> far.
>
>
>
> I have added a temporary exception to a BOR method when a user has the
> object locked.  On other workflows where we have a temporary exception, the
> workflow log shows a yellow warning indicator on the execution of the step
> that you can click on and get the temporary exception message:
>
>
>
>
>
>
>
> If you click on the warning, you get a pop-up window that displays the
> message:
>
>
>
>
>
>
>
> However, on the workflow where I just added the temporary exception, I do
> not get the warning message.  You can see in this example below, that the
> background task was executed twice by the retry program (RSWWERRE) before
> it finally completed but I did not get the warning messages:
>
>
>
>
>
>
>
> I have compared the two BOR methods (the one that works and the one that
> doesn’t work) and I believe I am doing everything correct.  They both have
> the exception defined as temporary:
>
>
>
>
>
>
>
> And the logic in the method is doing an EXIT_RETURN raising the temporary
> exception number:
>
>
>
> * If there is only one error message and it is a user lock
> * error (CJ-806), raise temporary exception 9001.
>       IF lv_lines = 1.
>         READ TABLE lt_result INDEX 1
>               INTO ls_result.
>         IF ls_result-message_id     = 'CJ' AND
>            ls_result-message_number = '806'.
>           lv_msg1 = ls_result-message_text.
>           exit_return 9001 lv_msg1 space space space.
>         ENDIF.
>       ENDIF.
>
>
>
>
>
> Even though these changes were made strictly to the BOR Object, I also
> generated a new version of the workflow to see if that would make the
> messages start appearing in the log, but that did not work either.
>
>
>
> Anyone have any ideas on what I might be missing here?
>
>
>
> Loren Bratzler
>
> Norfolk Southern Corporation
>
> 110 Franklin Road SE
>
> Roanoke, VA  24042-0060
>
>
>
> Phone: 540-524-3072
>
> Email: loren.bratzler at nscorp.com
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/5fa4e2d0/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 17911 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/5fa4e2d0/attachment-0004.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 14002 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/5fa4e2d0/attachment-0005.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 6141 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/5fa4e2d0/attachment-0006.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 15260 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/5fa4e2d0/attachment-0007.png