Workflow issue in SC (WS10000276) - Value limit 1 step approval

Dear Experts,
We are configuring 1 step value limit approval in SRM 7.0 for SC.
We have maintained the attribute SLAPPROVAL for the employee who raises the shopping cart with the manager.
For the roles assigned to Manager and employee we have specified the spendding limit and approval limit.
Activated the WF WS10000276.
When I create the SC it is not determining the approver based on value.
We have even tried out by assigning agents for the WF WS10000276.
Can any one help me in this regard.
Is there any attribue SLAPPROVERLIST where we need to maintain the approvers.
Please give me the steps to configure.
Thanks,
B.N.Karthikeyan.

Hello BN,
I tested the WF in SRM 5.0 and had to set the SLAPPROVER attribute to "USMANAGER01" if the approver/manager was the User Id MANAGER01. Meaning with US in front of the User Id of the Approver.
But you might have already done this.
Franz

Similar Messages

Workflow Issue - Adding parameter to my decision step.

Hi
I am working on workflow and in decision step there are 4 parameters that I can use for Title. I have a requirement of 6 parameters. Is there any way in which I can add another parameter to my Decision step.
Himanshu Verma.
Patni Knowledge Park, India.

Would it be possible for you to concatenate the values of two parameters into one in a previous step?
Or even having only one parameter and a previous step that generates the full title you want to display...
Data element is SWD_PARAM1 which is CHAR255, long enough for holding a custom title.
Hope that helps,
Andres.

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

Restart Workflow on changing the SC value

Hi SRM Champs,
There is a interesting requirement in our project for Shopping Cart workflow with value limit approval.
Here, for the workflow there are two approvers APPROVER1 and APPROVER2 with the following condition :
upto 1001 $ > more APPROVER1 should approve
from 10001 $ > more APPROVER2 should approve
Now please look into the below scenario :
When creating a shopping cart passing values like qty as 1 and value as 10020 $ and ordering the shopping cart. The system should determine the only 2 Approvers it is happening perfectly.
But,after approved by the APPROVER1 ( Remember APPROVER2 yet to be approved) The requester changing the value as 1600. Now the value is < 10001 Now workflow should restart and control should go to APPROVER1 this is not happening, wherelse the Shopping cart is showing to be approved by APPROVER1 in the check status.
Logic should be whenever changes are happening in SC workflow need to restart and approval process start from the beginning.
Please help in this direction, any help shall be profoundly appreciated and rewarded points.
Regards,
Vikas.

Hi Imthiaz Ahmed,
 Please accept my apologies first for the late reply.
 Thanks for correcting me as it has it should have been as follows :
Now the value is < 10001 Now workflow should restart and control should go to APPROVER1 this is not happening, whereas the Shopping cart is getting approved in the
check status .
Hi Nimish Sheth,
 Thanks for your suggestions, we have implemented all the suggestions given you, but unfortunately still the workflow is not getting restarted as expected !!
Dear Friends,
This issue is still pending from our development team and the client is expecting some feasible solution. If you have any idea, please suggest, it would be a great gesture.
Regards,
Vikas.

Limit steps

Hi , I'm using TS 3.1 and LV7.1 .
I have a VI which reads the value of step.limits.low and step.limits.high via the sequencer context and get properties methods.
This vi is called by a numeric limit step type within a flow ( loop) step in TS, the values of step.limits.low and step.limits.high are forced to different values within the loop.
The Edit Limits TAB has this entered in the data source window:
Step.Limits.Low = Locals.TempWindowLow ,Step.Limits.High = Locals.TempWindowHigh
the locals being defined in a Fx step previous.
The problem I have is that the VI gets the default test limits ( ie the relevant fixed ones ) on the first iteration of the loop, and is subsequently one behind on later iterations.However the report shows that the limits are correct by the time the results comparism in TS takes place.
So the issue is probably in the order at which things happen when calling the vi, the Step.Limits.Low being evaluated after the properties have been sent to the VI.
Has anyone any experience of this, and possible work arounds?.
thanks dht

For a numeric limit step, the data source expression gets evaluated as part of the status expression, thus, as you saw, it happens after the module is called. Move your limit initialization expression to the PreExpression on the Expressions tab of the step properties dialog box.

One step approval workflow in SRM 7.0 BRF

Hi,
Please le tme know how to configure the one step approval workflow for Shopping cart in.SAP SRM 7.0
We ant to know where we can specify the approva limit lik if sc value is greater than 50 it should go for one level of approval else no approval required.
We are using process controlle workflows.
Thanks,
Venky
Edited by: SAP SRM123 on Jul 14, 2011 12:18 PM

I was get some trouble when implement one step approval from HQ in my company.
It's a logical when some one just implement one step approval it is not make a hugh impact for controlling and sometimes end-user was change their own approval step make negative impact for workflow. Not logical but they make it logical but system still make sure it work.

Purchase order workflow issue

Hi All,
A PO is created and rejected by a user in user decision step.The workflow will end.If the PO is changed(amount) again,the release strategy is triggered for the same user.But the workflow is not triggering.If the release strategy is for a different user,its triggering the workflow.I have used a fork inside which 1 parallel branch contains a wait for significantly changed event & another branch contains the user decision step,po release step & rejection reason scenario.
Please refer the thread below.
PO Release Strategy Issue
Replies will be greatly appreciated.
Edited by: Feddie on Jan 3, 2008 11:43 AM

Hi,
This is not workflow issue(work flow is different term)
It seem problem of BADI (program written for creation of purchase order based on sales order)
Take help of ABPer so he/she can solve this issue
Kapil

How can I restrict a vendor with certain value limit?

Hi Gururs,
How can I restrict a vendor with certain value limit?.
Scenario is like this
If my company was decided to purchase goods from a particular vendor upto Rs.1000, if cross the rs.1000 limit don't allow the Posting the PO and get the Message as warning/error.
Give the configuration setting's and T.codes
Thanks and regards
G.N.Rao

Hi
Go to T.Code oms4 and then select the material status BP (Blocked for purchasing)
Click on Details
In that under Purchasing select the option A= Warning or B=Error
Click on Save
Thus by doing this no further purchasing function for that material can be done. So the PO can not be issued
So as and when the value limit reaches see that purchasing option is blocked
So no further PO are generated in the future
I hope this helps you out
If found useful reward accordingly
Thanks
pavan

Evaluating NaN Comparison Type in TestStand Numeric Limit Step

I'm using a 4070 DMM to return Resistance Measurements to a TestStand numeric Limit step. How can I use a comparison type when the LabView vi returns NaN (Not a Number). I want the step to pass as long as the Resistance Measurement is > GT some value.

NAN comparison in expressions and limit tests works as follows
(NAN > x) == false
(NAN == x) == false
(NAN < x) == false
(NAN == NAN) == true
To summarize, a NAN is neither greater or less than another number and is only equal to another NAN.
If you want NAN to fail and measurement > some_limit to pass, then just use the > (GT) operator.
If you want NAN to also pass, then you need to check for it separately. You can do this dozens of ways. Here are a few:
a) Use a pass/fail step with an expression like: Locals.x > 10 || Locals.x == NAN
b) Use two limit steps, one to check for NAN and one to check the limit. Use preconditions to specify the NAN check only runs for the NAN value and the limit check only runs for non-NAN values. This will ensure
the measurement makes it to the report.
c) If NAN is your instruments way of returning "resistance too high to measure", then you could transform the NAN into an INF in the data source expression and then use a GT limit. Example data source expression:
Step.Result.Numeric == NAN ? INF : Step.Result.Numeric

One step approval workflow

Hi All,
I have added a step in one step approval workflow to check shop on behalf.
When a person shop's on behalf of a manager, and 1 step approval is triggered, i want the approver to be the manager.
But what is happening is that Manager's Manager is getting the workitem!
My query is that :if A shop's for B, the approver should be B for the shopping cart. How can i achieve this????
Anybody knows what needs to be done in this scenario?
Thanks & Regards,
San

Hi San,
In addition to Usman's views also look at the below mentioned points :
1. In your org. structure if you have named somebody else as the head of the department for that org. unit, it will go to that person for approval.
2. And there is no point in taking approval from the same guy for whom you are shopping on behalf. In such a case that guy can himself create a shopping cart.
Looks like there is some mis / lack of understanding about the correct client requirements.
But there are few work arounds you define this guy as the substitute for his manager.Then either of them can approve the shopping cart.
Or.. don't make any body as H.O.D of org. unit and define the approval agent in the work flow builder using SWDD txn and let the approver will be taken from there.
Hope this makes you more clear and helps in resolving your issue. Clarifications are welcome.
Award points for helpful answers.
Rgds,
Teja

2 step approval workflow

How to create a 2 step approval workflow in CLM system. The scenario is like this- The contract first craeted by owner goes for internal review (legal or business as collaborators) and then goes to Product category manager (first approver) and once all stakeholders including supplier gives go-ahead on acceptance of contract, it will be signed off by Financial authority (value based approval)(second step approver).
Appreciate if someone guide on this....
Cheers!
Amit

Dear Pras,
I've a similar requirement.
Credit / Debit Note Generation
Credit note:
A credit note is a document that decreases the company's receivables and decreases the customer's liability.
Debit note:
A debit note is a document that increases the company's receivables and the customer's liability.
Both the above cases, system generate notes msg. and transmit to the concerned authority.
Criteria
Less than Rs 1,00000 - workflow only to User1
Between Rs, 1,00000 - Rs, 2,00000 - workflow to User1 and then to User2.
Please help me ... I'm new to Workflow.
Regards,
Abir

Support for UInt64 Datatypes in Numeric Limit Step

It would be good to be able to use UInt64 directly in numeric limit step, instead of something like this:
Step.Result.Status = CheckLimits(FileGlobals.F1_10, Locals.FrequencyInputLimits.Freq10GhzMax, Locals.FrequencyInputLimits.Freq10GhzMin, "GELE", False)

NikolajEgeskovOstergaard wrote:
It works if i convert my UInt64 to Float64...
is that really it ?
I would advise against doing that. Not all UInt64 values can be exactly represented in a Float64 so you will get some rounding error. It depends on what you are doing whether or not that would matter.
The numeric limit step does not currently support 64-bit integers, however the CheckLimits() expression function does support them so you could do something like:
Step.Result.Status = CheckLimits(Locals.Measured, Locals.High, Locals.Low, "GELE", False)
Also you might want to post a feature request to:
http://forums.ni.com/t5/NI-TestStand-Idea-Exchange/idb-p/teststandideas
Hope this helps,
-Doug

LR 3 Bug Report - file renaming error - significant workflow issue

System configuration:
MacPro Dual 2x2.66Ghz Dual Core Intel Xeon
9GB RAM
OSX 10.6.4
Lightroom Application on System Drive
Canon .CR2 files and Lightroom Catalog on internal software-based RAID drive
Camera Raw Cache set to 50GB and resident on System drive
Here is the issue:
Once I finish the first round of editing a group of photos, I then rename them with the title of the event and a sequence number. I use LR's batch rename feature in the Library module. If I then delete 1 or more of these photos and attempt to rename them again(same event title + numerical sequence), the new names do not properly apply the numerical sequence after the filename. Either of the following can happen, and whcih one will happen is not dependednt on what I do.
1. The files can be renamed, with the first image having a sequence number 1 number higher than the lowest number I typed into the sequence box in the batch rename dialog (if I type a number 1, the sequence starts at 2). There are also random gaps in the sequence numbering scheme. For example, the numbers will count to 15, then skip to 17, then count to 176, then skip to 178. The rest of the files might be renamed correctly, or there might be gaps. The gaps always skip a single number, and most of the time the numbers skipped are odd numbers, though numbers with a 16 are usually skipped (16, 116, 216)
2. The files can be renamed as mentioned above, but with the addition of a -1 to the end of the sequence (example: filename-200-1 or filename-3-1). The addition of the -1 is also random, though it is more common with lower-numbered files than higher-numbered files.
I have experienced this bug on groups as small as 50 photos or as large as several hundred. I have tried remaning the files to a completely different text/sequence combination and then back to the one I want, and it does not help the issue. The sequence numbering is more likely to have more gaps the more virtual copies are present in the series of photos being renamed.
This is a major workflow issue for me because the files I deliver have to be named sequentially, without gaps, following a specific text/numer naming convention. The bug is currently adding many extra hours to my post-production time. Any assitance would be greatly appreciated.
Thank you

Thanks for the detailed description. I was able to repro this with your steps and have logged a bug for futher investigation.
Becky

Creating numeric limit step types

Hello,
I'm new in TestStand and I'm trying to create my own step types.
Right now I need a step type that reads the voltage from one channel on my MIO board and reads one Digital IO from my DIO board.
I was able to create one step type - run VI and EDIT VI (to choose the channel), but my problem is that my step type is not a numeric step type (so it is not returning a value) and I don't know how to change it!
1. Are there these kind of step types (DAQ) available anywhere?
2. How do I set the type of my step type (I think the ones I'm creating are allways action step types and not tests)?
Thanks ahead!

Hi,
The easies why to create your NumericLimit type is to select your step type and right mouse click and select create useing then select the NumericLimit type.
This will create a new step type combining your step type with a Numeric Limit step type.
Before you start just rename your step type to someother name by just appending "_1". Then when the new combined step type is created. You can then rename this step type to your original name and easily delete your "_1" named step type.
Hope this helps
Regards
Ray Farmer
Regards
Ray Farmer

Workflow issue after upgrade to ECC 6.0

Hi,
we are facing an workflow issue and thought if someone has faced similar issue and could help us.
We've an approval workflow for purchase requisitions through release strategies. For some steps, if the approver is 'WF-BATCH' user, we are executing that step using a program. This program first set the workitem to completed status( this part is working), then it will close the purchase requisition to release status for a particular release code( this part is working) and then we are triggering the 'RELEASE' event for the business object providing the Object key which should take it to the next step( THIS IS NOT WORKING). The business object is custom. This was working perfectly in 4.7 version of SAP but this logic is not working in ECC6.0. we are using SAP_WAPI_CREATE_EVENT to trigger the event. But the workflow doesn't move on to next step.
Have anyone of you have any idea as why this might be happening. Any information on this would be of great help.
This is happening in ECC 6.0. USED TO WORK IN EARLIER VERSION.
Regards,
Sam K

Hi,
Is WF-BATCH having proper auth. ?
Or, if you are using the FM SAP_WAPI_CREATE_EVENT in some program and is scheduled as a batch job, then that user under which this batch job is runnign should have proper auth. to raise the event. Please check those.
Also, what the error (if any) says in SWEL ?
venu

Workflow issue in SC (WS10000276) - Value limit 1 step approval

Similar Messages

Maybe you are looking for