sap_wapi_start_workflow

[Kjetil Kilhavn]

Check the book at page 532 for a short explanation of the macros to handle
containers (and objects).
 
Take a look at the container from the log of one of your successfully
started workflows to see what the element name and value format of your
objects should be - or simply check the container of the workflow template.
--
Kjetil Kilhavn
 
 
 
 
 
                    Sunni sunni
                    <sunnilondon at hotmail        To:     SAP-WUG at MITVMA.MIT.EDU
                    .com>                       cc:     (bcc: Kjetil Kilhavn)
                    Sent by: SAP                Subject:     Re: sap_wapi_start_workflow
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
                    10.02.2003 19:21
                    Please respond to
                    "SAP Workflow Users'
                    Group"
 
 
 
 
 
 
Hi
 
Still not sure exactly how to populate the container manually using
swc_set_element and pass it to the table parameter.  The object type is
zbus2080.
 
I've tried every permutation I can think of, but to no avail, only to hit
short dumps& errors.  Do you have any sample code or example?
 
Many thanks
Sunni
 
 
 
 
>From: "Breslavets, Sergey" <Sergey.Breslavets at anheuser-busch.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: sap_wapi_start_workflow
>Date: Mon, 10 Feb 2003 11:12:17 -0600
>
>Hi Sunni,
>
>use swc_ macros to populate the container (swc_set_element and
>swc_set_table).
>Macro definitions are in <CNTN01>.
>
>Regards,
>Sergey
>
>P.S. your guess is right: when you start your workflow via event, the
event
>object key and additional values are passed to the workflow container via
>the
>event parameters (as you specified in the event binding definition).
>When you start workflow directly using SAP_WAPI_START_WORKFLOW, you need
to
>populate the container manually and pass it as the table parameter in the
>FM
>call.
>
>
>
>-----Original Message-----
>From: Sunni sunni [mailto:sunnilondon at hotmail.com]
>Sent: Monday, February 10, 2003 10:49 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: sap_wapi_start_workflow
>
>
>Hi Workflow experts,
>
>I'm trying to start a workflow explicitly using the WAPI
>SAP_WAPI_START_WORKFLOW.  I was able to start it with an event
>swe_event_create easily enough, but this did not support synchronous
dialog
>chain (advance with dialogue), hence I'm trying out the WAPI.
>I'm confused with what parameters to send it in my program.
>
>'Task' is ok, I pass it the Workflow template number. I don't know how to
>get it to pick up the object type (BUS2080) and object key (from object
>instance).  I think I'm suppose to use the input container, but all this
>contains is two string variables, element and value??? I don't know how
>these value pairs work.  I've done the courses and read the book, no
>details
>to be found on how to make this work.
>
>CALL FUNCTION 'SAP_WAPI_START_WORKFLOW'
>          EXPORTING
>               TASK            = TASK
>*            LANGUAGE        = SY-LANGU
>          IMPORTING
>               RETURN_CODE     = RETURN_CODE
>               WORKITEM_ID     = WORKITEM_ID
>          TABLES
>               INPUT_CONTAINER = INPUT_CONTAINER
>               MESSAGE_LINES   = MESSAGE_LINES
>          EXCEPTIONS
>               OTHERS          = 0.
>
>I would appreciate if anyone has used this before and can give me a little
>guidance.  I'm starting a workflow from a bespoke button on a screen, and
I
>need the first step to show up immediately.
>
>Any ideas?
>
>Kind regards
>Sunni Marcus
>
>
>
>
>
>_________________________________________________________________
>Surf together with new Shared Browsing
>http://join.msn.com/?page=features/browse&pgmarket=en-gb&XAPID=74&DI=1059
 
 
_________________________________________________________________
Express yourself with cool emoticons http://messenger.msn.co.uk
 
 
 
 
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.