no update in workplace item status

[Kjetil Kilhavn]

I think you should start by fixing that "only" abnormality and then ask
again if you still have problems.
--
Kjetil Kilhavn
 
 
 
 
|--------+-------------------------------->
|        |          Jeffrey Goldmuntz     |
|        |          <JGoldmuntz at california|
|        |          steel.com>            |
|        |          Sent by: SAP Workflow |
|        |          <Owner-SAP-WUG at MITVMA.|
|        |          MIT.EDU>              |
|        |                                |
|        |                                |
|        |          06.05.2003 03:17      |
|        |          Please respond to "SAP|
|        |          Workflow Users' Group"|
|        |                                |
|--------+-------------------------------->
  >-----------------------------------------------------------------------------------------------------------|
  |                                                                                                           |
  |       To:     SAP-WUG at MITVMA.MIT.EDU                                                                      |
  |       cc:     (bcc: Kjetil Kilhavn)                                                                       |
  |       Subject:     no update in workplace item status                                                     |
  >-----------------------------------------------------------------------------------------------------------|
 
 
 
 
Hello,
I'm encountering a couple of abnormalities while running workflow
WS20000077 (upgrading to 46C).
When the workflow is executed (in this case release of
requisition)completely, the item remains in the workflow inbox without
changing the Title nor the Status (always "In Process"), yet it is
complete because it cannot be processed again.  The log shows no error.
Stranger yet, the task doens't start automatically (no task ID is
generated), I need to run it with Trans SWUS for it to kick in.  I've
checked that the trigger was set and that the event linkage to BUS2105
was active.
So far the only abnormality I found was for the RFC destination
configuration (Using SWUD) it displays "RFC Destination: User Locked"
the user in this case is WF_BATCH.
 
Any input, even partial would be greatly appreciated as I'm still in the
steep part of the learning curve.
 
Many thanks,
Jeffrey
 
 
 
 
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.