SAP LT Replication Server · Security

In the SLT authorization concept, S_DMIS_SLT is described as needing a manual step that the other SLT authorization objects don't. What is it, and what breaks if skipped?

This is one card from the KnowCard library. The full way to learn it — spaced-repetition review, progress tracking, and AI explanations — lives in the KnowCard app, free to start on the web. iOS & Android are coming soon.

Get started — it’s free

Already have an account? Sign in →

More in Security

Access restriction in the ABAP source moved from one table to another across support packs. Which table is legacy, which is current, and what's the precedence rule after upgrade?

For an S/4HANA 2020+ source, besides SAP_IUUC_REPL_REMOTE, which role and which two authorization objects drive fine-grained CDS-view/table restriction?

When configuring the RFC connection from SLT to an ABAP source in SM59, which connection type and user type are correct, and what's the gotcha if the two systems share a host?

When SLT manages the HANA target connection versus an external (unmanaged) one, who owns defining the target security, and what's the practical consequence?

The SAP_IUUC_REPL_ADMIN role lets a user create and change SLT configurations, but the admin complains they cannot see the actual data being replicated from source to target. What are they missing?

A user needs to view/edit migration objects in the Migration Object Modeler for an SLT scenario. Which authorization object governs this, and why isn't it S_DMIS?