Workflow changes in EHP6

Wed Oct 10 11:03:38 EDT 2012

Hi,

This option was already set for some bindings and not set for others.
I set the option for all bindings with error and it is solved (for one step and crashed in the next step), but I have to do this operation for a lot of steps...
But why do I have the error in the first place? I debugged the method CL_SWF_BND_BINDING->GET_BINDING and I saw that a type error is found between the source element and the target element, but the two elements are both defined as type BO BUS2081 and working perfectly before the upgrade...

________________________________
 From: "Morris, Eddie" <eddie.morris at sap.com>
To: SAP Workflow Users' Group <sap-wug at mit.edu> 
Sent: Wednesday, October 10, 2012 4:37 PM
Subject: RE: Workflow changes in EHP6

Hi George,

In the binding instruction section (Black arrow between container elements in binding line) can you set the option “Handle Errors as warning”.

Does this allow the execution?

Regards,
Eddie

From:sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of George Caramaliu
Sent: Tuesday, October 09, 2012 12:27 PM
To: SAP Workflow Users' Group
Subject: Re: Workflow changes in EHP6

Hi Eddie, thanks' for your help.
I checked the tables and only fields EXETYP (S and E) and CONT_INDEX (in one case different, in one case identical) are different.

George

________________________________

From:"Morris, Eddie" <eddie.morris at sap.com>
To: SAP Workflow Users' Group <sap-wug at mit.edu> 
Sent: Tuesday, October 9, 2012 12:50 PM
Subject: RE: Workflow changes in EHP6

Hi George,

Can you check tables SWDSBINDEF (UI) and SWD_BINDEF (runtime) and compare the entries for your binding…are they different?

If so then please create a message for SAP support and include it for my attention (Eddie Morris).

Regards,
Eddie

From:sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of George Caramaliu
Sent: Tuesday, October 09, 2012 7:55 AM
To: SAP Workflow Users' Group
Subject: Re: Workflow changes in EHP6

Hi,
I checked and all container elements have valid data elements, in fact some container elements have values, so there is nothing wrong with the data definition. Pfiu... crappy error message... 

________________________________

From:Mike Gambier <madgambler at hotmail.com>
To: SAP Workflow Users' Group <sap-wug at mit.edu> 
Cc: SAP Workflow Users' Group <sap-wug at mit.edu> 
Sent: Monday, October 8, 2012 2:46 PM
Subject: Re: Workflow changes in EHP6

George,

We noticed that SAP withdrew (i.e. deleted) a few of their own structures without warning and that tripped us up at the time. 

My advice would be to revisit your binding and adjust the definitions. You may find you have to find or create alternative data types to support the changes. 

Any runtime instances that have been affected that you want to keep rather than kill you'll have to perform surgery on in tables like SWDSWFCONT and repoint the bindings to valid types supported by the data dictionary post-upgrade. 

Mike GT

Sent from my iPhone

On 8 Oct 2012, at 12:35, "George Caramaliu" <george_caramaliu at yahoo.com> wrote:
Hi,
>
>We already have this note applied. Anyway, we have the same error also for simple container elements (structures), not only for BOR objects.
>If I use the check bindings function in the workflow builder I do not have any error. This is strange. 
> 
>George
>
>________________________________
>
>From:"Morris, Eddie" <eddie.morris at sap.com>
>To: SAP Workflow Users' Group <sap-wug at mit.edu> 
>Sent: Monday, October 8, 2012 1:54 PM
>Subject: RE: Workflow changes in EHP6
> 
>Hi George,
> 
>In relation to binding issue please apply note 1696315 if not already in the system. It is a BOR related note.
> 
>Regards,
>Eddie
> 
>From:sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of George Caramaliu
>Sent: Monday, October 08, 2012 9:01 AM
>To: sap-wug at mit.edu
>Subject: Workflow changes in EHP6
> 
>Hello,
> 
>We are currently testing the upgrade to EHP6 and we have some problems with our already developed workflows.
>it seems that there are significant changes in workflow runtime classes, a lot of our enhancements are failing because standard attributes were deleted and we have to change the code. Now we found other problems in WF execution and errors during binding ("Source expression & invalid" when passing an empty object).
> 
>Can anyone provide a document/link with the changes done by EHP6 in workflow area? I was not able to find it.  
> 
>Thank you,
>George Caramaliu
>
>_______________________________________________
>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

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20121010/60886266/attachment-0001.htm