SAP_WAPI_START_WORKFLOW vs. SWW_WI_START

[Mike Pokraka]

Nope, it should definitely work. Test the SAP_WAPI in SE37 (with a simple
test wf if necessary) and work back from there.



On Wed, April 16, 2008 6:00 pm, Sample, Rick wrote:
> That's what I thought. So, bottom line, can't user the WAPI_SAP_* to
> pass in TABLES?
>
> Back to using SWW_WI_START I suppose...
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Wednesday, April 16, 2008 10:23 AM
> To: SAP Workflow Users' Group
> Subject: RE: SAP_WAPI_START_WORKFLOW vs. SWW_WI_START
>
> Nope, the WAPI containers are simple containers. A different animal
> altogether, simple containers are just a name-value pair.
>
> data: lt_cont type standard table of swr_cont,
>       lv_cont type swr_cont.
>
> lv_cont-element = 'SINGEELEMENT'.
> lv_cont-value = 'somevalue'.
> append lv_cont to lt_cont.
>
> lv_cont-element = 'MULTIELEMENT'.
> lv_cont-value = 'value1'.
> append lv_cont to lt_cont.
>
> lv_cont-value = 'value2'.
> append lv_cont to lt_cont.
>
> On Wed, April 16, 2008 3:07 pm, Sample, Rick wrote:
>> Mike, I tried several different approaches to what I 'think' you are
>> saying, but WF still does not start.
>> Below is a Y test snip. Can you point out what you mean?
>>
>> FUNCTION y_test_start_dla_msg.
>>   INCLUDE: <cntn01>.
>>
>>   DATA:
>>    container        TYPE swcont OCCURS 0 WITH HEADER LINE,
>>    return_code     TYPE sy-subrc,
>>    workitem_id     TYPE swr_struct-workitemid,
>>    bapi_return      TYPE bapiret2 OCCURS 0 WITH HEADER LINE.
>> *+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>>   bapi_return-type    = 'W'.
>>   bapi_return-message = '1'.
>>   APPEND bapi_return.
>>
>>   bapi_return-type    = 'S'.
>>   bapi_return-message = '2'.
>>   APPEND bapi_return.
>>
>>   swc_set_table container 'BAPI_Return' bapi_return.
>>
>>   CALL FUNCTION 'SAP_WAPI_START_WORKFLOW'
>>        EXPORTING
>>             task            = 'TS90000212'
>>        IMPORTING
>>             return_code     = return_code
>>             workitem_id     = workitem_id
>>        TABLES
>>             input_container = container.
>>
>> ENDFUNCTION.
>>
>> -----Original Message-----
>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf
>> Of Mike Pokraka
>> Sent: Wednesday, April 16, 2008 2:40 AM
>> To: SAP Workflow Users' Group
>> Subject: Re: SAP_WAPI_START_WORKFLOW vs. SWW_WI_START
>>
>> Hi Rick,
>> Just repeat the same container element name with different values for
>> the
>> SAP_WAPI container.
>> Cheers,
>> Mike
>>
>> On Tue, April 15, 2008 10:47 pm, Sample, Rick wrote:
>>> I forgot that the interface changed for SAP_WAPI_START_WORKFLOW. We
>> can
>>> no longer pass in 'tables' to this FM?
>>>
>>> What I need is, to start a WF and pass in TABLES.
>>>
>>> What are the risks of using SWW_WI_START? Or, how do I pass in tables
>> to
>>> the
>>> new WAPIs?
>>>
>>> Rick Sample
>>> SAP Business Workflow Developer
>>> Graybar, Inc.
>>>
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>