Triggering of mail through workflow once status of quotation changed.

[former_member1191953]

I have requirement. I have to design workflow for quotation. Once quotation(VA22) status changed

mail should trigger to concern person. can any one expalin me briefly.? I am new to workflow.

Is it possible to debugg workflow? . User exits can be used inside worflow.?

Regards,

Mr. Nice

[former_member186746]

Hi,

If the functional requirement is: upon change of quotation send mail to person.

Then you don't have to use workflow to accomplish your goal.

Kind regards, Rob Dielemans

[Former Member]

Hi,

1) if your re requirement is just to send an email norifications when quotation status changes, dont go with workflow. You can send emails from some user exits/BAdI also. We use workflows when there is any user/agent/approver intervention is required, when someone is required to take any action on work item. if your requirement is just to send emails then search for some exits for VA22 and write your code foe email triggering.

2) It is NOT possible to debug workflows. Though SAP have started to provide feasibility to debug in some very new workflows (e.g. process and forms workflow in HCM) but debugging workflow is almost impossible because SAP exeuctes task methods in BACKGROUND using WF-BATCH user id. Even if you want to debug it, there are two options.

• Set WF-BATCH as dialog user in SU01 then you can set external breakpoint for it. But WF-BATCH is always set as a system user by basis team when automatic workflow customization is done using SWU3. Ideally it is not advisable to set WF-BATCH as dialog user and debug, but you can give a try in your dev or quality systems.
• For this method you need to have access of SM50 tcode. Write an infinite loop at the start of your class/BO method which you want to debug. Execute workflow. your workflow will go in infinite loop. then go to SM50 from there you can debug.

3) There is no use of user exits in workflow. We create own own methods of BO and classes and use them in workflows. Yes, yoo can use user exits to trigger your workflows. But inside workflow there is no user exits. There is a concept of program exit in workflows which is a different story. http://saptechnical.com/Tutorials/Workflow/Exit/Index.htm

[ronen_weisz]

User status (or system status) changes can be used to raise events (via transaction BSVW - http://help.sap.com/saphelp_40b/helpdata/fr/c5/e4aee2453d11d189430000e829fbbd/content.htm)

from the event you can trigger a workflow to send a mail or a task to the user.

It is possible to debug workflow tasks, but since the tasks are simply calling object/class methods it's easier to debug them directly (using transactions SWO1/SE24). all the data transferred to and from your tasks is visible in the workflow log and can be used to check binding errors.

As for user exits, since you control the method you are calling in the task, and have the ability to write your own methods (Extending and Adapting Object Types (BOR) - SAP Business Workflow - SAP Library), I don't see the need.

There are user exits in workflow but those are for more advanced developments such as removing decision options in specific cases or workitem preview display in the SAP business workplace.