Approvers may want to be instantly informed about the documents for approval. There are some standard and non-standard ways to do this. Some BADIs can be used for this process. Also, the workflow can be copied and a mail step can be added to the new workflow. But I want to show the standard way for this process. I will try to explain it step by step as much as I can.
Firstly, if the workflows are activated in the system, the workitems on the user's will fall into the user's "Business Workplace".
You can go to the business workplace by clicking the button marked or with the "SBWP" transaction code.
Documents falling into the inbox on the business workplace will look like the following.
The next step is to forward the document in the inbox by e-mail.
Workitems do not fall directly into the inbox. Workflows must be active for this.
1.First of all, there are a few small steps to complete in the "SWU3" transaction code.
2.Then, the workflow belonging to the document(PR/PO) that is requested to drop to the inbox from the "SWDD operation" code must be activated.
3.Then the mail server must be activated.
BASIS must complete this process. After completing the steps in this process, you should see the lines in the SWU3 transaction code with a green tick as below.
In this step, the worklow (WS20000077) belonging to the document (for example PR) to be inboxed must be activated.
The relevant workflow should be entered and the header button should be clicked.
Then the marked yellow button must be clicked.
Then the line should be selected and the "attributes" button should be clicked.
Then come back and click on the "Start Event" tab. The BUS **** object must be activated by clicking on the marked icon.
When saved, Workflow activation process is completed. The workitems that fall into the user's inbox after the workflow is activated will be listed as follows.
BASIS must complete this process. It can be checked whether the domain is correct in the "SCOT" transaction code.
There are 2 different ways for forwarding mail. One of them is individual forwarding. In this forwarding type, each approver should make settings for the routing process specific to its own user. After the user has made this setting, the workitems falling into the user's inbox will be forwarded to the desired e-mail address. This individual action required by each approver is described in section 3.1.
The second of these is to activate the mail forward operation for all users in the system. With a simple operation, the mail forwarding process can be activated. It is ensured that the e-mail address defined in the information of the users is used for this process. This process is explained in detail in 3.2.
First of all, the business workplace must open.
SBWP>Settings>Ofice settings – Automotic forward tab
Mail forward activation has been completed. After this stage, the workitem ids and document numbers are expected to flow into the email entered, but the RSWUWFML program must be run regularly for this flow to occur. For this, a job must be set up.
With this transaction, mail forwarding from inbox is activated for all users in the system. It is more useful than individual forwarding. You must go to t-code SO16.
SO16>Send tab
"Externel sending only using address management" should be selected.
SO16>Mail Group tab
Mail forward activation has been completed. After this stage, the workitem ids and document numbers are expected to flow into the email entered, but the RSWUWFML program must be run regularly for this flow to occur. For this, a job must be set up.
The mails to be forwarded are triggered by this program. This program determines the way the mail is forwarded (collective or per), the text of the mail and the workitems of which task ID you will forward.
The task ids of the document types to be forwarded must be entered into the program. If this restriction is not entered, all workitems falling into the user's inbox will be forwarded by e-mail. (Task ID: TS20000159-PR, TS20000166-PO, TS20000172-Contract)
“One mail per workitem” must be clicked.
There is a standard dialog text for the content of the mail. You can use this standard dialog text if you want.
If desired, a new dialog text can be created in the se61 transaction code, thus changing the content of the mail.
This program must be run in order to trigger e-mails falling into the inbox. Therefore, job should be established for the program to work regularly. The program should be saved as above or as a variant as you wish. This variant job should also be used.
When the program runs, the workitems that fall into the inbox are sent to the approver by mail in the format below.
I hope that will be useful.
Regards,
Adem Müminoğlu
Firstly, if the workflows are activated in the system, the workitems on the user's will fall into the user's "Business Workplace".
You can go to the business workplace by clicking the button marked or with the "SBWP" transaction code.
Documents falling into the inbox on the business workplace will look like the following.
The next step is to forward the document in the inbox by e-mail.
1. Activating the Business Workplace
Workitems do not fall directly into the inbox. Workflows must be active for this.
1.First of all, there are a few small steps to complete in the "SWU3" transaction code.
2.Then, the workflow belonging to the document(PR/PO) that is requested to drop to the inbox from the "SWDD operation" code must be activated.
3.Then the mail server must be activated.
1.1 SWU3 – Automatic Workflow Customizing
BASIS must complete this process. After completing the steps in this process, you should see the lines in the SWU3 transaction code with a green tick as below.
1.2 SWDD – Activating Workflow
In this step, the worklow (WS20000077) belonging to the document (for example PR) to be inboxed must be activated.
The relevant workflow should be entered and the header button should be clicked.
Then the marked yellow button must be clicked.
Then the line should be selected and the "attributes" button should be clicked.
Then come back and click on the "Start Event" tab. The BUS **** object must be activated by clicking on the marked icon.
When saved, Workflow activation process is completed. The workitems that fall into the user's inbox after the workflow is activated will be listed as follows.
2. Activating Mail Server
BASIS must complete this process. It can be checked whether the domain is correct in the "SCOT" transaction code.
3. Mail Forwarding Process
There are 2 different ways for forwarding mail. One of them is individual forwarding. In this forwarding type, each approver should make settings for the routing process specific to its own user. After the user has made this setting, the workitems falling into the user's inbox will be forwarded to the desired e-mail address. This individual action required by each approver is described in section 3.1.
The second of these is to activate the mail forward operation for all users in the system. With a simple operation, the mail forwarding process can be activated. It is ensured that the e-mail address defined in the information of the users is used for this process. This process is explained in detail in 3.2.
3.1 Mail Forwarding Activation From Inbox (Individual)
First of all, the business workplace must open.
SBWP>Settings>Ofice settings – Automotic forward tab
Mail forward activation has been completed. After this stage, the workitem ids and document numbers are expected to flow into the email entered, but the RSWUWFML program must be run regularly for this flow to occur. For this, a job must be set up.
3.2 Mail Forwarding Activation From Inbox (Mass)
With this transaction, mail forwarding from inbox is activated for all users in the system. It is more useful than individual forwarding. You must go to t-code SO16.
SO16>Send tab
"Externel sending only using address management" should be selected.
SO16>Mail Group tab
Mail forward activation has been completed. After this stage, the workitem ids and document numbers are expected to flow into the email entered, but the RSWUWFML program must be run regularly for this flow to occur. For this, a job must be set up.
4. RSWUWFML Program
The mails to be forwarded are triggered by this program. This program determines the way the mail is forwarded (collective or per), the text of the mail and the workitems of which task ID you will forward.
The task ids of the document types to be forwarded must be entered into the program. If this restriction is not entered, all workitems falling into the user's inbox will be forwarded by e-mail. (Task ID: TS20000159-PR, TS20000166-PO, TS20000172-Contract)
“One mail per workitem” must be clicked.
There is a standard dialog text for the content of the mail. You can use this standard dialog text if you want.
If desired, a new dialog text can be created in the se61 transaction code, thus changing the content of the mail.
This program must be run in order to trigger e-mails falling into the inbox. Therefore, job should be established for the program to work regularly. The program should be saved as above or as a variant as you wish. This variant job should also be used.
When the program runs, the workitems that fall into the inbox are sent to the approver by mail in the format below.
I hope that will be useful.
Regards,
Adem Müminoğlu
- SAP Managed Tags:
11 Comments
