Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

  • 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_BTCH_ADM: 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 - creating and generating 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 SNP Glue is through the transaction code /DVD/GLUE.Other dedicated transaction codes may access parts of the functionality. Even when entering SNP Glue through the main transaction /DVD/GLUE, the user should have access to these transaction codes through the authorization object S_TCODE.

SNP Glue-specific transaction codes:

...