Set CDS_CLIENT Before HANA CDS View Extracts

Sara Kim breaks down what you need to know

If you pull data from ABAP CDS views directly in HANA without setting the client, you will get wrong numbers. This is not a rare edge case. It happens every time someone forgets the session parameter in a multi-client landscape.

The Real Story

CDS views rely on the implicit client filter that ABAP adds at runtime. When you bypass the ABAP layer and query the view from a HANA studio session or an external extraction job, that filter disappears. The view then returns rows from every client present in the table.

The fix is simple but mandatory: run

SET 'CDS_CLIENT' = '400';

before any SELECT. Omitting it produces mixed-client data that looks plausible until reconciliation fails or downstream reports show duplicates.

What This Means for You

Developers writing extraction pipelines or test scripts hit this immediately. Consultants migrating data flows to HANA-native tools discover it after the first production load. Both roles waste hours chasing data inconsistencies that disappear once the client context is forced at the session level.

The issue surfaces most often in:

• Custom SLT or SDI replication jobs
• Direct JDBC/ODBC queries from analytics tools
• Automated test data extraction scripts

Action Items

• Add SET 'CDS_CLIENT' = '<client>'; as the first statement in every HANA session or script that touches CDS views.
• Store the command in connection profiles or job templates so it runs automatically.
• Add a quick validation query that counts rows per client right after connection to catch missing context early.
• Document the requirement in any runbook that mentions direct HANA access to CDS artifacts.

Community Perspective

The original Reddit thread showed developers who spent days reconciling numbers before realizing the client filter was missing. Several people reported the same pattern: data looked correct in small tests, then exploded once real volumes arrived. The consensus was that this should be a connection-level default in future tooling, yet today it still requires explicit handling.

Bottom Line

Treat client context as non-negotiable when you leave the ABAP runtime. One line of session configuration prevents hours of data cleanup and protects report accuracy. Until the tools enforce it automatically, the responsibility stays with the developer who writes the query.

Source: Original discussion/article

References

• SAP HANA Platform Overview- ABAP Development Guide
• SAP News Center

References

• ABAP Development Guide
• SAP News Center
• SAP HANA Platform Overview