Scribd
Upload
83 views3 pages

Why Is It Important To Configure An RFC Destination For Your Workflow Execution? What Are The Steps For Configuring This RFC Destination? C

The document discusses configuring an RFC destination for workflow execution. You need to create a WF-BATCH user, assign it the System type and SAP_ALL and SAP_NEW authorizations, specify a password for it, and test the configured RFC destination using transaction SWF_RFC_DEST. It also lists important workflow customizing transactions like SWU2, SWU3, SU01, SM37, SWETYPV, and SWELS.

Uploaded by

Rajiv Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
83 views3 pages

Why Is It Important To Configure An RFC Destination For Your Workflow Execution? What Are The Steps For Configuring This RFC Destination? C

The document discusses configuring an RFC destination for workflow execution. You need to create a WF-BATCH user, assign it the System type and SAP_ALL and SAP_NEW authorizations, specify a password for it, and test the configured RFC destination using transaction SWF_RFC_DEST. It also lists important workflow customizing transactions like SWU2, SWU3, SU01, SM37, SWETYPV, and SWELS.

Uploaded by

Rajiv Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

39 39 39 39 39

15. Why is it important to configure an RFC destination for


your workflow execution? What are the steps for
configuring this RFC destination?
It is important to configure the RFC destination as this
is the mechanism for which the workflow engine
executes its tasks. You may configure the RFC
destination for workflows via the transaction SM59 or
SWU3. You need to know the password of the WF-
BATCH user when you configure the RFC destination.
It is preferable to use SWU3 to configure the RFC
destination (to minimize issues in configuring the
workflow engine ensure that whoever is running
SWU3 has SAP_ALL and SAP_NEW authorizations)
(as shown in Figure 1.3).
Figure 1.3
The steps required are shown below:
Create the WF-BATCH user. The first step is to
create the WF-BATCH user. This user is required
for logging on to the logical destination
WORKFLOW_LOCAL_XXX. Click on the
Maintain User option.
Cust omi zi ng Set t i ngs
40 40 40 40 40
This user must be assigned the type System
(background) as well as the authorization profiles
SAP_ALL and SAP_NEW.
Specify a password for the WF-BATCH user. The
next step is to specify a password for the WF-
BATCH user. Enter the password on the screen
and then click on the Synchronize Passwords
button.
To test the configured RFC destination, click on
the Test button.
16. Name some important transactions pertinent to workflow
customizing.
Important transactions pertinent to workflow
customizing are shown below:
SWU2 - Workflow RFC Monitor
SWU3 - Automatic Workflow Customizing
SWF_RFC_DEST - RFC destination
SU01 - Create User
SM37 - Job creation
SWETYPV - Event activation
SWELS - Activate event trace
Chapt er 1 : Wor kf l ow Basi cs and Cust omi zi ng
41 41 41 41 41
17. In addition to the entries created via the automatic
customizing option (via transaction SWU3), there is an
entry that must be created manually, in a development
environment, by the workflow administrator. State this
entry and explain the entry creation process.
In addition to the table entries created by the
automatic customizing option, you must maintain the
prefix number for the custom tasks and templates to
be created.
This may be done via the IMG path Basis Components
Business Management SAP Business Workflow
Basic Settings Maintain Prefix Numbers (see
Figure 1.5).
Figure 1.5
This path leads you to the screen shown in Figure 1.6.
Cust omi zi ng Set t i ngs

You might also like