Workflow not working in production system

[Dart, Jocelyn]

Karin,
A lot of event linkage configuration is client/system dependent.   Which can mean the logical system id is tied into the configuration and certainly the runtime.  A system copy would stuff that up nicely - i.e. you probably have stuff still pointing to the test system/client in your production system.
 
Suggest you:
1. Run transaction SWU0 for the event and check your event linkage is ok
2. Check transaction SM58 to see if there is anything sitting there
3. Go to SM59, check your RFC destination WORKFLOW_LOCAL_XXX where XXX is your client - test it here and check that it works
4. Check your IDOC configuration - this also has logical system ids plastered all over the place
 
Regards,
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]
Sent: Tuesday,2 November 2004 7:16 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow not working in production system
 
Hi Partha,
 
Thanks for trying to help me out.  I appreciate it!
 
All my SWU3 settings are green.  My WF-BATCH is assigned SAP_ALL and
SAP_NEW authorizations.
 
I know the event is being raised because someone is getting the workflow
message when it occurs.
 
Do you have any other ideas???  I'm open to suggestions.
 
Thanks
Karin
 
 
 
 
                      "Chatterjee, Partha
                      (US - San Ramon)"
                      <pchatterjee at deloit To:     SAP-WUG at MITVMA.MIT.EDU
                      te.com>             cc:
                      Sent by: SAP        Subject:
                      Workflow                    Re: Workflow not working in production system
                      <Owner-SAP-WUG at MITV
                      MA.MIT.EDU>
 
 
                      10/28/04 04:20 PM
                      Please respond to
                      SAP Workflow Users'
                      Group
 
 
 
 
 
Hi Karin,
 
1) Make sure the appropriate settings in SWU3 are green (especially RFC
destination and WF-BATCH settings).  If the settings in SWU3 are not
green click the Automatic Customizing button.
 
2) Make sure WF-BATCH is assigned SAP_ALL for authorizations.
 
3) Check and make sure your workflow tasks are set to general.  Until
you get this working make sure event log is turned in production (and
then turn it off).  This will at least let you know if events are being
raised.
 
Best regards,
Partha
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Karin A. Caccavale
Sent: Thursday, October 28, 2004 8:18 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Workflow not working in production system
 
Hello everyone,
 
I hope someone out there can help me.
 
We have inbound orders coming into our system via EDI.  They are
translated
to IDOC's and sent to SAP (Version 4.5B).  We have set up workflow for
any
Idoc errors.   I created a new position and assigned a number of holders
(user id's) to that position.  I have also assigned that position to my
partner profile.
 
The only person in our production system that is receiving the workflow
messages is the one person that is also assigned to another position
that
we have for outbound idoc processing.
 
Here's where it gets really strange.  We copied our entire database from
production to our test system.  All security, workflow etc is identical
to
that in our production system.  Believe it or not, workflow actually
works
correctly in our test system!  All of the users assigned to the workflow
position get a workflow message in their inbox.  Yet is still does not
work
in production.  You would think after a system copy that it wouldn't
work
in the test environment, but it does.
 
What am I missing?  Is there some setting that someone knows of that
maybe
is not copied during a system copy that could cause this?  I am truly
stumped and would appreciate any and all advice you can give me.  Why
would
it work in one environment and not the other when the environments are,
as
far as I can tell, identical?
 
Please help!
 
Thanks
Karin
 
 
 
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.
If you are not the intended recipient, you should delete this message.  Any
disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited.