Task to WF binding failing for reject execution

[Praveen Johri]

G'Day Robin,
U better create a new version...if that does not go against ur project
specific processes and move it to ur production environment.
 
Kindly, post ur reply to mailing list for the benefit of others
also....this is the way we learn more ........
 
 
Cheers..
 
Praveen Johri
SAP Practice
Extn : 2597
Ph    : 91-0120-2582323
Fax   : 91-0120-2582322
Computer Science Corporation India Ltd.
 
No Worries......
 
 
 
 
-
 
 
----------------------------------------------------------------------------------------
 
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.
----------------------------------------------------------------------------------------
 
 
 
 
 
                      Workflow
                      Developer                To:      Praveen Johri/GTS/CSC at CSC
                      <mysapwug                cc:
                      @yahoo.com>              Subject: Re: Task to WF binding failing for reject execution
 
                      08/24/2004 01:42
                      AM
 
 
 
 
 
 
Hi Praveen,
 
Thanks for your suggestion. Usually when making a significant change like
adding an additional step I create a new version of the template. If I want
existing runtime versions instantiated prior to upgrade to also work, I
will have to change the current version. Is it safe and recommended to add
steps to existing version of productive workflow templates?
 
Thanks again
 
Robin Sahasranam
Praveen Johri <pjohri at csc.com> wrote:
 G'Day Robin,
 
 I also had a similar experience during our upgrade from 4.6C to 4.7 SR1,
 we
 have a Custom Procurement worklow which undergone similar problem of an
 attribute not getting populated at runtime and that workflow was running
 fine for long in 4.6C. I spent lot of time in digging around and could not
 see any possible cause why this is happening, up to the visibility
 provided
 by diagnostic tools, everything seemed to be correct but some how value
 was
 not getting transferred....i tried several ways like mapping the datatype
 of attribute according to 4.7 datatypes thinking it might be a
 problem....but to be true i never found the cause...i did a workaround..i
 created a container step and populated that particular attribute like in
 ur
 case LAST_AGENT = WI_ACTUAL_AGANT. just before the task which needed it to
 run. and everything started running smoothly.
 
 Maybe, if u donot find the root cause of the problem u might like to use
 this workaround and if you do find the solution then do share it with me.
 
 
 Cheers...
 
 Praveen Johri
 SAP Practice
 Extn : 2597
 Ph : 91-0120-2582323
 Fax : 91-0120-2582322
 Computer Science Corporation India Ltd.
 No Worries.......
 
 
 
 
 -
 
 
 ----------------------------------------------------------------------------------------
 
 
 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.
 ----------------------------------------------------------------------------------------
 
 
 
 
 
 
 Workflow
 Developer To: SAP-WUG at MITVMA.MIT.EDU
 @yahoo.com> Subject: Task to WF binding failing for reject execution
 Sent by: SAP
 Workflow
 
 
 08/20/2004 08:52
 PM
 Please respond
 to "SAP Workflow
 Users' Group"
 
 
 
 
 
 
 Greetings,
 We have upgraded our development system from 4.6c to 6.20 sp41. One of
 our custom workflows goes into error status because a container element
 is not set after reject execution of the dialog step (standard task)
 TS...). The error is WL410 'Workitem could not be created'. We also get
 the error 'Mandatory import element LASTAGENT has no value', which
 causes the WL410 error.
 
 The task has a binding from _WI_ACTUAL_AGENT of the task container to a
 LASTAGENT element of the workflow container. The LASTAGENT element is
 then used as actual agent for the next step, which is a subworkflow
 that handles reject processing.
 
 In examining the containers from the Workflow technical log, I can see
 that the element _WI_ACTUAL_AGENT of the task has the correct value.
 However the LASTAGENT element of the workflow container has initial
 value, indicating that the runtime binding after task completion did
 not take place.
 
 This workflow has been productive in 4.6c for about two years, without
 problems. Also checking the workflow and task shows no binding errors
 or warnings.
 
 Thanks in advance for any assistance you can offer.
 
 Robin Sahasranam
 Workflow Administrator/Developer
 World Bank
 
 
 
 ---------------------------------
 Do you Yahoo!?
 New and Improved Yahoo! Mail - Send 10MB messages!
 
 
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com