Issue with the inner join on EKKO and EKPO.

Question

Dear All,
The report using this join takes a long time to execute.
Does this inner join have an issue?
Do i need to code this in a different way for lesser execution time?
Please give me your inputs.
SELECT
        a~ebeln
        b~ebelp
        a~bukrs
        a~bstyp
        a~bsart
        a~ekorg
        a~ekgrp
        a~kdatb
        a~kdate
        FROM ekko AS a JOIN ekpo AS b
        ON aebeln = bebeln
        INTO TABLE t_ekpo
        WHERE
        a~bukrs EQ p_bukrs
        AND a~bstyp EQ c_k
        AND a~bsart IN s_bsart
        AND a~ekorg IN s_ekorg
        AND a~ekgrp IN s_ekgrp
        AND a~kdate GE s_fdate-low
        AND a~loekz EQ space
        AND b~loekz EQ space.
Regards,
SuryaD.

Answer 1

Index EKKO~D consists top-down of BSTYP and BEDAT. BSTYP is already an EQ-condition in your selection, but not very selective (many rows with the same value). So including BEDAT should help in efficiently reducing the data that needs to be scanned for finding the relevant rows. However, just a new optional S_BEDAT select option that can be left empty by the user would not help, you must force a narrow selection (one month, one week, even one day? the less the better).
This is just a quick guess from my side, there might be other options that occur to you once you have analysed the available indexes. Sometimes alternative tables could be the solution, and even less sometimes introducing a new secondary index for a standard table might be the last option (takes up space and adds processing time to insert/update/delete operations).
Thomas