How an emptyWF to Task container element can supply value to method??

[Praveen Johri]

David,
 
You have enlightened me and as well as increased my worries.
 
Thanks & Regards
 
Praveen Johri
SAP Practice
Extn : 2597
Ph    : 91-0120-2582323
Fax   : 91-0120-2582322
Computer Science Corporation India Ltd.
 
 
 
 
----------------------------------------------------------------------------------------
 
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
 
 
 
                      "Trant, David"
                      <David.Trant             To:      SAP-WUG at MITVMA.MIT.EDU
                      @andrew.com>             cc:
                      Sent by: SAP             Subject: Re: How an emptyWF to Task container element can supply value to method??
                      Workflow
                      <Owner-SAP-WUG
 
 
                      05/20/2004 08:21
                      PM
                      Please respond
                      to "SAP Workflow
                      Users' Group"
 
 
 
 
 
 
You're having a nightmare, and it's very similar to one of mine!  I'd
noticed the same type of behavior for quite some time between the task and
method containers, and had a most interesting series of conversations on it
at the ASUG spring conference last month.  Although on paper, it seems that
one would generally pass data from the event container to the workflow
container to the task container to the method container to the function
module (if that's the method's particular method of execution), it seems
that in reality, SAP doesn't need, or even want, the task to method
container binding.  As long as the parameters of the method match the
container elements being passed from the workflow container to the task
container, SAP simply "dumps" that container in one operation.  I am told
that there is a performance hit (makes sense) for manipulating the extra
binding, so SAP prefers not to do it.  Of course, being a relatively anal,
logical person, I find it difficult to envision data being passed when the
binding is missing, but that is what happens.  One SAP guru recommended
never having a binding at this point; another couple of experts didn't seem
to completely agree with that.  One person told me this binding was
actually going away altogether in future releases, though I'm not sure
which one (I'm on 4.6C).  I used to insist upon a correct binding during my
review process for new workflows, and now am faced with reversing course on
that one.
 
David
 
 -----Original Message-----
From:   SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]
Sent:   Thursday, May 20, 2004 9:02 AM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        How an emptyWF to Task container element can supply value
to method??
 
Hi all,
 
i m facing a weird scenario........the container element in Wf to Task
binding has no value set...( as seen in Tech. Log while the task is waiting
to be executed)..........but while executing the task in debug mode at
SWC_GET statement i saw a value against same element.......just couldn't
understand from where it came..........moreover after completion of
task...........again when i checked the container the element is not
set..........but the value was there in method........
 
any ideas.......or i m having a dream...........
 
Thanks & Regards
 
Praveen Johri
SAP Practice
Extn : 2597
Ph    : 91-0120-2582323
Fax   : 91-0120-2582322
Computer Science Corporation India Ltd.
 
 
 
 
----------------------------------------------------------------------------------------
 
 
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
 
 
------------------------------------------------------------------------------------------------
 
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
 
[mf2]