Work process is a tool for the automation of the business procedure, comprising of arrangement of steps, task or event. One comparative case to work process is the automated lines in the assembling business with station focuses or stacking focuses. You can organize and deal with the dependency of task. Clients can be sent notification for the task waiting in the SAP inbox for approval or action. users can be educated of developments all the while. By automating the procedure, you free the clients from knowing what to do when. Work items are sent to the members telling them of what they need to do, and a solitary tap on the notification calls the right exchange and explores to the important screen. WebFlow is the web usefulness of SAP Business Workflow.
 |
SAP Workflow |
Some mistakes made by SAP Workflow Beginners:
1. Trying to muddle through work process utilizing only your ABAP skills
Most common errors, users always do that they use ABAP knowledge to debug that workflow log & figure out how it all fit together. workflow is more about 'ideas' and 'arrangement' than it is about 'code'.
2. Confusing workitems with emails
An exceptionally basic error. Put essentially, a workitem is a solitary bit of work – commonly a decision task – that can be seen from numerous inboxes, and vanishes when one specialist forms it. Workitems must be sent to SAP framework clients. Conversely, emails are regularly flat information items. Various duplicates are made and sent independently to inboxes. They stay in every individual's inbox until separately perused or erased. Emails can be sent to anybody.
3. Not executing SWU_OBUF before testing your workflow changes
I once in a while hear that workflow is 'flaky' or 'unpredictable'. Also, it certainly is – in the event that you have no comprehension of how buffering functions. This applies during development, yet in addition in Test or Production frameworks after a workflow has been transported in. The entire cradle is invigorated at midnight.
4. Flooding clients' inboxes with many workitems
I've learnt the most difficult way possible that not all endorsement/choice procedures are suited to work process. On the off chance that several things are created every day for one process, it's likely better to deal with them by means of a report. It might simply be a psychological thing, yet clients respond fiercely to inboxes that they can't in any way, shape or form clear. They either quit utilizing their inboxes totally or commotion to get the work process turned off. No news is superior to a tidal wave of terrible news.
5. Not changing the default 'Receiver error feedback' setting in SWEQADM
On the off chance that you begin a workflow by means of an occasion, and something turns out badly, the default SAP reaction is to deactivate the linkage between the occasion and workflow. In SWEQADM, the setting ought to rather be 'Mark linkage as having mistakes'. This implies the linkage won't be cut, and the events will be put away until the point that they can be securely conveyed later.
6. Beginning workflow straightforwardly from a program, rather than utilizing events
Many sites in workflows (and even TS* standard tasks!) are begun specifically by a call to SAP_WAPI_START_WORKFLOW. Bzzzt. It is far superior to trigger workflows utilizing events.
There are a large number of reasons behind this, however right now I can just consider five:
– you can without much of a stretch switch a workflows on/off (even in Production) by (de)activating the occasion linkage.
– you can without much of a stretch change from an old workflow to another one, by controlling the occasion linkage.
– you can pick new workflow to be begun by a similar event.
– if a workflow doesn't begin for reasons unknown, you can look at the occasion log (SWEL)
– there are no approval issues with beginning workflows.
7. Falling behind in the housekeeping
It isn't right to accept that if clients are not detailing any issues, at that point the workflows must be humming along. You must be proactive and go out searching for mistakes, particularly when another work process goes live.
8. Using internal function modules (and tables) instead of SAP_WAPI*s
A common question is: what table holds the workflow container value? Who has test code for work SWE_EVENT_CREATE? Bzzzt (once more). Designers ought not to upset inner SAP work modules or tables. These could be changed on the following discharge, which implies your code may stop working. These are the SAP work process likeness BAPIs: function modules that give an archived benefit, with an interface that is ensured not to change. For instance: SAP_WAPI_CREATE_EVENT,SAP_WAPI_READ_CONTAINER,SAP_WAPI_GET_WI_AGENTS.
9. Not putting enough data in the workitem content
The three 'R's of workflow are that work arrives on the work area of the 'right' person at the 'right' time, and that all the data they have to settle on a choice, is 'ideal' there readily available. A decent workitem content contains all – yes all – of this data. The client shouldn't have to go anyplace or click anything. (Tip: utilizing webdynpros to render workitems makes rich shows a considerable measure simpler). On the off chance that that all appears an extension too far, at any rate give hyperlinks to all the significant business objects. This implies the data is just a single tick away.
10. Agreeing to develop custom workflow reports.
This is one of my pet abhors.We get brought in to 'fix the workflows' and things being what they are the primary issue is really with a dodgy workflow report. In the event that you, as a workflow developer, give in to these solicitations, you will soon be up to your armpits in Z tables and refresh BADIs. Be that as it may, this agony includes no an incentive by any stretch of the imagination.
What we promise at SAPVITS
1) We offer convenient batches and timings for the classes are arranged upon the flexibility of both the Trainee and the Trainer according to their availability.
2) We offer free online demo session, Trainee can attend the demo session, asses the Trainer and after that join the course.
3) We offer excellent course material and also share project scenarios which are like what you work when you go to the corporate environment.
4) We share recorded videos of each training session so that you can review them later as well. The videos created by experts make it easier for the learning professionals.
The SAP Workflow Course is suitable for Fresher’s and professionals wanting to get highly paid jobs. SAP Workflow Online Training is available in several approaches. Contact us for more details regarding SAP Online Training in UK, India, USA.
For more details, contact us:
India +91 992 284 8898
USA +1 678 389 8898
UK +44 141 416 8898
