Receiver Function Module impact on SWEL

Mark Pyc mark.pyc at gmail.com
Tue Sep 12 08:00:48 EDT 2006


G'day Karl,

Which finer details ends up in SWEL has always seemed a bit random to me.
Really why do you care about it anyway? It's not like SWEL will be on in
Prod and it's easy enough to determine which WF triggered.

Also just from a style point of view, rec-type functions are a bit poo-poo'd
these days. Start Conditions offer a much more visible, and less techo
(i.e. you
don't necessarily need to read code to understand) alternative. Simply put
your logic in an attribute or multiple attributes if possible, although in
your case I assume doc creator is available and no coding is needed.

Have fun,
Mark


On 9/12/06, Nietz, Karl K <Karl.Nietz at bhpbilliton.com> wrote:
>
>  Hi,
>
> I have implemented a simple receiver function module based on
> SWE_TEMPLATE_RECTYPE_FB for object BUS2081-POSTED.
>
> Depending on the creating userid of the object I initiate one of two
> workflows using the receiver type function module.  The desired workflow is
> initiated successfully.  However, when I view the entry in the event trace
> in transaction SWEL the* Receiver Data* panel does not show the workitem
> id of the generated workflow in the field* Object Key* - it is blank.
> Also, the field Receiver Type does contain the correct workflow name, albeit
> bracketed.
>
> How can the workitem id be retained in the SWEL entry?
>
> *Karl Nietz*
> GSAP Workflow Team Leader
> Melbourne
>   This message and any attached files may contain information that is
> confidential and/or subject of legal privilege intended only for use by the
> intended recipient. If you are not the intended recipient or the person
> responsible for delivering the message to the intended recipient, be advised
> that you have received this message in error and that any dissemination,
> copying or use of this message or attachment is strictly forbidden, as is
> the disclosure of the information therein. If you have received this message
> in error please notify the sender immediately and delete the message.
>
> _______________________________________________
> 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/20060912/c752d693/attachment.htm


More information about the SAP-WUG mailing list