Temporary Exception Message Not Showing Up in Workflow Log
Bratzler, Loren
loren.bratzler at nscorp.com
Wed Dec 11 17:13:51 EST 2013
Mark,
Thank you for pointing this out. I changed my message number to 001 and I am now getting my warning messages!
[cid:image005.png at 01CEF691.F62713D0]
And to Rick's point about debugging the method: I did that and I noticed some odd behavior in our Purchase Order workflow (BUS2012). The BAPI that is used to release the PO has a parameter that basically tells the BAPI if any exceptions are going to be raised:
CALL FUNCTION 'BAPI_PO_RELEASE'
EXPORTING
use_exceptions = useexceptions
po_rel_code = relcode
no_commit = nocommit
purchaseorder = object-key-purchaseorder
IMPORTING...
If this parameter is not populated with an "X", the BAPI will not raise any exceptions at all.
I then saw this code at the beginning of the PO Release method:
swc_get_element container 'RelCode' relcode.
swc_get_element container 'UseExceptions' useexceptions.
swc_get_element container 'NoCommit' nocommit.
IF sy-subrc <> 0.
MOVE 'X' TO useexceptions.
ENDIF.
During debugging, I noticed that the first GET_ELEMENT command got a return-code of zero. But the next two both got return-codes of 0008. Looking at the bindings, I could see that we were passing the workflow container elements to the task container, but the workflow container elements were never populated anywhere in the workflow. What is the criteria for when a GET_ELEMENT command will return a SY-SUBRC of 0008? What I found interesting was that if I tested the BOR method stand-alone through SWO1, these GET_ELEMENT commands always got return codes of zero, even though I did not key anything into the importing fields on the test screen. They only got return-codes of 0008 when running in the workflow itself. So is it possible that the SWO1 test screen was populating these fields with spaces which was accepted? And then when running in the workflow they were INITIAL which caused the return-code 0008?
The other thing I notice here is that the check of SY-SUBRC is after the GET of the NoCommit parameter but it is populating the UseExceptions parameter if sy-subr is not zero. That looks to me like an error in the code and this code came from the standard RELEASE method of BUS2012. I think the only reason we have been getting any exceptions at all from this process is because we just happened to not populate the NoCommit parameter which caused SY-SUBRC to be 0008 which then caused us to move the "X" to the UseExceptions variable.
Loren
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mark Pyc
Sent: Tuesday, December 10, 2013 5:38 PM
To: SAP Workflow Users' Group
Subject: Re: Temporary Exception Message Not Showing Up in Workflow Log
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<mailto: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:
[cid:image001.png at 01CEF691.7B7ACFA0]
If you click on the warning, you get a pop-up window that displays the message:
[cid:image002.png at 01CEF691.7B7ACFA0]
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:
[cid:image003.png at 01CEF691.7B7ACFA0]
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:
[cid:image004.png at 01CEF691.7B7ACFA0]
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<tel:540-524-3072>
Email: loren.bratzler at nscorp.com<mailto:loren.bratzler at nscorp.com>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto: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/c0336271/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14002 bytes
Desc: image001.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/c0336271/attachment-0005.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 6141 bytes
Desc: image002.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/c0336271/attachment-0006.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 17911 bytes
Desc: image003.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/c0336271/attachment-0007.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 15260 bytes
Desc: image004.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/c0336271/attachment-0008.png
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 31926 bytes
Desc: image005.png
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20131211/c0336271/attachment-0009.png
More information about the SAP-WUG
mailing list