Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Using join on pooled table

Former Member
0 Likes
463

hai can any one tell how to use sql statements on pooled tables like bseg,

can i use join on them if so how

bye

afzal

2 REPLIES 2
Read only

Former Member
0 Likes
406

Hi,

We can't use join on Pooled table or cluster tables. We need to use for all entries only.

Reward with points if satisfied

REgards,

Krishna K.

Read only

Former Member
0 Likes
406

Hi you should not use joins or atleast SELECT's on POOLED and CLUSTERED tables....

Instead you can use the realted transparent tables....

CHeck the below details...

Where possible, avoid select statements which read table BSEG. This is an enormous table and reading it can have major performance implications. An alternative is to use one of the index tables instead. These contain most of the fields from the accounting document (BKPF) and the document line (BSEG) and all of the fields are indexed giving major performance advantages. There are 6 index tables which between them cover all of the document lines in BSEG.

BSIS G/L items (uncleared)

BSAS G/L items (cleared)

BSIK A/P items (uncleared)

BSAK A/P items (cleared)

BSID A/R items (uncleared)

BSAD A/R items (cleared)

If you don't know whether an item is cleared or not, it usually pays to do a select on the 'uncleared' table (eg BSIS for G/L lines) and if nothing is found then select from the 'cleared' table(in this case BSAS). This still has major performance advantages over a direct select on BSEG if you don't have the key fields.

On the few occasions where a field is required which is not available in the index it will still usually be faster to read the index to find the Document and Line Item numbers and then read BKPF/BSEG with these key fields.