Skip to Content
-1

How to assign workflow task to Sales Order Quote

May 02, 2017 at 03:47 PM

250

avatar image

Greetings,

How can I assign a workflow task to a sales order quote type (VA21) to send notifications to Agent's SAP inbox?

The new quote type ZAB is a direct copy of quote type ZAA and upon saving the document there should be a task that is triggered, sending a notification to the user's inbox. This works for the previously existing order type but not with the new one.

The BUS object has already been set up in PFTC, is there anything that may have been missed?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Jelena Perfiljeva
May 02, 2017 at 05:18 PM
1

Quotation and sales order are two different document types in SAP.

Using Google -> "sales quotation workflow site:sap.com" you can find some general information. Regarding specific implementation for a custom type at your organization I'd suggest to look for the documentation locally. When someone implemented ZAA surely they should've left some kind of document behind.

Share
10 |10000 characters needed characters left characters exceeded
Veselina Peykova
May 02, 2017 at 06:24 PM
0

I am not a workflow expert, but there could be plenty of things - just because a task for a method is created and some process is implemented for one document type, it does not mean, that it will work for any new document type.

How is the event triggered - outputs, change documents, BTE?

Or it this done by some custom program?

Did you look at output condition records, FMs flogic for the BTE?

What about Check FMs in SWETYPV?

And are you 100% sure that this task is not actually a part of a workflow and that there are no additional start conditions?

And how do you determine the recipients - is it a custom rule with responsibilities or some in-house developed FM?

Look at how exactly your original process is implemented, there is a chance that it is even documented in some functional design document, if yes - it could help you a lot.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Greeting Vesilina, thanks for your input. There are no updated documentation on this task, it was one of my first research points. The task is a 'standard task' and not part a workflow; I have already checked SWDD and table SWWWIHEAD. The recipients/agents are determined based on the 'Agent Assignment' that can be displayed PFTC. I am working with programmer to decipher the issue that my be in FM that is not being called.

0
Anjan Paul May 03, 2017 at 06:24 AM
0

Hi,

If it is working for old type, then you first check where it is maintained any custom logic in workflow. Might be there have some condition or custom table maintain due to that old type is triggering . So in that case you have to find and assign the new order type in proper place.

So first look at the Technical specification document of Workflow

Thanks

Share
10 |10000 characters needed characters left characters exceeded
Rob Dielemans May 03, 2017 at 09:16 AM
0

Hi,

Pleace check if there are Event-->Workflow conditions (swb_cond) or even a check function module SWE2.

If not then you are missing customizing so pleace consult your local SD consultant.

Kind regards, Rob Dielemans

Share
10 |10000 characters needed characters left characters exceeded
Aditya Varrier May 03, 2017 at 10:10 AM
0

Hi Anderson,

the easiest way to find a solution is to check SWE2 transaction, search for your BUS there. Since you said that it was already set for your quote-type, similarly, either create a new task or check the method that your BUS might be using.

Basically if you want your BUS to be linked to any of your WF template or Task, that needs to be maintained in SWE2 transaction.

Hope it helps.

Aditya V

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hello Aditya

I checked transaction SWE2 but am not sure if that is the correct approach. The Linkage Check box is unchecked in each environment but the Prod environment where the issue is occurring has the same setup as Dev and Quality and the latter 2 work as expected for the new order type. Working with developer on this issue....any other suggestions will greatly be appreciated.

0