SOLVED: Generating email from activity in e-recruiting

[Hilsbos, Margaret A]

Okay, problem solved. 

You were on the right track with the WF-BATCH suggestion...except it wasn't the email address that was missing.

Whenever the user WF-BATCH was created, no default printer was entered. We entered the value LOCL for the printer (Output device) in the defaults tab of SU01 for WF-BATCH, and it started working. Deleted the printer value, it stopped working. Put it back in, it works.

Yep, you read that right. PRINTER.  So the system can send an email.

I guess there is some logic to that somewhere...


(oh and forgot to mention in my original email, for anyone who wants to file this away: the system is NW04 (WAS 640) with E-Recruiting 3.0)



-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Hilsbos, Margaret A
Sent: Wednesday, June 28, 2006 12:15 PM
To: SAP Workflow Users' Group
Subject: RE: Generating email from activity in e-recruiting


Hi Alan,

1) There is no exception trapped. The workflow completes with all green lights, no errors or warnings.

2) This is a SAP-delivered task.

3) There is no binding from the task to the method.

4) I searched SAP Notes for the task number and various other terms and came up empty.

I am not sure how to use technical trace...do you think it's worth the effort in this case, or is it time to submit a customer message to SAP?

This one is really puzzling me...I appreciate your effort to help!

Margaret


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Rickayzen, Alan
Sent: Wednesday, June 28, 2006 11:40 AM
To: SAP Workflow Users' Group
Subject: RE: Generating email from activity in e-recruiting


Hi Margret,
 
If you look at the work item generated you should see an exception
message
which explains the reason for failure (assuming that the exception is
trapped). This is a blue "i" button on the technical work item display.

One cause of failure might be that the data that is passed to the task
is
not being passed to the method (e.g. the sendto address). Normally the
task
container is simply copied but if someone has created a binding between
the
task and the method this may be incorrect (technical trace helps locate
this
if an inspection of the binding is not sufficient). 

If the task is delivered by SAP then searching SAP Notes for this task
ID
would be the best approach.

Sorry I can't help more (but I'm curious about the outcome).

Best regards,
Alan