topic Re: bseg table in Application Development and Automation Discussions

bseg table

Former Member — Wed, 15 Nov 2006 10:54:37 GMT

BSEG is a cluster table. so it contains records in large numbers. so if i want to get the data the performance issue will be raised. is anybody knows in which other tables i can get this data.

i want a report that displays the values from bseg and vbak table how can i solve this problem. At the same time can any one tell exactly what is the main difference between the cluster and transparent table plz.

Re: bseg table

seshatalpasai_madala — Wed, 15 Nov 2006 10:58:06 GMT

Hi,

I can answer the later part of your question.

The difference between cluster table and transperent table is for each transperent table there is one DATABASE table in the database where as for a group of cluster tables you will have one database table. That is 2 3 tables will be clubbed into one table in the DATABASE. this is basically done to group the related data.

And also the data in cluster table is stored in compressed format.

Regards,

Sesh

Re: bseg table

Former Member — Wed, 15 Nov 2006 11:00:06 GMT

There's always performance issues associated with BSEG. To reduce to some extent, use Index. Either use an index already provided based on ur requirement or create a new index.

Regards,

Santosh.

Re: bseg table

Former Member — Wed, 15 Nov 2006 11:10:29 GMT

u can work with BKPF table instead of bseg bcoz u can get all the datas in that table also.

Re: bseg table

Former Member — Wed, 15 Nov 2006 14:41:53 GMT

I'ts a common misconception that because BSEG is a large cluster table, performance will be bad. But it's just a table. If you SELECT from it based on BUKRS, BELNR and GJAHR, it will be as fast as any other select.

Rob

Re: bseg table

Former Member — Wed, 15 Nov 2006 18:22:26 GMT

BSEG is actually a accounting document segment table and BKPF is a accounting document header table.If u just want the line item details then go for BSEG else go for BKPF

Re: bseg table

Former Member — Wed, 15 Nov 2006 19:34:23 GMT

FIrst of all any table access on BSEG is goint to take a lot of time.

The only thing to do it to always take the primary keys of BSEG whenever a select is done.

If you want a join between VBAK and BSEG... you will have to first take

a select on VBAK (t_vbak) and then on BSEG(t_bseg)..

Then loop at t_vbak).

Read t_bseg where the keys are equal

endloop.

These are some of the secondary tables which are taken to access the same records. Helps in performance.

BSAD Accounting- Secondary Index for Customers (Cleared Items)

BSAK Accounting- Secondary Index for Vendors (Cleared Items)

BSAS Accounting- Secondary Index for G/L Accounts (Cleared Items)

BSEC One-Time Account Data Document Segment

BSID Accounting- Secondary Index for Customers

BSIK Accounting- Secondary Index for Vendors

BSIM Secondary Index, Documents for Material

BSIS Accounting- Secondary Index for G/L Accounts

Following such steps will help increas the performance.

Regards,

Prince

Re: bseg table

Former Member — Wed, 15 Nov 2006 19:53:57 GMT

Hi srivallika,

tell me which data u r looking for .

If you want Account receivbles go to BSAD a BSID

If you looking form Account Paybles BSAK BSIK.

Re: bseg table

Former Member — Wed, 15 Nov 2006 21:02:02 GMT

In most cases a select on bseg table causes a performance issue. In such cases we use package size.