Report workflow

Hi,
I created a workflow for approval appropriation request.
There are various approval levels for an appropriation request.
Is there a report that show me, who process the appropriation request at a given time? More precisely, is there a report that shows me who must to make the step of workflow at a given time?
Thanks
regards
Raffaele

Hi Raffael,
     There is no report for exact use your mentioning. But yes you can develop a quick report based on SWWWIHEAD and SWWUSERWI. Where as SWWWIHEAD will give you details of workitem and SWWUSERWI wil give you details about possible or actual agents for a given work item.
    Theer are some standard transactions as mentioned by other forum members. But by my experience users need to be more advanced than basic level users to understand it. if it is for your self then thos might be ok. But still if you need a report for regular monitoring i would recommend a bespoke report.
Warm Regards,
Anuj Nagpal

Similar Messages

  • SharePoint 2010: Scheduled Web Analytics Reports workflow is not sending ANY email

    Hello,
    I've a SharePoint 2010 Enterprise farm. I setup a Scheduled Web Analytics Reports workflow in a site collection with different web analytics reports options checked. So far I've not got ANY email. When I went to Site Workflows, I'm seeing that the workflow
    is running. When I click on Completed status, I see below outcome in the Workflow History section:
    "Email sent but reports with no data were not attached."
    And I see below information in the Workflow History list:
    "Attached are the daily Web Analytics reports for 1/7/2015 through 1/7/2015 for SharePoint Site Collection
    http://server/team/site scheduled by workflow "SharePoint Site Web Analytics Reports". "
    I am able to generate the reports manually by going to Site Collection Web Analytics Reports, but I want to schedule them. The problem is I'm not getting ANY email in my inbox. What am I missing here? Are the emails getting filtered by Outlook or workflow
    is not sending emails at all?
    Please help! This is getting frustrated.
    Thanks,
    Ashish

    Hi Ashish,
    Based on your description, my understanding is that the email is not sent from the Scheduled Web Analytics Reports workflow.
    I recommend to the things below:
    1. Check if the Outgoing email has been configured for the web application where you run the Scheduled Web Analytics Reports workflow.
    In Central Administration > Application management > Manage web applications > select the corresponding web application > click General Settings in the ribbon and select Outgoing E-mail.
    2. Make sure that your account has email address configured.
    Thanks,
    Victoria
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Victoria Xia
    TechNet Community Support

  • User decision history report, workflow summary log

    Hello SAP Workflow community,
    In our project there is a task to implement User Decision history/log management. I want to get programmatically (via ABAP, in order to be able to store this data in DB too) the history all user decisions (statuses of all User Decision work items) inside of specific workflow and send the summary report to the workflow initiator/workflow administrator upon the workflow completion.
    After some search I found the complete set of relevant function modules under SAP_WAPI_WORKITEM_*, where you can get detailed information per work item, including their statuses, but I'm not sure, that this is the best practice to implement such task.
    Of course, we can go «brute force» and built such log manually: to log each user decision and store it in multiline container and after that find some way to send it to the desired person. But I'm pretty sure, that there must be another way, should be some standard, SAP-provided way to build such summary report. Could you, please, point me to the relevant directions.
    The Bottom line is at the end of each workflow execution I want to send to workflow initiator the report with list of all User Decisions, their statuses (approved/declined) and username, who took the decision.
    Thanks.

    GOS->workflow->workflow overview should show the workflow log showing the status of the workflow until now (workitem name/start data & time/end date &time/decision/status/user name).
    Table swwwihead has the fields wi_cd (creation date) wi_aed (end date) and wi_aagent (actual agent)
    Table sww_wi2obj has the link to the object.
    Table swwloghist has the workitem history.
    You could use the way suggested by Karri, since the decision is hard to read directly. But for workflow reports,I usually use BW see Workflow reporting in BW – extractor improvements

  • Work book, web reporting, workflow, structures

    HI all,
    Can u please send the any of the documents which is mentioned above..it will b very helpful
    Points assured
    Email: [email protected]
    Regards
    Pushkar

    Hi,
    Check these
    WEB REPORTING:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ec20a990-0201-0010-f291-d1d039975e41
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a249a990-0201-0010-e18e-b2f5ed135497
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bc4fa990-0201-0010-588e-ca4e63050d6d
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b931a890-0201-0010-268d-a7bedf8aa720
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f0aca990-0201-0010-0380-f3aac4127a57
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3541a990-0201-0010-f1ae-b24b72690df7
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2642ab90-0201-0010-9193-d59de66cbab4
    Regards,
    R.Ravi

  • Upgrade from 11i to R12 - Custom Forms,Reports and Workflows

    Dear Community Friends,
    We are planning for upgrade from oracle apps 11.5.10.2 to R12.
    We have custom Forms,Form Libraries,Reports and Workflows.
    Kindly provide me for approach on how to migrate Custom form libraries,reports and Workflows.
    I beleive, this thread will exists as one shot point for custom forms,reports,workflow upgradation from 11i to r12 with detailed steps.
    I know that many links exists here in the forum for all the above objects mentioned,but still from all those i am able to get a clear picture for oracle forms but not for custom form libraries ,reports and workflows.
    Also,this post will provide a low level,practical picture of the steps for those who are in line with this.
    Links i have read for all these in our forum are:
    For Custom Forms,
    Re: Planning to upgrade from 11i to R12
    Re: Custom forms: After upgrading 11i to R12
    ofcourse,'n' number of links exists providing metalink notes also.
    Hussain,Helios and some others also has given many updates regd this.
    For custom workflow upgradation,
    Upgrade Workflow 11i to R12
    Workflow Upgrade
    Workflow Upgrade
    For reports,links mentioned the below metalink notes:
    Do Not Compile EBS R12 Reports Using rwconverter.sh or Reports Builder from IDS 10gR2 [ID 786794.1]
    Using the OracleAS 10.1.2 Forms and Reports Builders with Oracle Applications Release 12 [ID 444248.1]
    Per my understanding, after searching in many threads,i am here by summarising the practical low level steps for custom forms migration
    Please correct me,if i am wrong.
    1) Download the Forms(.fmb's) and all PLL's(all the PLL from resource folder in AU_TOP) into a Local Machine Folder
    2) Open the forms using Forms Developer 10G and connect to DB
    3) Compile by clicking compilein Forms Developer and then save it.
    4) Upload the Saved Forms(.fmb's) into the new R12 server(system) in the respective custom paths(paths similar to 11i Server)
    5) Compile all the forms using the command like below(example command is shown below or f60 gen commands or frmcmp.sh utility) in the respective custom form paths,
    this will generate the .fmx's.
    frmcmp_batch module=FORMNAME.fmb userid=apps/apps output_file=FORMNAME.fmx compile_all=yes
    Link for compiling forms: https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=359210362972527&type=DOCUMENT&id=1085928.1&displayIndex=3&_afrWindowMode=0&_adf.ctrl-state=c348xvwbg_98
    6) Open the form and check in R12 instance
    As per my understanding for custom form libraries,we can just copy paste the PLL's from 11i server to R12 server (Please correct me,if i am wrong)
    Can anyone please help me out in custom reports and custom workflows.Sorry that,i could not get a practical and clear picture for reports and also for workflow even after referring many threads and metalink notes mentioned.
    As for reports,some says that Developer Suite 10g can be used and .rdf can be used in R12.
    Some says that reports should be converted to XML published as reports does not exists in R12.
    So,i am not clear on this.
    Thanks,
    Ganesh
    [email protected]

    Per my understanding, after searching in many threads,i am here by summarising the practical low level steps for custom forms migration
    Please correct me,if i am wrong.
    1) Download the Forms(.fmb's) and all PLL's(all the PLL from resource folder in AU_TOP) into a Local Machine Folder
    2) Open the forms using Forms Developer 10G and connect to DB
    3) Compile by clicking compilein Forms Developer and then save it.
    4) Upload the Saved Forms(.fmb's) into the new R12 server(system) in the respective custom paths(paths similar to 11i Server)
    5) Compile all the forms using the command like below(example command is shown below or f60 gen commands or frmcmp.sh utility) in the respective custom form paths,
    this will generate the .fmx's.
    frmcmp_batch module=FORMNAME.fmb userid=apps/apps output_file=FORMNAME.fmx compile_all=yes
    Link for compiling forms: https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=359210362972527&type=DOCUMENT&id=1085928.1&displayIndex=3&_afrWindowMode=0&_adf.ctrl-state=c348xvwbg_98
    6) Open the form and check in R12 instance
    As per my understanding for custom form libraries,we can just copy paste the PLL's from 11i server to R12 server (Please correct me,if i am wrong)You are right, and the steps mentioned above should be sufficient.
    Can anyone please help me out in custom reports and custom workflows.Sorry that,i could not get a practical and clear picture for reports and also for workflow even after referring many threads and metalink notes mentioned.
    As for reports,some says that Developer Suite 10g can be used and .rdf can be used in R12.
    Some says that reports should be converted to XML published as reports does not exists in R12.
    So,i am not clear on this.You can still use RDF files in R12, and just follow the approach you mentioned above, and you do not have to migrate them to XML publisher (though it is recommended, but this can be done after the upgrade as an enhancement task).
    For custom workflow, you need also to do the same thing, open them using workflow builder and make sure they work in R12 (correct the code if required and save them again in R12 once they work properly).
    Thanks,
    Hussein

  • Problem in executing report in background in CS workflow

    Hi All,
    I am using ECC 6.0 version.
              In my scenario , Once notification is closed , workflow should trigger. and along with this , one report should execute in background with input parameter as a Notification no. from workflow . Report  should pick up input parameter dynamically.As I know instead of function module we can choose report option in business object .
               My question is how that report will get input parameter as notification no.& How I do the binding for this (Between report & workflow)?
                Valuable suggestions are excepted.
    Regards,
    Sheetal

    Hi Sheetal,
    As I had mentioned earlier (you have already implemented), add the report to your BO as a method. Then click on method and then click 'Parameters'. Create the required parameters, which is 'Notification No.' and go to the system generated 'Program'. Here you will have to do a bit of macro coding. Obtain the No. (once you add as parameter, you will get it through binding) and pass to report.
    You might also retrieve (only if required or only in certainb cases) values, for that observe how the attributes are retrieved on the basis of key field.
    Best regards,
    Abir.

  • Timed out error when running a report

    The error is:
    "Request timed out because there has been no reply from the server in 600000 ms"
    Does anybody have any idea how to solve the issue?
    The following is more info on the report:
    Report has 8 subreports and data set is around 7MB size
    We generated another report with 83MB of data and this report doesn't have any subreports and its running completely.
    using Crystal reports XI r2 SP3, Visual studio 9, BOXI server SP3 and using XML as data source.
    Any help would be appreciated.
    The following is the Stack Trace:
    System.Exception was unhandled by user code
      Message="Load report failed."
      Source="CrystalDecisions.CrystalReports.Engine"
      StackTrace:
           at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
           at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, OpenReportMethod openMethod, Int16 parentJob)
           at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename)
           at CrystalDecisions.CrystalReports.Engine.ReportDocument.Load(String filename, EnterpriseSession enterpriseSession)
           at Covance.ED.Framework.Reporting.Workflow.CreateReportOutputActivity.executeCrystalReport_ExecuteCode(Object sender, EventArgs e) in C:\Source\TR\Components\Framework\Covance.ED.Framework.Reporting\Workflow\CreateReportOutputActivity.cs:line 189
           at System.Workflow.ComponentModel.Activity.RaiseEvent(DependencyProperty dependencyEvent, Object sender, EventArgs e)
           at System.Workflow.Activities.CodeActivity.Execute(ActivityExecutionContext executionContext)
           at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
           at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(Activity activity, ActivityExecutionContext executionContext)
           at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
      InnerException: System.Runtime.InteropServices.COMException
           Message="Failed to load info object."
           Source="Analysis Server"
           ErrorCode=-2147467259
           StackTrace:
                at CrystalDecisions.ReportAppServer.ClientDoc.ReportClientDocumentClass.Open(Object& DocumentPath, Int32 Options)
                at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.Open(Object& DocumentPath, Int32 Options)
                at CrystalDecisions.ReportAppServer.ReportClientDocumentWrapper.EnsureDocumentIsOpened()
           InnerException:

    There are a few timeouts that could come into play here. One is a Corba timeout.
    You'll want to adjust your ConnectionTimeout in your regisry under HKEY_LOCAL_MACHINE\SOFTWARE\BUSINESS OBJECTS\Suite 11.5\CER. The default value is 600000. Try doubling it to 1200000.
    You may also want to increase your httpExecution timeout as well in your web.config file.
    http://msdn.microsoft.com/en-us/library/e1f13641.aspx

  • WorkFlow Tutorials with Screen Shot

    HI Experts,
    Can anyone send WorkFlow Tutorials with Screen Shots??..My email id is <REMOVED BY MODERATOR>.. Full points will be rewarded for this immediate help..Thanks..
    Edited by: Alvaro Tejada Galindo on Jun 6, 2008 1:52 PM

    Hi Satheesh,
    Please find some questions related to WorkFlow
    1. Is there a good book about this subject?
    Yes, "Practical Workflow for SAP" by Rickayzen, Dart, Brennecke and Schneider. Available from SAP press at the end of July. A german translation of this workflow book is also available directly from Galileo-Press, the publisher.
    2. How do I convince my company to use workflow?
    Feedback from user groups emphasizes that although the competitive advantage gained by using workflow eclipses the financial savings, it is the financial savings that are the deciding factor when obtaining support from senior management. Projects getting the blessing at the CEO level are much easier to manage, and far more likely to reach their goal within the project time frame. So plan well, and don't neglect the business case.
    Because the following questions deal with the financial case in more detail, this section will finish by listing the competitive advantages.
    The quality of the process is assured by pushing the relevant information together with links to related transactions directly to the user. Managers don't have the time to search for information so give them what they need to reach the correct decision.
    Cycle time is reduced by pushing the process directly to the users. The users receive notification of a task immediately and can even be prioritized by the system.
    The tasks are performed consistently and diligently by the users. The workflow system pushes all the necessary information needed to perform a task, including a clear description of what has to be done, how to do it and the impact this task has on the business process for your company. At any time, the user can check the list of tasks pending and determine at a glance which are the important tasks, and which tasks can be completed the next day without any negative impact.
    The process instance is transparent. Any user can check at any time how far the process has progressed and which stage the process has reached. For example the call center can immediately see the status of a purchase order, an employee requisitioning a purchase would see at a glance if a colleague has been sitting on it for too long, the ad hoc notes made when approving an engineering change request are visible long after the request has gone into production.
    The process is flexible, allowing it to be changed on the fly without retraining everyone involved. The description accompanying the change takes care of on-the-fly process improvements.
    Deadline handing ensures that users perform the tasks within the time planned. Escalation measures ensure that the failure to meet a deadline can be corrected by other means.
    Intelligent reporting highlights the weaknesses of a process. Often there is a simple cure to such weaknesses such as reeducating the users involved in the bottleneck or providing additional information (automatically). The difficulty of a non-automated process is identifying such bottlenecks.
    The process definition is transparent. You can see at a glance how the process works and who will be selected to perform the different tasks. Think of the workflow as the process book. If you can spot the pattern and define the process without headaches, you can create a workflow definition effortlessly. However, don't forget that if a company has business processes that are erratic and lack a consistent pattern, the company is very likely to be losing a lot of money in terms of lost contracts, labor intensive administration and low customer confidence. It is my personal opinion that automating exactly this type of processes will yield the best returns, but only if you limit yourself to automating the basic skeleton of the process first. Don't get bogged down in the detailed exception handling. That can be done in the next phase once you've checked the process statistics and determined which exceptions are worth tackling.
    As with most software the reasons for automating business processes are primarily to increase the competitive edge of your company and to cut costs. Although the increase in competitively gained by radically reducing process times is by far the most insignificant gain from workflow, you should not ignore the cost savings. The cost saving calculations are needed by upper management in order to approve workflow projects. This upper management signature will be very useful in different phases of the project and cannot be underestimated.
    3. How do I calculate the cost saved by workflow?
    Calculate the cost of the manual process in terms of man hours. Don't neglect the time spent gathering information. Ask the following questions:
    Is the user forced to log into different systems, or scan through printed documentation....?
    Does a skilled user spend time on parts of a task, where less skilled (less expensive) user could do the groundwork? I.e. Can a single task be split into skilled and unskilled tasks to free the skilled worker for work where his/her skills are really needed?
    Is time spent researching the progress of a process (usually done by someone not involved in the process directly)?
    Is time spent determining who to give the task to next?
    Probably the most significant cost will the be the cost of failure?
    How often does the process fail?
    What is the real cost of failure? Loss of a contract? Loss of a customer? Law suit?
    If the failure can be rectified, how labor intensive is it?
    4. What are typical costs saved by workflow?
    A manually processed accounts payable invoice will cost about 25 USD. After workflow enabling about 15 USD (one example based on customer feedback from a user group meeting).
    5. What are typical reductions in processing time caused by workflow?
    A traditional paper based approval process involving three people will typically take seven days to complete. The automated process will take one day (results based on customer feedback).
    6. What do customers say are the strengths of SAP WebFlow?
    WebFlow is the internet functionality of SAP Business Workflow. Based on customer feedback from the various regional users groups, the main strengths of SAP Business Workflow are:
    Robust production workflow system, (upgrade continuity with the rest of the SAP system, versioning, scalability, no gluing....)
    Standard workflow templates delivered by SAP can be used out-of-the-box or tweaked to deliver the optimum business process for your company. Workflows can be up and running including training in under a day (thanks to the knowledgeware delivered as part of the template packet).
    Seamlessly integrated into the SAP environment, be it R/3, Business to Business Procurement, CRM, APO, mySAP.com.... Examples of integration are:
    Business Reporting (WIS),
    Context sensitive availability at any time through the system menu (available anytime, anywhere)
    More and more standard SAP functionality is being provided by using SAP Business Workflow so your homegrown workflows fit the landscape exactly,
    More and more workflow functionality is available directly within the SAP transaction or Web MiniApp.
    WebFlow is becoming more and more important because companies are no longer being judged by their own performance but by the combined performance of the company AND its partners. In other words it is not enough that the business processes within your company run smoothly and faster than your competitors. You have to ensure that the processes between you and your partners are also as fast, efficient and flexible as possible. WebFlow delivers this.
    7. How are users notified about their work pending?
    The users are informed by a work item which you may think of as being very like an e-mail. The difference is the work item contains intelligence and by executing the work item you will be taken to the form or SAP transaction that makes up the step in the workflow. This form or transaction could be a decision, a request for information or a request for confirmation that a particular task has been performed.
    The work item is usually accompanied by a description of what has to be done, where to refer to when assistance is needed (help desk, intranet...) and a summary of information about the business object or process which enables the operator to attack the task immediately.
    This work item can be received and executed in MS OutlookÒ, Lotus NotesÒ, mySAP Workflow MiniApp or the SAP integrated inbox. If this is not enough, the workflow system can transmit e-mail notifications directly to any mail system, informing the user of the need to log in to the SAP system to execute the task. The e-mail notification is done on a subscription basis so that users can de-subscribe from this service if they already check their work item inbox regularly.
    8. What workflow reporting is available and is it useful?
    Standard workflow reports exist which allow the administrator to check statistics such as the frequency and average duration of the workflow processes. However the real strength of the workflow reporting is that it allows reports to be configured which analyze the process statistics in combination with the data involved within the workflow process and the organizational units associated with the process. For example you can determine the average time invested in a failed contract renewal request, the time taken to create material masters in different plants or the frequency of rejected purchase requisitions on a department to department basis. Often, big reducations in cost or cycle time can be obtained without touching the workflow definitions. Reeducating a particular group of users or incorporating supplementary information in a work item description can often cause dramatic improvements on the cycle times of particularly critical subsets of the process. It is not unusual that this may have a big impact on specific products, plants or organizational units. This will show up in the WebFlow reporting in LIS or the Business Warehouse but it might not show up in traditional statistical workflow reporting. Even though the average time does not change significantly, the impact on costs and profit can be dramatic.
    9. How do I choose who to distribute the tasks to?
    A work item is assigned to one or more users. Whoever reserves or executes the task first wins and the work item vanishes from the other users' inboxes. This eliminates the need to assign the user to one single user. I.e. No need for complicated algorithms to determine which single user will receive the work item and no need to worry about what will happen when one user is ill for the week (also taken care of by sophisticated substitution mechanisms which can be linked to the SAP organizational model).
    Tasks can be assigned to an organizational unit but the strength of the workflow system is to enable business rules which select users according to the data being processed. For example, you might have one group of users associated with one quality notification type. The workflow can be configured to query the QM module directly to determine the users. You can define fallbacks using the default role associated with a task and allow agents to be specified on the fly by a supervisor.
    Tasks can be assigned to office distribution lists which is useful when you want your users to subscribe or unsubscribe to a particular task. A typical use of this would be where you have a work rote or want to reduce user maintenance to an absolute minimum. The users subscribe or unsubscribe by joining or leaving an office distribution list (one mouse click).
    10. What happens when a deadline is missed?
    This depends on your workflow definition. In the simplest case an e-mail is sent to another user by the system (typically your supervisor so watch out!). However in more sophisticated scenarios a missed deadline can redirect that path that the workflow takes. One customer uses deadlines to automatically make an approval if the deadline is missed (at about the eighth approval level!!!). This gives the user the chance to make rejections but does not force him/her to go into the system to approve the other 99.9% of the requests. In safety critical environments the workflow might trigger off preventative action when a deadline is missed or might put other processes on hold. There is no limit as to how you can use this functionality.
    11. What deadlines can be monitored?
    Many different types of deadlines can monitored. At the single workflow step level you can define deadlines which trigger when the work item has not completed within a certain time and other deadlines when no one starts working on the work item within a given time. You can specify the task deadline statically (e.g. 1 week) or dynamically (e.g. 1 week for material type A and 2 weeks for all the other materials). The offset can be related to the step (e.g. you have 1 week to complete this step) or related to the process (e.g. complete within 2 weeks of the complete process starting, irrespective of how long your colleagues have hogged the previous steps).
    Last but not least, deadlines can be set for sub-processes, which is often more important than the deadline of a single step in a workflow.
    12. How can I check the status of a workflow?
    This is one of the very cool features of SAP Business Workflow. You can usually navigate directly from the business object to check the workflow progress. For example, while viewing a purchase order you can select "workflow" from the system menu or toolbar and you will see a list of workflows related to the purchase order. Usually just one, but if you have created a few of your own and these have been triggered you will see the status of these too. And that is not all. You also see a simplified summary of all the steps that have taken place so far including who performed them, when they were executed and which ad hoc notes were attached.
    13. How are workflows triggered?
    Workflows can be triggered automatically by changes in the system or manually by an operator. Manually triggered workflows are good for processes that remedy a problem the operator has noticed or for dealing with a forms-based requests (E.g. my PC won't boot). Automatically triggered workflows are useful because the operator does not even have to be aware of the workflow's existence to trigger it. In addition to triggers embedded in transactions there are also generic triggering mechanisms such as a change in the status of a business object or a change in the HR data. Irrespective of how the workflow is triggered, it is linked to the business object as described in the previous answer and can be tracked easily. Because WebFlow is part of the basis system, this triggering is reliable and easy to implement.
    Workflows may be triggered by events but this is not essential. The event-handling makes it easy to trigger workflows from transactions and system changes without you having to make modifications. If you are creating your own report or transaction which triggers a workflow, avoid events and trigger the workflow directly with the WAPI function call. This is particularly important when triggering a workflow from outside the SAP system. This method reduces flexibility (the workflow ID is hard-coded) but increases performance if this is an issue (we're talking about 50 000 work items a day here!).
    Any exception handling workflows that are intended to be triggered manually can be triggered from the system menu when viewing the relevant transaction. The SAP system has the intelligence to suggest workflows that can be triggered manually based on the authorization of the operator and the context that the operator is working in. No additional customizing is needed here.
    14. What open interfaces are supported?
    The most significant interface supported is the Wf-XML standard from the Workflow Management Coalition. This is an independent organization of which SAP is a funding member, along with most other major workflow vendors. The Wf-XML interface is based on XML and allows workflows from different vendors to communicate with each other. A detailed description of the interface is available on the WfMCs web site at www.wfmc.org.
    15. What is Wf-XML used for?
    Although a company is far better off workflow enabling their system with SAP WebFlow when SAP software is used anywhere within the process, a collaborative process can take place between partners using different software platforms employing different workflow systems. To support SAP customers in this situation, WebFlow offers the open interface Wf-XML. This allows Business Processes enabled using different tools to communicate and control each other. Any workflow tool offering this interface can connect up with other tools that also offer this interface.
    Wf-XML is the only open interface for supporting interoperability of business processes, independent of what the business process being integrated.
    16. Where does Wf-XML come from?
    Wf-XML comes from the Workflow Management Coalition, an independent body of workflow vendors, customers and higher education establishments.
    17. How does the workflow call procedures from non-SAP systems?
    The Actional control broker integrates directly into SAP WebFlow enabling proxy objects to be called directly from the workflow step. When called, the proxy method will make a call to the outside system either as a background task or as a dialogue step. These proxy objects are generated in the SAP system using a converter which converts the objects interface (DCOM, CORBA...) to the SAP syntax. A syntax converter also lets developers view any object in any of the participating systems in the developer's preferred language.
    18. How can I get the workflow initiator information in my task?
    1) From your triggering event to the workflow, bind the event creator element to the workflow initiator element.
    2) Create a workflow container element based on USR01.
    3) Add a step based on USR01.FINDUSERFROMAGENTSTRUCTURE to convert your initiator to a USR01 object.
    4) Pass the USR01 object to each task you want to display the details.
    Mailing
    19. What differences are there between a work item and a notification mail?
    a) The work item cannot be used to notify several users.
    Mails can be routed to several users, just like work items. When a mail is sent, and one recipient reads and deletes the mail, all other recipients will still have access to their own copy in their own inbox. However, when a work item is processed by one of the recipients it will automatically disappear from all the other inboxes. So you can see that a work item is unsuitable for notifying several users.
    It is also worth noting that a mail can be forwarded in many different ways (fax, internet...) whereas the work item cannot.
    b) The work item holds up the workflow
    When the workflow sends a mail (usually as a background step) it continues with the process immediately after transmitting the mail. When a work item is generated, the workflow will not continue until the work item has been processed. This slows down the process. Occasionally this is what is intended (using the work item as an approval step without the ability to reject) but usually you will better off using mails for notifications.
    Note: You can send business objects as references with the mail either as a business object reference attached to the mail or as an URL (ABAP required).
    What is the difference between sending a mail to a recipient list compared to sending individual mails via a dynamic loop?
    Performance. Sending 1 mail to 20 recipients will cost considerably less performance than sending 20 individual mails. If the mail is sent as a SAP Office mail (as opposed to e-mail, fax...) disk space will also be a factor because the SAP office mail will only exist once in the database, with references being created for each of the recipients.
    The only time you need to consider individual mails with a dynamic loop is when the text of the mail varies from one recipient to another.
    20. How do I send a standard text as an e-mail from workflow?
    It is very easy sending standard text , which may include data from the workflow. You simply create a background step which sends the work item description. This may include variables which will be substituted when mail is sent.
    In early releases you have to create your own task based on the method SELFITEM SendTaskDescription. In later releases a wizard is available for creating the step and in release 4.6 there is even a step type which does this all for you automatically.
    Whichever path you take, there is very good online documentation describing exactly what has to be done.
    21. How do I send a complex text from the workflow?
    You may create mails using SAPscript. These mails can include conditions which are evaluated in order to determine which text blocks which are used in the mail. Workflow variables can be used in these conditions and workflow variables can be substituted into the body of the e-mail text.
    22. How do I send really complex mails from the workflow?
    If you this is not enough for you will probably want to write your own ABAP routines for generating the text and generating the attachments to go with the text.
    Use the function group SO01 which contains functions of the form SO_*_API1 which are ideal for creating your own sophisticated messages. There are plenty of advantages of how these are used within the SAP system.
    23. How do I send reports?
    There are wizards (Release 3.1) which will create workflows for you to send reports to a distribution list. You can specify whether the results should be transmitted or evaluated at the time the recipient wishes to view the report. It is usually better to send the evaluation because this allows the recipient to see the results instantaneously, without having to wait for the report to execute first.
    Deadlines
    24. How can I configure the workflow so that different types of messages are sent out to different people depending on how late the processing is?
    Follow these steps:
    1. Specify a deadline period for the step.
    2. Specify a name for the event. This adds new branch from the step.
    3. Add a new step to the branch which sends a mail message.
    4. Add another step to the branch which sends out the second deadline warning (see mail steps above). Use deadlines in this step to configure an earliest start so that the second message is not sent until a further time has elapsed.
    5. Repeat step 5 as often as you like.
    25. How can I configure the workflow so that when the deadline is missed the workflow step is simply skipped?
    This is tricky to explain but easy to implement once you know how.
    Follow these steps (in later releases there is a wizard which takes you through the steps):
    1. In the terminating events view of the workflow step activate the "obsolete" event and give it a name.
    2. Specify a deadline period for the step.
    3. Specify a name for the event. This adds new branch from the step.
    4. Add a new step to the deadline path. This step must be of type "process control".
    5. Select the control "Make step obsolete" and use the search help to specify the workflow step that has the deadline. Only steps with obsolete paths defined will be displayed (see step 1).
    26. How do I trigger a workflow with an e-mail?
    You can customize the system to call a BOR method when an external mail (fax, e-mail...) arrives in the system. You BOR method should either trigger the e-mail directly or trigger an event. To customize this user exit use the transaction SCOT.
    27. How can I make sure that user's access their tasks via the workflow and not via the menu or launch pad?
    The routing mechanism for work items uses roles and organizational assignments to determine who receives which work item. However the routing does not provide extra authorization checks based on the routing configuration. If you want to ensure that the tasks are executed within the workflow, and not via the standard transaction, service or MiniApp, then you will have to apply your own protection.
    The simplest way of doing this is to remove the standard transaction from the user's menu or Workplace role (but include it in the supervisor's role, just in case).
    If you want to allow the user to execute the task from the menu if and only if they have received the work item then you should replace the standard transaction with your own custom built transaction. Your own transaction simply calls the standard transaction but performs it's own authorization check first, based on the routing mechanism used in the workflow. Tip: Add a second (ored) authorization check to make sure that a supervisor can execute the transaction in an emergency.
    28. What is a workflow? What is a single-step task?
    A single-step task is based on an object type from the object business repository (BOR) (for example, a purchase order) and a method for the object (for example, change). A workflow can contain several single-step tasks and activities such as loops and forks. Through a workflow, you create a logical sequence for the single-step tasks. The tool for creating or changing these types of workflows (workflow template) is the Workflow Builder (transaction SWDD).
    29. What is a work item (important terms)?
    A work item is the runtime object of a workflow or of a single-step task.You can execute dialog work items with the inbox (transaction SBWP). Each workflow and single-step task started is assigned a unique number known as the work item ID.
    30. How is an event triggered from the application and a workflow then started?
    An event can be triggered from the application in three different ways:
    Directly:
    Within the application, the SWE_EVENT_CREATE function module or the SWE_EVENT_CREAT_IN_UPD_TASK function module, for example, generates an event in the update.
    With a change document:
    Change documents are written within the application when you change application objects in the update. You can link events that have the same key with these types of change documents via transaction SWEC.
    With status management:
    The SWE_EVENT_CREATE_STATUS function module triggers an event in the same way as the direct method when a status is changed. This event contains the object type (for example, purchase order), the object key (for example, purchase order 4711) and other information. Using transaction PFTC, you can assign the event to a specific workflow or single-step task. More settings are available in transaction SWE2.
    31. How are the responsible agents determined?
    You can assign agents to a single-step task in transaction PFTC. For example, you can do this using organizational units, work center roles or positions. Within a workflow pattern, you can assign specific agents for this workflow to a single-step task. The overlap between both numbers of 'possible agents' represents the number of agents ('selected agents') who have the work item in the inbox later.
    32. What is the difference of between an e-mail and a work item?
    E-mails and work items are two completely separate things. They just happen to be displayed in the same inbox. An e-mail is a message sent to one or several people. However, a work item is a runtime object of a single-step task or workflow. Consequently, a work item cannot be deleted from the inbox of a user. In this case in fact, you have to adjust the agent assignment or delete the work item as described in note 49545.
    33. PFAC no longer works for my role responsibility setup...
    Use tx: OOCU_RESP
    34. How do I transport workflow definitions and agent assignments?
    When transporting workflows, you have to differentiate between the workflow definition and the agent assignment.
    A workflow definition is a workbench request. When you save the workflow, a workflow version is created and a request written. Further information about the transport or about the status management is provided in note 378487 and in the notes mentioned there under related notes.
    However, where the agent assignment is concerned, this is a Customizing request. To allow transport of agent assignments, the value of the semantic abbreviation CORR for the TRSP group name must be empty in table T77S0.
    35. How do you debug a background workflow process?
    In your method write the following code:
    data exit.
    Do.
    if exit = 'X'.
    exit.
    endif.
    enddo.
    Run the workflow, causing an infinite loop on that step, and then go to SM50.
    Here you can debug the process.
    36.What is the Workflow basic Customizing?
    Before you can use the Workflow module, you must first execute the basic Customizing in transaction SWU3. All of the listed points should be green (the number range for customer tasks is no longer required). A detailed description of the activities is provided in the relevant information buttons. You can also execute some (but not all) of the points using the Automatic Customizing button. See the online documentation for an exact description of what happens there. The RFC destination must work correctly and the user (usually WF BATCH) should have the SAP_ALL profile.
    37.: What options do I have as a user to configure the inbox individually?
    You have the following options:
    You can create separate user-dependent or user-independent layouts so that you can adapt the displayed columns individually. You can access the function in the Workplace via an application function key.
    You can set filters to set certain criteria for individual columns or several columns simultaneously, according to which specific work items are then filtered.
    You can add dynamic columns in the layout that then display dynamic elements for certain tasks and users from the work item container. However, this is only possible if all tasks in the inbox belong to just one task. If they have several tasks in the inbox, filtering serves no useful purpose because all tasks are first completely read once. You can define these dynamic columns using transaction SWL1.
    38. What does the substitute rule system look like in the workflow?
    You have a choice of two different substitute rulings:
    Active substitute ruling (for example, for absence due to vacations): In this case, the items belonging to the absent person are automatically assigned to the substitutes inbox (in addition to his own work items).
    Passive substitution (for example, for absence due to illness): the substitute must explicitly assume the substitution and can only view the items of the absent person in this mode.
    For other questions, you must also refer to note 74000.
    39. How can users be automatically notified that new work items are available for processing?
    Unfortunately, the dialog box that informs users of new work items which appears in SAPoffice is not available within SAP Systems.
    However, the following two options are provided:
    In the Workflow Builder, you can designate the item as an express item via additional data. The user then receives a corresponding express dialog box.
    The RSWUWFML report (note 131795) is a more flexible option. This report sends an e-mail to an external Internet address to notify the user of new work items.
    40. Can I set deadlines for the latest processing of work items?
    this is where you can use deadline monitoring for work items. In the Workflow Builder, you can set dates for a requested/latest start/end date for each individual step. You must schedule the SWWDHEX job via transaction SWU3 for this. Schedule the job permanently in the production system otherwise it is difficult for the job to schedule individual deadline monitoring scenarios when workflow is heavy.
    41. Can I also execute work items with external programs such as Outlook?
    You can use the Web GUI for HTML instead of the Windows GUI. However, note that some functions do no work in the WEB GUI, due to technical restrictions in the browser. You must refer to note 487649 on this subject.
    SAP also provides interfaces which allow you to process work items with external programs such as Lotus Notes or Microsoft Outlook. Refer to notes 77099, 98408 and 454845 for details.
    More stuff on WORKFLOW
    Transactions
    AWUV Wizard for event creation Definition tools -> Event creation -> Set up with wizard
    MCA1 Workflow Information System Reporting -> Workflow Information System (WIS)
    OOAW Evaluation paths
    PFAC Maintain standard roles
    PFAC_CHG Change roles Definition tools -> Standard roles -> Change
    PFAC_DEL Delete roles Definition tools -> Standard roles -> Delete
    PFAC_DIS Display roles Definition tools -> Standard roles -> Display
    PFAC_INS Create roles Definition tools -> Standard roles -> Create
    PFOM Maintain assignment to SAP organizational objects Definition tools -> SAP org. objects -> Create assignments
    PFOS Display assignment to SAP organizational objects Definition tools -> SAP org. objects -> Display assignments
    PFSO Organizational environment of a user
    PFT Maintain customer task
    PFTC General task maintenance
    PFTC_CHG Change tasks Definition tools -> Task/Task groups -> Change
    PFTC_COP Copy tasks Definition tools -> Task/Task groups -> Copy
    PFTC_DEL Delete tasks Definition tools -> Task/Task groups -> Delete
    PFTC_DIS Display tasks Definition tools -> Task/Task groups -> Display
    PFTC_INS Create tasks Definition tools -> Task/Task groups -> Create
    PFTR Standard task for transaction
    PFTS Standard task
    PFWF Maintain workflow task (customer)
    PFWS Maintain workflow template
    PPOC Create organizational plan Definition tools -> Organizational plan -> Create
    PPOM Maintain organizational plan Definition tools -> Organizational plan -> Change
    PPOS Display organizational plan Definition tools -> Organizational plan -> Display
    SWDA Ongoing Settings Administration -> Settings
    SWDC Workflow editor administration data
    SWDM Business Workflow Explorer Definition tools -> Business Workflow Explorer
    SWE2 Display and maintain event type linkage Utilities -> Events -> Type linkages
    SWE3 Display instance linkages Utilities -> Events -> Instance linkages
    SWE4 Switch event log on/off Utilities -> Events -> Event/log -> On/Off
    SWEC Link change documents to events Definition tools -> Event creation -> Change documents -> Linkage
    SWED Assignment of change document objects to object types Definition tools -> Event creation -> Change documents -> Define workflow properties
    SWEL Display event log Utilities -> Events -> Event log -> Display
    SWF3 Workflow Wizard Explorer Definition tools -> Wizards -> Workflow Wizard Explorer
    SWF4 Workflow Wizard Repository Definition tools -> Wizards -> Workflow Wizard Repository
    SWI1 Selection report for workflows Utilities -> Work item selection
    SWI2 Work item analysis Reporting -> Work item analysis
    SWI3 Workflow outbox Runtime tools -> Workflow outbox
    SWI4 Task analysis Reporting -> Task analysis
    SWI5 Workload analysis Reporting -> Workload analysis
    SWI6 Object links Runtime tools -> Object links
    SWI7 Workflow resubmission folder From Integrated Inbox or Workflow Outbox
    SWI8 Error overview Part of administration of workflow runtime system (transaction SWUF)
    SWL1 Settings for dynamic columns Customizing, part of ongoing settings
    SWLC Check tasks for agents Utilities -> Consistency check -> Organizational assignment
    SWLD Workbench for Workflow 4.0
    SWLP Copy plan version
    SWLV Maintain work item views Customizing, part of ongoing settingS
    SWLW Workbench for Workflow 3.0
    SW01 Business Object Builder Definition tools -> Business Object Builder
    SW06 Customizing object types From Business Object Builder, choose Settings -> Delegate -> System-wide
    SWU0 Event simulation Utilities -> Events -> Simulate event
    SWU2 RFC monitor Utilities -> Workflow RFC monitor
    SWU3 Customizing consistency check Utilities -> Customizing
    SWU4 Consistency check for standard tasks Utilities -> Consistency check -> Task -> Standard task
    SWU5 Consistency check for customer tasks Utilities -> Consistency check -> Task -> Customer task
    SWU6 Consistency check for workflow tasks Utilities -> Consistency check -> Task -> Workflow task
    SWU7 Consistency check for workflow templates Utilities -> Consistency check -> Task -> Workflow template
    SWU8 Switch technical trace on/off Utilities -> Technical trace -> On/off
    SWU9 Display technical trace Utilities -> Technical trace -> Display
    SWUD Diagnostic tools Utilities -> Diagnosis
    SWUE Trigger event Utilities -> Events -> Generate event
    SWUF Runtime system administration Administration -> Runtime system
    SWUG Workflow start transactions Definition tools -> Workflow start transactions
    SWUI Start workflows From the R/3 initial screen, choose Office -> Start Workflow
    SWUS Start tasks Runtime tools -> Start workflow
    SWUY Wizard for message linkage to workflow Definition tools -> Wizards -> Create "Call workflow from message"
    SWX1 Create notification of absence
    SWX2 Change notification of absence
    SWX3 Display notification of absence
    SWX4 Approve notification of absence
    SWXF Form applications: Access point Environment -> Demo examples -> Fill out form
    Reports
    RSWWWIDE – Delete work items
    RHSOBJCH to fix PD Control Tables
    Tables
    SWW_OUTBOX - Lists Workflows in outbox together with status
    SWW_CONT - Container Contents for Work Item Data Container
    SWW_CONTOB- Container Cont. for Work Item Data Container (Only Objects)
    SWWLOGHIST- History of a work item
    SWWORGTASK- Assignment of WIs to Org.Units and Tasks
    SWWUSERWI - Current Work Items Assigned to a User
    SWWWIHEAD - Header Table for all Work Item Types
    <REMOVED BY MODERATOR>
    Regards,
    Amber S
    Edited by: Alvaro Tejada Galindo on Jun 6, 2008 1:51 PM

  • Start workflow

    Hi,
    My friend asked me to post this question in his name here.
    He wants to create a simple workflow in PM. After user creation of the equipment in IE01 workflow need to be started and give the task for asset number creation to the next user.
    Do you have any manuals like "workflow for dummies" )?
    BR
    Saso
    P

    Hi
    Workflow automates the steps and activities in a business process according to predefined procedures and rules.
    Workflow presents information and documents to the appropriate knowledge worker or agent (another entity such as a program) to make a decision or perform an activity.
    Workflow tracks each and every step in the process flow and maintains an ongoing status.
    Workflow also collects and reports all of the metrics associated with the execution and completion of the process.
    Check the below links u will get lot of info..
    http://www.sap-press.com/product.cfm?account=&product=H950
    Workflow
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    For examples on WorkFlow...check the below link..
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    Go through the following links on FORK :
    http://help.sap.com/saphelp_nw04/helpdata/en/24/e2283f2bbad036e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/8d/25f1e7454311d189430000e829fbbd/frameset.htm
    http://help.sap.com/saphelp_46c/helpdata/en/c5/e4a930453d11d189430000e829fbbd/content.htm
    http://www.insightcp.com/res_23.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    For more reference on workflow: http://****************/Tutorials/Workflow/Workflow.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/04/9277a346f311d189470000e829fbbd/frameset.htm
    Check these links.
    http://www.sapgenie.com/workflow/index.htm
    /people/ginger.gatling/blog/2005/12/01/link-workflow-business-objects-to-your-collaboration-tasks
    http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
    http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
    http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm
    http://www.sap-press.com/product.cfm?account=&product=H950
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    Workflow
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    For examples on WorkFlow...check the below link..
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    For examples on WorkFlow...check the below link..
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    Workflow tutorials with step-by-step and with screenshots are available at http://www.****************/Tutorials/Workflow/Workflow.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/42/c14a9b55103116e10000000a1553f7/frameset.htm
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/e4a930453d11d189430000e829fbbd/frameset.htm
    http://www.sapgenie.com/workflow/
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2857887
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2855919
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2735228
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    Debug a workflow.
    This has a step by step procedure :
    http://fuller.mit.edu/workflow/debugging.pdf
    www.erpgenie.com/sap/workflow/debugging.htm
    http://www.erpgenie.com/workflow/debugging.htm?2b5de440
    Workflow tutorials with step-by-step and with screenshots are available at
    http://www.****************/Tutorials/Workflow/Workflow.htm
    http://www.sapgenie.com/workflow/
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2857887
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2855919
    https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2735228
    http://www.sapbrain.com/TUTORIALS/TECHNICAL/WORKFLOW_tutorial.html
    Regarding Work Flow   
    work flow scenarios.
    1. applying for a leave.
    2. approval process.
    3. material creation process.
    4. mainly work flow is for notification purpose.
    chk this links
    http://help.sap.com/saphelp_erp2005/helpdata/en/fb/135962457311d189440000e829fbbd/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/c5/e4a930453d11d189430000e829fbbd/frameset.htm
    Workflow
    http://www.sap-img.com/workflow/sap-workflow.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
    For examples on WorkFlow...check the below link..
    http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.workflowing.com/id18.htm
    http://www.e-workflow.org/
    http://web.mit.edu/sapr3/dev/newdevstand.html
    http://www.erpgenie.com/workflow/index.htm
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    http://www.insightcp.com/res_23.htm
    A good tutorial
    http://www.thespot4sap.com/articles/Invoice_Verification_Automation_Using_SAP_Workflow.asp
    http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
    /people/alan.rickayzen/blog
    /people/jocelyn.dart/blog/2006/06/19/why-use-abap-oo-with-workflow
    a good book
    http://www.sap-press.com/product.cfm?account=&product=H950
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
    http://www.sap-press.com/downloads/h950_preview.pdf
    Check the following PDF
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
    also seach the workflow forum: SAP Business Workflow
    Transactions
    AWUV Wizard for event creation Definition tools -> Event creation -> Set up with wizard
    MCA1 Workflow Information System Reporting -> Workflow Information System (WIS)
    OOAW Evaluation paths
    PFAC Maintain standard roles
    PFAC_CHG Change roles Definition tools -> Standard roles -> Change
    PFAC_DEL Delete roles Definition tools -> Standard roles -> Delete
    PFAC_DIS Display roles Definition tools -> Standard roles -> Display
    PFAC_INS Create roles Definition tools -> Standard roles -> Create
    PFOM Maintain assignment to SAP organizational objects Definition tools -> SAP org. objects -> Create assignments
    PFOS Display assignment to SAP organizational objects Definition tools -> SAP org. objects -> Display assignments
    PFSO Organizational environment of a user
    PFT Maintain customer task
    PFTC General task maintenance
    PFTC_CHG Change tasks Definition tools -> Task/Task groups -> Change
    PFTC_COP Copy tasks Definition tools -> Task/Task groups -> Copy
    PFTC_DEL Delete tasks Definition tools -> Task/Task groups -> Delete
    PFTC_DIS Display tasks Definition tools -> Task/Task groups -> Display
    PFTC_INS Create tasks Definition tools -> Task/Task groups -> Create
    PFTR Standard task for transaction
    PFTS Standard task
    PFWF Maintain workflow task (customer)
    PFWS Maintain workflow template
    PPOC Create organizational plan Definition tools -> Organizational plan -> Create
    PPOM Maintain organizational plan Definition tools -> Organizational plan -> Change
    PPOS Display organizational plan Definition tools -> Organizational plan -> Display
    SWDA Ongoing Settings Administration -> Settings
    SWDC Workflow editor administration data
    SWDM Business Workflow Explorer Definition tools -> Business Workflow Explorer
    SWE2 Display and maintain event type linkage Utilities -> Events -> Type linkages
    SWE3 Display instance linkages Utilities -> Events -> Instance linkages
    SWE4 Switch event log on/off Utilities -> Events -> Event/log -> On/Off
    SWEC Link change documents to events Definition tools -> Event creation -> Change documents -> Linkage
    SWED Assignment of change document objects to object types Definition tools -> Event creation -> Change documents -> Define workflow properties
    SWEL Display event log Utilities -> Events -> Event log -> Display
    SWF3 Workflow Wizard Explorer Definition tools -> Wizards -> Workflow Wizard Explorer
    SWF4 Workflow Wizard Repository Definition tools -> Wizards -> Workflow Wizard Repository
    SWI1 Selection report for workflows Utilities -> Work item selection
    SWI2 Work item analysis Reporting -> Work item analysis
    SWI3 Workflow outbox Runtime tools -> Workflow outbox
    SWI4 Task analysis Reporting -> Task analysis
    SWI5 Workload analysis Reporting -> Workload analysis
    SWI6 Object links Runtime tools -> Object links
    SWI7 Workflow resubmission folder From Integrated Inbox or Workflow Outbox
    SWI8 Error overview Part of administration of workflow runtime system (transaction SWUF)
    SWL1 Settings for dynamic columns Customizing, part of ongoing settings
    SWLC Check tasks for agents Utilities -> Consistency check -> Organizational assignment
    SWLD Workbench for Workflow 4.0
    SWLP Copy plan version
    SWLV Maintain work item views Customizing, part of ongoing settingS
    SWLW Workbench for Workflow 3.0
    SW01 Business Object Builder Definition tools -> Business Object Builder
    SW06 Customizing object types From Business Object Builder, choose Settings -> Delegate -> System-wide
    SWU0 Event simulation Utilities -> Events -> Simulate event
    SWU2 RFC monitor Utilities -> Workflow RFC monitor
    SWU3 Customizing consistency check Utilities -> Customizing
    SWU4 Consistency check for standard tasks Utilities -> Consistency check -> Task -> Standard task
    SWU5 Consistency check for customer tasks Utilities -> Consistency check -> Task -> Customer task
    SWU6 Consistency check for workflow tasks Utilities -> Consistency check -> Task -> Workflow task
    SWU7 Consistency check for workflow templates Utilities -> Consistency check -> Task -> Workflow template
    SWU8 Switch technical trace on/off Utilities -> Technical trace -> On/off
    SWU9 Display technical trace Utilities -> Technical trace -> Display
    SWUD Diagnostic tools Utilities -> Diagnosis
    SWUE Trigger event Utilities -> Events -> Generate event
    SWUF Runtime system administration Administration -> Runtime system
    SWUG Workflow start transactions Definition tools -> Workflow start transactions
    SWUI Start workflows From the R/3 initial screen, choose Office -> Start Workflow
    SWUS Start tasks Runtime tools -> Start workflow
    SWUY Wizard for message linkage to workflow Definition tools -> Wizards -> Create "Call workflow from message"
    SWX1 Create notification of absence
    SWX2 Change notification of absence
    SWX3 Display notification of absence
    SWX4 Approve notification of absence
    SWXF Form applications: Access point Environment -> Demo examples -> Fill out form
    Reports
    RSWWWIDE – Delete work items
    RHSOBJCH to fix PD Control Tables
    Tables
    SWW_OUTBOX - Lists Workflows in outbox together with status
    SWW_CONT - Container Contents for Work Item Data Container
    SWW_CONTOB- Container Cont. for Work Item Data Container (Only Objects)
    SWWLOGHIST- History of a work item
    SWWORGTASK- Assignment of WIs to Org.Units and Tasks
    SWWUSERWI - Current Work Items Assigned to a User
    SWWWIHEAD - Header Table for all Work Item Types
    Regards
    Anji

  • Audit Expense Report Error in R12.1.3

    Hi,
    We encountered a workflow error after audit expense report. We are on R12.1.3 version.
    Issue:
    We set up a Audit Rule Sets and assign it to OU, and create an expense report. Manager can approve it and Auditor can approve it, also we can see confirmation message " The audit for this expense report is complete. The approved parts of this expense report are ready for Payables invoice import and payment." But can not create expense report invoice in AP.
    We then check the expense report workflow status, it stuck in "AP Approval Process".
    Another testing:
    We end date the Audit Rule Set OU assignment, and run the same testing, this time, we can create expense report invoice successfully.
    Please help!
    Winston

    Thanks, this note asks to have AP department to audit the expense report from Internet Expenses Auditor responsibility. We already have done this. Acutally, the issue happens after we audit the expense report.

  • Hi guys please provide me the concepts on workflow

    hi guys,
    please provide me the concepts on workflow.
    i have no idea on workflow,
    if you have any helpfull documentation and also some scenarios where u have faced and solved those,also some real time examples.
    please help me, and also i will give points if it is helpfull.
    thanks.
    prasadnn.

    Hi Prasad
    Please find some questions related to WorkFlow
    1. Is there a good book about this subject?
    Yes, "Practical Workflow for SAP" by Rickayzen, Dart, Brennecke and Schneider. Available from SAP press at the end of July. A german translation of this workflow book is also available directly from Galileo-Press, the publisher.
    2. How do I convince my company to use workflow?
    Feedback from user groups emphasizes that although the competitive advantage gained by using workflow eclipses the financial savings, it is the financial savings that are the deciding factor when obtaining support from senior management. Projects getting the blessing at the CEO level are much easier to manage, and far more likely to reach their goal within the project time frame. So plan well, and don't neglect the business case.
    Because the following questions deal with the financial case in more detail, this section will finish by listing the competitive advantages.
    The quality of the process is assured by pushing the relevant information together with links to related transactions directly to the user. Managers don't have the time to search for information so give them what they need to reach the correct decision.
    Cycle time is reduced by pushing the process directly to the users. The users receive notification of a task immediately and can even be prioritized by the system.
    The tasks are performed consistently and diligently by the users. The workflow system pushes all the necessary information needed to perform a task, including a clear description of what has to be done, how to do it and the impact this task has on the business process for your company. At any time, the user can check the list of tasks pending and determine at a glance which are the important tasks, and which tasks can be completed the next day without any negative impact.
    The process instance is transparent. Any user can check at any time how far the process has progressed and which stage the process has reached. For example the call center can immediately see the status of a purchase order, an employee requisitioning a purchase would see at a glance if a colleague has been sitting on it for too long, the ad hoc notes made when approving an engineering change request are visible long after the request has gone into production.
    The process is flexible, allowing it to be changed on the fly without retraining everyone involved. The description accompanying the change takes care of on-the-fly process improvements.
    Deadline handing ensures that users perform the tasks within the time planned. Escalation measures ensure that the failure to meet a deadline can be corrected by other means.
    Intelligent reporting highlights the weaknesses of a process. Often there is a simple cure to such weaknesses such as reeducating the users involved in the bottleneck or providing additional information (automatically). The difficulty of a non-automated process is identifying such bottlenecks.
    The process definition is transparent. You can see at a glance how the process works and who will be selected to perform the different tasks. Think of the workflow as the process book. If you can spot the pattern and define the process without headaches, you can create a workflow definition effortlessly. However, don't forget that if a company has business processes that are erratic and lack a consistent pattern, the company is very likely to be losing a lot of money in terms of lost contracts, labor intensive administration and low customer confidence. It is my personal opinion that automating exactly this type of processes will yield the best returns, but only if you limit yourself to automating the basic skeleton of the process first. Don't get bogged down in the detailed exception handling. That can be done in the next phase once you've checked the process statistics and determined which exceptions are worth tackling.
    As with most software the reasons for automating business processes are primarily to increase the competitive edge of your company and to cut costs. Although the increase in competitively gained by radically reducing process times is by far the most insignificant gain from workflow, you should not ignore the cost savings. The cost saving calculations are needed by upper management in order to approve workflow projects. This upper management signature will be very useful in different phases of the project and cannot be underestimated.
    3. How do I calculate the cost saved by workflow?
    Calculate the cost of the manual process in terms of man hours. Don't neglect the time spent gathering information. Ask the following questions:
    Is the user forced to log into different systems, or scan through printed documentation....?
    Does a skilled user spend time on parts of a task, where less skilled (less expensive) user could do the groundwork? I.e. Can a single task be split into skilled and unskilled tasks to free the skilled worker for work where his/her skills are really needed?
    Is time spent researching the progress of a process (usually done by someone not involved in the process directly)?
    Is time spent determining who to give the task to next?
    Probably the most significant cost will the be the cost of failure?
    How often does the process fail?
    What is the real cost of failure? Loss of a contract? Loss of a customer? Law suit?
    If the failure can be rectified, how labor intensive is it?
    4. What are typical costs saved by workflow?
    A manually processed accounts payable invoice will cost about 25 USD. After workflow enabling about 15 USD (one example based on customer feedback from a user group meeting).
    5. What are typical reductions in processing time caused by workflow?
    A traditional paper based approval process involving three people will typically take seven days to complete. The automated process will take one day (results based on customer feedback).
    6. What do customers say are the strengths of SAP WebFlow?
    WebFlow is the internet functionality of SAP Business Workflow. Based on customer feedback from the various regional users groups, the main strengths of SAP Business Workflow are:
    Robust production workflow system, (upgrade continuity with the rest of the SAP system, versioning, scalability, no gluing....)
    Standard workflow templates delivered by SAP can be used out-of-the-box or tweaked to deliver the optimum business process for your company. Workflows can be up and running including training in under a day (thanks to the knowledgeware delivered as part of the template packet).
    Seamlessly integrated into the SAP environment, be it R/3, Business to Business Procurement, CRM, APO, mySAP.com.... Examples of integration are:
    Business Reporting (WIS),
    Context sensitive availability at any time through the system menu (available anytime, anywhere)
    More and more standard SAP functionality is being provided by using SAP Business Workflow so your homegrown workflows fit the landscape exactly,
    More and more workflow functionality is available directly within the SAP transaction or Web MiniApp.
    WebFlow is becoming more and more important because companies are no longer being judged by their own performance but by the combined performance of the company AND its partners. In other words it is not enough that the business processes within your company run smoothly and faster than your competitors. You have to ensure that the processes between you and your partners are also as fast, efficient and flexible as possible. WebFlow delivers this.
    7. How are users notified about their work pending?
    The users are informed by a work item which you may think of as being very like an e-mail. The difference is the work item contains intelligence and by executing the work item you will be taken to the form or SAP transaction that makes up the step in the workflow. This form or transaction could be a decision, a request for information or a request for confirmation that a particular task has been performed.
    The work item is usually accompanied by a description of what has to be done, where to refer to when assistance is needed (help desk, intranet...) and a summary of information about the business object or process which enables the operator to attack the task immediately.
    This work item can be received and executed in MS OutlookÒ, Lotus NotesÒ, mySAP Workflow MiniApp or the SAP integrated inbox. If this is not enough, the workflow system can transmit e-mail notifications directly to any mail system, informing the user of the need to log in to the SAP system to execute the task. The e-mail notification is done on a subscription basis so that users can de-subscribe from this service if they already check their work item inbox regularly.
    8. What workflow reporting is available and is it useful?
    Standard workflow reports exist which allow the administrator to check statistics such as the frequency and average duration of the workflow processes. However the real strength of the workflow reporting is that it allows reports to be configured which analyze the process statistics in combination with the data involved within the workflow process and the organizational units associated with the process. For example you can determine the average time invested in a failed contract renewal request, the time taken to create material masters in different plants or the frequency of rejected purchase requisitions on a department to department basis. Often, big reducations in cost or cycle time can be obtained without touching the workflow definitions. Reeducating a particular group of users or incorporating supplementary information in a work item description can often cause dramatic improvements on the cycle times of particularly critical subsets of the process. It is not unusual that this may have a big impact on specific products, plants or organizational units. This will show up in the WebFlow reporting in LIS or the Business Warehouse but it might not show up in traditional statistical workflow reporting. Even though the average time does not change significantly, the impact on costs and profit can be dramatic.
    9. How do I choose who to distribute the tasks to?
    A work item is assigned to one or more users. Whoever reserves or executes the task first wins and the work item vanishes from the other users' inboxes. This eliminates the need to assign the user to one single user. I.e. No need for complicated algorithms to determine which single user will receive the work item and no need to worry about what will happen when one user is ill for the week (also taken care of by sophisticated substitution mechanisms which can be linked to the SAP organizational model).
    Tasks can be assigned to an organizational unit but the strength of the workflow system is to enable business rules which select users according to the data being processed. For example, you might have one group of users associated with one quality notification type. The workflow can be configured to query the QM module directly to determine the users. You can define fallbacks using the default role associated with a task and allow agents to be specified on the fly by a supervisor.
    Tasks can be assigned to office distribution lists which is useful when you want your users to subscribe or unsubscribe to a particular task. A typical use of this would be where you have a work rote or want to reduce user maintenance to an absolute minimum. The users subscribe or unsubscribe by joining or leaving an office distribution list (one mouse click).
    10. What happens when a deadline is missed?
    This depends on your workflow definition. In the simplest case an e-mail is sent to another user by the system (typically your supervisor so watch out!). However in more sophisticated scenarios a missed deadline can redirect that path that the workflow takes. One customer uses deadlines to automatically make an approval if the deadline is missed (at about the eighth approval level!!!). This gives the user the chance to make rejections but does not force him/her to go into the system to approve the other 99.9% of the requests. In safety critical environments the workflow might trigger off preventative action when a deadline is missed or might put other processes on hold. There is no limit as to how you can use this functionality.
    11. What deadlines can be monitored?
    Many different types of deadlines can monitored. At the single workflow step level you can define deadlines which trigger when the work item has not completed within a certain time and other deadlines when no one starts working on the work item within a given time. You can specify the task deadline statically (e.g. 1 week) or dynamically (e.g. 1 week for material type A and 2 weeks for all the other materials). The offset can be related to the step (e.g. you have 1 week to complete this step) or related to the process (e.g. complete within 2 weeks of the complete process starting, irrespective of how long your colleagues have hogged the previous steps).
    Last but not least, deadlines can be set for sub-processes, which is often more important than the deadline of a single step in a workflow.
    12. How can I check the status of a workflow?
    This is one of the very cool features of SAP Business Workflow. You can usually navigate directly from the business object to check the workflow progress. For example, while viewing a purchase order you can select "workflow" from the system menu or toolbar and you will see a list of workflows related to the purchase order. Usually just one, but if you have created a few of your own and these have been triggered you will see the status of these too. And that is not all. You also see a simplified summary of all the steps that have taken place so far including who performed them, when they were executed and which ad hoc notes were attached.
    13. How are workflows triggered?
    Workflows can be triggered automatically by changes in the system or manually by an operator. Manually triggered workflows are good for processes that remedy a problem the operator has noticed or for dealing with a forms-based requests (E.g. my PC won't boot). Automatically triggered workflows are useful because the operator does not even have to be aware of the workflow's existence to trigger it. In addition to triggers embedded in transactions there are also generic triggering mechanisms such as a change in the status of a business object or a change in the HR data. Irrespective of how the workflow is triggered, it is linked to the business object as described in the previous answer and can be tracked easily. Because WebFlow is part of the basis system, this triggering is reliable and easy to implement.
    Workflows may be triggered by events but this is not essential. The event-handling makes it easy to trigger workflows from transactions and system changes without you having to make modifications. If you are creating your own report or transaction which triggers a workflow, avoid events and trigger the workflow directly with the WAPI function call. This is particularly important when triggering a workflow from outside the SAP system. This method reduces flexibility (the workflow ID is hard-coded) but increases performance if this is an issue (we're talking about 50 000 work items a day here!).
    Any exception handling workflows that are intended to be triggered manually can be triggered from the system menu when viewing the relevant transaction. The SAP system has the intelligence to suggest workflows that can be triggered manually based on the authorization of the operator and the context that the operator is working in. No additional customizing is needed here.
    14. What open interfaces are supported?
    The most significant interface supported is the Wf-XML standard from the Workflow Management Coalition. This is an independent organization of which SAP is a funding member, along with most other major workflow vendors. The Wf-XML interface is based on XML and allows workflows from different vendors to communicate with each other. A detailed description of the interface is available on the WfMCs web site at www.wfmc.org.
    15. What is Wf-XML used for?
    Although a company is far better off workflow enabling their system with SAP WebFlow when SAP software is used anywhere within the process, a collaborative process can take place between partners using different software platforms employing different workflow systems. To support SAP customers in this situation, WebFlow offers the open interface Wf-XML. This allows Business Processes enabled using different tools to communicate and control each other. Any workflow tool offering this interface can connect up with other tools that also offer this interface.
    Wf-XML is the only open interface for supporting interoperability of business processes, independent of what the business process being integrated.
    16. Where does Wf-XML come from?
    Wf-XML comes from the Workflow Management Coalition, an independent body of workflow vendors, customers and higher education establishments.
    17. How does the workflow call procedures from non-SAP systems?
    The Actional control broker integrates directly into SAP WebFlow enabling proxy objects to be called directly from the workflow step. When called, the proxy method will make a call to the outside system either as a background task or as a dialogue step. These proxy objects are generated in the SAP system using a converter which converts the objects interface (DCOM, CORBA...) to the SAP syntax. A syntax converter also lets developers view any object in any of the participating systems in the developer's preferred language.
    18. How can I get the workflow initiator information in my task?
    1) From your triggering event to the workflow, bind the event creator element to the workflow initiator element.
    2) Create a workflow container element based on USR01.
    3) Add a step based on USR01.FINDUSERFROMAGENTSTRUCTURE to convert your initiator to a USR01 object.
    4) Pass the USR01 object to each task you want to display the details.
    Mailing
    19. What differences are there between a work item and a notification mail?
    a) The work item cannot be used to notify several users.
    Mails can be routed to several users, just like work items. When a mail is sent, and one recipient reads and deletes the mail, all other recipients will still have access to their own copy in their own inbox. However, when a work item is processed by one of the recipients it will automatically disappear from all the other inboxes. So you can see that a work item is unsuitable for notifying several users.
    It is also worth noting that a mail can be forwarded in many different ways (fax, internet...) whereas the work item cannot.
    b) The work item holds up the workflow
    When the workflow sends a mail (usually as a background step) it continues with the process immediately after transmitting the mail. When a work item is generated, the workflow will not continue until the work item has been processed. This slows down the process. Occasionally this is what is intended (using the work item as an approval step without the ability to reject) but usually you will better off using mails for notifications.
    Note: You can send business objects as references with the mail either as a business object reference attached to the mail or as an URL (ABAP required).
    What is the difference between sending a mail to a recipient list compared to sending individual mails via a dynamic loop?
    Performance. Sending 1 mail to 20 recipients will cost considerably less performance than sending 20 individual mails. If the mail is sent as a SAP Office mail (as opposed to e-mail, fax...) disk space will also be a factor because the SAP office mail will only exist once in the database, with references being created for each of the recipients.
    The only time you need to consider individual mails with a dynamic loop is when the text of the mail varies from one recipient to another.
    20. How do I send a standard text as an e-mail from workflow?
    It is very easy sending standard text , which may include data from the workflow. You simply create a background step which sends the work item description. This may include variables which will be substituted when mail is sent.
    In early releases you have to create your own task based on the method SELFITEM SendTaskDescription. In later releases a wizard is available for creating the step and in release 4.6 there is even a step type which does this all for you automatically.
    Whichever path you take, there is very good online documentation describing exactly what has to be done.
    21. How do I send a complex text from the workflow?
    You may create mails using SAPscript. These mails can include conditions which are evaluated in order to determine which text blocks which are used in the mail. Workflow variables can be used in these conditions and workflow variables can be substituted into the body of the e-mail text.
    22. How do I send really complex mails from the workflow?
    If you this is not enough for you will probably want to write your own ABAP routines for generating the text and generating the attachments to go with the text.
    Use the function group SO01 which contains functions of the form SO_*_API1 which are ideal for creating your own sophisticated messages. There are plenty of advantages of how these are used within the SAP system.
    23. How do I send reports?
    There are wizards (Release 3.1) which will create workflows for you to send reports to a distribution list. You can specify whether the results should be transmitted or evaluated at the time the recipient wishes to view the report. It is usually better to send the evaluation because this allows the recipient to see the results instantaneously, without having to wait for the report to execute first.
    Deadlines
    24. How can I configure the workflow so that different types of messages are sent out to different people depending on how late the processing is?
    Follow these steps:
    1. Specify a deadline period for the step.
    2. Specify a name for the event. This adds new branch from the step.
    3. Add a new step to the branch which sends a mail message.
    4. Add another step to the branch which sends out the second deadline warning (see mail steps above). Use deadlines in this step to configure an earliest start so that the second message is not sent until a further time has elapsed.
    5. Repeat step 5 as often as you like.
    25. How can I configure the workflow so that when the deadline is missed the workflow step is simply skipped?
    This is tricky to explain but easy to implement once you know how.
    Follow these steps (in later releases there is a wizard which takes you through the steps):
    1. In the terminating events view of the workflow step activate the "obsolete" event and give it a name.
    2. Specify a deadline period for the step.
    3. Specify a name for the event. This adds new branch from the step.
    4. Add a new step to the deadline path. This step must be of type "process control".
    5. Select the control "Make step obsolete" and use the search help to specify the workflow step that has the deadline. Only steps with obsolete paths defined will be displayed (see step 1).
    26. How do I trigger a workflow with an e-mail?
    You can customize the system to call a BOR method when an external mail (fax, e-mail...) arrives in the system. You BOR method should either trigger the e-mail directly or trigger an event. To customize this user exit use the transaction SCOT.
    27. How can I make sure that user's access their tasks via the workflow and not via the menu or launch pad?
    The routing mechanism for work items uses roles and organizational assignments to determine who receives which work item. However the routing does not provide extra authorization checks based on the routing configuration. If you want to ensure that the tasks are executed within the workflow, and not via the standard transaction, service or MiniApp, then you will have to apply your own protection.
    The simplest way of doing this is to remove the standard transaction from the user's menu or Workplace role (but include it in the supervisor's role, just in case).
    If you want to allow the user to execute the task from the menu if and only if they have received the work item then you should replace the standard transaction with your own custom built transaction. Your own transaction simply calls the standard transaction but performs it's own authorization check first, based on the routing mechanism used in the workflow. Tip: Add a second (ored) authorization check to make sure that a supervisor can execute the transaction in an emergency.
    28. What is a workflow? What is a single-step task?
    A single-step task is based on an object type from the object business repository (BOR) (for example, a purchase order) and a method for the object (for example, change). A workflow can contain several single-step tasks and activities such as loops and forks. Through a workflow, you create a logical sequence for the single-step tasks. The tool for creating or changing these types of workflows (workflow template) is the Workflow Builder (transaction SWDD).
    29. What is a work item (important terms)?
    A work item is the runtime object of a workflow or of a single-step task.You can execute dialog work items with the inbox (transaction SBWP). Each workflow and single-step task started is assigned a unique number known as the work item ID.
    30. How is an event triggered from the application and a workflow then started?
    An event can be triggered from the application in three different ways:
    Directly:
    Within the application, the SWE_EVENT_CREATE function module or the SWE_EVENT_CREAT_IN_UPD_TASK function module, for example, generates an event in the update.
    With a change document:
    Change documents are written within the application when you change application objects in the update. You can link events that have the same key with these types of change documents via transaction SWEC.
    With status management:
    The SWE_EVENT_CREATE_STATUS function module triggers an event in the same way as the direct method when a status is changed. This event contains the object type (for example, purchase order), the object key (for example, purchase order 4711) and other information. Using transaction PFTC, you can assign the event to a specific workflow or single-step task. More settings are available in transaction SWE2.
    31. How are the responsible agents determined?
    You can assign agents to a single-step task in transaction PFTC. For example, you can do this using organizational units, work center roles or positions. Within a workflow pattern, you can assign specific agents for this workflow to a single-step task. The overlap between both numbers of 'possible agents' represents the number of agents ('selected agents') who have the work item in the inbox later.
    32. What is the difference of between an e-mail and a work item?
    E-mails and work items are two completely separate things. They just happen to be displayed in the same inbox. An e-mail is a message sent to one or several people. However, a work item is a runtime object of a single-step task or workflow. Consequently, a work item cannot be deleted from the inbox of a user. In this case in fact, you have to adjust the agent assignment or delete the work item as described in note 49545.
    33. PFAC no longer works for my role responsibility setup...
    Use tx: OOCU_RESP
    34. How do I transport workflow definitions and agent assignments?
    When transporting workflows, you have to differentiate between the workflow definition and the agent assignment.
    A workflow definition is a workbench request. When you save the workflow, a workflow version is created and a request written. Further information about the transport or about the status management is provided in note 378487 and in the notes mentioned there under related notes.
    However, where the agent assignment is concerned, this is a Customizing request. To allow transport of agent assignments, the value of the semantic abbreviation CORR for the TRSP group name must be empty in table T77S0.
    35. How do you debug a background workflow process?
    In your method write the following code:
    data exit.
    Do.
    if exit = 'X'.
    exit.
    endif.
    enddo.
    Run the workflow, causing an infinite loop on that step, and then go to SM50.
    Here you can debug the process.
    36.What is the Workflow basic Customizing?
    Before you can use the Workflow module, you must first execute the basic Customizing in transaction SWU3. All of the listed points should be green (the number range for customer tasks is no longer required). A detailed description of the activities is provided in the relevant information buttons. You can also execute some (but not all) of the points using the Automatic Customizing button. See the online documentation for an exact description of what happens there. The RFC destination must work correctly and the user (usually WF BATCH) should have the SAP_ALL profile.
    37.: What options do I have as a user to configure the inbox individually?
    You have the following options:
    You can create separate user-dependent or user-independent layouts so that you can adapt the displayed columns individually. You can access the function in the Workplace via an application function key.
    You can set filters to set certain criteria for individual columns or several columns simultaneously, according to which specific work items are then filtered.
    You can add dynamic columns in the layout that then display dynamic elements for certain tasks and users from the work item container. However, this is only possible if all tasks in the inbox belong to just one task. If they have several tasks in the inbox, filtering serves no useful purpose because all tasks are first completely read once. You can define these dynamic columns using transaction SWL1.
    38. What does the substitute rule system look like in the workflow?
    You have a choice of two different substitute rulings:
    Active substitute ruling (for example, for absence due to vacations): In this case, the items belonging to the absent person are automatically assigned to the substitutes inbox (in addition to his own work items).
    Passive substitution (for example, for absence due to illness): the substitute must explicitly assume the substitution and can only view the items of the absent person in this mode.
    For other questions, you must also refer to note 74000.
    39. How can users be automatically notified that new work items are available for processing?
    Unfortunately, the dialog box that informs users of new work items which appears in SAPoffice is not available within SAP Systems.
    However, the following two options are provided:
    In the Workflow Builder, you can designate the item as an express item via additional data. The user then receives a corresponding express dialog box.
    The RSWUWFML report (note 131795) is a more flexible option. This report sends an e-mail to an external Internet address to notify the user of new work items.
    40. Can I set deadlines for the latest processing of work items?
    this is where you can use deadline monitoring for work items. In the Workflow Builder, you can set dates for a requested/latest start/end date for each individual step. You must schedule the SWWDHEX job via transaction SWU3 for this. Schedule the job permanently in the production system otherwise it is difficult for the job to schedule individual deadline monitoring scenarios when workflow is heavy.
    41. Can I also execute work items with external programs such as Outlook?
    You can use the Web GUI for HTML instead of the Windows GUI. However, note that some functions do no work in the WEB GUI, due to technical restrictions in the browser. You must refer to note 487649 on this subject.
    SAP also provides interfaces which allow you to process work items with external programs such as Lotus Notes or Microsoft Outlook. Refer to notes 77099, 98408 and 454845 for details.
    Hi ,
    More stuff on WORKFLOW
    Transactions
    AWUV Wizard for event creation Definition tools -> Event creation -> Set up with wizard
    MCA1 Workflow Information System Reporting -> Workflow Information System (WIS)
    OOAW Evaluation paths
    PFAC Maintain standard roles
    PFAC_CHG Change roles Definition tools -> Standard roles -> Change
    PFAC_DEL Delete roles Definition tools -> Standard roles -> Delete
    PFAC_DIS Display roles Definition tools -> Standard roles -> Display
    PFAC_INS Create roles Definition tools -> Standard roles -> Create
    PFOM Maintain assignment to SAP organizational objects Definition tools -> SAP org. objects -> Create assignments
    PFOS Display assignment to SAP organizational objects Definition tools -> SAP org. objects -> Display assignments
    PFSO Organizational environment of a user
    PFT Maintain customer task
    PFTC General task maintenance
    PFTC_CHG Change tasks Definition tools -> Task/Task groups -> Change
    PFTC_COP Copy tasks Definition tools -> Task/Task groups -> Copy
    PFTC_DEL Delete tasks Definition tools -> Task/Task groups -> Delete
    PFTC_DIS Display tasks Definition tools -> Task/Task groups -> Display
    PFTC_INS Create tasks Definition tools -> Task/Task groups -> Create
    PFTR Standard task for transaction
    PFTS Standard task
    PFWF Maintain workflow task (customer)
    PFWS Maintain workflow template
    PPOC Create organizational plan Definition tools -> Organizational plan -> Create
    PPOM Maintain organizational plan Definition tools -> Organizational plan -> Change
    PPOS Display organizational plan Definition tools -> Organizational plan -> Display
    SWDA Ongoing Settings Administration -> Settings
    SWDC Workflow editor administration data
    SWDM Business Workflow Explorer Definition tools -> Business Workflow Explorer
    SWE2 Display and maintain event type linkage Utilities -> Events -> Type linkages
    SWE3 Display instance linkages Utilities -> Events -> Instance linkages
    SWE4 Switch event log on/off Utilities -> Events -> Event/log -> On/Off
    SWEC Link change documents to events Definition tools -> Event creation -> Change documents -> Linkage
    SWED Assignment of change document objects to object types Definition tools -> Event creation -> Change documents -> Define workflow properties
    SWEL Display event log Utilities -> Events -> Event log -> Display
    SWF3 Workflow Wizard Explorer Definition tools -> Wizards -> Workflow Wizard Explorer
    SWF4 Workflow Wizard Repository Definition tools -> Wizards -> Workflow Wizard Repository
    SWI1 Selection report for workflows Utilities -> Work item selection
    SWI2 Work item analysis Reporting -> Work item analysis
    SWI3 Workflow outbox Runtime tools -> Workflow outbox
    SWI4 Task analysis Reporting -> Task analysis
    SWI5 Workload analysis Reporting -> Workload analysis
    SWI6 Object links Runtime tools -> Object links
    SWI7 Workflow resubmission folder From Integrated Inbox or Workflow Outbox
    SWI8 Error overview Part of administration of workflow runtime system (transaction SWUF)
    SWL1 Settings for dynamic columns Customizing, part of ongoing settings
    SWLC Check tasks for agents Utilities -> Consistency check -> Organizational assignment
    SWLD Workbench for Workflow 4.0
    SWLP Copy plan version
    SWLV Maintain work item views Customizing, part of ongoing settingS
    SWLW Workbench for Workflow 3.0
    SW01 Business Object Builder Definition tools -> Business Object Builder
    SW06 Customizing object types From Business Object Builder, choose Settings -> Delegate -> System-wide
    SWU0 Event simulation Utilities -> Events -> Simulate event
    SWU2 RFC monitor Utilities -> Workflow RFC monitor
    SWU3 Customizing consistency check Utilities -> Customizing
    SWU4 Consistency check for standard tasks Utilities -> Consistency check -> Task -> Standard task
    SWU5 Consistency check for customer tasks Utilities -> Consistency check -> Task -> Customer task
    SWU6 Consistency check for workflow tasks Utilities -> Consistency check -> Task -> Workflow task
    SWU7 Consistency check for workflow templates Utilities -> Consistency check -> Task -> Workflow template
    SWU8 Switch technical trace on/off Utilities -> Technical trace -> On/off
    SWU9 Display technical trace Utilities -> Technical trace -> Display
    SWUD Diagnostic tools Utilities -> Diagnosis
    SWUE Trigger event Utilities -> Events -> Generate event
    SWUF Runtime system administration Administration -> Runtime system
    SWUG Workflow start transactions Definition tools -> Workflow start transactions
    SWUI Start workflows From the R/3 initial screen, choose Office -> Start Workflow
    SWUS Start tasks Runtime tools -> Start workflow
    SWUY Wizard for message linkage to workflow Definition tools -> Wizards -> Create "Call workflow from message"
    SWX1 Create notification of absence
    SWX2 Change notification of absence
    SWX3 Display notification of absence
    SWX4 Approve notification of absence
    SWXF Form applications: Access point Environment -> Demo examples -> Fill out form
    Reports
    RSWWWIDE – Delete work items
    RHSOBJCH to fix PD Control Tables
    Tables
    SWW_OUTBOX - Lists Workflows in outbox together with status
    SWW_CONT - Container Contents for Work Item Data Container
    SWW_CONTOB- Container Cont. for Work Item Data Container (Only Objects)
    SWWLOGHIST- History of a work item
    SWWORGTASK- Assignment of WIs to Org.Units and Tasks
    SWWUSERWI - Current Work Items Assigned to a User
    SWWWIHEAD - Header Table for all Work Item Types
    Reward poits if helpful.
    Regards,
    Amber S

  • Workflow all down

    Hi:
    I have cloned a instance a couple of weeks ago. Everything was working. Today a User reported workflow all down including Notification Mailers, Agent Listeners and Service Components. We have not make any changes. Please tell me the steps to start them, which one first, next...
    Thanks
    Hi: I ran Diagnostic on workflow and found 2 tests failed as below:
    *1. ==== Notification Preference Validation Test Details ===========*
    Current Execution
    Date: 2011-03-28 11:35:26.0 Time Consumed: 5089 milliseconds Status: Failed
    Version Info:
    None
    Inputs:
    Diagnostic Test Executed By= XXXXX
    Error:
    Found Roles with invalid Notification Preference and E-mail Address combination.
    Help:
    Please make sure a valid E-mail Address is assigned to a role with Notification Preference like MAILXXXX in order for the Notification Mailer to send e-mail notifications.
    Summary:
    Found 51973 Invalid Roles.
    Following are the details of first hundred Roles with valid Notification Preference but null E-mail Address.
    *2. ==== Rule Function Validation Test Report =============*
    PLSQL Rule Function Error Information
    HR_SCH_ELIG_OBJ_PKG.CREATE_SCH_ELIG_OBJ Package Spec HR_SCH_ELIG_OBJ_PKG Doesnot Exist
    HR_SCH_ELIG_OBJ_PKG.DELETE_SCH_ELIG_OBJ Package Spec HR_SCH_ELIG_OBJ_PKG Doesnot Exist
    OBSOLETE Standalone Function OBSOLETE Doesnot Exist
    Java Rule Function Error Information
    oracle.apps.cln.m4u.uccadapter.M4UAdapterWrapper Java Rule Function oracle.apps.cln.m4u.uccadapter.M4UAdapterWrapper is not found or does not implement interface SubscriptionInterface
    PLSQL Generate Function Error Information
    EVENT THAT WILL BE RAISED TO GENERATE OUTBOUND XML FILE FOR PELL. Package Spec EVENT THAT WILL BE RAISED TO GENERATE OUTBOUND XML FILE FOR PELL Doesnot Exist
    EVENT THAT WILL BE RAISED TO UPLOAD THE RESPONSE XML FILE TO THE DATABASE TABLES Standalone Function EVENT THAT WILL BE RAISED TO UPLOAD THE RESPONSE XML FILE TO THE DATABASE TABLES Doesnot Exist
    Java Generate Function Error Information
    Edited by: user9231603 on Mar 28, 2011 8:42 AM

    More errors after ora-04031. (I should copied and pasted more):
    [  :-1:ERROR:[SVC-GSM-WFWSSVC-263724 : oracle.apps.
    fnd.cp.gsc.SvcComponentMonitor.process()]:Monitoring failed this iteration -> oracle.apps.fnd.cp.gsc.ProcessorException: Could not retrieve list of Automatic
    components for this container -> oracle.apps.fnd.cp.gsc.server.GenericSvcComponentEOException: Failure to executeQuery() or read ResultSet. Query was: SELECT
    application_id, component_class_name, component_id, component_name, component_status, component_status_display_name, component_status_info, component_type,
    component_type_display_name, concurrent_queue_display_name, concurrent_queue_id, concurrent_queue_name, container_type, container_type_display_name, correlati
    on_id, created_by, customization_level, inbound_agent_display_name, inbound_agent_name, max_idle_time, object_version_number, outbound_agent_display_name, out
    bound_agent_name, standalone_container_name, startup_mode, startup_mode_display_name FROM fnd_svc_components_v WHERE startup_mode = :1 AND (component_status
    = :2 OR component_status = :3 ) AND ( (container_type = :4 AND concurrent_queue_name = :5) ) -> java.sql.SQLException: ORA-04031:
    unable to allocate 4096 bytes of shared memory ("shared pool","SELECT application_id, comp...","Typecheck heap","kgghteInit")
    ==

  • Workflow related transactions in HR-PD

    Could anyone please provide the Workflow related transactions in HR-PD? 
    Thanks in advance.
    Paul

    Hi Paul,
    Transactions
    •     AWUV    Wizard for event creation    Definition tools -> Event creation -> Set up with wizard
    •     MCA1    Workflow Information System    Reporting -> Workflow Information System (WIS)
    •     OOAW    Evaluation paths
    •     PFAC    Maintain standard roles
    •     PFAC_CHG    Change roles    Definition tools -> Standard roles -> Change
    •     PFAC_DEL    Delete roles    Definition tools -> Standard roles -> Delete
    •     PFAC_DIS    Display roles    Definition tools -> Standard roles -> Display
    •     PFAC_INS    Create roles    Definition tools -> Standard roles -> Create
    •     PFOM    Maintain assignment to SAP organizational objects    Definition tools -> SAP org. objects -> Create assignments
    •     PFOS    Display assignment to SAP organizational objects    Definition tools -> SAP org. objects -> Display assignments
    •     PFSO    Organizational environment of a user
    •     PFT    Maintain customer task
    •     PFTC    General task maintenance
    •     PFTC_CHG    Change tasks    Definition tools -> Task/Task groups -> Change
    •     PFTC_COP    Copy tasks    Definition tools -> Task/Task groups -> Copy
    •     PFTC_DEL    Delete tasks    Definition tools -> Task/Task groups -> Delete
    •     PFTC_DIS    Display tasks    Definition tools -> Task/Task groups -> Display
    •     PFTC_INS    Create tasks    Definition tools -> Task/Task groups -> Create
    •     PFTR    Standard task for transaction
    •     PFTS    Standard task
    •     PFWF    Maintain workflow task (customer)
    •     PFWS    Maintain workflow template
    •     PPOC    Create organizational plan    Definition tools -> Organizational plan -> Create
    •     PPOM    Maintain organizational plan    Definition tools -> Organizational plan -> Change
    •     PPOS    Display organizational plan    Definition tools -> Organizational plan -> Display
    •     SWDA    Ongoing Settings    Administration -> Settings
    •     SWDC    Workflow editor administration data
    •     SWDM    Business Workflow Explorer    Definition tools -> Business Workflow Explorer
    •     SWE2    Display and maintain event type linkage    Utilities -> Events -> Type linkages
    •     SWE3    Display instance linkages    Utilities -> Events -> Instance linkages
    •     SWE4    Switch event log on/off    Utilities -> Events -> Event/log -> On/Off
    •     SWEC    Link change documents to events    Definition tools -> Event creation -> Change documents -> Linkage
    •     SWED    Assignment of change document objects to object types    Definition tools -> Event creation -> Change documents -> Define workflow properties
    •     SWEL    Display event log    Utilities -> Events -> Event log -> Display
    •     SWF3    Workflow Wizard Explorer    Definition tools -> Wizards -> Workflow Wizard Explorer
    •     SWF4    Workflow Wizard Repository    Definition tools -> Wizards -> Workflow Wizard Repository
    •     SWI1    Selection report for workflows    Utilities -> Work item selection
    •     SWI2    Work item analysis    Reporting -> Work item analysis
    •     SWI3    Workflow outbox    Runtime tools -> Workflow outbox
    •     SWI4    Task analysis    Reporting -> Task analysis
    •     SWI5    Workload analysis    Reporting -> Workload analysis
    •     SWI6    Object links    Runtime tools -> Object links
    •     SWI7    Workflow resubmission folder    From Integrated Inbox or Workflow Outbox
    •     SWI8    Error overview    Part of administration of workflow runtime system (transaction SWUF)
    •     SWL1    Settings for dynamic columns    Customizing, part of ongoing settings
    •     SWLC    Check tasks for agents    Utilities -> Consistency check -> Organizational assignment
    •     SWLD    Workbench for Workflow 4.0
    •     SWLP    Copy plan version
    •     SWLV    Maintain work item views    Customizing, part of ongoing settingS
    •     SWLW    Workbench for Workflow 3.0
    •     SW01    Business Object Builder    Definition tools -> Business Object Builder
    •     SW06    Customizing object types    From Business Object Builder, choose Settings -> Delegate -> System-wide
    •     SWU0    Event simulation    Utilities -> Events -> Simulate event
    •     SWU2    RFC monitor    Utilities -> Workflow RFC monitor
    •     SWU3    Customizing consistency check    Utilities -> Customizing
    •     SWU4    Consistency check for standard tasks    Utilities -> Consistency check -> Task -> Standard task
    •     SWU5    Consistency check for customer tasks    Utilities -> Consistency check -> Task -> Customer task
    •     SWU6    Consistency check for workflow tasks    Utilities -> Consistency check -> Task -> Workflow task
    •     SWU7    Consistency check for workflow templates    Utilities -> Consistency check -> Task -> Workflow template
    •     SWU8    Switch technical trace on/off    Utilities -> Technical trace -> On/off   
    •     SWU9    Display technical trace    Utilities -> Technical trace -> Display
    •     SWUD    Diagnostic tools    Utilities -> Diagnosis
    •     SWUE    Trigger event    Utilities -> Events -> Generate event
    •     SWUF    Runtime system administration    Administration -> Runtime system
    •     SWUG    Workflow start transactions    Definition tools -> Workflow start transactions
    •     SWUI    Start workflows    From the R/3 initial screen, choose Office -> Start Workflow
    •     SWUS    Start tasks    Runtime tools -> Start workflow
    •     SWUY    Wizard for message linkage to workflow    Definition tools -> Wizards -> Create "Call workflow from message"
    •     SWX1    Create notification of absence
    •     SWX2    Change notification of absence
    •     SWX3    Display notification of absence
    •     SWX4    Approve notification of absence
    •     SWXF    Form applications:    Access point Environment -> Demo examples -> Fill out form
    •     Revise
    Reports
    •     RSWWWIDE – Delete work items
    •     RHSOBJCH to fix PD Control Tables
    Tables
    •     SWW_OUTBOX     -Lists Workflows in outbox together with status
    •     SWW_CONT     -Container Contents for Work Item Data Container
    •     SWW_CONTOB     -Container Cont. for Work Item Data Container (Only Objects)
    •     SWWLOGHIST     -History of a work item
    •     SWWORGTASK     -Assignment of WIs to Org.Units and Tasks
    •     SWWUSERWI     -Current Work Items Assigned to a User
    •     SWWWIHEAD     -Header Table for all Work Item Types
    Regards
    Vijay

  • Workflow issue plz guide

    gugys i have a training on workflow of two hours
    so i wanna do som initial preperation to ask som questions
    plz tel me
    what are the imp topics of workflow that should be covered in the session
    if u have any step by step guide
    plz send me at [email protected]
    or all kind of documents
    plz give me the links if u have
    plz help me its urgent
    thanks in advance

    Hi Anit,
    Please find some questions related to WorkFlow
    1. Is there a good book about this subject?
    Yes, "Practical Workflow for SAP" by Rickayzen, Dart, Brennecke and Schneider. Available from SAP press at the end of July. A german translation of this workflow book is also available directly from Galileo-Press, the publisher.
    2. How do I convince my company to use workflow?
    Feedback from user groups emphasizes that although the competitive advantage gained by using workflow eclipses the financial savings, it is the financial savings that are the deciding factor when obtaining support from senior management. Projects getting the blessing at the CEO level are much easier to manage, and far more likely to reach their goal within the project time frame. So plan well, and don't neglect the business case.
    Because the following questions deal with the financial case in more detail, this section will finish by listing the competitive advantages.
    The quality of the process is assured by pushing the relevant information together with links to related transactions directly to the user. Managers don't have the time to search for information so give them what they need to reach the correct decision.
    Cycle time is reduced by pushing the process directly to the users. The users receive notification of a task immediately and can even be prioritized by the system.
    The tasks are performed consistently and diligently by the users. The workflow system pushes all the necessary information needed to perform a task, including a clear description of what has to be done, how to do it and the impact this task has on the business process for your company. At any time, the user can check the list of tasks pending and determine at a glance which are the important tasks, and which tasks can be completed the next day without any negative impact.
    The process instance is transparent. Any user can check at any time how far the process has progressed and which stage the process has reached. For example the call center can immediately see the status of a purchase order, an employee requisitioning a purchase would see at a glance if a colleague has been sitting on it for too long, the ad hoc notes made when approving an engineering change request are visible long after the request has gone into production.
    The process is flexible, allowing it to be changed on the fly without retraining everyone involved. The description accompanying the change takes care of on-the-fly process improvements.
    Deadline handing ensures that users perform the tasks within the time planned. Escalation measures ensure that the failure to meet a deadline can be corrected by other means.
    Intelligent reporting highlights the weaknesses of a process. Often there is a simple cure to such weaknesses such as reeducating the users involved in the bottleneck or providing additional information (automatically). The difficulty of a non-automated process is identifying such bottlenecks.
    The process definition is transparent. You can see at a glance how the process works and who will be selected to perform the different tasks. Think of the workflow as the process book. If you can spot the pattern and define the process without headaches, you can create a workflow definition effortlessly. However, don't forget that if a company has business processes that are erratic and lack a consistent pattern, the company is very likely to be losing a lot of money in terms of lost contracts, labor intensive administration and low customer confidence. It is my personal opinion that automating exactly this type of processes will yield the best returns, but only if you limit yourself to automating the basic skeleton of the process first. Don't get bogged down in the detailed exception handling. That can be done in the next phase once you've checked the process statistics and determined which exceptions are worth tackling.
    As with most software the reasons for automating business processes are primarily to increase the competitive edge of your company and to cut costs. Although the increase in competitively gained by radically reducing process times is by far the most insignificant gain from workflow, you should not ignore the cost savings. The cost saving calculations are needed by upper management in order to approve workflow projects. This upper management signature will be very useful in different phases of the project and cannot be underestimated.
    3. How do I calculate the cost saved by workflow?
    Calculate the cost of the manual process in terms of man hours. Don't neglect the time spent gathering information. Ask the following questions:
    Is the user forced to log into different systems, or scan through printed documentation....?
    Does a skilled user spend time on parts of a task, where less skilled (less expensive) user could do the groundwork? I.e. Can a single task be split into skilled and unskilled tasks to free the skilled worker for work where his/her skills are really needed?
    Is time spent researching the progress of a process (usually done by someone not involved in the process directly)?
    Is time spent determining who to give the task to next?
    Probably the most significant cost will the be the cost of failure?
    How often does the process fail?
    What is the real cost of failure? Loss of a contract? Loss of a customer? Law suit?
    If the failure can be rectified, how labor intensive is it?
    4. What are typical costs saved by workflow?
    A manually processed accounts payable invoice will cost about 25 USD. After workflow enabling about 15 USD (one example based on customer feedback from a user group meeting).
    5. What are typical reductions in processing time caused by workflow?
    A traditional paper based approval process involving three people will typically take seven days to complete. The automated process will take one day (results based on customer feedback).
    6. What do customers say are the strengths of SAP WebFlow?
    WebFlow is the internet functionality of SAP Business Workflow. Based on customer feedback from the various regional users groups, the main strengths of SAP Business Workflow are:
    Robust production workflow system, (upgrade continuity with the rest of the SAP system, versioning, scalability, no gluing....)
    Standard workflow templates delivered by SAP can be used out-of-the-box or tweaked to deliver the optimum business process for your company. Workflows can be up and running including training in under a day (thanks to the knowledgeware delivered as part of the template packet).
    Seamlessly integrated into the SAP environment, be it R/3, Business to Business Procurement, CRM, APO, mySAP.com.... Examples of integration are:
    Business Reporting (WIS),
    Context sensitive availability at any time through the system menu (available anytime, anywhere)
    More and more standard SAP functionality is being provided by using SAP Business Workflow so your homegrown workflows fit the landscape exactly,
    More and more workflow functionality is available directly within the SAP transaction or Web MiniApp.
    WebFlow is becoming more and more important because companies are no longer being judged by their own performance but by the combined performance of the company AND its partners. In other words it is not enough that the business processes within your company run smoothly and faster than your competitors. You have to ensure that the processes between you and your partners are also as fast, efficient and flexible as possible. WebFlow delivers this.
    7. How are users notified about their work pending?
    The users are informed by a work item which you may think of as being very like an e-mail. The difference is the work item contains intelligence and by executing the work item you will be taken to the form or SAP transaction that makes up the step in the workflow. This form or transaction could be a decision, a request for information or a request for confirmation that a particular task has been performed.
    The work item is usually accompanied by a description of what has to be done, where to refer to when assistance is needed (help desk, intranet...) and a summary of information about the business object or process which enables the operator to attack the task immediately.
    This work item can be received and executed in MS OutlookÒ, Lotus NotesÒ, mySAP Workflow MiniApp or the SAP integrated inbox. If this is not enough, the workflow system can transmit e-mail notifications directly to any mail system, informing the user of the need to log in to the SAP system to execute the task. The e-mail notification is done on a subscription basis so that users can de-subscribe from this service if they already check their work item inbox regularly.
    8. What workflow reporting is available and is it useful?
    Standard workflow reports exist which allow the administrator to check statistics such as the frequency and average duration of the workflow processes. However the real strength of the workflow reporting is that it allows reports to be configured which analyze the process statistics in combination with the data involved within the workflow process and the organizational units associated with the process. For example you can determine the average time invested in a failed contract renewal request, the time taken to create material masters in different plants or the frequency of rejected purchase requisitions on a department to department basis. Often, big reducations in cost or cycle time can be obtained without touching the workflow definitions. Reeducating a particular group of users or incorporating supplementary information in a work item description can often cause dramatic improvements on the cycle times of particularly critical subsets of the process. It is not unusual that this may have a big impact on specific products, plants or organizational units. This will show up in the WebFlow reporting in LIS or the Business Warehouse but it might not show up in traditional statistical workflow reporting. Even though the average time does not change significantly, the impact on costs and profit can be dramatic.
    9. How do I choose who to distribute the tasks to?
    A work item is assigned to one or more users. Whoever reserves or executes the task first wins and the work item vanishes from the other users' inboxes. This eliminates the need to assign the user to one single user. I.e. No need for complicated algorithms to determine which single user will receive the work item and no need to worry about what will happen when one user is ill for the week (also taken care of by sophisticated substitution mechanisms which can be linked to the SAP organizational model).
    Tasks can be assigned to an organizational unit but the strength of the workflow system is to enable business rules which select users according to the data being processed. For example, you might have one group of users associated with one quality notification type. The workflow can be configured to query the QM module directly to determine the users. You can define fallbacks using the default role associated with a task and allow agents to be specified on the fly by a supervisor.
    Tasks can be assigned to office distribution lists which is useful when you want your users to subscribe or unsubscribe to a particular task. A typical use of this would be where you have a work rote or want to reduce user maintenance to an absolute minimum. The users subscribe or unsubscribe by joining or leaving an office distribution list (one mouse click).
    10. What happens when a deadline is missed?
    This depends on your workflow definition. In the simplest case an e-mail is sent to another user by the system (typically your supervisor so watch out!). However in more sophisticated scenarios a missed deadline can redirect that path that the workflow takes. One customer uses deadlines to automatically make an approval if the deadline is missed (at about the eighth approval level!!!). This gives the user the chance to make rejections but does not force him/her to go into the system to approve the other 99.9% of the requests. In safety critical environments the workflow might trigger off preventative action when a deadline is missed or might put other processes on hold. There is no limit as to how you can use this functionality.
    11. What deadlines can be monitored?
    Many different types of deadlines can monitored. At the single workflow step level you can define deadlines which trigger when the work item has not completed within a certain time and other deadlines when no one starts working on the work item within a given time. You can specify the task deadline statically (e.g. 1 week) or dynamically (e.g. 1 week for material type A and 2 weeks for all the other materials). The offset can be related to the step (e.g. you have 1 week to complete this step) or related to the process (e.g. complete within 2 weeks of the complete process starting, irrespective of how long your colleagues have hogged the previous steps).
    Last but not least, deadlines can be set for sub-processes, which is often more important than the deadline of a single step in a workflow.
    12. How can I check the status of a workflow?
    This is one of the very cool features of SAP Business Workflow. You can usually navigate directly from the business object to check the workflow progress. For example, while viewing a purchase order you can select "workflow" from the system menu or toolbar and you will see a list of workflows related to the purchase order. Usually just one, but if you have created a few of your own and these have been triggered you will see the status of these too. And that is not all. You also see a simplified summary of all the steps that have taken place so far including who performed them, when they were executed and which ad hoc notes were attached.
    13. How are workflows triggered?
    Workflows can be triggered automatically by changes in the system or manually by an operator. Manually triggered workflows are good for processes that remedy a problem the operator has noticed or for dealing with a forms-based requests (E.g. my PC won't boot). Automatically triggered workflows are useful because the operator does not even have to be aware of the workflow's existence to trigger it. In addition to triggers embedded in transactions there are also generic triggering mechanisms such as a change in the status of a business object or a change in the HR data. Irrespective of how the workflow is triggered, it is linked to the business object as described in the previous answer and can be tracked easily. Because WebFlow is part of the basis system, this triggering is reliable and easy to implement.
    Workflows may be triggered by events but this is not essential. The event-handling makes it easy to trigger workflows from transactions and system changes without you having to make modifications. If you are creating your own report or transaction which triggers a workflow, avoid events and trigger the workflow directly with the WAPI function call. This is particularly important when triggering a workflow from outside the SAP system. This method reduces flexibility (the workflow ID is hard-coded) but increases performance if this is an issue (we're talking about 50 000 work items a day here!).
    Any exception handling workflows that are intended to be triggered manually can be triggered from the system menu when viewing the relevant transaction. The SAP system has the intelligence to suggest workflows that can be triggered manually based on the authorization of the operator and the context that the operator is working in. No additional customizing is needed here.
    14. What open interfaces are supported?
    The most significant interface supported is the Wf-XML standard from the Workflow Management Coalition. This is an independent organization of which SAP is a funding member, along with most other major workflow vendors. The Wf-XML interface is based on XML and allows workflows from different vendors to communicate with each other. A detailed description of the interface is available on the WfMCs web site at www.wfmc.org.
    15. What is Wf-XML used for?
    Although a company is far better off workflow enabling their system with SAP WebFlow when SAP software is used anywhere within the process, a collaborative process can take place between partners using different software platforms employing different workflow systems. To support SAP customers in this situation, WebFlow offers the open interface Wf-XML. This allows Business Processes enabled using different tools to communicate and control each other. Any workflow tool offering this interface can connect up with other tools that also offer this interface.
    Wf-XML is the only open interface for supporting interoperability of business processes, independent of what the business process being integrated.
    16. Where does Wf-XML come from?
    Wf-XML comes from the Workflow Management Coalition, an independent body of workflow vendors, customers and higher education establishments.
    17. How does the workflow call procedures from non-SAP systems?
    The Actional control broker integrates directly into SAP WebFlow enabling proxy objects to be called directly from the workflow step. When called, the proxy method will make a call to the outside system either as a background task or as a dialogue step. These proxy objects are generated in the SAP system using a converter which converts the objects interface (DCOM, CORBA...) to the SAP syntax. A syntax converter also lets developers view any object in any of the participating systems in the developer's preferred language.
    18. How can I get the workflow initiator information in my task?
    1) From your triggering event to the workflow, bind the event creator element to the workflow initiator element.
    2) Create a workflow container element based on USR01.
    3) Add a step based on USR01.FINDUSERFROMAGENTSTRUCTURE to convert your initiator to a USR01 object.
    4) Pass the USR01 object to each task you want to display the details.
    Mailing
    19. What differences are there between a work item and a notification mail?
    a) The work item cannot be used to notify several users.
    Mails can be routed to several users, just like work items. When a mail is sent, and one recipient reads and deletes the mail, all other recipients will still have access to their own copy in their own inbox. However, when a work item is processed by one of the recipients it will automatically disappear from all the other inboxes. So you can see that a work item is unsuitable for notifying several users.
    It is also worth noting that a mail can be forwarded in many different ways (fax, internet...) whereas the work item cannot.
    b) The work item holds up the workflow
    When the workflow sends a mail (usually as a background step) it continues with the process immediately after transmitting the mail. When a work item is generated, the workflow will not continue until the work item has been processed. This slows down the process. Occasionally this is what is intended (using the work item as an approval step without the ability to reject) but usually you will better off using mails for notifications.
    Note: You can send business objects as references with the mail either as a business object reference attached to the mail or as an URL (ABAP required).
    What is the difference between sending a mail to a recipient list compared to sending individual mails via a dynamic loop?
    Performance. Sending 1 mail to 20 recipients will cost considerably less performance than sending 20 individual mails. If the mail is sent as a SAP Office mail (as opposed to e-mail, fax...) disk space will also be a factor because the SAP office mail will only exist once in the database, with references being created for each of the recipients.
    The only time you need to consider individual mails with a dynamic loop is when the text of the mail varies from one recipient to another.
    20. How do I send a standard text as an e-mail from workflow?
    It is very easy sending standard text , which may include data from the workflow. You simply create a background step which sends the work item description. This may include variables which will be substituted when mail is sent.
    In early releases you have to create your own task based on the method SELFITEM SendTaskDescription. In later releases a wizard is available for creating the step and in release 4.6 there is even a step type which does this all for you automatically.
    Whichever path you take, there is very good online documentation describing exactly what has to be done.
    21. How do I send a complex text from the workflow?
    You may create mails using SAPscript. These mails can include conditions which are evaluated in order to determine which text blocks which are used in the mail. Workflow variables can be used in these conditions and workflow variables can be substituted into the body of the e-mail text.
    22. How do I send really complex mails from the workflow?
    If you this is not enough for you will probably want to write your own ABAP routines for generating the text and generating the attachments to go with the text.
    Use the function group SO01 which contains functions of the form SO_*_API1 which are ideal for creating your own sophisticated messages. There are plenty of advantages of how these are used within the SAP system.
    23. How do I send reports?
    There are wizards (Release 3.1) which will create workflows for you to send reports to a distribution list. You can specify whether the results should be transmitted or evaluated at the time the recipient wishes to view the report. It is usually better to send the evaluation because this allows the recipient to see the results instantaneously, without having to wait for the report to execute first.
    Deadlines
    24. How can I configure the workflow so that different types of messages are sent out to different people depending on how late the processing is?
    Follow these steps:
    1. Specify a deadline period for the step.
    2. Specify a name for the event. This adds new branch from the step.
    3. Add a new step to the branch which sends a mail message.
    4. Add another step to the branch which sends out the second deadline warning (see mail steps above). Use deadlines in this step to configure an earliest start so that the second message is not sent until a further time has elapsed.
    5. Repeat step 5 as often as you like.
    25. How can I configure the workflow so that when the deadline is missed the workflow step is simply skipped?
    This is tricky to explain but easy to implement once you know how.
    Follow these steps (in later releases there is a wizard which takes you through the steps):
    1. In the terminating events view of the workflow step activate the "obsolete" event and give it a name.
    2. Specify a deadline period for the step.
    3. Specify a name for the event. This adds new branch from the step.
    4. Add a new step to the deadline path. This step must be of type "process control".
    5. Select the control "Make step obsolete" and use the search help to specify the workflow step that has the deadline. Only steps with obsolete paths defined will be displayed (see step 1).
    26. How do I trigger a workflow with an e-mail?
    You can customize the system to call a BOR method when an external mail (fax, e-mail...) arrives in the system. You BOR method should either trigger the e-mail directly or trigger an event. To customize this user exit use the transaction SCOT.
    27. How can I make sure that user's access their tasks via the workflow and not via the menu or launch pad?
    The routing mechanism for work items uses roles and organizational assignments to determine who receives which work item. However the routing does not provide extra authorization checks based on the routing configuration. If you want to ensure that the tasks are executed within the workflow, and not via the standard transaction, service or MiniApp, then you will have to apply your own protection.
    The simplest way of doing this is to remove the standard transaction from the user's menu or Workplace role (but include it in the supervisor's role, just in case).
    If you want to allow the user to execute the task from the menu if and only if they have received the work item then you should replace the standard transaction with your own custom built transaction. Your own transaction simply calls the standard transaction but performs it's own authorization check first, based on the routing mechanism used in the workflow. Tip: Add a second (ored) authorization check to make sure that a supervisor can execute the transaction in an emergency.
    28. What is a workflow? What is a single-step task?
    A single-step task is based on an object type from the object business repository (BOR) (for example, a purchase order) and a method for the object (for example, change). A workflow can contain several single-step tasks and activities such as loops and forks. Through a workflow, you create a logical sequence for the single-step tasks. The tool for creating or changing these types of workflows (workflow template) is the Workflow Builder (transaction SWDD).
    29. What is a work item (important terms)?
    A work item is the runtime object of a workflow or of a single-step task.You can execute dialog work items with the inbox (transaction SBWP). Each workflow and single-step task started is assigned a unique number known as the work item ID.
    30. How is an event triggered from the application and a workflow then started?
    An event can be triggered from the application in three different ways:
    Directly:
    Within the application, the SWE_EVENT_CREATE function module or the SWE_EVENT_CREAT_IN_UPD_TASK function module, for example, generates an event in the update.
    With a change document:
    Change documents are written within the application when you change application objects in the update. You can link events that have the same key with these types of change documents via transaction SWEC.
    With status management:
    The SWE_EVENT_CREATE_STATUS function module triggers an event in the same way as the direct method when a status is changed. This event contains the object type (for example, purchase order), the object key (for example, purchase order 4711) and other information. Using transaction PFTC, you can assign the event to a specific workflow or single-step task. More settings are available in transaction SWE2.
    31. How are the responsible agents determined?
    You can assign agents to a single-step task in transaction PFTC. For example, you can do this using organizational units, work center roles or positions. Within a workflow pattern, you can assign specific agents for this workflow to a single-step task. The overlap between both numbers of 'possible agents' represents the number of agents ('selected agents') who have the work item in the inbox later.
    32. What is the difference of between an e-mail and a work item?
    E-mails and work items are two completely separate things. They just happen to be displayed in the same inbox. An e-mail is a message sent to one or several people. However, a work item is a runtime object of a single-step task or workflow. Consequently, a work item cannot be deleted from the inbox of a user. In this case in fact, you have to adjust the agent assignment or delete the work item as described in note 49545.
    33. PFAC no longer works for my role responsibility setup...
    Use tx: OOCU_RESP
    34. How do I transport workflow definitions and agent assignments?
    When transporting workflows, you have to differentiate between the workflow definition and the agent assignment.
    A workflow definition is a workbench request. When you save the workflow, a workflow version is created and a request written. Further information about the transport or about the status management is provided in note 378487 and in the notes mentioned there under related notes.
    However, where the agent assignment is concerned, this is a Customizing request. To allow transport of agent assignments, the value of the semantic abbreviation CORR for the TRSP group name must be empty in table T77S0.
    35. How do you debug a background workflow process?
    In your method write the following code:
    data exit.
    Do.
    if exit = 'X'.
    exit.
    endif.
    enddo.
    Run the workflow, causing an infinite loop on that step, and then go to SM50.
    Here you can debug the process.
    36.What is the Workflow basic Customizing?
    Before you can use the Workflow module, you must first execute the basic Customizing in transaction SWU3. All of the listed points should be green (the number range for customer tasks is no longer required). A detailed description of the activities is provided in the relevant information buttons. You can also execute some (but not all) of the points using the Automatic Customizing button. See the online documentation for an exact description of what happens there. The RFC destination must work correctly and the user (usually WF BATCH) should have the SAP_ALL profile.
    37.: What options do I have as a user to configure the inbox individually?
    You have the following options:
    You can create separate user-dependent or user-independent layouts so that you can adapt the displayed columns individually. You can access the function in the Workplace via an application function key.
    You can set filters to set certain criteria for individual columns or several columns simultaneously, according to which specific work items are then filtered.
    You can add dynamic columns in the layout that then display dynamic elements for certain tasks and users from the work item container. However, this is only possible if all tasks in the inbox belong to just one task. If they have several tasks in the inbox, filtering serves no useful purpose because all tasks are first completely read once. You can define these dynamic columns using transaction SWL1.
    38. What does the substitute rule system look like in the workflow?
    You have a choice of two different substitute rulings:
    Active substitute ruling (for example, for absence due to vacations): In this case, the items belonging to the absent person are automatically assigned to the substitutes inbox (in addition to his own work items).
    Passive substitution (for example, for absence due to illness): the substitute must explicitly assume the substitution and can only view the items of the absent person in this mode.
    For other questions, you must also refer to note 74000.
    39. How can users be automatically notified that new work items are available for processing?
    Unfortunately, the dialog box that informs users of new work items which appears in SAPoffice is not available within SAP Systems.
    However, the following two options are provided:
    In the Workflow Builder, you can designate the item as an express item via additional data. The user then receives a corresponding express dialog box.
    The RSWUWFML report (note 131795) is a more flexible option. This report sends an e-mail to an external Internet address to notify the user of new work items.
    40. Can I set deadlines for the latest processing of work items?
    this is where you can use deadline monitoring for work items. In the Workflow Builder, you can set dates for a requested/latest start/end date for each individual step. You must schedule the SWWDHEX job via transaction SWU3 for this. Schedule the job permanently in the production system otherwise it is difficult for the job to schedule individual deadline monitoring scenarios when workflow is heavy.
    41. Can I also execute work items with external programs such as Outlook?
    You can use the Web GUI for HTML instead of the Windows GUI. However, note that some functions do no work in the WEB GUI, due to technical restrictions in the browser. You must refer to note 487649 on this subject.
    SAP also provides interfaces which allow you to process work items with external programs such as Lotus Notes or Microsoft Outlook. Refer to notes 77099, 98408 and 454845 for details.
    More stuff on WORKFLOW
    Transactions
    AWUV Wizard for event creation Definition tools -> Event creation -> Set up with wizard
    MCA1 Workflow Information System Reporting -> Workflow Information System (WIS)
    OOAW Evaluation paths
    PFAC Maintain standard roles
    PFAC_CHG Change roles Definition tools -> Standard roles -> Change
    PFAC_DEL Delete roles Definition tools -> Standard roles -> Delete
    PFAC_DIS Display roles Definition tools -> Standard roles -> Display
    PFAC_INS Create roles Definition tools -> Standard roles -> Create
    PFOM Maintain assignment to SAP organizational objects Definition tools -> SAP org. objects -> Create assignments
    PFOS Display assignment to SAP organizational objects Definition tools -> SAP org. objects -> Display assignments
    PFSO Organizational environment of a user
    PFT Maintain customer task
    PFTC General task maintenance
    PFTC_CHG Change tasks Definition tools -> Task/Task groups -> Change
    PFTC_COP Copy tasks Definition tools -> Task/Task groups -> Copy
    PFTC_DEL Delete tasks Definition tools -> Task/Task groups -> Delete
    PFTC_DIS Display tasks Definition tools -> Task/Task groups -> Display
    PFTC_INS Create tasks Definition tools -> Task/Task groups -> Create
    PFTR Standard task for transaction
    PFTS Standard task
    PFWF Maintain workflow task (customer)
    PFWS Maintain workflow template
    PPOC Create organizational plan Definition tools -> Organizational plan -> Create
    PPOM Maintain organizational plan Definition tools -> Organizational plan -> Change
    PPOS Display organizational plan Definition tools -> Organizational plan -> Display
    SWDA Ongoing Settings Administration -> Settings
    SWDC Workflow editor administration data
    SWDM Business Workflow Explorer Definition tools -> Business Workflow Explorer
    SWE2 Display and maintain event type linkage Utilities -> Events -> Type linkages
    SWE3 Display instance linkages Utilities -> Events -> Instance linkages
    SWE4 Switch event log on/off Utilities -> Events -> Event/log -> On/Off
    SWEC Link change documents to events Definition tools -> Event creation -> Change documents -> Linkage
    SWED Assignment of change document objects to object types Definition tools -> Event creation -> Change documents -> Define workflow properties
    SWEL Display event log Utilities -> Events -> Event log -> Display
    SWF3 Workflow Wizard Explorer Definition tools -> Wizards -> Workflow Wizard Explorer
    SWF4 Workflow Wizard Repository Definition tools -> Wizards -> Workflow Wizard Repository
    SWI1 Selection report for workflows Utilities -> Work item selection
    SWI2 Work item analysis Reporting -> Work item analysis
    SWI3 Workflow outbox Runtime tools -> Workflow outbox
    SWI4 Task analysis Reporting -> Task analysis
    SWI5 Workload analysis Reporting -> Workload analysis
    SWI6 Object links Runtime tools -> Object links
    SWI7 Workflow resubmission folder From Integrated Inbox or Workflow Outbox
    SWI8 Error overview Part of administration of workflow runtime system (transaction SWUF)
    SWL1 Settings for dynamic columns Customizing, part of ongoing settings
    SWLC Check tasks for agents Utilities -> Consistency check -> Organizational assignment
    SWLD Workbench for Workflow 4.0
    SWLP Copy plan version
    SWLV Maintain work item views Customizing, part of ongoing settingS
    SWLW Workbench for Workflow 3.0
    SW01 Business Object Builder Definition tools -> Business Object Builder
    SW06 Customizing object types From Business Object Builder, choose Settings -> Delegate -> System-wide
    SWU0 Event simulation Utilities -> Events -> Simulate event
    SWU2 RFC monitor Utilities -> Workflow RFC monitor
    SWU3 Customizing consistency check Utilities -> Customizing
    SWU4 Consistency check for standard tasks Utilities -> Consistency check -> Task -> Standard task
    SWU5 Consistency check for customer tasks Utilities -> Consistency check -> Task -> Customer task
    SWU6 Consistency check for workflow tasks Utilities -> Consistency check -> Task -> Workflow task
    SWU7 Consistency check for workflow templates Utilities -> Consistency check -> Task -> Workflow template
    SWU8 Switch technical trace on/off Utilities -> Technical trace -> On/off
    SWU9 Display technical trace Utilities -> Technical trace -> Display
    SWUD Diagnostic tools Utilities -> Diagnosis
    SWUE Trigger event Utilities -> Events -> Generate event
    SWUF Runtime system administration Administration -> Runtime system
    SWUG Workflow start transactions Definition tools -> Workflow start transactions
    SWUI Start workflows From the R/3 initial screen, choose Office -> Start Workflow
    SWUS Start tasks Runtime tools -> Start workflow
    SWUY Wizard for message linkage to workflow Definition tools -> Wizards -> Create "Call workflow from message"
    SWX1 Create notification of absence
    SWX2 Change notification of absence
    SWX3 Display notification of absence
    SWX4 Approve notification of absence
    SWXF Form applications: Access point Environment -> Demo examples -> Fill out form
    Reports
    RSWWWIDE – Delete work items
    RHSOBJCH to fix PD Control Tables
    Tables
    SWW_OUTBOX - Lists Workflows in outbox together with status
    SWW_CONT - Container Contents for Work Item Data Container
    SWW_CONTOB- Container Cont. for Work Item Data Container (Only Objects)
    SWWLOGHIST- History of a work item
    SWWORGTASK- Assignment of WIs to Org.Units and Tasks
    SWWUSERWI - Current Work Items Assigned to a User
    SWWWIHEAD - Header Table for all Work Item Types
    Reward poits if helpful.
    Regards,
    Amber S

  • In the Extended Classic scenario, what creates the PO on the SRM side?

    Hi Experts,
    This sounds like a simple question, however, I've been unable to find the answer.
    What I am looking for is the process (report, workflow or function module etc etc) that actually creates the PO on the SRM side once the shopping cart has been approved (before it is replicated to ECC).
    The reason for this is, after a support stack upgrade, the creation of the PO seems to have slowed down once the shopping cart has been created.  I'm trying to track down where the PO gets created and what triggers that to happen, in order to work out why it isn't as quick as it was prior to the upgrade, but can't piece together the full end to end process.
    I can see the "Workflow Without Approval Shopping Cart" workflow that obviously Releases the shopping cart and sets the status to Approved...  I can then see the equivalent workflow for the PO (Workflow Without Approval for PurchOrder), but I can't work out the bit inbetween -
    - How does the PO actually gets created in SRM and what triggers that to happen?
    Any help will be gratefully received - thanks in advance.

    its an event related to the shopping cart business object- BUS2121.
    your approval workflow should be of status set released, which will trigger the methor BBP_REQREQ_TRANSFER, finished approval is the event which will be triggered by the workflow, based on this event, system will trigger reqreq_transfer.

Maybe you are looking for