Is "Joins & For all entries" in same SQL Query Possible?

Question

Hi all Professional,
Can we use "Inner Joins" and "For All Entries In" in the same SQL Query. if possible then pls clarify this query.
Here I am using three Transparent Table and fetching data from them.
SELECT abukrs abelnr ahkont axref2 ashkzg awrbtr agsber azfbdt azterm amwskz asgtxt axref1 agjahr abuzei
           bkunnr bwerks bmenge bmeins bmatnr bkoart
           cbukrs cbelnr cblart cbldat cbudat cxblnr cgjahr cstgrd cstblg cstblg c~xreversal
           INTO CORRESPONDING FIELDS OF TABLE it_bsid FROM ( ( bsid AS a
           INNER JOIN acctit AS b ON abukrs = bbukrs )
           INNER JOIN bkpf AS c ON cbukrs = abukrs
                               AND cbelnr = abelnr
                               AND cgjahr = agjahr )
           FOR ALL ENTRIES IN it_bkpf
              WHERE
                a~belnr EQ it_bkpf-belnr
            AND a~gjahr EQ it_bkpf-gjahr
            AND a~bukrs EQ it_bkpf-bukrs
            AND a~gsber IN so_bus.
After executing this query, I'm getting Dump Error.
Error analysis
    When the program was running, it was established that more
    memory was needed than the operating system is able to provide savely.
    To avoid a system crash, you must prevent this
    situation.
               Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server Development_DVL_01 on host Development (wp
     2)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1886
Pls resolve, if anybody knows.
Thanks
Devinder

Answer 1

Hi,
During testing i notice that splitting into multiple selects does improve performance. But the best performance I achieved using DB Hints instead of splitting the select statements.
Generally performance of joins together with for all entries is bad.
However if you will look into SAP note 1662726 you will notice that this issue (bad performance in using join and for all entries together) has been addressed.
Even though the note is for HANA DB, FM RSDU_CREATE_HINT_FAE can be used independent of DB.
On HANA DB performance improvement is huge (i achieved 62 seconds using DB Hints compared to 1656 seconds using for all entries). On Oracle DB the same code initially run in 99 seconds with for all entries and with DB Hints in 82 seconds for ~ 1.000.000 records and ~660 seconds compared to 1349 seconds for ~8.000.000 records..
Sample code from SAP Note below:
Original statement:
SELECT COL1 COL2 COL3 COL4 COL5
  FROM TAB1
  INTO CORRESPONDING FIELDS OF TABLE LT_RESULT
  FOR ALL ENTRIES IN LT_SOURCE_TMP
  WHERE COL3 = LT_SOURCE_TMP-COL3
  AND   COL4 = LT_SOURCE_TMP-COL4
  AND   COL5 = LT_SOURCE_TMP-COL5
Revision:
DATA: L_T_TABLNM TYPE RSDU_T_TABLNM,
      L_LINES TYPE I,
      L_HINT TYPE RSDU_HINT.
APPEND 'TAB1' TO L_T_TABLNM.
L_LINES = LINES( LT_SOURCE_TMP ).
CALL FUNCTION 'RSDU_CREATE_HINT_FAE'
  EXPORTING
    I_T_TABLNM   = L_T_TABLNM
    I_FAE_FIELDS = 3
    I_FAE_LINES  = L_LINES
    I_EQUI_JOIN  = RS_C_TRUE
  IMPORTING
    E_HINT       = L_HINT
  EXCEPTIONS
    OTHERS       = 0.
SELECT COL1 COL2 COL3 COL4 COL5
  FROM TAB1
  INTO CORRESPONDING FIELDS OF TABLE LT_RESULT
  FOR ALL ENTRIES IN LT_SOURCE_TMP
  WHERE COL3 = LT_SOURCE_TMP-COL3
  AND   COL4 = LT_SOURCE_TMP-COL4
  AND   COL5 = LT_SOURCE_TMP-COL5
          %_HINTS ADABAS  L_HINT.
Best regards,
Octavian