Rewrite SQL query to improve performance

Question

Hello,
The below queries are very time consuming.Could you please suggest how to improve performance for these 2 queries:
QUERY1:
SELECT avbeln aposnr aauart avkorg avtweg aspart
avkbur akunnr bmatnr bkwmeng b~vrkme
bnetwr bwerks blgort bvstel babgru berdat b~ernam
cfaksk cktext cvdatu czzbrsch ckvgr1 caugru
INTO CORRESPONDING FIELDS OF TABLE g_t_sodata
            FROM vapma AS a INNER JOIN vbap AS b ON
            avbeln = bvbeln AND aposnr = bposnr
            INNER JOIN vbak AS c ON avbeln = cvbeln
              WHERE a~vkorg IN so_vkorg
              AND a~vtweg IN so_vtweg
              AND a~vkbur IN so_vkbur
              AND a~auart IN so_auart
              AND a~vbeln IN so_vbeln
              AND b~abgru IN so_abgru
              AND c~faksk IN so_faksk
              AND ( b~erdat GT g_f_zenkai_date OR
        ( berdat EQ g_f_zenkai_date AND berzet GE g_f_zenkai_time ) )
        AND ( b~erdat LT g_f_kaisi_date  OR
         ( berdat EQ g_f_kaisi_date  AND berzet LT g_f_kaisi_time ) ).
QUERY2:
SELECT avbeln aposnr aauart avkorg avtweg aspart
        avkbur akunnr bmatnr bkwmeng  b~vrkme
        b~netwr
        bwerks blgort bvstel babgru berdat bernam
        cfaksk cktext cvdatu czzbrsch ckvgr1 caugru
        INTO CORRESPONDING FIELDS OF TABLE g_t_sodata
       FROM vapma AS a INNER JOIN vbap AS b ON
       avbeln = bvbeln AND aposnr = bposnr
       INNER JOIN vbak AS c ON avbeln = cvbeln
         WHERE a~vkorg IN so_vkorg
         AND a~vtweg IN so_vtweg
         AND a~vkbur IN so_vkbur
         AND a~auart IN so_auart
         AND a~vbeln IN so_vbeln
         AND b~abgru IN so_abgru
         AND c~faksk IN so_faksk.

Answer 1

Questions like this a one of the favorites here in this forum.
I guess that the statements are o.k.
The problem is the usage!  There are so many Ranges, if they are filled then some index should support it. If no range is filled then it is usually slow, you can not do anything.
You must find out, which are actually used and under which conditions it is slow and when it is o.k.
Ask again, when you can provide the actual cases.
Use SQL trace to check the performance:
SQL trace:
The SQL Trace (ST05) – Quick and Easy
I know the probabilty is high, that you will ignore this recommendation and you will points to the
'Use FOR ALL ENTRIES' recommendations' ... but then I can not help you.
Siegfried