Ansicht
Dokumentation

ABENDDIC_DATABASE_TABLES_POCLURE - DDIC DATABASE TABLES POCLURE

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Restrictions in Pooled Tables and Cluster Tables

The following general restrictions apply to pooled tables and cluster tables:

• Access to pooled tables and cluster tables using Native SQL is not possible.

• Pooled tables and cluster tables cannot be data sources of CDS views. Views like this can be activated but not used.

• Cluster tables cannot be buffered.

• Pooled tables and cluster tables cannot be global temporary tables (GTTs).

• No replacement objects can be defined for pooled tables and cluster tables.

The following restrictions apply when accessing pooled tables and cluster tables using Open SQL:

• CDS views that contain pooled tables or cluster tables as a data source cannot be used as data sources of the statement SELECT.

• The addition DISTINCT of the statement SELECT cannot be used when accessing pooled tables or cluster tables if single columns are specified in the SELECT list.

• When accessing pooled tables or cluster tables, not all columns of a data source can be specified in the statement SELECT using data_source~* in the SELECT list.

• When accessing pooled tables or cluster tables, no aggregate expressions except COUNT( * ) can be created in the statement SELECT. COUNT(*) is emulated in this case.

• When accessing pooled tables or cluster tables, no SQL expressions can be used.

• When accessing pooled tables or cluster tables, no joins can be created in the statement SELECT.

• No path expressions for associations of CDS views can be used when accessing pooled tables or cluster tables.

• When accessing pooled tables or cluster tables, no columns of the data source can be specified on the right side in comparisons in a WHERE condition.

• In pattern matches using LIKE in a WHERE condition, the addition ESCAPE cannot be specified when a pooled table is accessed.

• The additions GROUP BY and HAVING of the statement SELECT cannot be specified when accessing pooled tables or cluster tables.

• When accessing pooled tables or cluster tables, it is not possible to use ORDER BY to sort by single columns in the statement SELECT.

• When accessing pooled tables or cluster tables, no subqueries can be used, either as a WHERE condition or as a data source of the statement INSERT.

• The primary key fields of pooled tables or cluster tables cannot be overwritten using the addition SET of the statement UPDATE.

• Secondary database connections cannot be used to access pooled tables or cluster tables. The addition CONNECTION of the statement SELECT and the addition CONNECTION in write statements cannot be used.

General Material Data   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 6259 Date: 20240425 Time: 150604     sap01-206 ( 74 ms )