Container operation: remove?

[Hill, Anna]

Hi Kietil

FYI - If you want to experiment with programmed bindings, here's an example of a very simple function module you can use. Once you have created your programmed binding FM, you then enter it on to the binding on the step; in the binding editor, click on the black arrow assignment button and you then have the option to swtich to programmed binding. Enter the FM in there. Note that the FM holds a dataflow variable which defines the direction of the binding execution at run time. Note that E is for export from the workflow to the task, the workflow container is the calling container and the task container is the called container. 

Cheers
Anna
SAP UK

function z00_bind_wf_to_display_step.
*"----------------------------------------------------------------------
*"*"Local interface:
*"       IMPORTING
*"             VALUE(DATAFLOW) LIKE  SWABINDEF-DATAFLOW
*"       TABLES
*"              CALLED_CONTAINER STRUCTURE  SWCONT
*"              CALLING_CONTAINER STRUCTURE  SWCONT
*"----------------------------------------------------------------------
  data: mat_object type swc_object.
  data: mat_view   like t132t-statm.

  if dataflow eq 'E'.
    " only consider export dataflow from wf to wi container
    " read data from workflow (= calling) container
    swc_get_element calling_container 'MaterialMaster'   mat_object.
    swc_get_element calling_container 'MaterialView'     mat_view.

    .... Do your coding in here

    " write data to work item (= called) container
    swc_set_element called_container   wi_leading_object mat_object.
    swc_set_element called_container   'MaterialView'    mat_view.
  endif.
endfunction.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Kjetil Kilhavn
Sent: Wednesday, October 26, 2005 8:05 AM
To: SAP Workflow Users' Group
Subject: RE: Container operation: remove?

There should only be one... - but that is a good question. 

I think, with the particular design we have here, we should actually remove only one (the first one) as the table is really a queue of who approval is (still) required from. Multiple approvers can be required, and then the approvals take place in parallell - i.e. it is not multiple _levels_. When responsibility changes I don't want to terminate and start new workflows for those who are still responsible, and the design we have come up with (which may be stupid or may be smart) uses a queue to determine when the document approval has been completed. 

I've attached the design to confuse you further :-)
The "Evaluate document" workflow is started by "external" events when a document is created/changed significantly, while the ApprovedFor, Rejected, and Refused events are published by the approval report that documents are presented in.


PS: I've seen programmed binding mentioned many times, but after trying to find it in our screens with absolutely no luck I have come to the conclusion that this is available only to those exploring the frontiers, i.e. anything newer than 4.6C :-)
-- 
Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis - and I appreciate it if you delete Statoil's (and other) company disclaimers when you reply to this message, since that helps the readability.


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Pokraka
Sent: 20. oktober 2005 16:57
To: SAP Workflow Users' Group
Subject: Re: Container operation: remove?

Hi Kjetil,

Would you want to remove the exact value or all matching values, treating it as a kind of key? If you have the value multiple times should it remove just one or all of them?

Not really such a simple operation.

I saw bits of the next version on the way (6.40s) which should do indexed multiline containers, which is nice. I think there were some more extensive container operation capabilities available to go with it. But it's not for us mortals to play with for a while.

I've had to resort to custom methods and the odd programmed binding to work around stuff like that (6.20).

Cheers
Mike

Kjetil Kilhavn wrote:
> I am working on a solution (R/3 46C) where it would be VERY nice to be 
> able to have two types of container operations.
> "Add this value to table" is possible with a standard container 
> operation.
> "Remove this value from table" is not quite as easy. There is a "-"
> operator, but I assume the workflow builder is not quite that object 
> oriented (yet)...
>
> As far as I know the only option I have with respect to removal is to 
> write a method on a business object.
>
> Is this any different in new versions?
> Has anyone created a super-duper object type which can perform generic 
> operations like this?
> --
> Kjetil Kilhavn, Statoil KTJ IT BKS


Mike Pokraka
Senior Consultant
Workflow Connections Ltd.
Mobile: +44 (0)7786 910 855


-------------------------------------------------------------------
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.