Workflow issue- Dereferencing of the NULL reference

Hello All,
I have an issue with sending mails to external e-mail ids through a workflow process. I am using the FM SO_DOCUMENT_SEND_API1 for sending mails. However, because of the latest Basis version I need to call this FM in a seperate task when the process is in BACKGROUND mode.
The current scenario is, my workflow will trigger a method, which internally call this FM in a seperate TASK. When I run the workflow/process I get an error in the method, which triggers this FM. The erro says "Dereferencing of the NULL reference"
Is this because of calling the FM in a seperate task, as the workflow already has a pre-defined TASK? if yes, how do we go about this?
Thanks,
Anil

Hello Anil,
I am facing a similar message when i am running the SAP standard workflow 18900044 for leave encashment. I am calling a class CL_HRPBSIN_HANDLE_LEREQ_WF and the method CALL_WORKFLOW.
Can you please tell me how you managed to solve your issue.
Regards,
Ritwik

Similar Messages

  • Error: Dereferencing of the NULL reference

    Dear Friends,
    one of our user is running a report on web bex  and he is getting following error.
    com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException:
    Termination message sent ABEND RS_EXCEPTION (000): Dereferencing of the NULL reference 
    MSGV1: Dereferencing of the NULL reference
    But when we run this with our user we are not getting any error.
    if we run this report using RSRT usin user's user id it is not giving any error.
    only genrating error when we try to run using Web Bex .
    Any help hightly Appicated.
    Malik

    Thanks friends,
    i already check the given sap note but that note is for support pack till17 and we have already 19 support level.
    thats why this is not the solution.
    second i check it publishing. its working fine with all the users except 3 of our users. i dont know why the error is
    comming with them only.
    and i also check the url  no specific variable values.
    any other idea.
    regards
    Naeem

  • Dereferencing of the NULL reference

    Hi,
    I have created an a form view with a value node "ZINVOICE" , i have written few lines of code to set the collection,
    create object lr_col
        type
          cl_crm_bol_bo_col.
       create data lr_tabline.
       ls_favs-PROCESS = 'mahe'.
       ls_favs-SERTYPE = 'SRVR'.
       create object lr_valuenode
          exporting
            iv_data_ref = lr_tabline.
      lr_valuenode->set_properties( ls_favs ).
      lr_col->add( lr_valuenode ).
    set collection
      me->zinvoice->set_collection( lr_col ).
    After this the node "ZINVOICE" has the collection ref and entity list shows the entity as well,
    But still wen i try to test the view it gives errors saying
    Cannot display view ZCNODE_INST/ZWASL of UI Component ZCNODE_INST
    An exception has occurred Exception Class  CX_SY_REF_IS_INITIAL - Dereferencing of the NULL reference 
    BSP Application:  ZCNODE_INST 
    View Layout:  ZWASL.htm 
    Method:  CL_O2D8A1MNCT9O5WAN3TF3CDQNNQY=>_ONLAYOUT 
    Source Text Row:  42
    can somebody help me with this,

    Hi Mannif,
    I am not including this view in any component as an AB, when i include in any other standard component it does work fine. The problem is when i try to run it as a stand alone component. I am trying to set the collection of the contect node. I tried the same for a model node with bol entity "BuilHeader". I set the collection using "CL_CRM_bol_query_services", and it worked fine.
    try.
    query ?= cl_crm_bol_dquery_service=>get_instance( iv_query_name = 'BuilHeaderAdvancedSearch' ).
    catch cx_sy_no_handler.
    endtry.
    CALL METHOD QUERY->add_selection_param
    EXPORTING
    iv_attr_name = 'PARTNER'
    iv_sign = 'I'
    iv_option = 'EQ'
    iv_low = '*'.
    *get query result*
    col = QUERY->get_query_result( ).
    CALL METHOD me->BP->SET_COLLECTION
      EXPORTING
        COLLECTION                    = col
    By the same logic is not working for a value node.

  • Dereferencing the NULL reference while saving a Survey

    While saving a survey first time, I am getting an error message "Dereferencing the NULL reference".
    More details as follows:
    Exception: Class CX_SY_REF_IS_INITIAL
    Program: CL_SVY_H_SVYDETAIL_IMPL=======CP
    Include: CL_SVY_H_SVYDETAIL_IMPL=======CM001
    ABAP Class: CL_SVY_H_SVYDETAIL_IMPL
    Method: DO_PREPARE_OUTPUT
    Line: 26 
    Long text: An attempt was made to execute a dynamic method callon an initial(NULL-) object reference. The reference must refer to an object.
    I opened the Survey creation page in crm ui, and filled in the ID, Application as Marketing and  selected CSS Style Sheet as CRM_SVY_OPP_WINLOSS.CSS
    I am very new to CRM module.
    Regards,
    Harsh

    Are you using internal CATT Server? If yes then you might need to turn on the CATT server again, see below:
    JTS based internal CATServer:
    Execute method SET_CATSERVER_JTS of class CL_SURVEY_CATSERVER. Leave parameter USER empty.
    ABAP based internal CATServer:
    Execute method SET_CATSERVER_ABAP of class CL_SURVEY_CATSERVER. Leave parameter USER empty.
    Cherrs,
    Ankur

  • Null reference method call behaving oddly

    Hi all, and a very happy new year!!
    My question concerns the null reference; simply, why does the following code chooses to call any other method than the Object version (try it out). No matter what type i choose to replace the current String version with... I have not paid much thought to this, but i would have guessed the null reference calls the Object version in such a situation.
    If i leave only the Object method and comment out all others, the code compiles fine and calls the Object version at runtime - but in case there are sub class versions, those will be called. WHY?
    (im running jre 1.4.1).
    The code:
    public class NullTest {
         public void method(Object o) {
              System.out.println("Object Version");
         public void method(String s) {
              System.out.println("String Version");
         public static void main(String args[]) {
    NullTest nullTest = new NullTest();
              nullTest.method(null);
    }

    schapel, the question related specifically to
    null, in a context where no runtime type can be
    inferred. It wasn't about overloading in general.Yes, I understand that. But here is the rule from the JLS:
    "If more than one method declaration is both accessible and applicable to a method invocation, it is necessary to choose one to provide the descriptor for the run-time method dispatch. The Java programming language uses the rule that the most specific method is chosen."
    Note that it does not refer specifically to a null argument.
    The question is "why is the most specific method called?" The reason is that there are only a few possibilities for this rule:
    1. The least specific method should be called. In this case, overloaded methods with more specific types could not be called.
    2. If there is more than one method, it is a compile time error. Again, this would cause overloading to be useless.
    3. The most specific method is called. It is only with this rule that overloading works. That's why Java uses this rule.

  • The list of workflow actions on the server references an assembly that does not exist

    Hi,
    This issue has been discussed many times in this forum , the reason why I am posting is I tried the resolution steps but I dont see any luck.
    I am getting the below message from the SharePoint designer 2007 when I am trying to modify a workflow
    "This list of workflow actions on the server references an assembly that does not exist. Some actions will not be available. The assembly strong name is Microsoft.SharePoint.WorkflowActions, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c.
    Contact your server administrator for more information."
    #1 : One of the post says "Normally you would see that error because someone has extended the Workflow actions available in SPD with a custom action developed in Visual Studio.  These custom actions are loaded when your workstation reads the WSS.ACTIONS
    file on the server.  The file is located in the 12 hive under Template\1033\workflow.  Your WSS.Actions file contains a reference to a custom action .dll which is not available on the server."
    I opened the WSS.Actions file in notepad, I dont see any line with *.dll in it. Am I missing something?
    #2: Another post says "The solution I discovered was that the server running my SharePoint Services was not up to .NET 3.0.  As soon as I updated to .NET 3.0 everything worked.I had made sure the machine running SharePoint Designer was updated, but
    had missed the SHarePoint Services server."
    The server is already updated to .Net 3.0.
    #3: I went to the %System Drive%\Documents and Settings\Local Settings\ApplicationData\Microsoft\SharePointDesigner.
    Deleted the ProxyAssemblyCache folder but no luck.
    Just checking if any one was able to resolve this issue by following any of the solution other than the above mentioned ones.
    Thanks,
    Cutloo

        I have the similar issue with my custom work flow. I have searched the whole day for the solution but no success, then at last a simple track works for me. Please try this if any one faces such issue.
    Basically the assembly that we have define in the ACTIONS file dose not exists on the server, because of two reasons, either we have given the wrong assembly name (in our case the namespace name inside our solution) or the PublicKeyToken may differ from the
    original assembly, that are deployed in GAC.
        So cross check both of these, in my case the assembly name was fine,
     <Action
        Name="Move Item to Another List and Send Email"
        ClassName="MyAssemblyName.Classname"
        Assembly="MyAssemblyName,Version=1.0.0.0, Culture=neutral, PublicKeyToken=4053d1fde8a1c781"
        AppliesTo="all"
        Category="Email actions">
    But the problem was in the 'PublicKeyToken', so i double click on the feature inside my solution,then in the bottom i have clicked on the manifest tab to check the entries.
    <Feature xmlns="http://schemas.microsoft.com/sharepoint/" Title="MyAssemblyName Feature1" Id="f7f1bda0-5f65-40f1-a705-f6f15a41da3a" ReceiverAssembly="MyAssemblyName, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0c32dbb769ed64b5"
    ReceiverClass="MyAssemblyName.Features.Feature1.Feature1EventReceiver" Scope="WebApplication"></Feature>
    Here i got the actual PublicKeyToken for my assembly (0c32dbb769ed64b5), i have replaced this number inside ACTIONS file, deploy the soultion, reset IIS.
    It works for me,

  • Regenerate the Object Reference in workflow

    Hi All
    Is it possible to regenerate the object reference in workflow BOR.
    Please clarify below my query.
    I am using custom workflow at initial stage i am sending dialog work item one user to another user, Once user opens his work item i want to change the object reference.
    Is these any function module available please let me know.
    Thanks & Regards
    K.Gunasekar.

    Did it via the Call transaction and BDC in the object method code and working perfectly fine.
    Regards,
    Archana

  • Workflow issue - When i execute the workitem it just disappears

    Hi
    i am learning workflow. i am just following some instructions on one of the tutorials and i developed a simple workflow for editing material number when a material is created. i create the material in mm01 and the event gets triggered and i get the work item in my inbox. When i execute the workitem it just disappears and comes into my outbox. I am not able to go to the edit screen of the material( mm02) what am i missing? if i only use task then it works fine without any issues, if i include the same task in a workflow and trigger it does not open mm02. plz help
    ~Suresh

    Have you checked the workflow log ?
    If not in your business work place, got to Outbox --> Work Items executed by me
    The click on the workflow log button. Analyze the log.
    There are various reasons why this can happen, so cant really say much about why this issue is occurring without more details.
    Also you will probably get better answers if post this in the Workflow forum than in the ABAP forum.
    Regards,
    Srihari

  • Select list null value issue - for filtering the tabular form report

    hello,
    I have a tabular form created on emp table and in the table their are entries for the employees who don't have a location, like it is null for some of the employees.
    Now I have created a select list item - for filtering the results based on location.
    my select query for select list item is
    select distinct location_name d,location_id r from emp order by 1
    -- so my select list contains all the distinct location_name including the null on my tabular form.
    so based on the selelcted value(in the select list), I am able to filter the results in my tabular form.
    but the thing is that when i try to select an null value from my select list - i am not able to filter my report - like its displaying all the records, its not filtering.
    can anyone help me out with this.
    thanks.

    Hi
    Try below select for LOV
    select distinct nvl(location_name,'No Location') d,nvl(location_name,'No Location') r from emp order by 1 And then change tabular from select where clause also use nvl(location_name,'No Location') like
    SELECT *
    FROM emp
    WHERE nvl(location_name,'No Location') = :Px_YOUR_ITEMBr, Jari

  • Notification issue:wf_notifications mail_status is null, status is CANCELED

    Hi All,
    In our HR systems, we use workflows extensively and in one of our custom workflows we send a notification to one group mail box. The FND_USER is defined and the group mail box address is given correctly.
    In the workflow we recursively send notifications to that user as long as there are some unprocessed records in our custom table. The issue now is the users claim that the mails are not received by them in our live instance. While debugging we noticed that the mail_status is null and status is CANCELED for this particular workflow always.
    I checked the following and they are correct:
    1. Notification 'On Revisit' parameter set to 'Reset'
    2. Checked in fnd_user and wf_local_roles, the user is active and the email id is correct there
    3. No timeout parameters set for this notification
    P.S. Notifications to this user are sent properly when sent from some other workflows. So not sure whether something is missing in the above workflow process.
    It is really strange that the notification status is CANCELED. The begin and end date are same for such notifications. So these are not canceled by some abort process activities.
    Please suggest.

    Please post the details of the application release, database version and OS.
    In the workflow we recursively send notifications to that user as long as there are some unprocessed records in our custom table. The issue now is the users claim that the mails are not received by them in our live instance. While debugging we noticed that the mail_status is null and status is CANCELED for this particular workflow always.
    I checked the following and they are correct:
    1. Notification 'On Revisit' parameter set to 'Reset'
    2. Checked in fnd_user and wf_local_roles, the user is active and the email id is correct there
    3. No timeout parameters set for this notification
    P.S. Notifications to this user are sent properly when sent from some other workflows. So not sure whether something is missing in the above workflow process. Can you find any errors in the Workflow log file?
    It is really strange that the notification status is CANCELED. The begin and end date are same for such notifications. So these are not canceled by some abort process activities.
    Please suggest.How To Troubleshoot Java-based Workflow Notification Mailer [ID 242941.1]
    Troubleshooting Workflow Java Notification Mailer - Technical Reference [ID 1191125.1]
    A Guide For Troubleshooting Workflow Notification Emails - Inbound and Outbound [ID 831982.1]
    Oracle Workflow Release 12 Diagnostics [ID 469822.1]
    OWF H Diagnostics, Solutions and Information [ID 332152.1]
    Thanks,
    Hussein

  • How to avoid the null values from xml publisher.

    I am creating a report which have the claim numbers with the values CLA001,CLA111,null, null . when i preview my report it is showing some spaces for null values also. How can i avoid the spaces from the report.
    I am giving for loop for the claim numbers in the template.
    <?for-each:ROW?> <?sort:CLAIMNUMBER;'ascending';data-type='text'?>
    <?CLAIMNUMBER?>
    <?end for-each?>
    Please help me out to solve this problem.
    Thanks,
    vasanth.

    Hi Sheshu,
    According to your description, you are experiencing the null values and infinity values when browser the calculated measure, right?
    Based on my research, the issue is caused by that dividing a non-zero or non-null value by zero or null. In this cases, we need to check for division by zero to avoid this situation. Here is the sample query for you reference.
    IIF(
    Measures.[Measure B]=0,null,
    Measures.[Measure A] / Measures.[Measure B]
    If you have any questions, please feel free to ask.
    Regards,
    Charlie Liao
    TechNet Community Support

  • How to use the Cross Reference fields in P4P

    I have been receiving questions related to the Cross Reference section from many different customers and partners. This post represents my attempt to describe the Cross Reference Section and the Equivalent Numbers stored within.
    Identity
    A term that Kelly uses and I will borrow is “identity”. A given specification can have many identities. The basic identity is the specification number generated by GSM. This is useful during early stages of design. Once we get past a draft or development status in the workflow the organization quickly wants to identify the specification in other ways. Examples include:
    Execution System Number: Operations and Supply Chain quickly need to formalize an item or material for forecasting, inventory and purchasing…
    Custom Numbering Conventions: Sometimes an organization has very specific custom logic for identifying materials. Usually terms like smart numbering are used to describe their methods.
    Data Migration Identifier: In some cases customers have extensive data clean up projects. As part of the effort systems and processes are developed and an identity is created. In my experience we loaded a “Base Stock” number to represent Packaging Materials. The label stock that was commonly used was historically not represented so we created a number as part of the migration project.
    Identity Functionality:
    The Fields: The four major fields that make up the Cross Reference section are as follows:
    >>System Name: This field describes the system generating the identifier. Examples I like to use are Oracle EBS or SAP Material Master. Sometimes geography must also be concatenated to the system, i.e. Oracle EBS – NA. This occurs when the customer is a large multinational where multiple ERP implementations exist. Therefore the same material may be known by many different numbers, i.e. Oracle EBS – NA = 77432, Oracle EBS – EU = 88883.
    >>System Code: The system code is merely the syntax used during integration. Using CSS or various APIs you may chose to identify the system using an abbreviation, EBSNA or SAPMM.
    >>Equivalent: The value representing the identity within a given system.
    >>Externally Managed: If you are using CSS or an API to receive Cross Reference data you can define the field as "Externally Manged". When a cross reference is marked in this manner the general user community will not be able to edit the field. Administrators associated with the role [Externally_Managed_Cross_Ref_Admin] can edit the field if needed.
    Syndication: While some users enter equivalent numbers manually, others use integration tools to generate and transmit identities. If a given cross reference is marked as “Externally Managed” then users are unable to manually enter data. On initial syndication the specification will not have a given equivalent. The specification is sent to middleware, a number is generated by the appropriate system and the response is sent back to GSM to add the System Code to the specification with the appropriate identity value.
    Copy verses Issue:
    >>Copy: When a user copies a specification the Cross Reference data is NOT included. Since the identities refer to the originating specification it does not make sense to carry over to the copy. If we did then users would quickly need to delete the data.
    >>Issue: When a user issues a specification it maintains the Cross Reference data. This is an important concept because it is expected that a system like GSM will have many issues related to a single ERP #. ERP systems are usually not interested in many of the fields stored in the Product Data Management system.
    Reference: As raw materials are consumed as inputs into Formulation or Trade Specifications the organization may come to identify the materials based on equivalent numbers. Therefore GSM allows for an equivalent number to appear next to the GSM number.
    Implementation Issue:  Ingredients In Packaged Quantities
    Some customers run into a situation where the ingredient specification does not represent a packaged quantity. From an R&D perspective the developer does not care if the material comes in a box or a tanker. In this situation the GSM ingredient may be represented in the ERP system by many items and therefore more than one cross reference value. These items represent packaging differences that are important to purchasing, manufacturing, warehousing, and other execution systems.
    I hope this helps describe some of the purposes and implementation issues around the Cross Reference field.

    You need to get jmf.jar in your CLASSPATH, either on the command line, in an environment variable, by putting a symlink in $JAVA_HOME/lib/ext, whatever works for you. Have you done that? Once it's in the classpath, you can run jmstudio from any directory with the command "java JMStudio".
    Items in the bin directory are just shell scripts, run with "sh jmstudio" or whatever suits your shell (on Mac OS X, copy one of these guys and append ".command" to the filename to make him double-clickable in the Finder).
    --invalidname

  • MDG - S Workflow issue

    Hi,
    I have configured the MDG for Supplier where I am using the standard workflow template for Supplier Create - WS53100044.
    I have a couple of questions here where I need your expert help.
    1.I create a CR, it goes for approval. When I run validation it starts asynchronously. Any idea why this is happening? Though there are no validation errors.
    2. I can also approve the CR. If I have Company Code and Purchasing Org data in it then it needs processing but the workflow log says 'No Processor assigned'.
    3. If I do not have these information fed in the CR, the workflow gets approved and the next step is 'Decision on Process Contact person'. Here it looks for a reference BP. I do not get the list of BPs to select from. Please advise what is missing.
    Thank you in advance..
    Regards,
    Jayati

    Hello Jayati
    your validation will always start Asynchronously as it is native feature within MDG. So no issues about it. The good part is you are not getting any validation error.
    Since you using standard workflow template, try using other MDG workflow for the Processor assignment. Check the step number under "Define Workflow Step Numbers" step and then check if the correct processor is assigned there. More details can be found if you see the workflow log of your change request.
    Regarding the BP issue, try completing the configurations suggested in MDGIMG under Master Data Governance for Supplier --> Set up Business Partner.
    Hope this helps you.
    thanks
    Rahul

  • AME APEXP Workflow Issue

    Hi All,
    In R12 I have issue in APEXP (Expenses) Workflow.
    User has created expense report and the workflow has started.
    It went through AME process where it has find the approver for the expense and then notification went to the approver.
    After this we have a block acitivity which waits untill the approver apporves or rejects.
    The problem here is though the approver says that he is approved the expense sheet , the work flow status is not moving beynod the block activity in the AME process.
    AME Workflow (12345-1) shows the process is complete, the notification to the first approver is closed with an Activity of ‘Approve’.
    The main workflow (12345) is blocked and waiting for the response back from the AME workflow. It appears the spawned workflow is not updating the main workflow when it completes.
    Please guide me on this how to resolve.
    Thanks
    Kumar.

    Hi Kumar/All
    I am facing the exactluy similar issue in R12 APEXP workflow.
    In my case also approver has approved the workflow but it got stuck at block activity in the main workflow.
    I tried to debug the issue and found that in the AME approval workflow ,a function AME Complete Approval is called after the approver has taken the action(reject or approve).
    this function in turn calls the wf_engine.completeactivity API......the output of this API should act as the response to main workflow(block) and it should start moving but its not happening.
    Declare
    result           varchar2(1);
    begin
    WF_ENGINE.CompleteActivity(itemtype => 'APEXP',itemkey => XITMKEYW ,activity => 'AME_APPROVAL_BLOCK',result => Null);
    DBMS_OUTPUT.PUT_LINE('result is : '||result);
    EXCEPTION
    WHEN OTHERS
    THEN
    DBMS_OUTPUT.PUT_LINE('Error message : '||SQLERRM);
    end;
    I tried to run the complete activity from outside also and to my suprise i could see time stamp getting changed for the block but it still didnt proceed.
    i think this may be an oracle bug with R12. Please guide.
    Regards
    Gopal

  • 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

Maybe you are looking for