Work flow definition.

Give me information about Work Flow Definition?

hi payal,
SAP Business Workflow
Purpose
SAP Business Workflow® is a cross-application tool which makes it possible to integrate business tasks between applications. This component supplements the existing, comprehensive, business functions of the R/3 System.
With this component, you can adapt the standard functions of the SAP R/3 System to the specific requirements of your enterprise. The component contains the functions and tools with which you can control and edit the cross-application processes.
Implementation Considerations
Many application components of the R/3 System use and integrate SAP Business Workflow functions. Therefore, be sure to execute the function Maintain standard settings for SAP Business Workflow in SAP Business Workflow Customizing.
Integration
Integration of SAP R/3 Functions
SAP Business Workflow is incorporated at an integration level above the transaction level. The component uses the existing transactions and function modules. The functionality and operability of the existing transactions and function modules are neither changed nor restricted by the workflow control. SAP Business Workflow does not intervene in the programmed processes within a transaction.
The component SAP Business Workflow, as a cross-application workflow management system, hence separates the organizational aspects of the control logic from the application logic. The component makes the R/3 System easier to operate, which is particularly useful for inexperienced or occasional users.
Integration of Organizational Management
The integration of the application component Organizational Management into SAP Business Workflow allows you to link tasks with the agents possible from an organizational point of view. This link allows the workflow management system to find the "right" agents and assign tasks to them.
Tasks and agents are linked on an abstract descriptive level based on jobs and organizational units. It is therefore possible for several employees having equal authorization within the organization to receive the same task for execution. One of these employees takes on this task and processes it. This assignment principle supports automatic load distribution within work groups with the same activity profile.
This means a high degree of transparency of business processes, including responsibilities.
Changes to the organizational structure of the enterprise and employee turnover therefore have direct effects in SAP Business Workflow as well, without changes having to be made there.
Features
With this component, you can automate and coordinate several business processes:
u2022     Complete work processes executed frequently
The level of complexity of these processes can vary. It ranges from functions which must be called by the user to continue processing, to event-driven business processes in which the R/3 System determines the individual steps by evaluating process-dependent information, and various agents then execute all the processing steps required.
The processing of activities is not necessarily tied to specific persons, but perhaps only to organizational units, project groups, or job descriptions.
u2022     Subprocesses
Examples of these include release or approval procedures involving two persons.
u2022     Reaction to error or exception situations
hope it helps u...

Similar Messages

CONFIGURATION WORK FLOW IN ESS (LEAVE)

Hi gurus.
He wanted to know what form it's to indicate that a leave's class should not generate Work Flow when it's post from ESS.
In T554S_WEB it is possible to leave in white the fields of WF's codes. The problem is that there is a field in the above mentioned table, APPROVAL_PROCESS, that if has the value "W" (Workflow) , though the fields have been left in whiteof workflow, tries to generate a WF with code WS00000000.
The case is that the field APPROVAL_PROCESS is not located by me from what point of the parametrización it is possible to modify.
I am grateful for your help.
Thank you very much.

If you need this option then you need to change the WF Task.
General Forwarding Not Allowed
This indicator enables you to determine that work items for this task can only be forwarded to users who are agents for the task.
If this indicator is not set, a work item for this task can be forwarded to all users.
The best way to take care of User
Forwaring authorization is the Task Classification (PFTC -> Additional
Data -> Classification). Classify tasks with General Forwarding Not
allowed, will give you the oppotunity to let the user allow to forward
items JUST to the Possible Agents Assigned to the task
(Additional Data -> Agent Assingment -> Maintain)...
Clear that everything depends on How you have developed your workflows
definitions. In that cases the best think to do is
create Different Tasks definition (TSxxxxxx) and let they start
depending on Company Code (That can be driven via Conditions steps in
the workjflow definition, for example). This will allow you to define
Just the responsible Agents per each task, depending on the Companny
Code. This definitively Resolve the Forwarding frelated Question.

Data/Work Flow in SAP

Hi All,
Plz. explain the Data/Work Flow in SAP
Is there any difference between this if so explain,
and kindly tell me the process.
thank you,
Narender

Hii..
Work Flow- SAP Business Workflow
Purpose
SAP Business Workflow can be used to define business processes that are not yet mapped in the R/3 System. These may be simple release or approval procedures, or more complex business processes such as creating a material master and the associated coordination of the departments involved. SAP Business Workflow is particularly suitable for situations in which work processes have to be run through repeatedly, or situations in which the business process requires the involvement of a large number of agents in a specific sequence.
You can also use SAP Business Workflow to respond to errors and exceptions in other, existing business processes. You can start a workflow when predefined events occur, for example an event can be triggered if particular errors are found during an automatic check.
SAP provides several workflows that map predefined business processes. These workflows do not require much implementation. For an overview of these SAP workflows, refer to Workflow Scenarios in Applications.
Integration
SAP Business Workflow uses the existing transactions and functions of the R/3 System and does not change the functions. You can combine the existing functions of the R/3 System to form new business processes with SAP Business Workflow. The workflow system takes over control of the business processes. If you are already using SAP Organizational Management, you can use the organizational structure created there to have the relevant agents carry out the individual activities. It is possible to have an activity carried out by a position. This ensures that the respective occupiers of the position can carry out the individual activities during execution of the workflow. This means that personnel changes in your organization are taken into account immediately in the execution of a workflow.
Features
SAP Business Workflow provides a number of tools for defining and analyzing workflows as well as for monitoring operation.
The Workflow Builder is for displaying and making changes to workflows. You can make small extensions directly to the original workflows supplied by SAP, such as carrying out your own agent assignments or changing deadline monitoring.
There are several Workflow Wizards to support you in the definition of workflows, with which you can create specific parts of a workflow. The Workflow Wizard Explorer gives you an overview of the existing Workflow Wizards.
In order to make the functions of the R/3 Systems available to a workflow, you use business objects, which you can define and analyze in the Business Object Builder. These business objects are made available to the workflow in reusable tasks. The Business Wizard Explorer gives you an overview of all existing tasks.
The end user receives information about the activities they are to carry out in their Business Workplace. This provides them with a central overview of all the activities that they are authorized to carry out. They can commence the activities from here.
Several tools are available to the workflow system administrator, with which they can control and analyze the current workflows. The workflow system administrator is notified of problems automatically by the system.
DATAFLOW-Data flow means flow of data from one module to another within a sap system.
Regards,
Aakash

How to add repeat step in Schedule Manager - Flow Definition

Hi Everyone,
I am trying to design a Flow Definition in Schedule Manager which involves repeating a step based on the user decision. Please explain me how to achieve the following:
Change the task options (user Decisions)
Repeat a step based on the Task option.
Thanks,
Sandeep

Hai Krishna,
Step 1 : create condition at disired position i work flow.
step 2. cut the block which u want to place in that condition.
step 3 : paste the block in the condition
Thanks
Ramesh

Schedule Manager (add Tcode to Flow Definition step)

Hello together,
I have got a problem with the schedule manager ("scma").
I would like to add the Tcode cja1 (Project-Related Incoming Orders) alternatively the program "SAPLKAZB" to a flow definition step with a variant.But the program "SAPLKAZB" is used for more tcodes than "cja1".
How can I solve this problem?
Thanks in advance!
Greetings,
Peter

Hello,
The Program 'SAPLKAZB' cannot be added to the flow definition step since its function pool and not an executable program due to which you wont be able to execute it.
So its better the transaction 'CJA1' can be added to flow definition step and no alternative for program with varaint coz it wont work.
Regards,
Mansi.

How to reflect new changes in older instance of work flow?

Hi All,
I am working on a custom workflow.
This workflow is triggered by web dynpro component.
Earlier my custom infotype was getting updated from web dynpro, and work flow is used to maintain process flow.
But currently we started facing some authorization issue while updating infotypes for approvers.
So now i introduced an activity in work flow to update this infotype from work flow using WF_Batch
(calling method of a class to update the infotype), and commented the code to update infotype from web dynpro.
Now the problem is, i have few requests raised using older version of work flow,
in which the activity to update infotype was not there.
New requests are working fine, infotype is getting updated using work flow.
But in older requests when i am viewing from SWIA that new activity to update infotype is not visible.
How can i implement the changes to older instances of work flow?
Because for older requests in web dynpro also there is no code to update infotype as well as in older work flow instance
my activity to update infotype is not visible.
Waiting for help.....
Regards,
Amar

Hi Amar,
The changes will be reflected for new instances that are created after the transport of the new workflow definition.
The instances of old definition will continue as it is.
However a workaround could be that you can end the old definition instances by logically deleting them and start new workflow by T code SWUS or generating event by SWUE and go through the whole process again.
Re- triggering of the workflow seems to be only solution here .
Hope this helps.
Regards,
Sangvir Singh

Solution Manager : CHARM Work Flow - Mail sending

Hi All,
Can you please help me in CharM work flow - Mail sending?
I have created a Action definition say "Z_SEND_MAIL_TO CHANGE_MANAGER : Sending Mail to Change Manger " and given process type as Smart Forms Mail.
My Concern is in Condition Configuration.
I want to give the start confition for Z_SEND_MAIL_TO CHANGE_MANAGER action as
E0005ZDHFHEAD or E0004ZDHFHEAD or E0001ZDHFHEAD.
How do I give more than once condition ata time for an action.
Regards,
SK

Hi Team,
Looking for the details as earliest. Thanks in advance.
Regards,
SK

Info required on work flows

Hi all,
Can anyone provide me info on work flows . Any documents is highly appreciated.
Regards,
Rajashree

Hi Rajashree,
Workflow is a tool for automating the business process so that the process itself flows smoothly, without bottlenecks and without dead ends. Critical parts of the process can be streamlined with deadline monitoring and contingency options. Participants are informed of milestones in the process. The process definition itself is powerful enough to allow business re-engineering with re-training and to eliminate the impact of workforce changes on the basic business process.
SAP Business Workflow is the R/3 tool for handling the process automation within R/3 or between R/3 systems and other systems involved in the business process. It is flexible enough to handle ad hoc processes such as the circulation of an electronic document. It is robust enough to handle mission critical process in the production system such as the creation of a material master.
The different R/3 applications supply standard workflows for the commonly occurring processes. Once these workflow templates are activated, they are ready for immediate use. A complete set of workflow tools, including the workflow editor and workflow generation wizard, are provided to enhance these standard workflows or create new workflows. These tools are complemented with transactions for monitoring, tracking and the statistical analysis of the processes.
Because the business process often does not step at the R/3 boundary, various interfaces and third party tools are available for extending the process across systems.
Workflow is the technique for automating business processes. It is particularly beneficial
when different people are involved in different parts of the process
when a process only occurs sporadically and the users need to be reminded of what they need to do
when the duration of the process is critical and deadlines have to be met
when the process definition is likely to change on the fly and retraining users is not possible.
By automating the process, you free the users from having to know what to do when. Work items are sent to the participants notifying them of what they have to do, and a single click on the notification calls the correct transaction and navigates to the relevant screen.
When the workflow runs it creates work items which are like e-mails, but
they have the advantage that they contain the intelligence needed to execute the relevant task with the correct data when the operational user executes them,
they provide their own functionality so that the operational user has access to everything that is useful to improve the flow of the process,
they disappear on their own when they have been executed by someone else or made obsolete.
These work items can be received in the R/3 business workplace, MS Outlook (or any other MAPI compatible client), Lotus Notes, or work item notifications can be distributed by e-mail.
SAP Business Workflow:
accelerates the workflow across applications, functional areas, organizational units, and time periods,
supplements the integrated management of processes in the SAP System with individually tailored options for automating and actively controlling business and communication processes,
combines integrated organizational management with flexible assignment of tasks and responsibilities to locations, positions, jobs, groups, or individuals,
actively supports a quick implementation of workflow technologies through predefined workflow templates, Workflow Wizards and flexible adjustment options,
integrates every employee in the value chain by providing a versatile integrated inbox ("universal inbox") at their work centers that can be configured individually,
provides a Workflow Information System that is the foundation for process change management and continuous business engineering,
was designed to be a change-management tool,
simplifies continuous business engineering and process change management with user-friendly tools for defining and dynamically changing workflow tasks
conforms to the workflow standards of the Workflow Management Coalition (WfMC)
interfaces to other mail clients such as Lotus Notes and MS Outlook
Check these links.
http://www.sapgenie.com/workflow/index.htm
/people/ginger.gatling/blog/2005/12/01/link-workflow-business-objects-to-your-collaboration-tasks
http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm
http://www.sap-press.com/product.cfm?account=&product=H950
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
For examples on WorkFlow...check the below link..
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
Workflow tutorials with step-by-step and with screenshots are available at
http://www.****************/Tutorials/Workflow/Workflow.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/42/c14a9b55103116e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/e4a930453d11d189430000e829fbbd/frameset.htm
Hope this resolves your query.
Reward all the helpful answers.
Regards

Closing Cockpit/Scheduler Manager Flow Definition

Hello,
I am having a problem with CLOCOC flow definitions. I created a flow definition that sends notifications in case of a task is overdue but I need to access the information of the task, namely the person responsible to know who to send the email.
The problem to do this is that the workflow container doesnu2019t have the info from the task required it only has the WF Initiator. Anyone know a way to work around this problem and get the person responsible for the task?
Best regards,
Ricardo Candeias

Hello,
Normally for a workflow you would look in the Workflow Builder to see if the agent is assigned using a container element.
Then use that same container element for the mail.
regards
Rick Bakker
hanabi technology

Work flows in E-sourcing

Hi,
I need a sample exercise to work on E-Sourcing work flows.
Please share the links or material which will help me to work on work flows.
Regards,
Naresh

Dear vaibhav,
Thanks for your reply. I sincerely appreciate you in analyzing and giving the detailed reply.
Please let me know pre script and post script are defined after uploading the xpdl file into esourcing or need to be defined in XPDL file itself.
Please clarify on the following points.
Point 1:You have to add a attribute in that task called Pre-Script
and in that value you have to write logic for retrieveing MA_02_01 from ES
My understanding :-
I need to define a a workflow variable for MA_02_01.But where is pre script available in the XPDL definition.
We need to create an activity (no Implementation )called preScript and we need to pass this variable to this activity.
Point No.2 :-
Also in the task test_contract1_wp1_act1 you have to add a attribute Pre-Script
and write logic to retrieve the extended filed in the document and add it as a approver.
No idea what needs to be done for accomplishing the above.
Also what is the use of post script. as per my knowledge once approved it should go to executed phase or rejected it should go to draft phase can be defined here.Please let me know how to define this.
grateful if you could send one sample xpdl file which contains definitions of prescript and post script.
Thanks in advance and happy diwali
venkat.

Error in work flow wait for change event

Error in work flow wait for change event of business object bus1014, Actually this business object is triggering for two transaction one is me21n and another is c201 . am trying to create fork with two branches one is create and another if change occurs wait will trigger, bt when i trigger work flow controll is not after fork, it will stop in fork only. and am not getting my workflow container variable getting instantiate, am getting error in wait. please any one get out of me in this

Hi Sangeetha
What is LV_MATERIAL? is it a BO container element? or a class element or a just a simple variable?
Error message is clear, you are trying to evaluate LV_MATERIAL but it does not contain a value.
This is a custom workflow as it begins with WS9xxxxxxx... what is LV_MATERIAL used for? what are we expecting it to hold? maybe, from event to workflow binding we can pass the value to it.
Please share the following:
1) Definition screen shot of LV_MATERIAL
2) Screen shot of The step where it is first used - from SWDD
3) Screenshot of Event to Workflow Binding
4) name of your base Business Object (seen in the triggering events tab of the WF template in PFTC)
5) What is the corresponding variable for that BO in your workflow container
6) Screen shot of WF definition from SWDD - please identify the step going in error in that screen shot
Regards,
Modak

Work flow configuration

hi all,
I have a problem regarding the work flow configuration as from work flow developer i am taking a role of work flow adminstration for a new role out. I have problem configuring the swu3 tcode for new SAP ECC6.0. please let me know what are the necessary work bench requests and custom requests needed to be done and transported to production.
I have a problem with the new configured SAP ECC 6.0 in swdd the view is not changing from Tree mode to Graphical mode please help with this issue.
Thanks for your help in advance.
Krishna C M

Hello Chaitanya,
The option to change the modeling view is disabled in ECC 6.0, which is Graphical(Network) by default. But you can have a similar type of view of the steps in the displayed in the workflow definition under the navigation area tab. This is present to the left in the screen of workflow builder under the Information area.
From the SAP online help you can see that "You can only use the graphical modeling view if you are working with the SAPGUI for Windows. If you call the Workflow Builder using a different SAP GUI, the tree view is displayed automatically."
But still if you want to see the tree view of a workflow definition just change the tab "Graphical Tab" to "Tree Modelling" which is present at the top of the workflow graphical diagram beside the Information area tab.
Hope this will help you.
Regards,
Samson

Hi all ,i need a good documentation for a beginner in WORK FLOW ?

hi all ,
i need a good documentation for a beginner in WORK FLOW ?
please,try to send the attached documents as much as u can apart from giving the weblinks ?
hope you will send it soon ....
thanks & regards
vishnuvardhan k.v.

Hi
Developing a simple application using steps "User Decision" and "Mail"
Basic terminology used in the workflow:
The workflow definition is the set of rules that determine the path that the process takes. For example, how a purchase requisition is processed, from the initial request to the creation of the purchase order
A Workflow Instance, which is often simply referred to as the workflow, is a single workflow run. For example, the processing of a single purchase requisition for computers.
The Tasks are the steps in the process, which have to be performed either by people or automatically by the software. For example, to check for the availability of the spare computers in the company.
A Work item is the task instance that is performed as a single workflow step. For example, check that there are no spare computers available in the company.
Agents are the people who process the tasks (via the work items). For example, requisitioner and a member of the purchasing department.
Container is the place where all the data used in the workflow is collected.
Binding is the set of rules that define which data is passed to which part of the process.
Building a simple workflow application
The central tool for creating, displaying and processing a workflow is the workflow builder (Transaction SWDD). Within the workflow builder you can create all components of a workflow, including all the containers you need for getting the data from one step to another.
Generally, most of the workflows are started by an event (for example, when a material is created or when a new purchase requisition arrives). You define which data from this event needs to be passed to the workflow via binding.
However you can also start any workflow directly. Let us create a simple workflow and start the workflow directly, using the testing tools.
Call transaction SWDD. When the workflow builder is called for the first time, a newly created initial workflow definition appears or else last created workflow appears. In such cases you can opt to create a new workflow by pressing Create New Workflow(ctrl + shft + F5). The following screen appears.
The initial workflow screen has the following parts:
a. The start of the workflow definition, indicated by .
b. The end of the workflow definition, indicated by .
c. The area in which you insert the new workflow definition is indicated by .
Now select the undefined step and select Create step or double click the undefined step. Now among the different steps chose the User Decision by double clicking on it.
Developing a simple application using steps "User Decision" and "Mail"
Previous
Now enter the title for the user decision Please make a decision. Also enter the decision texts as Approve and Reject. On pressing enter, the outcome values default to the Decision texts but you can specify your own names, if desired. Now we need to select the agent. Agent is the person to whom the work item needs to be sent.. Since this is just a beginning, we would hardcode the user name. Select the User from the drop down list and enter the user name to whom the work item needs to be sent. In general, this type of agent assignment is not done. Agents are generally assigned using the expression, agent assignment rule or organization object (job, position etc.).
Now select Transfer and to graphic button. Following screen appears:
Now we need to include a mail step to be sent to the requestor. Now select the line Approve and do a right click. Different options on shown on the context menu. Select Create.
Now select the step Send Mail from the list.
Developing a simple application using steps "User Decision" and "Mail"
...Previous
Now enter the subject and the body of the message for the mail to be sent.
Do not change the recipients. Our mail is intended for the persons who triggered this workflow. &_WF_INITIATOR& contains the value who executed the workflow. Since this is a test object, we are using &_WF_INITIATOR&. But we wouldnt be using this variable in real time scenarios. We would discuss about this in the coming documents.
Now select Transfer and to graphic button.
A popup appears requesting for the abbreviation and the name for this task. Enter the same and press enter.
Now enter the package as local object and press enter.
Follow the steps 5 through 9 for the step Reject. The following screen appears:
Press SAVE to save the workflow application. You need to enter an abbreviation and name for your workflow as shown below. You can change any of these at any later point. After saving, a number is assigned to your workflow starting with WS, as shown below.
Developing a simple application using steps "User Decision" and "Mail"
...Previous
To execute the workflow, activate it by choosing the activate button.
Test the workflow by choosing Test. The following screen appears.
Now choose Execute to start the workflow.
Now the recipient would receive a work item in his SAP® inbox (Transaction SBWP).
Now execute the work item by pressing Execute. The following screen appears:
Choose one among Approve or Reject as part of the user decision. He can select the third option to retain the work item in his inbox and make the decision later. Now suppose that the recipient has chosen one of the first options. Now a mail would be sent to the requestor with the status of his request.
Creating a Container element
This document details about creation of a container element in workflow and using it in the step "Mail".
Pre-requisites:
It is assumed that the reader of this Tutorial is aware of creating a workflow definition with the step Mail. If not, please go through the document on creating the same available, by clicking here.
Steps:
1. Create a workflow definition using the transaction SWDD.
2. Lets create a container element for Carrier id. Click on the Workflow Container on the left side of the screen (as shown in the screenshot below):
3. Now double-click on Double-Click to Create
4. Enter the details pertaining to CARRID here.
5. Click on tab Properties and select Import.
6. Click on Confirm (Enter).
7. Now the element created could be seen on the left side, below the Workflow Container.
Creating a Container element
Previous
1. Create a Mail step by double-clicking on Undefined step in the workflow.
2. Enter the recipient details in the Recipients box.
3. In the subject line, enter Carrid value entered is: and click on Insert Expression.
4. Select the element Carrid from the list.
5. Similarly enter the content in the Body area.
6. Save and activate the application.
Testing the Workflow application:
7. Test the workflow by clicking F8.
8. Enter the value of the Carrid as shown above and press execute.
9. A mail would be sent to the recipient mentioned earlier with the carrid value entered.
Condition Step
Agenda:
This document details about the steps Condition.
Pre-requisites: It is assumed that the reader of this document has a preliminary understanding of workflow and has worked with the container elements earlier. If not, please go through the first two Tutorials of workflow available in this site. (More details)
Procedure:
1. Create a new workflow definition.
2. Create a container element, CARRID (as demonstrated in tutorial 2).
3. Now click on undefined step and create the step Condition.
4. Enter the step name of your choice.
5. We would have the following condition here:
If carrid = AA.
Do this.
Else.
Do this.
Click on Click here to create a new condition. Following screen appears.
Double click on Carrid. Next click on = and enter the value AA in the constant field and press ENTER.
Enter the outcome names of your choice as shown above.
Click on Transfer and go to graphic.
As shown above, there are two branches here. One navigates to true, if CARRID = AA else the control takes the branch False.
Test the above scenario by inserting mail steps in the above 2 branches and by passing different CARRID values.
Condition Step
Agenda:
This document details about the steps Multiple Condition.
Pre-requisites: It is assumed that the reader of this document has a preliminary understanding of workflow and has worked with the container elements earlier. If not, please go through the first two Tutorials of workflow available in this site. (More details)
Procedure:
1. Create a new workflow definition.
2. Create a container element, CARRID (as demonstrated in tutorial 2).
3. Now click on undefined step and create the step Multiple Condition.
4. Enter the step name of your choice.
5. We would have the following condition here:
If carrid = AA.
Do this.
Elseif carrid = AH
DO this.
Elseif carrid = SQ
Do this.
Else.
Do this.
Select the CARRID using the F4 help for the comparison basis field.
Enter the values of the carrid under the Comparison values with the corresponding outcome name (of your choice)
Double click on Carrid. Next click on = and enter the value AA in the constant field and press ENTER.
Click on Transfer and go to graphic.
As observed above, there are different branches for each value of CARRID mentioned above.
Test the above scenario by inserting mail steps in all the branches and by passing different CARRID values.
Using "Container Operation" step
Agenda: Usage of step Container Operation.
Pre-requisites: It is assumed that the reader of this tutorial has worked in the concepts that are dealt in earlier tutorials. (click here for more details)
Scenario: In this tutorial, we would deal about how to work with the step Container Operation with an example of calculating the available seats by subtracting occupied seats from the maximum seats at the workflow level.
Procedure:
1. Create a new workflow definition using the transaction SWDD.
2. Create two container elements MaxSeats, Occ_Seats with the import property set. You can use the reference fields sflight-seatsmax, sflight-seatsocc for this.
3. Create another container element AvailableSeats without setting either import or export property as this is calculated within the workflow and used within the workflow. You might use any of the above reference fields as data types.
4. Define a new step Container Operation in the workflow definition by double-clicking on the Undefined step.
5. In this step, we would calculate the available seats from the max seats and seats occupied.
I would recommend entering all the container elements from the F4 help instead of typing them manually.
6. Return to the main screen.
7. Create a mail step after this to send the available seats information.
8. Test the above functionality by passing some values to the maximum and the seats occupied.
9. Result would be as follows:
Triggering Events Programmatically
Purpose: This document details the procedure in triggering the business object events programmatically.
Pre-requisites: It is assumed that the reader of this document is aware of the business object concepts and good in ABAP.
Procedure:
In this document, we would take an example of the business object BUS1001006 (Material) and the event CREATED. In general, this event is triggered whenever a material is created using a standard procedure like MM01 or any others. Now we would trigger this event from our own programs.
Following are the screenshots of the business object BUS1001006 and the event CREATED. Go to transaction SWO1 for more information of the business object.
Double-clicking on the key field parameter gives you technical information of the field.
In order to trigger an event programmatically, we would use the function module SWE_EVENT_CREATE.
Following is the sample code to trigger the events programmatically:
REPORT ZDEMO_TRIGGER_EVENT.
DATA: KEY LIKE SWEINSTCOU-OBJKEY.
KEY = '1163'. Material Number (hard-coded)
CALL FUNCTION 'SWE_EVENT_CREATE'
EXPORTING
objtype = 'BUS1001006'
objkey = KEY
event = 'CREATED'
CREATOR = ' '
TAKE_WORKITEM_REQUESTER = ' '
START_WITH_DELAY = ' '
START_RECFB_SYNCHRON = ' '
NO_COMMIT_FOR_QUEUE = ' '
DEBUG_FLAG = ' '
NO_LOGGING = ' '
IDENT =
IMPORTING
EVENT_ID =
TABLES
EVENT_CONTAINER =
EXCEPTIONS
OBJTYPE_NOT_FOUND = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
WRITE 'Event Triggered'.
ENDIF.
COMMIT WORK.
In order to test whether the event is getting triggered or not, we can make use of Event Trace. Switch on the event trace using the transaction SWELS.
Press Switch On.
Now execute the program developed earlier. Now switch-off the event trace using the same transaction SWELS.
Now go to transaction SWEL. Here you can list out the events triggered in the particular period of time. Here is the event-trace list:
Deadline Monitoring in SAP Workflow
A major advantage of workflow is the ability to monitor the workflow steps according to a predefined schedule. Following are different deadlines that can be monitored against each workflow step:
Requested Start
Latest Start
Requested End
Latest End
In this example, we will define a deadline to the User Decision example created earlier (click here). Following is the screenshot of the application developed using the User Decision example:
We would extend this example to the deadline monitoring.
In the User Decision step, click on the latest end tab.
By default, No deadline monitoring is active (as seen in the above screenshot).
Choose the Work Item Creation from the list box.
After selecting Work Item Creation, chose an offset of 5 minutes. This means that the work item must be executed within 5 minutes of the creation, if not this would trigger.
Deadline Monitoring in SAP Workflow
Enter recipient details to whom the message to be escalated, if the work item is not executed with in 5 minutes after work item creation.
Save and activate the workflow definition.
Testing the workflow application:
Execute your workflow.
Check for the work item in the SAP Inbox. This time do NOT execute the work item.
Wait for the deadline to be triggered. After that, a deadline message is delivered to the recipient mentioned in the Latest End tab. See the screenshot below.
Dont worry if the deadline message doesnt appear immediately after 5 minutes. This depends on various factors including how the deadline monitoring program is scheduled and also on the availability of the background processors.
Use SWWA to check how the deadline monitoring program is scheduled in program.
For example, assume that our work item has been created at 09:10 hrs and the deadline message is expected to trigger at 09:15 hrs. From the above screenshot, it is understood that the background program is scheduled to execute for every 3 minutes. Assume that the last run of the program is at 09:14hrs and the next run is expected at 09:17hrs. So even our deadline expires at 09:15, the deadline message would appear only at 09:17hrs after execution of the background program.
Some more points
In our above example, we have used the deadline on the Work Item creation time. i.e., 5 minutes after creation time, the deadline message would be sent. Now we would check the other option Expression. Here we can mention the date and time, when the deadline message should appear irrespective of the work item creation date/time.
As seen in the above screenshot, we can provide the target date and time by which the task should be finished. Container elements could be used in this case. Please refer to our example on creation of container elements (click here).
Personal Substitute in Workflow
Requirement: Need to have at least one substitute who can act upon work items in your absence.
Important: The appointed substitute would be able to see all your work items. A substitute cannot be assigned for only particular area of organization or any other item. So need to ensure that the substitute have the necessary authorizations to act upon the work items.
Procedure:
1. Go to SAP Business Work Place (TCode: SBWP)
2. Now from the menu bar, select Settings à Workflow settings à Maintain Substitute
3. Highlight/Select the name on the window, in this case SAPDEV02 and click on Create Substitute.
4. List of users available in the system are displayed.
5. Select the required substitute user name. Following screen appears.
Validity field describes about the period in which the setting would be active. Note that the dates on the screen would range from the current date to 31st Dec 9999.
Regarding the checkbox Substitution active, it is advised to leave this checkbox unchecked for system performance reasons. A check in this box indicates that the substitution is permanent and if left unchecked it is treated as as-needed. A permanent substitute will automatically receive the primary users work items in their own box. In the case of as-needed, substitute must manually adopt the work items from the primary users inbox.
6. Save the entries
7. Click Enter to leave the screen.
Adopting a Substitute in Workflow
If you have been designated as an as-needed substitute, you must manually adopt the substitution. If you are designated as a permanent substitute, the work items would automatically appear in the inbox.
Before adopting a substitution, there are 19 work items in the inbox. See the screenshot below:
To adopt a substitution, select Settings à Workflow settings à adopt substitution.
Select the corresponding User-id (if you have been assigned as a substitute for multiple people, then this option would allow you to select the user name of whom you would to check the work items)
The corresponding users work items would appear in our inbox now.
You can end the substitution, by selecting settings à Workflow settings à End substitution.
Note: Substitutes can only adopt work items that are directly routed to the person for whom they are a substitute. If you are a substitute for a user (SAPDEV02) who has been made a substitute for another user (SAPDEV01), you will only see work items for user SAPDEV02 and not of the user SAPDEV01.
Notification of Work Items via e-Mail
SAP provides us with a facility of notifying the user via the email address of your choice when there are any pending work items in the SAP Inbox..
1. Go to Transaction SO13.
2. Click on Automatic Forwarding tab.
3. Click on Create icon .
4. Enter the details in the above screen.
5. Click ENTER to complete the entries.
6. Now the notification would be received at the provided email address if there are any pending work items in the inbox.
Filtering the Work Items in the SAP Inbox using BADI
This document details about the procedure in filtering some of the work items from the SAP inbox using a BADi.
Following is the screenshot of the SAP inbox, before implementing BADi:
The BADi that is used in filtering the work items is WF_BWP_SELECT_FILTER. To implement the BADi, go to transaction SE18. From the menu, select Implementation à Create. (See the screenshot below)
Enter the implementation name and press ENTER
Enter any meaningful short text for the implementation and click on the tab Interface
The implementing class, ZCL_IM_BWP_SELECT_FILTER, is automatically proposed. Double click on the implementing class name.
You are now navigated to the class builder. Now double-click on the method name shown on the screen (see the snapshot below)
Now let us filter out the work items belonging to the task TS2000066. See the code below:
Activate the method and also the implementation. In the state of active, you wouldnt be able to make any changes. To make any changes, we need to deactivate it and then make the changes.
Now check the inbox and would notice that the work items related to that task are no more appearing.
To notice the differences, try activating and deactivating the BADi implementation.
Workflow tutorials with step-by-step and with screenshots are available at http://www.****************/Tutorials/Workflow/Workflow.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/42/c14a9b55103116e10000000a1553f7/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/c5/e4a930453d11d189430000e829fbbd/frameset.htm
http://www.sapgenie.com/workflow/
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2857887
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2855919
https://forums.sdn.sap.com/click.jspa?searchID=791580&messageID=2735228
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
debug a workflow.
This has a step by step procedure :
http://fuller.mit.edu/workflow/debugging.pdf
www.erpgenie.com/sap/workflow/debugging.htm
http://www.erpgenie.com/workflow/debugging.htm?2b5de440

Work Flow & Procedure For Transportation Module Of SD

Dear All,
Currently, we have just got SD implemented. Now, we shall like to go for the Transportaion Module i.e. Order Booking, delivery and the PGI followed by Auto Invoicing. Now, we wants to go for Transportation Module i.e. Shipment Creation, Shipment cost calculation , Service Order Creation etc. As we are quite new to this. So, we shall like to know the complete work flow & the procedure for implementing the same. i.e. in what sequence the various transactions to be used for Master / Transaction.
Please advise further.
With Best Regards,
Sanjeev Chugh

Thanks for the reply. Definitely, i can share the details to the best of my knowledge about the transportation module.
This module is basically meant for controlling purpose. Our main objective is to control the Transportaion Charges. Vendor Invoice must be cross verified from the sytem as well.
Our Current Business Process : As per business process, we are having fixed rates per transporter for the type of vehicle and the source - destination combination. So, whenever, we are stock transferring the material from our mfg. plants to various depots, we are using various transporters (some one are specialised for south, some are spl. for east, so on and so forth). On the receipt of the material, receiver i.e. the destination branch , confirms the material receipt.. MIGO / MIRO etc. . We wants to capture the cost of the shipment as per the system and then on the receipt of the bill from transporter, the same must be cross verified.
On going thru various documents from Web, I could gather the following details :
1. After making deliveries, we have to make a shipment document. In our case, max. time it shall be an individual Shipment i.e. Tcode VT01N. Other type of shipment be Collective Shipment, which we use very less no. of times.
2. We have to prepare Shipment Cost document by using Tcode VI01
3. We have to create a service Purchase Order By using ME21N.
In our business scenario, we shall not be using legs concept as our shipments generally used to be from point to point basis.
Sir, logically, i know our needs.. But getting stuck at a couple of points ... Like where to define various rates per transporter..That's why, i named the subject as the Work Flow & Procedure for Tpt.Module.
I shall like to request you to kindly advise further in this regard or kindly let me know if some study material is available from where i can comes to know about the exact work flow of the Transportation Module As Such.
From Where I Can Get Help on Any Tcode Usage i.e How to use a Tcode and what be its basic functionality.
With Best Regards,
Sanjeev Chugh

ESS - Leave Administration - Work flow item

Hi experts,
My PM asked me to prepare a document on ESS i got some inputs from different threads.
Now I need an input regarding workflow item
In Leave Administration after approval of the leave employee can delete the information which was work flow id as assigned to services the id is WS1000109
Which work flow id should assign to services.
Please help me in this regard

Hi
There are two things
1. Workflow ID - Employee can't delete a WF ID can delete WF items
2. Workflow item - No need to assign workflow item to a service , coz this would be done by the system internally for all the modules .
Goto Extras -Workflows of this definition & execute
here you will find out the latest WF item & text for that WF
regards
durai

Work flow definition.

Similar Messages

Maybe you are looking for