Triggering WF from ABAP

[R Tannert]

Karsten,
 
We're still on 4.0B but maybe the same condition exists in 4.6C, namely
that you need to make the object reference persistent before you call
SWW_WI_START_SIMPLE.  If so, you can use macro swc_container_to_persistent
(in <CNTN01>) to accomplish this:
 
  swc_create_object object_ref 'BUSxxxx' objkey.
  swc_set_element container 'AccessRequestStep' object_ref.
  swc_container_to_persistent container.
  call function 'SWW_WI_START_SIMPLE' ....
 
OSS note 134527 deals with this topic in reference to generating an event
in an update task, but I've found that this fix applies equally well to
SWW_WI_START_SIMPLE, at least in 4.0B.  I hope this helps.
 
Rob
 
 
>Hi everybody,
>
>I have to trigger a workflow from an ABAP report in 4.6C and that doesn't
>work as I expected.
>
>I want to do this with the function module 'SWW_WI_START_SIMPLE' and I have
>to provide some key-data in a container.
>
>So in the report I do create an object (with a runtime version of type
>swc-object) with the macro swc_create_object and insert the element into
>the container (defined with swc_container) with the macro swc_set-element.
>The key data I insert with the element should be right, as I did my very
>best to use the same format (the name of the element in the container is
>the same as in the report) and data definitions and select  the data just
>in time.
>
>The Probleme is, that if I run the ABAP, I get the following message:
>'Wrong container (element 'ElementName' is not an object)'!
>
>I hope, you have a solution for this,
>because I do not want to use the function module 'SWE_CREATE_EVENT',
>
>Karsten
>
>
>
>
>
>----------------------------------------------------------------------------
>
>Karsten Ernst
>
>Dipl.-Betriebswirt (BA)
>Consultant
>
>Mummert + Partner Unternehmensberatung AG
>Business Intelligence Consulting
>Content Management
>
>eMail: Karsten.Ernst at mummert.de
>
>
>----------------------------------------------------------------------------
>
>
>The information contained in this email may be privileged, confidential and
>protected from disclosure. The opinions expressed are those of the
>individual. Internet communications are not secure and therefore we do not
>accept legal responsibility for the contents of this message. If you think
>you have received this email in error please, notify the sender and delete
>any copies of the mail.