3501459 - Objects Are Missing from the "SLT - SAP LT Replication Server" Container When Creating a Data Flow or Replication Flow - SAP Datasphere

While creating a Data Flow / Replication Flow in SAP Datasphere, the objects under "SLT - SAP LT Replication Server" Container / Folder in the selected connection are missing.

• Data Flow
  
  
  
• Replication Flow
  

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP Datasphere

Cause 1 — SLT configuration or Mass Transfer ID missing or incomplete

The SLT configuration or Mass Transfer ID (MTID) required for the selected SLT container is missing or incomplete in transaction `LTRC`.

Cause 2 — Connection user missing required authorization

The user configured in the source connection does not have all authorizations required to browse SLT source objects.

Cause 3 — ABAP Integration Notes or TCI prerequisites incomplete

Applicable ABAP Integration Notes, TCI prerequisites, or manual activities are missing or not yet applied in the source system.

Solution for Cause 1 — Verify SLT configuration in LTRC

In transaction LTRC, confirm that the required SLT configuration/Mass Transfer ID exists, is running, and uses the applicable scenario for the intended Data Flow or Replication Flow. Follow KBA 3261895 for guidance on LTRC configuration requirements.

Solution for Cause 2 — Fix connection user authorization

1. Reproduce the issue by opening the "SLT - SAP LT Replication Server" container in the Data Flow or Replication Flow source browser.
2. Capture the failed authorization check for the connection user:
- If the connection user can log on interactively: run SU53 immediately after reproducing the failure in the same user context.

- Otherwise: use STAUTHTRACE or ST01, filtered by the connection user.
3. Use SUIM to review roles and authorization objects assigned to the user. Use the authorization trace to determine the actual missing object (S_DHAMBSLT is one example).
4. In PFCG, maintain the missing or incomplete authorization values, generate the profile, and perform the required user comparison.

If assistance is required to correct the role or authorization profile in PFCG, open a case under component BC-SEC-USR.

Solution for Cause 3 — Complete ABAP Integration Note Check

Run transaction CNV_NA_DI and complete all applicable ABAP Integration Notes, TCI prerequisites, and manual activities for the source-system release. See KBA 3498095 for details.

-----------------------------------------

After applying the relevant fix, reopen or refresh the source browser in Datasphere and confirm that objects are displayed.

If all three causes are verified but objects are still missing, provide the connection details, system/client, MTID, authorization evidence, and CNV_NA_DI result to SAP Support.

• KBA 3100673 - SAP Data Intelligence / SAP Datasphere - ABAP Integration - Security Settings
• KBA 3261895 - ABAP Connection SLT Folder No Objects in Data Flow Editor LTRC Configuration
• KBA 3498095 - How to check SAP Datasphere notes requirements on S/4HANA on-premise systems

Connection, ABAP, Data Flow, Replication Flow, Sources, Editor, Import, Repository, Data Builder, SLT, SAP LT Replication Server, Datasphere, Dataflow, Replicationflow, ABAP connection , KBA , DS-DI-RF , Replication Flow Runtime , BC-SEC-USR , User Administration , DS-DI-DF , Data Flow Runtime , CA-DI-IS-ABA , Data Intelligence - ABAP Integration , Problem