!--a11y-->
Guided Procedures Authorizations in the ABAP
Stack 
The Guided Procedures (GP) framework integrates with the ABAP stack of SAP NetWeaver. For example, you can configure GP to use the SAP Business Workflow runtime. The GP transport system uses ABAP-based SAP systems, and you can also call RFC function modules and BSP applications within a process modeled with GP.
The following security aspects are related to the GP functions on the ABAP side:
Portal Roles
Role |
Description |
Guided Procedures SAP System User |
GP provides this portal role to enable users to trigger callable object execution from the ABAP stack. |
Roles in the ABAP Stack
Role |
Name |
SAP_BC_BMT_WFM_GP_SERVICE_USER |
This role contains the authorizations required for the service user that is used to connect from the GP runtime to the SAP Business Workflow runtime in the ABAP stack. The role is not intended for dialog users. It contains RFC authorizations for the function groups SWF_GP_CALLBACK, SWF_GP_DEF, SWF_GP_ROLES, SWF_GP_RUN and SWF_GP_UTL. |
SAP_BC_BMT_WFM_GP_ADMIN |
This role contains the authorizations and menu entries needed for accessing SAP Business Workflow transactions for GP. For example, you can use the administration transaction SWF_GP where the GP process instances that are deployed on the local Business Workflow Engine can be seen. This role must be assigned to the ABAP stack administrators for Guided Procedure environments, for example, to the existing Workflow administrators. |
EUP_GP |
This role contains the following authorization objects: · EUP_GP_TSP – contains an authorization field with value Execute, which defines a permission to import and export GP content. · EUP_GP_BSP – contains an authorization field with value Execute, which defines a permission to execute BSP applications in GP when an endpoint alias is used. |
See also:
