Users working with Glue should have access to relevant transaction codes and authorizations required for the Glue functionality.

The following SAP authorization objects are required for the Glue functionality. Please see below a description on how to set up the individual authorization objects.

S_TCODE - authorization for transaction codes
S_APPL_LOG - authorization for displaying logs
S_RFC_ADM - authorization for Hadoop storage access (create Glue table, extraction, etc.)
S_GUI - authorization for GUI activities
S_BTCH_ADM - authorization for background job administration (extraction)
S_BTCH_JOB - authorization for background job operations and scheduling (extraction)
S_DATASET - authorization for temporary storage (Extractor rules, Glue TMS)
S_SYS_RWBO - authorization for WBO Proxy Functions - creation and generation of a transport (Glue TMS)
S_TRANSPRT - authorization for transport (Glue TMS)
S_DEVELOP - authorization for inserting the ABAP code into the extraction (e.g. lookups, routines, etc.) and debugging

Set up of authorization objects

S_TCODE

The main entry point for Glue is through the transaction code /DVD/GLUE. Other dedicated transaction codes may access parts of the functionality. Even when entering Glue through the main transaction /DVD/GLUE, the user should have access to these transaction codes through the authorization object S_TCODE.

Glue specific transaction codes:

/DVD/GL11 - Glue Data Dictionary
/DVD/GL16 - Glue Data Browser
/DVD/GL14 - Glue Dictionary Utility
/DVD/GL38 - Glue Script Editor
/DVD/GL80 - Glue Object Navigator
/DVD/GLWB - Glue Extractor Workbench
/DVD/GLIP - Glue InfoProvider Management
/DVD/GLTR - Glue Transport Management
/DVD/GL_DBT - Glue Trigger Management

Users should also have these additional authorizations:

SM50 - Work process overview
SM04 - Work process details (required for detail display in the transaction SM50)
SE16 - Data Browser
SE38 - Program execution
SM36/SM37 - Background jobs

Browser not supported