Application Development 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: 

i used LDB for BKPF-BSEG ..any ALTERNATIVES to improve PERFORMANCE.

Former Member
0 Kudos
208

i basicaly draw data from BKPF and BSEG...for all GL accounts(HKONTS) In a COMPANY CODE(BUKRS) for a FISCAL YEAR(GJAHR)

I basicaly SUM up the NET VALUES(DMBTR) for a HKONT and display it across all COST CENTRES.

Since the Requirement needs GL's as COLOUMN HEADINGS and KOSTL as ROWS,

I used DYNAMIC INTERNAL TABLE concept...

However the runtime is high(as expected)..

DID I WRITE THE BEST CODE?

i used LDB for DRAWING DATA...

and rest is all basic coding for DYNAMIC ITABS..

now how can i better it?

the tables are indexed..

will using any other approach fasten the speed?????????????

also i ahve no idea how BW will come handy..

are these kind of reports supposed to be done in BW?

11 REPLIES 11

mvoros
Active Contributor
0 Kudos
135

Hi,

as you expected the running time of your report is high. I do not think you can improve it significantly. I would you use standard select from BKPF and BSEG (using FOR ALL ENTRIES) instead of logical DB.

Here is also nice blog about selecting FI documents from BSEG.

/people/rob.burbank/blog/2007/11/12/quickly-retrieving-fi-document-data-from-bseg

Cheers

mvoros
Active Contributor
0 Kudos
135

I forgot to mentioned that other blogs about performance from Rob Burbank are useful as well.

/people/rob.burbank/blog

ThomasZloch
Active Contributor
0 Kudos
135

>

> are these kind of reports supposed to be done in BW?

Sounds very much so (if you have a BW already anyway). Also see if you can use table COSS.

Thomas

0 Kudos
135

nah that doesnt have all data i want..however a handy table..thanks

christine_evans
Active Contributor
0 Kudos
135

If the starting point for your report is HKONT, I'd try using as a starting point for the selects tables BSIS or BSAS both of which hold FI lines data indexed on HKONT.

Former Member
0 Kudos
135

Hello Gaurav,

The Table BSEG is a cluster table and hence any queries on this table that does not use the Document number will cause performance problems.

To resolve the performance problems in your report try using database tables BKPF, BSIS and BSAS instead of using the LDB for fetching the data.

Hope this helps!

Regards

Vijai

0 Kudos
135

is it for sure that every GL ACC in BSEG,will be found either in BSIS or BSAS?

0 Kudos
135

ok

0 Kudos
135

> is it for sure that every GL ACC in BSEG,will be found either in BSIS or BSAS?

Only when the indicator SKB1-XKRES is checked in G/L account maintenance (applies to "old" general ledger only, as I just read).

Thomas

0 Kudos
135

yea,thanks for the info..

wondering if thers a better table(may be frm CO side) for capturing,all GLS,corresponding DMBTR & KOSTL

0 Kudos
135

ok i got this table COEP COBK .

thanks for inputs