SWEL event parameter value

Tue Oct 6 10:07:41 EDT 2015

Hi Florin,
Thanks for the hint with the message id, I may use that.This is a point that could be improved next year, I will add the improvement request when the project is started again.
Have a nice evening,George
      From: Florin Wach <florin.wach at systems-integration.net>
 To: SAP Workflow Users' Group <sap-wug at mit.edu> 
 Sent: Tuesday, October 6, 2015 4:48 PM
 Subject: Re: SWEL event parameter value

Hi George,

I see :-)

Well... sometimes I'm missing the authorization to switch on/off the event trace, while I can still take a look into it. And then I need to check, what events are being filtered. And w/o auth. to SWELS you just can't see that.

I'm missing that feature with the parameter-logging, too, and it's just not implemented into the runtime system and there's no chance to check that afterwards.

What I sometimes do is to use different Message-ID's and Message-parameters to indicate, what the values of the event-parameter(s) were, like "  OBJECTS was empty "... or   "OBJECTS   VBRK  not found"...

The message will then be visible in the log, as you know.

Maybe this workaround is helpful.

Next year you may remember to raise an improvement request at the SAP Customer's influence program for workflow, that the container is logged on exceptions ... when the event-log is turned on.

Mit freundlichen Gruessen / With kind regards
 Florin Wach
 Senior Workflow Engineer
 SAP Certified Development Associate for Workflow

--------------------------------------------------
http://www.systems-integration.net

george_caramaliu at yahoo.com hat am 6. Oktober 2015 um 14:45 geschrieben:

Hi Florian,
Table SWELCF contains the restrictions for event trace set in SWELS.Those values can be seen directly in SWELS.
I need to see the event parameters in SWEL, for example event VBRK.ASSIGNED is triggered, I want to see in SWEL the value received for event parameter DocumentType of VBRK.ASSIGNED.
BR,George 
 From: Florin Wach <florin.wach at systems-integration.net>
 To: SAP Workflow Users' Group <sap-wug at mit.edu> 
 Sent: Tuesday, October 6, 2015 3:07 PM
 Subject: Re: SWEL event parameter value

Dear George,

its stored in table SWELCF
SE16 w/o restriction and F8.

I found this through debugging of the SAVE-button of the detailed screen of transaction SWELS.

Mit freundlichen Gruessen / With kind regards
 Florin Wach
 Senior Workflow Engineer
 SAP Certified Development Associate for Workflow

--------------------------------------------------
http://www.systems-integration.net

george_caramaliu at yahoo.com hat am 5. Oktober 2015 um 18:24 geschrieben:

Hello,
Is there any way to check what are the event parameter values in SWEL? I see the event in the log, but I cannot check the event parameter.The thing is that I have a check function module that from time to time is triggering an exception and the WF is not started, and it should be started.I find it very odd that with Event trace activated in production I cannot check if the event is triggered correctly or not.
Errors started after transporting some changes to the check function module. By analyzing the code the FM should not raise exception, but it does randomly and I don't know why. If I raise again the event manually the workflow is started, so the problem is either in parameter transmission or something does not exist at the time of event creation. 
The event is VBRK.ASSIGNED triggered by the system when an archived document is linked to BO VBRK.
Any clues?
Thanks'George

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
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/20151006/1509a273/attachment-0001.html