Explore topic-wise InterviewSolutions in .

If you are approving from the ESS which is deployed in Enterprise PORTAL, you should ALSO deploy UNIVERSAL WORK List. It is only then that the Leave APPROVALS will work properly.

If you are approving from the ESS which is deployed in Enterprise Portal, you should also deploy Universal Work List. It is only then that the Leave Approvals will work properly.

No. What you can do is restart the workflow USING SWUE. This will be the same as recreating the workflow because it will START at the POINT where it has logically been DELETED.

No. What you can do is restart the workflow using SWUE. This will be the same as recreating the workflow because it will start at the point where it has logically been deleted.

You can ACCOMPLISH this by SETTING up the work ITEM priority to the HIGHEST level.

You can accomplish this by setting up the work item priority to the highest level.

You may consider USING DEADLINE monitoring facilities. For example:
Requested start, requested end;
Latest start or latest end on TASKS;
Apply whichever may be applicable to your case.

You may consider using deadline monitoring facilities. For example:
Requested start, requested end;
Latest start or latest end on tasks;
Apply whichever may be applicable to your case.

The only standard WF that comes CLOSE is 200038 but it could be too ROBUST for what you are trying to achieve. You may want to create your own WF and (at some POINT) call the method APPLICANTEVENTCREATE. This method is similar to PB40 but WITHOUT the FIRST screen.

The only standard WF that comes close is 200038 but it could be too robust for what you are trying to achieve. You may want to create your own WF and (at some point) call the method APPLICANTEVENTCREATE. This method is similar to PB40 but without the first screen.

You can create a start condition (transaction: SWB_COND) and SET it to start if the notification TYPE is M1. Just make sure to document this because months from now you might not REMEMBER why it STARTS selectively for some and not others. For the second question - if you are trying to notify the agent that they have a task, then try placing this standard task into a custom 2 step workflow template. The first step of the template should send an express mail then the next step should automatically send the task.

You can create a start condition (transaction: SWB_COND) and set it to start if the notification type is M1. Just make sure to document this because months from now you might not remember why it starts selectively for some and not others. For the second question - if you are trying to notify the agent that they have a task, then try placing this standard task into a custom 2 step workflow template. The first step of the template should send an express mail then the next step should automatically send the task.

Yes it is. From the WORKFLOW builder menu, choose Workflow > Import/Export and export to an XML file. You can also import from an XML file into a DIFFERENT system in which case the builder will create a new workflow in a 'New, Not Saved' status. Then when you save it, it will assign the UNIQUE IDs for the workflow and each task.
You might also consider getting the program LOGIC for any custom business objects. You can do this by going to the basic data of the business object and doubleclick the program name. From here, you can choose download from the utilities menu to get the program which includes the custom methods, ATTRIBUTES, etc.

Yes it is. From the workflow builder menu, choose Workflow > Import/Export and export to an XML file. You can also import from an XML file into a different system in which case the builder will create a new workflow in a 'New, Not Saved' status. Then when you save it, it will assign the unique IDs for the workflow and each task.
You might also consider getting the program logic for any custom business objects. You can do this by going to the basic data of the business object and doubleclick the program name. From here, you can choose download from the utilities menu to get the program which includes the custom methods, attributes, etc.

You can follow these steps:
1. Go to transaction PSO4 (Maintain INFOTYPE);
2. Then go to Object Type - RY (Responsibility);
3. Proceed to Object ID - This is the organizational id of your responsibility. The abbreviation will be the same as that of your rule. Use F4 to GET the ID.
4. Execute and CHANGE the infotype, selecting 1001 (Relationships). Change the validity here. LASTLY, you might need to wrap the whole operation in a BDC or something for automation.

You can follow these steps:
1. Go to transaction PSO4 (Maintain Infotype);
2. Then go to Object Type - RY (Responsibility);
3. Proceed to Object ID - This is the organizational id of your responsibility. The abbreviation will be the same as that of your rule. Use F4 to get the ID.
4. Execute and change the infotype, selecting 1001 (Relationships). Change the validity here. Lastly, you might need to wrap the whole operation in a BDC or something for automation.

Yes, WORKFLOW is position BASED. THEREFORE any turnover will not affect the workflow unless the person who has quit the JOB is the only person for the position you are talking about. Check the transaction as reference for PPOCE/PPOME for organizational STRUCTURES.

Yes, Workflow is position based. Therefore any turnover will not affect the workflow unless the person who has quit the job is the only person for the position you are talking about. Check the transaction as reference for PPOCE/PPOME for organizational structures.

You can CHANGE the status in table TOJTB > Field OBSOLETE and the object can be edited again. However, this is not recommended and there MIGHT be unknown IMPLICATIONS.

You can change the status in table TOJTB > Field OBSOLETE and the object can be edited again. However, this is not recommended and there might be unknown implications.

Go to “Latest end” tab in workflow STEP properties. From there set the DEADLINE parameters INCLUDING a RECIPIENT for missed deadline items. Alternatives will then be set.

Go to “Latest end” tab in workflow step properties. From there set the deadline parameters including a recipient for missed deadline items. Alternatives will then be set.

You already started TROUBLESHOOTING in the right TRACK. CONTINUE on and check the linkage if it is active or not. After that, it will TRIGGER AUTOMATICALLY.

You already started troubleshooting in the right track. Continue on and check the linkage if it is active or not. After that, it will trigger automatically.

CHANGE the PRIORITY of the STEP to 'Highest' in the 'Other' TAB.

Change the priority of the step to 'Highest' in the 'Other' tab.

In your custom program SET the parameters for type and ID (sap TRANSACTION. SWI5) and call the same transaction, USING call transaction statement.
Use the Type US and assign ID as its user name.

In your custom program set the parameters for type and ID (sap transaction. SWI5) and call the same transaction, using call transaction statement.
Use the Type US and assign ID as its user name.

This is not usually done. HOWEVER, you can TRY to WORK around this. Create one abap report BASED on transaction .SWI5 and SWI14. Use transparent tables SWWWWIHEAD, SWWWLOGHIST and some more, which will display all work item executed by that user.

This is not usually done. However, you can try to work around this. Create one abap report based on transaction .SWI5 and SWI14. Use transparent tables SWWWWIHEAD, SWWWLOGHIST and some more, which will display all work item executed by that user.

Yes you can. You can RETRIEVE Actual AGENT name after workitem EXECUTION. It’s name is _WI_Actual_Agent. Move it VIA task parameter BINDING.

Yes you can. You can retrieve Actual agent name after workitem execution. It’s name is _WI_Actual_Agent. Move it via task parameter binding.

You can use report RSWUWFML2 instead. It's available on 4.6C with BASIS support PACKAGE 47 or you can import support SECTION using transport attached to NOTE 691774.

You can use report RSWUWFML2 instead. It's available on 4.6C with basis support package 47 or you can import support section using transport attached to note 691774.

You need to create parameters in BO event and pass position to this. From the event CONTAINER, you can then map to the workflow container.
Under normal CIRCUMSTANCES, you would create an ELEMENT in the WF and LINK it to the one in your object. But this would mean that:
1. The element exists in your object as a parameter of the event that will trigger the WF;
2. That before you fire off the event, you populate the parameter of the event with the position;

You need to create parameters in BO event and pass position to this. From the event container, you can then map to the workflow container.
Under normal circumstances, you would create an element in the WF and link it to the one in your object. But this would mean that:
1. The element exists in your object as a parameter of the event that will trigger the WF;
2. That before you fire off the event, you populate the parameter of the event with the position;

Create a subtype of VBRK and add a new event 'created'. AFTERWARDS, generate and then add this as a SYSTEM WIDE DELEGATE for VBRK. You can get this new event to raise (VBRK.Created) through the ‘change DOCUMENTS’ (SWEC).

Create a subtype of VBRK and add a new event 'created'. Afterwards, generate and then add this as a system wide delegate for VBRK. You can get this new event to raise (VBRK.Created) through the ‘change documents’ (SWEC).

The ANSWER LIES in table HRS1201. CHECK to see if the field ‘BACKGROUND’ does not contain an X. If it doesn’t then it's a DIALOG task.

The answer lies in table HRS1201. Check to see if the field ‘Background’ does not contain an X. If it doesn’t then it's a dialog task.

GENERALLY, the agents for a task are STORED in a CLUSTER (index). The refresh BUTTON just POPULATES this cluster. When you push that button, the code function RH_TASK_AGENTS_INDEX is executed.

Generally, the agents for a task are stored in a cluster (index). The refresh button just populates this cluster. When you push that button, the code function RH_TASK_AGENTS_INDEX is executed.

In TR. SWO1, instantiate the business object. From there you can easily debug methods. To debug a BOR method you just need to put a breakpoint in your method and test the same. You can also debug attributes by placing the breakpoint and then initiating the object. If what you mean by DEBUGGING a method for a trigger event – is the method in a task that is triggered by an event, then you will have to debug all the way through the workflow engine from the point where you raised the event (SWUE) until the task calls the method. A breakpoint in ONE of the BINDING FMS would be useful here.
To trace the events, switch on the event trace SWELS and view SWEL.

In TR. SWO1, instantiate the business object. From there you can easily debug methods. To debug a BOR method you just need to put a breakpoint in your method and test the same. You can also debug attributes by placing the breakpoint and then initiating the object. If what you mean by debugging a method for a trigger event – is the method in a task that is triggered by an event, then you will have to debug all the way through the workflow engine from the point where you raised the event (SWUE) until the task calls the method. A breakpoint in one of the binding FMs would be useful here.
To trace the events, switch on the event trace SWELS and view SWEL.

You could start by TAKING a look at the STD. WF provided by SAP: WS20000075. From there, you would know how to PROCEED.

You could start by taking a look at the Std. WF provided by SAP: WS20000075. From there, you would know how to proceed.

You may follow these steps to start with:
1) Create change documents for TABLES of material in material master - transaction SCDO;
2) Then, create your own business object, please note the key field; it must COINCIDE with key fields of tables of material in material master - transaction SWO1;
3) Afterwards, create event "CHANGE" for your BO from point 2 and for your change document from point 1 - transaction SWU_EWCD;
4) Finally, create your WF start of triggering event from point 3.

You may follow these steps to start with:
1) Create change documents for tables of material in material master - transaction SCDO;
2) Then, create your own business object, please note the key field; it must coincide with key fields of tables of material in material master - transaction SWO1;
3) Afterwards, create event "CHANGE" for your BO from point 2 and for your change document from point 1 - transaction SWU_EWCD;
4) Finally, create your WF start of triggering event from point 3.

There is no SAP STANDARD cost center APPROVAL workflow. Workflow can only automate an existing process or a process you are about to develop. One OPTION would be to DESIGN a process where you store the data in a Z table, get the approvals and then create the CC.

There is no SAP standard cost center approval workflow. Workflow can only automate an existing process or a process you are about to develop. One option would be to design a process where you store the data in a Z table, get the approvals and then create the CC.

Go to the IDOC configuration. Set the "Business object" and EVENT to be used. From there, you can define the AGENTS who were RECEIVING the MESSAGE in IDOC configuration. Then, search from the CORRESPONDING standard task in PFTC. Lastly, activate the event linkage in task.

Go to the IDOC configuration. Set the "Business object" and event to be used. From there, you can define the agents who were receiving the message in IDOC configuration. Then, search from the corresponding standard task in PFTC. Lastly, activate the event linkage in task.

The SWUS SAP transaction is UTILIZED to test the workflow. If you have created the workflow template in wbuilder, then you can test it as well. Pass the data in ‘input’ push BUTTON. If you want to check that WHETHER any workflow has started or not, you can check with the LOG.

If your workflow template is not working as expected, you can DIAGNOSE it using transaction SWUD. Supply the WS and 8 digit name of your task appropriately.

The SWUS SAP transaction is utilized to test the workflow. If you have created the workflow template in wbuilder, then you can test it as well. Pass the data in ‘input’ push button. If you want to check that whether any workflow has started or not, you can check with the log.

If your workflow template is not working as expected, you can diagnose it using transaction SWUD. Supply the WS and 8 digit name of your task appropriately.

The FUNCTION of receiving MAILS is DEPENDENT on your WF DEFINITION. Re-check the WF definition.

The function of receiving mails is dependent on your WF definition. Re-check the WF definition.

SWDD_CONFIG is used to make changes to SAP WF templates. This transaction allows you to make changes like workitem TEXTS, agents and step NAMES. On the other HAND, SWDD is used to create your own WF templates.

SWDD_CONFIG is used to make changes to SAP WF templates. This transaction allows you to make changes like workitem texts, agents and step names. On the other hand, SWDD is used to create your own WF templates.

These would be the CHANGES that LEAD to a NEW Release GROUP or Release strategy.

These would be the changes that lead to a new Release group or Release strategy.

You can EITHER SEND an Express Email MESSAGE, or if it is a workitem, then make the PRIORITY = 9. It will send an express message to the RESPECTIVE Agent.

You can either send an Express Email message, or if it is a workitem, then make the Priority = 9. It will send an express message to the Respective Agent.

Go to that particular IDOC configuration (t-code WE20) and FIND the agents attached there. If the agent is determined through user id you can CHANGE the user id to B. If it is maintained USING work center you need to update the work center in accordance to your requirements.

Go to that particular IDOC configuration (t-code WE20) and find the agents attached there. If the agent is determined through user id you can change the user id to B. If it is maintained using work center you need to update the work center in accordance to your requirements.

Transaction SWWL (program RSWWWIDE) will delete workitems periodically but you need to be extremely careful running it in a productive environment. This is because you may end up unnecessarily deleting items that you did not WANT to. You should also run SWWH (program RSWWHIDE) to delete the workitem history for those workitems. This is an extreme operation though.

I would strongly RECOMMEND USING an archive instead. Archive out your completed workitems VIA SARA, object WORKITEM. This way, you can retrieve files WHENEVER necessary.

Transaction SWWL (program RSWWWIDE) will delete workitems periodically but you need to be extremely careful running it in a productive environment. This is because you may end up unnecessarily deleting items that you did not want to. You should also run SWWH (program RSWWHIDE) to delete the workitem history for those workitems. This is an extreme operation though.

I would strongly recommend using an archive instead. Archive out your completed workitems via SARA, object WORKITEM. This way, you can retrieve files whenever necessary.

Go to Task--> additional data-->agents-- >maintain agents screenàclick on PROPERTIES. In there, you will GET a pop-up, then SELECT "general task".

Go to Task--> additional data-->agents-- >maintain agents screenàclick on properties. In there, you will get a pop-up, then select "general task".

You should check the binding. Normal binding of container element from WF to task should accomplish this.

In terms of a task to workflow binding, you'd typically only want to pass back ACTUAL agent back into your workflow. There's no real LINKAGE between a role container and the workflow container, unless you've created an extra step in your workflow/a virtual ATTRIBUTE to EVALUATE a role and pass the results to a workflow container element so you can set your agent assignment for a subsequent workflow step via an EXPRESSION.

You should check the binding. Normal binding of container element from WF to task should accomplish this.

In terms of a task to workflow binding, you'd typically only want to pass back actual agent back into your workflow. There's no real linkage between a role container and the workflow container, unless you've created an extra step in your workflow/a virtual attribute to evaluate a role and pass the results to a workflow container element so you can set your agent assignment for a subsequent workflow step via an expression.

Do the FOLLOWING steps:
1) Create CHANGE documents for tables of material in material master - transaction SCDO.
2) Create your own business object, please note KEY field - it must coincide With key fields of tables of material in material master, transaction SWO1.
3) Create event "CHANGE" for your BO from point 2 and for your change document from point 1 - transaction SWU_EWCD.
4) Create your WF start of triggering event from point 3.

Do the following steps:
1) Create change documents for tables of material in material master - transaction SCDO.
2) Create your own business object, please note key field - it must coincide With key fields of tables of material in material master, transaction SWO1.
3) Create event "CHANGE" for your BO from point 2 and for your change document from point 1 - transaction SWU_EWCD.
4) Create your WF start of triggering event from point 3.

You may USE TRANSACTION SWIA to execute WF WITHOUT agent check. If this task has agents "Role", it is possible to use transaction ppom for assigning the Role Users. After which you can now use transaction ppwfbuf.

You may use transaction SWIA to execute WF without agent check. If this task has agents "Role", it is possible to use transaction ppom for assigning the Role Users. After which you can now use transaction ppwfbuf.

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 cons ider individual mails with a dynamic loop is when the text of the mail VARIES from one recipient to another.

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 cons ider individual mails with a dynamic loop is when the text of the mail varies from one recipient to another.

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.

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.

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.

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.

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.

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.

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.

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.

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. More...
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.

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. More...
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.

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).

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).

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-meil directly or trigger an event. To customize this user EXIT USE the transaction SCOT.

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-meil directly or trigger an event. To customize this user exit use the transaction SCOT.

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.

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.

By SPECIFYING the EVENT name for a missed deadline (of whatever type) you are INDIRECTLY telling the workflow system that you want to add flow logic to your workflow to meet this event. Don't be put off by he FACT that the branch does not lead anywhere. This is because the branch is not an alternative to the other results of the step. It is followed in addition to the other paths. In other words the workflow processing specified for a missed deadline is followed without affecting the STANDARD flow. The step with the missed deadline remains where it is and can still be processed as normal.

By specifying the event name for a missed deadline (of whatever type) you are indirectly telling the workflow system that you want to add flow logic to your workflow to meet this event. Don't be put off by he fact that the branch does not lead anywhere. This is because the branch is not an alternative to the other results of the step. It is followed in addition to the other paths. In other words the workflow processing specified for a missed deadline is followed without affecting the standard flow. The step with the missed deadline remains where it is and can still be processed as normal.

Business object like customer, product, etc; they are divided into CHARACTERISTICS and key FIGURES; characteristics are evaluation objects like customer and key figures are measurable objects like sales quantity, etc; characteristics also include SPECIAL objects like unit and time.

Business object like customer, product, etc; they are divided into characteristics and key figures; characteristics are evaluation objects like customer and key figures are measurable objects like sales quantity, etc; characteristics also include special objects like unit and time.

NUMC, CHAR (up to 60), DATS and TIMS.

NUMC, CHAR (up to 60), DATS and TIMS.

PRESENTATION hierarchies are stored in its own TABLES (HIERARCHY tables) for CHARACTERISTIC VALUES.

Presentation hierarchies are stored in its own tables (hierarchy tables) for characteristic values.