Binding user-exit with BOR-Container + SIBFLPORB

[Dart, Jocelyn]

Hi Florin and Thomas, 

You might want to look at <cntn02> and <cntn03> as well - these had additional macros for ABAP OO usage.  

Regards,
Jocelyn 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Florin Wach
Sent: Thursday, 2 February 2012 7:02 PM
To: SAP Workflow Users' Group
Subject: Re: Binding user-exit with BOR-Container + SIBFLPORB

Hello Thomas,

in the BOR-compatible function interface, there is no such object reference to the workflow container available, instead the <CNTN01> is beeing included (when looking at the SAP template).

I have found out that these tunneled parameters are being read by the ABAP class only, so one needs to instantiate a new class container from the BOR container (there's a factory method to do so), and then continue with getting the element from there (coming down to the wf_container.get() method after a while).

So it's a bit of a hack to work around here, and it would had been nice if the BOR macro could have handled with the tunnelled objects.

Best wishes,
   Florin

-------- Original-Nachricht --------
> Datum: Fri, 27 Jan 2012 10:54:41 -0800 (PST)
> Von: BPT Consulting <bptconsulting at sbcglobal.net>
> An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> Betreff: Re: Binding user-exit with BOR-Container + SIBFLPORB

> Florin,
> 
> You can look at include <SWFCNTN01> which has the macros for accessing the
> ABAP-OO-container.  Refer to FM SWA_BINDING_TEMPLATE for the container
> interface type necessary.  Your code would look something like:
> 
>  TRY.
> 
>       call method WF_CONTAINER->get
>         EXPORTING
>           name  = 'Releasable'
>         IMPORTING
>           value = RELCODE.
> 
>     CATCH cx_root. " 
>   ENDTRY.
> 
> Regards,
> Thomas Maue
> 
> --- On Thu, 1/26/12, Florin Wach <florin.wach at gmx.net> wrote:
> 
> > From: Florin Wach <florin.wach at gmx.net>
> > Subject: Binding user-exit with BOR-Container + SIBFLPORB
> > To: sap-wug at mit.edu
> > Date: Thursday, January 26, 2012, 6:49 AM
> > Dear wuggies,
> > 
> > I'm using a BOR programmed binding function module to create
> > a custom binding for the workflow start.
> > 
> > There's the called container (destination) and the calling
> > container (source) available and the usual elements are
> > there.
> > 
> > Once the ABAP-OO element is used, the reference to the
> > structure SIBFLPOR(B) becomes converted into some kind of
> > portablity interface. The structure is ripped as following:
> > 
> > ELEMENT / ... type / VALUE
> > _WF_IBF_PORTAB |000001   |004   
> >    |u   |SWFTSTRUCT 
> >    <
> > _WF_IBF_PORTAB |000002   |032   
> >    |C   |RELEASABLE 
> >    <
> > _WF_IBF_PORTAB |000004   |032   
> >    |C   |1CC21000C 
> >     <
> > _WF_IBF_PORTAB |000005   |104   
> >    |C   |006324037000032<
> > 
> > When I use the container macro (as suggested from the
> > example function module), I cannot simply access the element
> > "Releasable", as this is striped into these four elements.
> > 
> > Question:
> > Is there another macro / function method which I could use
> > to access the new kind of element?
> > 
> > No, I don't want to use the other exit-binding for XML
> > container. I have other restrictions that make me use the
> > BOR container here.
> > 
> > 
> > 
> > With the very best,
> >    Florin
> > _______________________________________________
> > 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