Configure RFC Destination
Execution
Automatic/Manual
Function
The workflow runtime system always executes its tRFC (transactional RFC) calls on the logical destination WORKFLOW_LOCAL_xxx (xxx stands for the three-digit number of the client).
The workflow runtime system only operates within one client. The naming for the logical destination guarantees that these names are unique across the system.
If you carry out this activity automatically, the logical RFC destination WORKFLOW_LOCAL_xxx is created if it does not yet exist. The user WF-BATCH is assigned to this destination.
If you belong to the SUPER user group, and the WF-BATCH user does not exist, it is created and automatically gets the maximum authorization of the current user (SY-UNAME). The system user must have the authorization SAP_ALL if the workflow system is to function without problems.
This function is to be performed once by a user who belongs to the SUPER user group.
If you carry out this activity manually, you can maintain another system user and another password.
Maintain Active Plan Version
Execution
Automatic/Manual
Function
Only one of the plan versions created in the system can be active. This plan version (with its contents) is seen by the workflow system as the only valid plan version. All SAP workflows supplied are then in the plan version marked as active automatically.
If you carry out this activity automatically, 01 is set as the active plan version.
If you carry out the activity manually, you enter the plan version that you want to use as the active plan version in the field Value Abbrev. in the group PLOGI with the semantic abbreviation PLOGI.
-Kiran
*Please reward useful answers
Bluesky
