Binding from method to task

[Keohan, Susan - 1140 - MITLL]

Hi Jocelyn,

Many thanks for confirming that method-task binding is not necessarily
required.  This was a new task, and yes, changes to the method underneath it
were made.  I did go into the task, and got the message about importing the
container elements from the method, which I accepted.  I did execute
SWU_OBUF several times as well (my tradition is to execute it three times
with my eyes closed and fingers crossed).

 

It took some backing out and container debugging before light dawned and I
tried the binding from the method to the task.  

This morning, I came back and deleted the binding from the method to the
task, and it all works fine.

 

I did have many sessions open, so I am going to chalk this up to EBKAC.  

 

Thanks again!
Sue

----

Susan R. Keohan

SAP Workflow Specialist

Enterprise Applications

Information Services Department

MIT Lincoln Laboratory

244 Wood Street, LI-200

Lexington, MA. 02420

781-981-3561

keohan at LL.MIT.EDU

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Dart, Jocelyn
Sent: Thursday, January 31, 2013 12:43 AM
To: SAP Workflow Users' Group
Subject: RE: Binding from method to task

 

Hi Sue, 

It's rare to have to do the binding in the method but not entirely unheard
of. 

But it shouldn't be happening just because you have upgraded. 

Was it an existing task or a new task? 

Usually if you change something at the method level and then go to the task
it should reimport the changes from the method. 

Perhaps that didn't happen?  Sometimes when you are working with multiple
sessions open I've seen this.  

Usually I just get out of the object editor and go to the task, and then you
should get the update message. 

Either that or there's a buglet in the new BOR editor if you are using that?


Cheers

Jocelyn 

 

 

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Keohan, Susan - 1140 - MITLL
Sent: Thursday, 31 January 2013 1:43 AM
To: SAP Workflow Users' Group
Subject: Binding from method to task

 

Hi all,

We are on ECC 6, and have recently applied EHP4 FOR SAP ERP 6.0 / NW7.01.

 

In the past, my practice has been to NOT bind elements from methods to
tasks.  I have a number of workflows running along for years now, simply
based on using SWC_SET_ELEMENT container 'elementname' l_value

 

This week, I was perplexed by the inability of SWC_SET_ELEMENT to work as I
had expected, and was actually required to perform the method-to-task
binding I have avoided for so long.  

 

Does anyone know if this is EHP4 related, or if there is a set of rules for
when you should perform this additional binding?
Or perhaps my 'best practice' (of not doing the binding) should be revised?

 

Cheers,
Sue

----

Susan R. Keohan

SAP Workflow Specialist

Enterprise Applications

Information Services Department

MIT Lincoln Laboratory

244 Wood Street, LI-200

Lexington, MA. 02420

781-981-3561

keohan at LL.MIT.EDU

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130131/08d5d271/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5465 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20130131/08d5d271/attachment-0001.bin