Need nested loop's solution....

Question

hi..
i have done following coding for my one senario..i've used nested loop.but can anyone pls give me other solution than nested loop statement?
i dont wnat to use nested loop...
SELECT WI_ID WI_STAT WI_CD WI_AAGENT FROM SWWWIHEAD           "FETCHING WORK ITEM DATA FROM THE SWWWIHEAD
    INTO TABLE IT_SWWWIHEAD
    WHERE WI_CD IN SO_WI_CD.
  SORT IT_SWWWIHEAD.
  IF SY-SUBRC = 0.
  <b>  LOOP AT IT_SWWWIHEAD INTO WA_SWWWIHEAD.</b>
      CALL FUNCTION 'SWI_GET_DEPENDENT_WORKITEMS'      "FUNCTION MODULE TO GET DEPENDENT WORK ITEM ID, IF ANY.
        EXPORTING
          WI_ID         = WA_SWWWIHEAD-WI_ID
        TABLES
          DEPENDENT_WIS = IT_SWWWIHEAD_D.
      IF IT_SWWWIHEAD_D IS NOT INITIAL.
        DELETE IT_SWWWIHEAD_D WHERE WI_TYPE <> 'W'.
        SORT IT_SWWWIHEAD_D.
      <b>  LOOP AT IT_SWWWIHEAD_D INTO WA_SWWWIHEAD_D.</b>
          CALL FUNCTION 'SAP_WAPI_READ_CONTAINER'          "FUNCTION MODULE TO GET DATA FROM EVERY DEPENDENT ID.
            EXPORTING
              WORKITEM_ID                    = WA_SWWWIHEAD_D-WI_ID
            LANGUAGE                       = SY-LANGU
            USER                           = SY-UNAME
          IMPORTING
            RETURN_CODE                    =
            IFS_XML_CONTAINER              =
            IFS_XML_CONTAINER_SCHEMA       =
           TABLES
             SIMPLE_CONTAINER               = IT_SIM_CONT
           MESSAGE_LINES                  =
           MESSAGE_STRUCT                 =
           SUBCONTAINER_BOR_OBJECTS       =
            SUBCONTAINER_ALL_OBJECTS       = IT_SUBCONTAINER
          READ TABLE IT_SIM_CONT
              INTO WA_SIM_CONT WITH KEY ELEMENT = '_WI_RESULT'.        "getting the result(approved or rejected).
          IF SY-SUBRC = 0.
            IF wa_sim_cont-value = '0001'.
              WA_FINAL-WI_STAT = 'APPROVED'.
            ELSEIF WA_SIM_CONT-VALUE = '0002'.
              WA_FINAL-WI_STAT = 'REJECTED'.
            ENDIF.
          ENDIF.
          READ TABLE IT_SUBCONTAINER
              INTO WA_SUBCONTAINER WITH KEY ELEMENT = 'SODATA'.  "getting SO DOCUMENT for this workitem.
          IF SY-SUBRC = 0.
            WA_FINAL-WI_AAGENT    = WA_SWWWIHEAD_D-WI_AAGENT.
          ENDIF.
            WA_FINAL-WI_ID        = WA_SWWWIHEAD-WI_ID.
            WA_FINAL-WI_ID_D      = WA_SWWWIHEAD_D-WI_ID.
            WA_FINAL-WI_CD        = WA_SWWWIHEAD-WI_CD.
            WA_FINAL-WI_SO        = wa_subcontainer-value+0(10).
            WA_FINAL-WI_RESULT    = WA_SIM_CONT-VALUE.
            SELECT SINGLE VKORG MAHDT FROM VBAK
              INTO (VKORG, MAHDT)
              WHERE VBELN = WA_FINAL-WI_SO.
            IF SY-SUBRC = 0.
              WA_FINAL-WI_VKORG = VKORG.
              IF MAHDT <> '00000000'.
                WA_FINAL-WI_FINAL_RESULT = 'OK'.
              ELSE.
                WA_FINAL-WI_FINAL_RESULT = 'PENDING'.
              ENDIF.
            ENDIF.
            APPEND WA_FINAL TO IT_FINAL.
            CLEAR WA_FINAL.
   <b>     ENDLOOP.</b>
        CLEAR IT_SWWWIHEAD_D[].
        CLEAR IT_SIM_CONT[].
      ENDIF.
  <b>  ENDLOOP.</b>  ENDIF.

Answer 1

hi sagar,
Pls go through the following explanations for understanding abt control level processing.
Control level processing is allowed within a LOOP over an internal table. This means that you can divide sequences of entries into groups based on the contents of certain fields.
Internal tables are divided into groups according to the sequence of the fields in the line structure. The first column defines the highest control level and so on. The control level hierarchy must be known when you create the internal table.
The control levels are formed by sorting the internal table in the sequence of its structure, that is, by the first field first, then by the second field, and so on. Tables in which the table key occurs at the start of the table are particularly suitable for control level processing.
The following diagram illustrates control level processing in a sorted table, where different field contents in the first three fields are indicated by different colors:
Each change of color in a column indicates a control level change in the corresponding hierarchy level. Within the processing block of a loop, you can use the control level statement AT to react to a control level change. This enables you to restrict statements to a certain set of lines. You can thus use the SUM statement to calculate totals from subsets of all lines.
The AT statement introduces a statement block that you end with the ENDAT statement.
AT <level>.
  <statement block>
ENDAT.
You can react to the following control level changes:
<level>
Meaning
FIRST
First line of the internal table
LAST
Last line of the internal table
NEW <f>
Beginning of a group of lines with the same contents in the field <f> and in the fields left of <f>
END Of <f>
End of a group of lines with the same contents in the field <f> and in the fields left of <f>
You can use control level statements to react to control breaks in internal tables instead of programming them yourself with logical expressions. Within the loop, you must order the AT-ENDAT statement blocks according to the hierarchy of the control levels. If the internal table has the columns <f1>, <f 2>, ...., and if it is sorted by these columns, you must program the loop as follows:
LOOP AT <itab>.
  AT FIRST. ... ENDAT.
    AT NEW <f1>. ...... ENDAT.
      AT NEW <f2 >. ...... ENDAT.
          <single line processing>
      AT END OF <f2>. ... ENDAT.
    AT END OF <f1>. ... ENDAT.
  AT LAST. .... ENDAT.
ENDLOOP.
The innermost hierarchy level <single line processing> processes the table lines that do not correspond to a control level change. You do not have to use all control level statements. But you must place the used ones in the above sequence. You should not use control level statements in loops where the line selection is restricted by WHERE or FROM and TO. Neither should the table be modified during the loop.
If a control level field <fi> is not known until runtime, you can specify it dynamically as (<n i>) where <n i> contains the field of <f i>. If <n i> is empty at runtime, the criterion for changing the control level is ignored. You can restrict the search to partial fields by specifying offset and length.
If you are working with a work area <wa>, it does not contain the current line in the AT... ENDAT statement block. All character fields to the right of the current group key are filled with asterisks (*). All other fields to the right of the current group key contain their initial value.
Within an AT...ENDAT block, you can calculate the contents of the numeric fields of the corresponding control level using the SUM statement.
SUM.
You can only use this statement within a LOOP. If you use SUM in an AT - ENDAT block, the system calculates totals for the numeric fields of all lines in the current line group and writes them to the corresponding fields in the work area (see example in ). If you use the SUM statement outside an AT - ENDAT block (single entry processing), the system calculates totals for the numeric fields of all lines of the internal table in each loop pass and writes them to the corresponding fields of the work area. It therefore only makes sense to use the SUM statement in AT...ENDAT blocks.
If the table contains a nested table, you cannot use the SUM statement. Neither can you use it if you are using a field symbol instead of a work area in the LOOP statement.
Examples
DATA: BEGIN OF LINE,
         COL1 TYPE C,
         COL2 TYPE I,
         COL3 TYPE I,
      END OF LINE.
DATA ITAB LIKE HASHED TABLE OF LINE
          WITH UNIQUE KEY COL1 COL2.
LINE-COL1 = 'A'.
DO 3 TIMES.
  LINE-COL2 = SY-INDEX.
  LINE-COL3 = SY-INDEX ** 2.
  INSERT LINE INTO TABLE ITAB.
ENDDO.
LINE-COL1 = 'B'.
DO 3 TIMES.
  LINE-COL2 = 2 * SY-INDEX.
  LINE-COL3 = ( 2 * SY-INDEX ) ** 2.
  INSERT LINE INTO TABLE ITAB.
ENDDO.
SORT ITAB.
LOOP AT ITAB INTO LINE.
  WRITE: / LINE-COL1, LINE-COL2, LINE-COL3.
  AT END OF COL1.
    SUM.
    ULINE.
    WRITE: / LINE-COL1, LINE-COL2, LINE-COL3.
    SKIP.
  ENDAT.
  AT LAST.
    SUM.
    ULINE.
    WRITE: / LINE-COL1, LINE-COL2, LINE-COL3.
  ENDAT.
ENDLOOP.
The output is:
A 1 1
A 2 4
A          3          9
A          6         14
B          2          4
B 4 16
B 6 36
B         12         56
        18         70
The program creates a hashed table ITAB, fills it with six lines, and sorts it. In the LOOP - ENDLOOP block, the work area LINE is output for each loop pass. The first field of the table key, COL1, is used for control level processing. The total for all numeric fields is always calculated when the contents of COL1 change and when the system is in the last loop pass.
DATA: BEGIN OF LINE,
        CARRID   TYPE SBOOK-CARRID,
        CONNID   TYPE SBOOK-CONNID,
        FLDATE   TYPE SBOOK-FLDATE,
        CUSTTYPE TYPE SBOOK-CUSTTYPE,
        CLASS    TYPE SBOOK-CLASS,
        BOOKID   TYPE SBOOK-BOOKID,
      END OF LINE.
DATA ITAB LIKE SORTED TABLE OF LINE WITH UNIQUE KEY TABLE LINE.
SELECT CARRID CONNID FLDATE CUSTTYPE CLASS BOOKID
       FROM SBOOK INTO CORRESPONDING FIELDS OF TABLE ITAB.
LOOP AT ITAB INTO LINE.
  AT FIRST.
    WRITE / 'List of Bookings'.
    ULINE.
  ENDAT.
    AT NEW CARRID.
      WRITE: / 'Carrid:', LINE-CARRID.
    ENDAT.
      AT NEW CONNID.
        WRITE: / 'Connid:', LINE-CONNID.
      ENDAT.
        AT NEW FLDATE.
          WRITE: / 'Fldate:', LINE-FLDATE.
        ENDAT.
          AT NEW CUSTTYPE.
            WRITE: / 'Custtype:', LINE-CUSTTYPE.
          ENDAT.
               WRITE: / LINE-BOOKID, LINE-CLASS.
            AT END OF CLASS.
              ULINE.
            ENDAT.
ENDLOOP.
In this example, the sorted internal table ITAB is filled with data from the database table SBOOK using the Open SQL statement SELECT. The sequence of the columns in the internal table defines the control level hierarchy. Since the table key is the entire line, the sort sequence and the control level hierarchy are the same. The sequence of the AT-ENDAT blocks within the LOOP and ENDLOOP statements is important.
The output is as follows:
List of Bookings
Carrid: AA
Connid: 0017
Fldate: 1998/11/22
Custtype: B
00063509 C
00063517 C
00063532 F
00063535 F
Custtype: P
00063653 C
00063654 C
00063668 F
00063670 F
Fldate: 1998/29/11
Custtype: B
00064120 C
00064121 C
and so on.
<b>pls reward if helpful.</b>