topic Re: Performance Issue While fetching from BSEG Table. in Application Development and Automation Discussions

Performance Issue While fetching from BSEG Table.

former_member196331 — Tue, 17 Jan 2017 06:03:00 GMT

Need Small information.

SELECT * INTO CORRESPONDING FIELDS OF TABLE it_bseg-debit FROM bseg WHERE shkzg EQ 'S' AND umskz EQ 'A' AND ebeln EQ i_ekko-ebeln.

The above Query i am Writing.Based on the Purchase order ebeln. I need to fetch the Data.
In Development the query is working fine, But in Quality Bseg is having much of data.So, performance is very slow.

In Where condition i mentioned ebeln. Actually i need to pass key fields. For getting key fields also, Again i need to write the query. May i know how could i reduce the time.
Po number wise i need to fetch data.

Re: Performance Issue While fetching from BSEG Table.

RaymondGiuseppi — Tue, 17 Jan 2017 06:49:02 GMT

Use so called secondary indexes like BSIS/BSAS to read the data, then if some fields are missing you can then read BSEG with primary keys of RFBLG the actual db table. You could also consider using table EKBE to get invoice documents associated to Purchase Orders, filtering on BEWTP to restrict to thoze.

Regards,
Raymond

Re: Performance Issue While fetching from BSEG Table.

former_member196331 — Tue, 17 Jan 2017 06:57:03 GMT

Ok, I will check it, EKBE i was forgotton.

Re: Performance Issue While fetching from BSEG Table.

Former Member — Tue, 17 Jan 2017 07:47:42 GMT

Avoid using ''CORRESPONDING FIELDS OF..'' Instead

SELECT * FROM bseg INTO TABLE it_bseg-debit WHERE shkzg EQ 'S' AND umskz EQ 'A' AND ebeln EQ i_ekko-ebeln....

Also, to further enhance the performance use fields instead of 'Select *'

Furthermore you can use secondary indexes.

Re: Performance Issue While fetching from BSEG Table.

former_member196331 — Tue, 17 Jan 2017 07:59:07 GMT

How can we use secondary indexed in my case. Can you explain.

Re: Performance Issue While fetching from BSEG Table.

Former Member — Tue, 17 Jan 2017 08:50:11 GMT

It depends on the queries you need to do.

For example my table has the following fields:

KEY1

KEY2

KEY3

FIELD1

FIELD2

FIELD3

If I often need to do a query using FIELD1 and FIELD2, I have to create an index with those two fields.

Every time I do a select like this:

SELECT * FROM <TABLE> WHERE FIELD1 = .....

AND FIELD2 = .....

The index'll be used.

But also if I do:

SELECT * FROM <TABLE> WHERE FIELD1 = .....

The index'll be used partially.