Email step not sending out mail

[Former Member]

Hi experts,

I have added a send email step after invoice rejection in WS10000051. But email could not be sent and the workflow just gets stuck after the invoice rejection step. Funny thing is if the email is sent out, it happens only once and after that it gets stuck again when i triggered the workflow again.

Thank you.

[Former Member]

Lester ,

Have you trying to send a mail to external email?

In the send mail step, In the recipient type what you have maintained?

Thanks,

Vijay.

[Former Member]

Hi,

I've not tried to send external email. The recepient type is "Expression" and the value is "workflow initiator". I need the mail to be sent to the workflow initiator.

Thank you.

[Former Member]

Ok. Where exactly the workflow getting strucked? After the Invoice rejection step means, that step is completed or not? If this step was completed, and workflow gets struck at the send mail step means,

Go to SBWP -> New message -> Enter Description & body.

In the Recipient tab, ENter your SAP user name & select recipient type as SAP logon name and send the mail.

Then check in SBWP whether its received that mail or not?

Thanks,

Vijay.

[Former Member]

Hi,

I've tried and the email is sent when i create a new message in SBWP. The workflow gets stuck after the Invoice Reject step and it is completed. The remaining steps after the Invoice Reject is not run at all.. Even if the email notification step is not direcly after the Invoice Reject step, the workflow also gets stuck after the rejection step..

Thank you.

Edited by: Lester Su on Mar 25, 2010 2:55 PM

[Former Member]

Hi,

What is the next step of Invoice Reject step. It could be binding problem. Please check all bindings and in workflow log try to check whether all binding variables get populated or not..

Thanks.

[Former Member]

Hi,

The next step is "Initialize Full Release". I've checked the binding and it's populated with the correct values.. Are there any other things to look out for?

Thank you.

[Former Member]

Hi,

The three step types are container operation, and used to populate the flags, Released_Flag1, Released_Flag2 and Released_Flag3.

By default there is no assignment. I think you should do the assignment. For that, double click the step type, Operation -> Expression-> press F4 and select, Released_Flag2 and save.

Likewise add the assignment for the remaining step types too. Hopefully it will work.

Thanks,

Vijay.

[Former Member]

Hi,

I've added in the expression and it worked for a couple of times. Then after which it didnt work any more.. In SWIA, the workflow stops at the above mentioned place again.

Do I have to add any entry into SWETYPV - Event Linkages?

Thank you.

[Former Member]

Hi,

Your workflow is getting triggered right? Then no need to do anything in SWETYPV.

Two times it was working perfectly. So please check those test data's with current test data's.

Thanks.

[Former Member]

Hi,

Also chek the workflow log and ensure that the key fields [Doc no, Year, company code] are populated or not.

Thanks.

[Former Member]

Hi,

Something I don't understand is why the email gets sent out once and then after that it refuse to send out if i trigger the workflow again.. The test data is exactly the same as i've been using the same set of data for testing.

Thank you.

[Former Member]

Lester,

Sending mail is not at all a problem. If the workflow is getting triggered and the values are populated correctly, then it will reach the send mail step and mail will send and the workflow will go with the remaining flow.

If the data's are not populated also the mail will send. It needs only a agent as a input and if nothing populated then the empty mail will send to the inbox. Its only for notification purpose.

If your workflow getting struk means, it has the problem. Go to SBWP -> Started workflows-> select your workflow -> Goto log.

Here you can see the data's hold by your workflow containers. Please check it.

Thanks.

[Former Member]

Hi Viji,

I've checked the data in the container and they are all the same.

Thank you.

[former_member184495]

Hi LS,

is the WF giving error after the mail is sent, if yes, then theres problem in the WF definition.

if there is no error in your WF graphical log, try to recreate (delete and create) the same SendMail step in your WF builder, also if this problem is faced by you in DEV, just run SWU_OBUF once and try to trigger WF again.

*Note, pls do not use SWU_OBUF in PRD.

Hope it helps.

Aditya

[former_member185167]

Hello,

Look in the technical view of the workflow log to see exactly where the workflow is stuck, and check for any error messages.

I assume it only gets stuck when the sending of the mail fails?

The workflow is always at one step or another, and there's always a reason why it's not continuing.

regards

Rick Bakker

Hanabi Technology

[Former Member]

Hi,

I've checked the workflow log(details) and I am getting the following message for the step "Waiting for event Rejected of object type FIPP".

Error msg1: Temporary error in result processing of work item 000000391129

Error msg2: Return message from work item 000000391129 within a closed component

What do they mean? Could not drill down the error message further..

Thank you.

[former_member185167]

Hello,

Temporary errors (eg locking) get resolved by job SWWERRE. Check in SWU3 if it's running and if not, get it going.

regards

Rick Bakker

Hanabi Technology

[Former Member]

Hi,

The job is set to run every 20min. Tried it once after the batch job finishes and the mail got sent out. But subsequently, it didn't get sent.. Why will there be temporary errors occuring?

Thank you.

[former_member185167]

Hello,

Temporary errors are almost always locking problems, e.g someone is in the related transaction at that time. It would take some research to find out what and why.

So it did work - after the batch job ran the mail was sent? Subsequent temporary errors would be fixed by subsequent runs.

regards

Rick Bakker

Hanabi Technology