RFC error in SWEQADM - Event Delivery

Tue Jul 15 12:32:00 EDT 2008

Thanks Mike for your reply.

WF-BATCH here is NOT a dialog user and the password is kept under lock
and key.  As I understand it, the password does not expire.

We looked in ST22 and SM21 but did not see anything that tells us what
happened.  The only clue is in the Event trace with the error message
below.  Does anyone know what the message means?  Could it have happened
because the RFC Gateway was full?

Another question.....Basis wants to know if there is a way to monitor
SWEQSRV and for it to trigger something if the job hangs up.  Does
anyone know how I can go about doing that?

Regards,

Sue T. Doughty

SAP Workflow Specialist

Old Dominion Freight Line, Inc.

500 Old Dominion Way

Thomasville, NC 27360

Phone:  (336) 822-5189

Toll Free (800 ) 432-6335, ext. 5189

Email:  sue.doughty at odfl.com

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Gambier
Sent: Tuesday, July 15, 2008 9:50 AM
To: SAP Workflow Users' Group
Subject: RE: RFC error in SWEQADM - Event Delivery

Sue,

We're still on 4.6c still but something similar-looking happened here a
while back.

I can't remember exactly what it was eventually put down to, but there
were three things that came out of it:

1. The password for user WF-BATCH was kept under lock and key and was
renewed regularly in a timely manner whenever the Workflow services were
turned off. Once the password expired in the middle of the online day,
ouch.

2. SWU3 was restricted to superusers only (because somebody had fluffed
a password reset without thinking)

3. No-one was allowed to submit Batch jobs as or attempt to log on as
WF-BATCH without approval. Somebody made the user account a dialog one
for debugging a rather nasty problem for a while and forgot to set it
back. (No, it wasn't me).

In SM37 the job may appear to be running but a dump probably stopped it
in its tracks. The screen can lie to you because its gauging runtime as
elapsed time, not actually processing time. ST22 or SM21 might give you
a clue as to when the program actually died.

We've had lock overflows kill a few programs before in a nasty manner, I
assume that wasn't a problem for you though? The new ECC 6 Workflow
service programs enqueue themselves to prevent multiple instances from
running...but if this enqueue fails the job should error not dump.

As a quick guide in ECC 6 I'm going to start to rely on the new table
SWWREPSTATUS to check when the system last registered a Workflow Service
job finishing successfully, rather than trawl through SM37.

Regards,

MGT

________________________________

Subject: RFC error in SWEQADM - Event Delivery
Date: Tue, 15 Jul 2008 09:16:59 -0400
From: Sue.Doughty at odfl.com
To: sap-wug at mit.edu

We're on ECC 6.0.

We had a problem in SWEQSRV last night.  In the event trace for the
event, it stated that the receiver was started correctly, but the RFC
Status had the following message:

Connection manual canceled by user WF-BATCH    , c

The workflow did not start.  It went to the Linkages with errors section
of SWEQADM.  The job SWEQSRV just ran and ran all night long, but did
nothing. The events just backed up.  I could not re-deliver the event -
I got a message that WF-BATCH had the event locked.  We killed the
SWEQSRV job and I was then able to re-deliver the event.

Basis wants to know what the problem was.....at the same time that this
problem happened the RFC Gateway started filling up and nothing was
processing.  I don't know id the SWEQSRV started the problem or if the
gateway problem caused the SWEQSRV problem.

Has anyone ever seen this message before?  If so, what was the issue?

Regards,

Sue T. Doughty

SAP Workflow Specialist

Old Dominion Freight Line, Inc.

500 Old Dominion Way

Thomasville, NC 27360

Phone:  (336) 822-5189

Toll Free (800 ) 432-6335, ext. 5189

Email:  sue.doughty at odfl.com

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Shai Eyal
Sent: Tuesday, July 15, 2008 3:06 AM
To: sap-wug at mit.edu
Subject: RE: Users to disable notifications

Dear Ananth,

There are plenty of ways to signal that user wants to receive e-mail and
I would specify it via SCOT because then it'll affect all mail sending
and not just claims.
Straightforward options:

1.	Use any non-used field in the material master.
2.	Create dummy role and assign to users who wishes to receive
emails.
3.	Define in SO36 users who wishes to receive emails.
4.	In case you have BP for this users, you can define it within the
BP.
5.	Define within user settings in SBWP.

Anyhow, I suggest not to limit via SCOT.

Good luck,

Regards,
Shai Eyal
SAP Logistics senior consultant
SAP Workflow specialist
Mobile: 972-52-5816633

----- Original Message ----
From: "sap-wug-request at mit.edu" <sap-wug-request at mit.edu>
To: sap-wug at mit.edu
Sent: Tuesday, July 15, 2008 8:39:46
Subject: SAP-WUG Digest, Vol 44, Issue 33

Send SAP-WUG mailing list submissions to
    sap-wug at mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
    http://mailman.mit.edu/mailman/listinfo/sap-wug
or, via email, send a message with subject or body 'help' to
    sap-wug-request at mit.edu

You can reach the person managing the list at
    sap-wug-owner at mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of SAP-WUG digest..."

Today's Topics:

  1. Users to disable notifications (Ananth)
  2. RE: Inbox substitution interrogation (Dart, Jocelyn)
  3. Re: SAP-WUG Digest, Vol 44, Issue 31 (Deepali Margaj)

----------------------------------------------------------------------

Message: 1
Date: Tue, 15 Jul 2008 08:51:42 +0530
From: Ananth <write2ananth at gmail.com>
Subject: Users to disable notifications
To: "SAP Workflow Users' Group" <SAP-WUG at mit.edu>
Message-ID:
    <7e1903b20807142021q232c2f54m4923aae6caa553a8 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Dear All,

We are on SAP CRM 6.0 system and trying to implement workflows. We
need to notify the business partners that their Claims are rejected or
approved by the Business users.

There is a unique requirement, where we need to send mails to the
business partners who are external users. But they would like to get
notified with the claim status only when they want to to receive,
otherwise they dont want to receive any notifications.

Presently mails are sent to their SAP Inbox and from there it is
auto-forwarded to the external email id. My suggestion was that, users
who want to get notified can be maintained in the SCOT transaction and
only they can receive the mails in their external email id. Ofcourse,
if this is to be done, then it has to be maintained by a BASIS person.

I would like to know, if there is a setting where we can setup/users
can maintain themselves in which we can check and according send or
not send the mails to the external user. Email address will always be
maintained for the business users in SU01.

Can someone please let me know, if we can enable or disable
notifications accordingly based on some checks/flag.

Thanks in advance,
Ananth

Send instant messages to your online friends
http://uk.messenger.yahoo.com 

**************************** 
CONFIDENTIALITY NOTICE: The information contained in this message may be
confidential, privileged, proprietary, or otherwise legally exempt from
disclosure. If the reader of this message is not the intended recipient,
or an employee or agent responsible for delivering this message to the
intended recipient, you are hereby notified that you are not authorized
to read, print, retain, copy or disseminate this message, any part of
it, or any attachments. If you have received this message in error,
please delete this message and any attachments from your system without
reading the content and notify the sender immediately of the inadvertent
transmission. Thank you for your cooperation. 

________________________________

Get Messenger on your Mobile! Get it now!
<http://clk.atdmt.com/UKM/go/101719964/direct/01/> 

****************************
CONFIDENTIALITY NOTICE: The information contained in this message may be confidential, privileged, proprietary, or otherwise legally exempt from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this message, any part of it, or any attachments. If you have received this message in error, please delete this message and any attachments from your system without reading the content and notify the sender immediately of the inadvertent transmission. Thank you for your cooperation.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080715/8da1fc16/attachment.htm