Users working with Glue should have access to relevant transaction codes and authorizations required for the Glue functionality.
...
- 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_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
- S_RS_COMP - authorization for BEx query extraction
- S_RS_ICUBE - authorization for InfoCube extraction
...
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.
...
T-code - required authorization object matrix:
| t-code | Development | Production |
|---|---|---|
| /dvd/gl16 | S_GUI, S_APP_LOG | S_GUI, S_APP_LOG |
| /dvd/gl11 | S_GUI, S_APP_LOG, S_DEVELOP | S_GUI, S_APP_LOG, S_DEVELOP |
| /dvd/gl14 | S_APP_LOG | S_APP_LOG |
| /dvd/gl38 | S_APP_LOG | S_APP_LOG |
| /dvd/gl80 | S_GUI, S_APP_LOG, S_DEVELOP,S_BTCH_JOB,S_BTCH_ADM ,S_RS_COMP, S_RS_ICUBE | S_GUI, S_APP_LOG, S_DEVELOP,S_BTCH_JOB,S_BTCH_ADM ,S_RS_COMP, S_RS_ICUBE |
| /dvd/glwb | S_GUI, S_APP_LOG, S_DEVELOP,S_BTCH_JOB,S_BTCH_ADM ,S_RS_COMP, S_RS_ICUBE | S_GUI, S_APP_LOG, S_DEVELOP,S_BTCH_JOB,S_BTCH_ADM ,S_RS_COMP, S_RS_ICUBE |
| /dvd/glip | S_APP_LOG | S_APP_LOG |
| /dvd/gl_tr | S_GUI, S_APP_LOG, S_DEVELOP, S_DATASET, S_SYS_RWBO, S_TRANSPRT | S_GUI, S_APP_LOG, S_DEVELOP |
| /dvd/gl_dbt | S_APP_LOG | S_APP_LOG |