Generally, parked documents can be deleted separately. However, there is no option for deleting several documents at the same time. This ZDELEPARKED program solve this issue.

Step 1. Call transaction SE38 and create the ZDELEPARKED report.

              Title: Mass deletion of parked documents

              Type: Executable program

              Copy the report from the correction instructions then save and activate it.

              

Step 2. Create following text symbols (SE38 - text elements):

              001 General selections

              002 Processing status

              003 Delete parked documents

              004 Do you really want to delete the documents selected?

              005 No documents found

              006 Number of documents:

              007 Documents were already deleted.

              Save and activate the change.

              

Step 3. Create the following selection texts with reference to the dictionary:

              BELNR Document number

              BKTXT Document header text

              BLART Document type

              BLDAT Document date

              BUDAT Posting date

              BUKRS Company code

              GJAHR Fiscal year

              USNAM User

              XBLNR Reference

              XFRGE Released

              XPRFG Document complete

              XWFFR Release required.

              Save and activate the change.

              

Step 4. Call transaction SE41 (Menu Painter) with the following parameters:

              Program: ZDELEPARKED

              Status: DELE

              Choose CREATE.

              Short text: Delete parked documents

              Status type: Dialog status

a) Fill the SAVE function key (diskette) with the 'DELE' function code with the following parameters:

                       Functional type: Empty

                       Function text: Delete

                       Icon name: ICON_DELETE

                       Icon text: Delete

                       Fastpath: space

b) Fill the BACK function key (green arrow) with the 'BACK' function code.

c) Fill the EXIT function key (yellow arrow) with the '%EX' function code.

d) Fill the CANCEL function key (red arrow) with the 'RW' function code.

e) Fill the PRINT function key with the '%PRI' function code.

              

f) Create the LIST entry for the menu bar and assign to it these menu options:

                       %PRI Print

                       %PC Download

                       %EX Exit

g) Create the EDIT entry for the menu bar and assign to it these menu options:

                       DELE Delete

                       %SC  Find string

                       RW   Cancel

h) Create the GOTO entry for the menu bar and assign to it this menu option:

                       BACK Back

              

i) Save and activate the status.

              

Step 5. Activate the ZDELEPARKED report.

This sample program to find BADI and enhancement for a given transaction code. Create a custom program in your system by cut and paste example below codes.

REPORT ZTEST.

TABLES: TSTC,

TADIR,

MODSAPT,

MODACT,

TRDIR,

TFDIR,

ENLFDIR,

SXS_ATTRT ,

TSTCT.

DATA: JTAB LIKE TADIR OCCURS 0 WITH HEADER LINE.

DATA: FIELD1(30).

DATA: V_DEVCLASS LIKE TADIR-DEVCLASS.

PARAMETERS: P_TCODE LIKE TSTC-TCODE,

P_PGMNA LIKE TSTC-PGMNA .

DATA: WA_TADIR TYPE TADIR.

START-OF-SELECTION.

IF NOT P_TCODE IS INITIAL.

SELECT SINGLE * FROM TSTC WHERE TCODE EQ P_TCODE.

ELSEIF NOT P_PGMNA IS INITIAL.

TSTC-PGMNA = P_PGMNA.

ENDIF.

IF SY-SUBRC EQ 0.

SELECT SINGLE * FROM TADIR

WHERE PGMID = 'R3TR'

AND OBJECT = 'PROG'

AND OBJ_NAME = TSTC-PGMNA.

MOVE : TADIR-DEVCLASS TO V_DEVCLASS.

IF SY-SUBRC NE 0.

SELECT SINGLE * FROM TRDIR

WHERE NAME = TSTC-PGMNA.

IF TRDIR-SUBC EQ 'F'.

SELECT SINGLE * FROM TFDIR

WHERE PNAME = TSTC-PGMNA.

SELECT SINGLE * FROM ENLFDIR

WHERE FUNCNAME = TFDIR-FUNCNAME.

SELECT SINGLE * FROM TADIR

WHERE PGMID = 'R3TR'

AND OBJECT = 'FUGR'

AND OBJ_NAME EQ ENLFDIR-AREA.

MOVE : TADIR-DEVCLASS TO V_DEVCLASS.

ENDIF.

ENDIF.

SELECT * FROM TADIR INTO TABLE JTAB

WHERE PGMID = 'R3TR'

AND OBJECT in ('SMOD', 'SXSD')

AND DEVCLASS = V_DEVCLASS.

SELECT SINGLE * FROM TSTCT

WHERE SPRSL EQ SY-LANGU

AND TCODE EQ P_TCODE.

FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.

WRITE:/(19) 'Transaction Code - ',

20(20) P_TCODE,

45(50) TSTCT-TTEXT.

SKIP.

IF NOT JTAB[] IS INITIAL.

WRITE:/(105) SY-ULINE.

FORMAT COLOR COL_HEADING INTENSIFIED ON.

• Sorting the internal Table

sort jtab by OBJECT.

data : wf_txt(60) type c,

wf_smod type i ,

wf_badi type i ,

wf_object2(30) type C.

clear : wf_smod, wf_badi , wf_object2.

• Get the total SMOD.

LOOP AT JTAB into wa_tadir.

at first.

FORMAT COLOR COL_HEADING INTENSIFIED ON.

WRITE:/1 SY-VLINE,

2 'Enhancement/ Business Add-in',

41 SY-VLINE ,

42 'Description',

105 SY-VLINE.

WRITE:/(105) SY-ULINE.

endat.

clear wf_txt.

at new object.

if wa_tadir-object = 'SMOD'.

wf_object2 = 'Enhancement' .

elseif wa_tadir-object = 'SXSD'.

wf_object2 = ' Business Add-in'.

endif.

FORMAT COLOR COL_GROUP INTENSIFIED ON.

WRITE:/1 SY-VLINE,

2 wf_object2,

105 SY-VLINE.

endat.

case wa_tadir-object.

when 'SMOD'.

wf_smod = wf_smod + 1.

SELECT SINGLE MODTEXT into wf_txt

FROM MODSAPT

WHERE SPRSL = SY-LANGU

AND NAME = wa_tadir-OBJ_NAME.

FORMAT COLOR COL_NORMAL INTENSIFIED OFF.

when 'SXSD'.

• For BADis

wf_badi = wf_badi + 1 .

select single TEXT into wf_txt

from SXS_ATTRT

where sprsl = sy-langu

and EXIT_NAME = wa_tadir-OBJ_NAME.

FORMAT COLOR COL_NORMAL INTENSIFIED ON.

endcase.

WRITE:/1 SY-VLINE,

2 wa_tadir-OBJ_NAME hotspot on,

41 SY-VLINE ,

42 wf_txt,

105 SY-VLINE.

AT END OF object.

write : /(105) sy-ULINE.

ENDAT.

ENDLOOP.

WRITE:/(105) SY-ULINE.

SKIP.

FORMAT COLOR COL_TOTAL INTENSIFIED ON.

WRITE:/ 'No.of Exits:' , wf_smod.

WRITE:/ 'No.of BADis:' , wf_badi.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE:/(105) 'No userexits or BADis exist'.

ENDIF.

ELSE.

FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.

WRITE:/(105) 'Transaction does not exist'.

ENDIF.

AT LINE-SELECTION.

data : wf_object type tadir-object.

clear wf_object.

GET CURSOR FIELD FIELD1.

CHECK FIELD1(8) EQ 'WA_TADIR'.

read table jtab with key obj_name = sy-lisel+1(20).

move jtab-object to wf_object.

case wf_object.

when 'SMOD'.

SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).

CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.

when 'SXSD'.

SET PARAMETER ID 'EXN' FIELD SY-LISEL+1(20).

CALL TRANSACTION 'SE18' AND SKIP FIRST SCREEN.

ENDCASE.

SAP provides two different ways to incorporate SAP ALV into your reports or programs which need to deal with tabular data. They are mentioned below:

Using REUSE_ALV_* function modules

SAP offers some easy to use function modules using which different kinds of ALV grid can be displayed from your program. These function modules provide a very simplified programming approach to use SAP ALV to display and work with tabular data. All such function modules can be found under the Function group SALV & SLVC_FULLSCREEN in the package (development class) SLIS. These function modules provide an easy & simple to program way of using SAP ALV, but on the other hand compromise with some advanced functionalities and gives lesser flexibility to the programmer. Still, this is the easiest way to program SAP ALV for simple reports and applications where the main purpose of report/ program is to display a tabular result.

There are four different forms of SAP ALV exposed through reuse function modules in order to cater different kinds of data display requirements.

(A) Simple ALV list

This form of ALV is used to display single table display. All the function modules in the above mentioned function group SALV with prefix REUSE_ALV_LIST_ belong to this form of ALV e.g. REUSE_ALV_LIST_DISPLAY, REUSE_ALV_LIST_LAYOUT_INFO_SET, REUSE_ALV_LIST_SELECTIONS_SET etc. This form of ALV outputs a single list on one complete screen. There’s a very limited possibility to control the layout of this output screen.

Simple SAP ALV List

(B) Hierarchical sequential ALV list

This form of ALV lists is used to display 2 tables of data which form a 2-step hierarchy. The main function module to display this kind of ALV is REUSE_ALV_HIERSEQ_LIST_DISPLAY in function group SALV. There are some more function modules in function group SALV with prefix REUSE_ALV_HS_ belonging to this form of ALV. Typical to REUSE_ALV_* method of using ALV, it has a very limited possibility to control the layout of this output screen.

Hierarchical Sequential ALV List

This form of ALV lists is used to display multiple independent tables. All the function modules in above mentioned function group SALV having prefix REUSE_ALV_BLOCK_ belong to this form of ALV. Block ALV list is used to display multiple ALV lists on the same output screen one after another.

Block ALV List

(D) ALV Grid

This is the new generation of ALV replacing classical list formats mentioned above with grids. It’s used for the purpose similar to simple lists, but overtakes simple lists in terms of better usability, more in-built functionalities and look & feel. All the function modules related to this form of ALV can be found under function group SLVC_FULLSCREEN of package SLIS.

ALV Grid

Using ABAP Class CL_GUI_ALV_GRID

This method of programming ALV grid runs on Control framework & is based on ABAP Objects. It gives 100% control of programming ALV to the developers. You can use this method to work with ALV similar to other screen elements and also freely add other screen elements on the same screen along with ALV. The main ABAP Class involved in this method is CL_GUI_ALV_GRID.

Multiple ALV Grids & Tree on same screen using CL_GUI_ALV_GRID method

I would be explaining important aspects of each of these methods to work with the SAP ALV in detail in my following posts.

Use the MODIFYstatement.

We can use the table key to find and change a single line using its key, or find and change a set of lines that meet a certain condition. If the table has a non-unique key and there are duplicate entries, the first entry is changed.

Changing a Line Using the Table Key

To change a single line, use the following statement:

MODIFY TABLE itab FROM wa [TRANSPORTING f₁ f₂ ...].

The work area wa, which must be compatible with the line type of the internal table, plays a double role in this statement. Not only it is used to find the line that you want to change, but it also contains the new contents. The system searches the internal table for the line whose table key corresponds to the key fields in wa.

The system searches for the relevant table types as follows:

·        Standard tables

Linear search, where the runtime is in linear relation to the number of table entries. The first entry found is changed.

·        Sorted tables

Binary search, where the runtime is in logarithmic relation to the number of table entries. The first entry found is changed.

·        Hashed tables

The entry is found using the hash algorithm of the internal table. The runtime is independent of the number of table entries.

If a line is found, the contents of the non-key fields of the work area are copied into the corresponding fields of the line, and sy-subrc is set to 0. Otherwise, sy-subrc is set to 4. If the table has a non-unique key and the system finds duplicate entries, it changes the first entry.

You can specify the non-key fields that you want to assign to the table line in the TRANSPORTING addition. You can also specify the fields f₁ f₂ … dynamically using (n₁) (n₂) … as the contents of a field n₁ n₂ …. If <n_i> is empty when the statement is executed, it is ignored. You can also restrict all fields f₁ f₂ … to subfields by specifying offset and length.

For tables with a complex line structure, the use of the TRANSPORTINGaddition results in better performance, provided the system does not have to transport unnecessary table-like components.

Changing Several Lines Using a Condition

To change one or more lines using a condition, use the following statement:

MODIFY itab FROM wa TRANSPORTING f₁ f₂ ... WHERE cond.

This processes all of the lines that meet the logical condition cond. The logical expression cond can consist of more than one comparison. In each comparison, the first operand must be a component of the line structure. If the table lines are not structured, the first operand can also be the expression TABLE_LINE. The comparison then applies to the entire line. If the line type of the internal table contains object reference variables as component comp or if the entire line type is a reference variable, the attributes of the attr object to which the respective line reference points can be specified as comparison values using comp->attr or table_line->attr.

The work area wa, which must be compatible with the line type of the internal table, contains the new contents, which in turn will be assigned to the relevant table line using the TRANSPORTING addition. Unlike the above MODIFYstatement, the TRANSPORTING addition is not optional here. Furthermore, you can only modify the key fields of the internal table if it is a standard table. If at least one line is changed, the system sets sy-subrc to 0, otherwise to 4.

REPORT demo_int_tables_modify .

DATA: BEGIN OF line,
        col1 TYPE i,
        col2 TYPE i,
      END OF line.

DATA itab LIKE HASHED TABLE OF line WITH UNIQUE KEY col1.

DO 4 TIMES.
  line-col1 = sy-index.
  line-col2 = sy-index ** 2.
  INSERT line INTO TABLE itab.
ENDDO.

line-col1 = 2.
line-col2 = 100.

MODIFY TABLE itab FROM line.

LOOP AT itab INTO line.
  WRITE: / line-col1, line-col2.
ENDLOOP.

The list output is:

         1        1
         2      100
         3        9
         4       16

The program fills a hashed table with a list of square numbers. The MODIFY statement changes the line of the table in which the key field col1 has the value 2.

REPORT demo_int_tables_modify_transp.

DATA: BEGIN OF line,
        col1 TYPE i,
        col2 TYPE i,
      END OF line.

DATA itab LIKE HASHED TABLE OF line WITH UNIQUE KEY col1.

DO 4 TIMES.
  line-col1 = sy-index.
  line-col2 = sy-index ** 2.
  INSERT line INTO TABLE itab.
ENDDO.

line-col2 = 100.

MODIFY itab FROM line TRANSPORTING col2
            WHERE ( col2 > 1 ) AND ( col1 < 4 ).

LOOP AT itab INTO line.
  WRITE: / line-col1, line-col2.
ENDLOOP.

The list output is:

         1        1
         2      100
         3      100
         4       16

The program fills a hashed table with a list of square numbers. The MODIFY statement changes the lines of the table where the content of field col2 is greater than 1 and the content of field col1 is less than 4.

Changing Table Lines Using the Index

You can use the MODIFY statement to change lines in tables using their index. There is also an obsolete variant of the WRITE TOstatement that you can use to modify lines in standard tables.

Changing Single Lines using MODIFY

To change a line using its index, use the following statement:

MODIFY itab FROM wa [INDEX idx] [TRANSPORTING f₁ f₂... ].

The work area wa specified in the FROM addition replaces the addressed line in the itab table. The work area must be convertible into the line type of the internal table.

If you use the INDEX option, the contents of the work area overwrite the contents of the line with the index idx. If the operation is successful, sy-subrc is set to 0. If the internal table contains fewer lines than idx, no line is changed and sy-subrc is set to 4.

Without the INDEX addition, you can only use the above statement within a LOOP. In this case, you delete the current line. idx is implicitly set to sy-tabix .

When you change lines in sorted tables, remember that you must not change the contents of key fields, and that a runtime error will occur if you try to replace the contents of a key field with another value. However, you can assign the same value.

The TRANSPORTING addition allows you to specify the fields that you want to change explicitly in a list.  If you change a sorted table, you may only specify non-key fields.

REPORT demo_int_tables_modify_ind.

DATA: BEGIN OF line,
        col1 TYPE i,
        col2 TYPE i,
      END OF line.

DATA itab LIKE TABLE OF line.

DO 3 TIMES.
  line-col1 = sy-index.
  line-col2 = sy-index ** 2.
  APPEND line TO itab.
ENDDO.

LOOP AT itab INTO line.
  IF sy-tabix = 2.
    line-col1 = sy-tabix * 10.
    line-col2 = ( sy-tabix * 10 ) ** 2.
    MODIFY itab FROM line.
  ENDIF.
ENDLOOP.

LOOP AT itab INTO line.
  WRITE: / sy-tabix, line-col1, line-col2.
ENDLOOP.

This produces the following output:

         1         1          1
         2        20        400
         3         3          9

Here, a sorted table itab is created and filled with three lines. The second line is replaced by the contents of the work area line.

REPORT demo_int_tables_modify_ind_ind.

DATA name(4) TYPE c VALUE 'col2'.

DATA: BEGIN OF line,
         col1 TYPE i,
         col2 TYPE i,
      END OF line.

DATA itab LIKE SORTED TABLE OF line WITH UNIQUE KEY col1.

DO 4 TIMES.
  line-col1 = sy-index.
  line-col2 = sy-index ** 2.
  APPEND line TO itab.
ENDDO.

line-col2 = 222.
MODIFY itab FROM line INDEX 2 TRANSPORTING (name).

line-col1 = 3.
line-col2 = 333.
MODIFY itab FROM line INDEX 3.

LOOP AT itab INTO line.
  WRITE: / sy-tabix, line-col1, line-col2.
ENDLOOP.

The list output is:

         1         1          1
         2         2        222
         3         3        333
         4         4         16

The example fills a sorted table with four lines. In the second and third lines, the component col2 is modified. If the third line were to be changed so that the value of line-col1 was no longer 3, a runtime error would occur, since the key fields of sorted tables may not be changed.