Leave Workflow Error

[Former Member]

Hi Experts,

I have copied the standard workflow WS12300111 to WS99900006(This is my custom workflow range). I changed the setting to General Task so that everybody in the system can execute this workflow and I activated it.

I configured the custom workflow no to one of the absence type defined in the system (Employee Exam Leave). When a person from Enterprise Portal tries to select this leave type and send it to the approver it shows "Unable to send request".

Can anybody tell me why it is giving error. I have just copied the standard workflow to custom and I am using it in one of the leave type it is giving this error. If I use WS12300111 instead of the custom workflow it works properly, I don't get any error, it works perfectly fine.

Can somebody throw some light on this issue.

[Former Member]

Hi Vaibhav,

You can check the following for this issues:-

1> SWU3 Settings - All should be green ticks

2> SCOT - SMTP Server Settings enabled by the BASIS Team

3> Check the Custom WF for BINDING...START CONDITION...ACTIVATION WITHOUT ERRORS..!!

Refer these links:-

https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/workflow%252bscenario

/people/sapna.modi/blog/2007/02/19/workflows-for-dummies--introductionpart-i

4> I have just copied the standard workflow to custom and I am using it in one of the leave type it is giving this error.

Check whether the WF is configured for these types or not.

Let me know if u still face any issues.

Regards,

Kanika

[Former Member]

Hi Kanika,

Thanks for your reply all the customisation and all is correct, because earlier i was using WS12300111 for the same absence type but when i copy this workflow and create a new one this is not working it says 'Unable to send the request'.

I tried testing the application through PTARQ their also it says the same thing "Unable to send the request".

Regards.

Edited by: vaibhav patil on Jan 8, 2009 8:43 AM

[Former Member]

Hi Viabhav,

I have a query here..!!

> because earlier i was using WS12300111 for the same absence type but when i copy this workflow and create a new one this is not working it says 'Unable to send the request'.

If earlier it was working fine with the Standard Functionality, what was the need of creating Custom WF..?

Regards,

Kanika

[Former Member]

Hi Kanika,

Previously they didn't had the requirement to have one more approver now they want one more approver as everybody knows the standard workflow has only 1 approver. So thats why there was a need to create a custom workflow.

Regards,

--VP

[Former Member]

Hi,

"Unable to send Request.."

This Error comes for the Second Approver or the First Approver..??

If this is for the Second Approver that you have added in the WF, then the issue lies with the Customization of the WF or else we need to figure out the reason.

Regards,

Kanika

[Former Member]

Hi,

This error comes at the first step before the task of 1st approver.

REgards,

--VP

[imthiaz_ahmed]

Did you configured the customizing step from PTARQ to bind your new WF template to the absence type.

Regards, IA

[Former Member]

Hi,

I have done that setting too. Still the ame problem

[Former Member]

Dear Mentors,

Can you guys atleast throw some light on this issue.

Regards,

Vaibhav Patil.

[pokrakam]

>

> Dear Mentors,
>        Can you guys atleast throw some light on this issue.

Hello,

May I suggest having a read through the Rules of Engagement, there's a section on why you aren't getting any answers and some good info on what you can do to try get more/better answers. In particular, show that you are also making some effort and not just, not sitting and waiting (as your post appears to suggest). This is not a support platform. If you aren't getting any answers, you're welcome to post back if you try something else, or give us more information.

With that in mind, let's move on to your question: What have you tried since the last post? Have you tried to debug it? Looked on OSS? You say you have carried out the config, and to me it seems correct so those are the only suggestions I can make without more info.

[Former Member]

Hi Mike,

Thanks for your help for showing me the rules and regulations. For your info I have tried everything then only I have posted my error in the forum. I have tried to my best level of knowledge as well as after getting suggestions I have tried that too. As you have asked me whether you have debugged and an answer to that is YES I have debugged the program too. If any more questions you have you can ask me.

Regards,

Vaibhav.

[Former Member]

Issue Resolved

[Former Member]

Solved

[former_member193382]

Hi VP,

Check out this link.

[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/103e2cf0-ec95-2b10-d198-a2d5edfbd7f8].

Regards,

Raj

[bpawanchand]

I Could not find any relation between the Question and the link you posted.

Wrong link

[former_member193382]

Thanks Pavan,

It is just a document that gives details about leave request from portal. So i thought vaibhav can cross check the same. And what i feel is instead of wasting your time on pointing my mistakes you can use this time to answer to the question and provide solution to vaibhav. Hope you understand and here after you'll try to make the best use of your time.

Regards,

Raj

[bpawanchand]

Thanks For your Suggestion I'll try my level best

[pokrakam]

>

> It is just a document that gives details about leave request from portal. So i thought vaibhav can cross check the same. And what i feel is instead of wasting your time on pointing my mistakes you can use this time to answer to the question and provide solution to vaibhav. Hope you understand and here after you'll try to make the best use of your time.

That's a bit odd since you do not seem to follow this advice in your original post which contained no relevance to the problem. The original poster is familiar with setting up the standard leave request workflow, so why waste his (and everyone else's) time posting info that does not address the error or anything about custom workflows.

Please keep your posts on topic and relevant.