topic Avoid querying BSEG in Application Development and Automation Discussions

Avoid querying BSEG

ricky_shaw — Mon, 22 Jun 2020 11:20:11 GMT

Hello,

I want to avoid hitting the BSEG table.

My requirement is to get the individual sum of line items in a given PO.

Is there any way that i can avoid querying BSEG table?

My queries are like below :

EKBE -->BKPF(awkey = belnr+year)-->BSEG table

1) Getting BELNR from EKBE .

2) And then using BELNR+GJAHR from EKBE to query the BKPF tables and get the BKPF-BELNR

3) Hit BSEG-BELNR (using above BKPF-BELR) and sum up different items.

Re: Avoid querying BSEG

MateuszAdamus — Mon, 22 Jun 2020 11:30:13 GMT

Are you using the BSEG-BUKRS and BSEG-GJAHR key fields too?

Kind regards,
Mateusz

Re: Avoid querying BSEG

Sandra_Rossi — Mon, 22 Jun 2020 16:08:02 GMT

Why do you want to avoid BSEG? You don't run S/4HANA?

Re: Avoid querying BSEG

ricky_shaw — Mon, 22 Jun 2020 22:23:01 GMT

Hi Sandra,

No, we are not using S/4 HANA. Will that make a difference?

Hi mateuszadamus Yes..i am mentioning all those fields in the query.

But getting data from BKPF is also taking more time.

Can you pls suggest.

Re: Avoid querying BSEG

MateuszAdamus — Tue, 23 Jun 2020 06:11:10 GMT

Please use "Comment" feature when providing more information or commenting.

Kind regards,
Mateusz

Re: Avoid querying BSEG

MateuszAdamus — Tue, 23 Jun 2020 06:16:52 GMT

Hello ricky.shaw

Please check if you have an AWKEY index in the BKPF table. It's a standard one, so you should have it. This index contains 4 fields: MANDT, AWTYP, AWKEY and AWSYS. If you will query the BKPF table using these fields (MANDT - automatically added, AWTYP and AWKEY) then the selection should be quite fast (thanks to the DB index). Please make sure you have the AWTYP field in your conditions.

Then, query the BELNR using the PRIMARY KEY of the table, which is BUKRS, BELNR, GJAHR - and it should be fast too.

Kind regards,
Mateusz

Re: Avoid querying BSEG

Sandra_Rossi — Tue, 23 Jun 2020 06:36:26 GMT

Yes, that makes a difference because BSEG is a special type of table (clustered) in versions before S/4HANA and that makes a lot of differences (in performance, in ABAP, etc.) With S/4HANA, all clustered tables have been converted into normal tables (I don't talk about tables containing "data clusters", like STXL, INDX, etc.)

Yet, my first main question is still unanswered: Why do you want to avoid BSEG?

NB: please use "comment".

Re: Avoid querying BSEG

MateuszAdamus — Tue, 23 Jun 2020 06:50:35 GMT

BSEG can be transparent, but it has to be converted during system upgrade. SAP OSS notes on the subject:

https://launchpad.support.sap.com/#/notes/1892354

https://launchpad.support.sap.com/#/notes/2227432

Kind regards,
Mateusz

Re: Avoid querying BSEG

Sandra_Rossi — Tue, 23 Jun 2020 13:31:46 GMT

Mateusz Adamus I wonder how much percentage of customers dared converting BSEG, I mean NOT under the direct advice of SAP 😉

Re: Avoid querying BSEG

gasparerdelyi — Wed, 24 Jun 2020 21:10:28 GMT

Let me add for the sake of completeness: with the assumption that there is everything OK with the indices, there is no bad need for a reorg etc.