Count number of records in a internal table

hi
i want to count number of records in internal table
pls let me know how to count the number of records in a internal table.
regards
Arora

hi
one way is
data field type i.
Decribe table itab lines field.
write: / field.
displays the no of records in tha internal table
or if u want to write logic.
data:
w_count type i.
loop at itab.
w_count = w_count + 1.
endloop.
write: / w_count.
displays the no of records.
reward points if useful.

Similar Messages

To count number of records in an internal table for a condition

Hello All,
I want to count number of records in an internal table for a condition.
For e.g. -- I have one internal table IT which having fields F1, F2, F3, F4, F5.
Now, I want number of records in itnternal table IT where F1 = 'ABC'.
Is it possible to do..?? If yes, then how.??
Thanks in advance...!!
Regards,
Poonam.

Hi,
If you mean an internal table, there are a few ways to do this.
1 One would be to loop over the table with a WHERE clause and increment a counter.
data: lv_counter type i.
clear lv_counter.
loop at itab where fld1 = 'ABC'.
lv_counter = lv_counter + 1.
endloop.
lv_counter now has the number of rows per the condiction.
2 Well, you may want to try this as well, and compare to the LOOP way. Not sure what kind of overhead you may get doing this way. Here ITAB is our main internal table, and ITAB_TMP is a copy of it. Again I think there may be some overhead in doing the copy. Next, delete out all records which are the reverse of your condition. Then whatever is left is the rows that you want to count. Then simply do a LINES operator on the internal table, passing the number of lines to LV_COUNT.
data: itab type table of ttab.
data: itab_tmp type table of ttab.
itab_tmp[] = itab[].
delete table itab_tmp where fld1 'ABC'.
lv_count = lines( itab_tmp ).
Thanks & Regards,
ShreeMohan

Spilt the number of records in a internal table

Hi all,
        I have a requirement where i must spilt the number of records in my internal table itab .Say if i have 2000 records , i must spilt it taking the first 990 records and doing some posting using Bapi and again take the next 990 records and do the posting .Can some one help me out.
Good answers will be rewarded with points.

Hi,
You can use these instructions using two internal tables, but please be aware to not forget any line.
REFRESH my_table2.
APPEND LINES OF my_table FROM 1 TO 990 TO my_table2.
CALL FUNCTION 'BAPI'....
             (with my_table2)
REFRESH my_table2.
APPEND LINES OF my_table FROM 991 TO my_table2.
CALL FUNCTION 'BAPI'....
             (with my_table2)
Regards,
Mathieu

Count Number of Records in Oracle Database Table

Please help me to see if I "set" and "return" the number of records in my database table correctly (I am using the Oracle 9i):
   public int getNumberOfRecipientBeans() throws AssertionException, DatabaseException
      Connection conn = null;
      PreparedStatement stmt = null;
      String query = "SELECT count(*) FROM ContactEntry WHERE ContactTypeID = 6";
      ResultSet rs = null;
      try
         conn = DBConnection.getDBConnection();
         stmt = conn.prepareStatement( query );
         rs = stmt.executeQuery();
         // do I have to set anything here?
         if ( !rs.next() )
            throw new AssertionException("Assertion in servuce.getNumberOfRecipients");
          // Am I returning the counts here?
          return rs.getInt( 1 );
      catch( SQLException sqle )
         sqle.printStackTrace();
         throw new DatabaseException( "Error executing SQL in service.getNumberOfRecipients." );
      finally
         if ( conn != null )
            try
               stmt.close();
               stmt = null;
               conn.close();
            catch( Exception Ex )
               System.out.println( "Problem occurs while closing " + Ex );
            conn = null;

public class MyE extends Exception {
    public MyE() {
        super(); // this line is not necessary. An empty method would suffice
    public MyE(String msg) {
        super(msg);
    // Check the API for Exception or Throwable--I may have the args backward
    public MyE(String msg, Throwable cause) {
        super(msg, cause);
    public MyE(Throwable cause) {
        super(cause);
// Replace the log_warn() calls with appropriate logging calls for your context
public class Closer {
    public static final void close(ResultSet closeMe) {
        if (closeMe != null) {
            try {
                closeMe.close();
            catch (Throwable th) { log_.warn("Closing " + closeMe + ": ", th); }
    public static final void close(Statement closeMe) {
        if (closeMe != null) {
            try {
                closeMe.close();
            catch (Throwable th) { log_.warn("Closing " + closeMe + ": ", th); }
    public static final void close(Connection closeMe) {
        if (closeMe != null) {
            try {
                closeMe.close();
            catch (Throwable th) { log_.warn("Closing " + closeMe + ": ", th); }
    public static final void close(ResultSet rs, Statement stmt, Connection con) {
        close(rs);
        close(stmt);
        close(con);
}

Count No of records in an internal table using 4 fields

Hi All,
I have an internal table with about 50,000 records. I need to group these (sort) based on 4 fields and then provide the count for each combination of the 4 fields.
For eg, if I have 3 records in the table which have the same values for all the 4 fields - say A,B,C,D, then the count is to be taken as 3 for that combination.
So my output will be
A B C D - COUNT -4 and so on.
I am looking for a efficient technique (good performance) to meet the above requirements given without too many loops. Please advise if you have a good method.
Thanks as always!
Liz

You can use SORT and DELETE ADJACENT DUPLICATES FROM.
SORT itab by field1 field2 field3 field4.
DELETE ADJACENT DUPLICATES FROM itab COMPARING field1 field2 field3 field4.
you will be left with the unique combinations of the 4 fields.
LINES( itab ) will give you the number of records.
Thanks,
Sai Ramesh.

Max number of records in an internal table

Hi,
Can any one tell me what is the Max Number of records we can get into an internal table.
if you have any link of sap help on this please FWD.
thanks in Adv.
Regards,
Lakshmikanth.T.V

Hi lakshmikanth,
Internal Tables as Dynamic Data Objects
Internal tables are always completely specified regarding row type, key and access type. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.
regards,
keerthi.

Count the Records in an internal table without a loop.

How do i count the number of records in an internal table without using the loop statement.
The Describe statement give the total no. of records in the internal table.But i want the count of the key fields in the internal table
For eg
Row Field
1       A
2       A
3       A
4       B
5       B
6       C
Count of A = 3
Count of B = 2
Count of C = 1

Dilip,
I think isn't posible. Only 3 ideas:
1ª, make other table "table2", similar to your actual table.
     table2[] = yourtable[].
     delete table2 where key <> 'A'.
     describe table table2 lines contA.
    But depending the amount of data, you may have problems in performance or memory consumption...
2ª, make other table, only with the keys fields and a count field,
    data begin table2
       key_field1,
       cont type i.
    end data.
   when you append lines to yourdata, make a collect to this table:
    table2-keys = yourtable-keys.
    table2-cont = 1.
   collect table2.
   But only works if you can modify the program where data is appended, and you may be carefull when data is deleted :-(...
3ª if your data if filled in a select, you may fill the table2 of point 2ª, making a similar select but:
   select keyfields count( * ) into table table2
from ...
where (the same you have to fill your original table...)
   group by keys.
But you have the same problem is data is deleted later...
I hope that any of the three is useful for you...
Edited by: Diego Alvarez on Jan 5, 2010 5:09 PM

Number of records in a standard table

Hi,
How to find number of records, without fetching them into a internal table?
is there any command for that?
I want to know the number of records of a standard table in a report.
Thanks

Hi,
If you want to know the number of records in your internal table after select statement.
You can use the below statement.
data : wa_lines like sy-tfill.
DESCRIBE TABLE itab LINES WS_LINES.
In wa_lines you will have the number of records.
If you want to know the number of records from standard itself.
You can use below :
select count(*) from table into variable
endselect.
Thanks,
Sriram Ponna.

Hi Gurus! how to count number of records in any column of ALV Grid report

Hi Guys!
I want to know how can we count the number of records in any column selected by the user. Like for oe customer there might be 20 sale order that means for 10 customer there will be 200 Sale order. So if i select cutomer number column ti should give 10 out put and whern select sale order it should give 200 as output.
-Anurag Jain

Hi,
Either you can use the hotspot_click event or double_click to show the Pop-up info of the Sales Order count or customer Count depending on the selection.
In the hotspot_click event method you have E_ROW_ID E_COLUMN_ID..using these you can find the Sales Ordert or customer Number.. Loop the internal table and find the Count.
In the double_click event method you have E_ROW E_COLUMN..using these you can find the Sales Ordert or customer Number.. Loop the internal table and find the Count.

How to find number of lines in an internal table

Dear all,
how to find number of records present in an internal table.

DESCRIBE TABLE
Syntax
DESCRIBE TABLE itab [KIND knd] [LINES lin] [OCCURS n].
Extras:
1. ... KIND knd
2. ... LINES lin
3. ... OCCURS n
Effect
This statement determines some properties of the internal table itab and assigns them to the specified variables. The various additions enable you to determine the table type, the number of currently filled rows and the initial memory requirement.
In addition, the system fields sy-tfill and sy-tleng are filled with the current number of table rows and the length of a table row in bytes.
Notes
For detailed information about an internal table, you should use the methods of RTTS of the DESCRIBE TABLE statement.
Without the specification of an addition, the statement DESCRIBE TABLE only sets the system fields sy-tfill and sy-tleng.
Addition 1
... KIND knd
Effect
The table type of the internal table itab is determined and a corresponding one-digit identification is assigned to the data object knd. A character-type data type is expected for the data object. The identifications are "T" for standard tables, "S" for sorted tables and "H" for hashed tables. These values are also defined as constants sydes_kind-standard, sydes_kind-sorted, and sydes_kind-hashed in the type group SYDES.
Addition 2
... LINES lin
Effect
The current number of table rows of the internal table itab is determined and is assigned to the data object lin.The data type i is expected for the data object.
Note
As of release 6.10, the current number of rows of an internal table can also be determined using the in-built function lines.
Addition 3
... OCCURS n
Effect
The initial memory requirement defined during the creation of the internal table with the addition INITIAL SIZE or the obsolete addition OCCURS is determined and assigned to the data object n. The data type i is expected for the data object.
Example
Descending sorting of a generically typed internal table in a subprogram. Since sorted tables cannot be sorted in a descending order, the table type is checked to avoid an exception that cannot be handled.
TYPE-POOLS sydes.
FORM sort_descending CHANGING itab TYPE ANY TABLE.
DATA tabkind(1) TYPE c.
DESCRIBE TABLE itab KIND tabkind.
IF tabkind = sydes_kind-standard OR
     tabkind = sydes_kind-hashed.
    SORT itab DESCENDING.
ELSEIF tabkind = sydes_kind-sorted.
    MESSAGE '...' TYPE 'E'.
ELSE.
    MESSAGE '...' TYPE 'E'.
ENDIF.
ENDFORM.
DESCRIBE FIELD INTO
Note
This statement is for internal use only.
It cannot be used in application programs.
Syntax
DESCRIBE FIELD dobj INTO td.
Effect
All characteristics of the field f, its components , sub-components etc. are displayed in the field td (type description). td has to be of the type SYDES_DESC, defined in Type Group SYDES. Because of this, the type group SYDES must be integrated into the ABAP-program with a TYPE-POOLS statement .
The structure SYDES_DESC has two table-type components TYPES and NAMES:
In TYPES, the tree structure of the type belonging to f is displayed. The components of a node are stored in the table TYPES in a continuous manner. Beginning and end of the line area that represents the components are stored in TYPES-FROM and TYPES-TO. The reference to the superior node can be found in TYPES-BACK. If no superior resp. subordinate node exists, then this is marked by the value 0 (For the relevance of further components, refer to the following sections).
The names of components, types etc. are not stored directly in TYPES. Instead, the components TYPES-IDX_... hold an index in the name table NAMES. The value 0 indicates that there is no reference to the name table.
NAMES contains the possibly fragmented names in the component NAMES-NAME. If a name continues in the following line, this is indicated by an asterisk ('*') in the component NAMES-CONTINUE.
The type description table (TYPES) not only stores information about the tree structure but also further information about the type of f resp. its components. This includes especially all information that can be determined using the usual additions to DESCRIBE FIELD. In detail, TYPES contains the following columns:
IDX_NAME
Component Name
IDX_USER_TYPE
Name of a user-defined type, i.e., a type that was defined through its TYPES-statement. Derived types (... TYPE A-B) and structures from the ABAP-Dictionary are not considered to be user-defined types.
CONTEXT
For user-defined types only: The context, in which the type is defined. Possible values are defined in the constant SYDES_CONTEXT of the type group SYDES. Please only use these constants to carry out a comparison. In detail, we distinguish between the following type contexts:
SYDES_CONTEXT-PROGRAM: Program-global type
SYDES_CONTEXT-FORM   : FORM-local type
SYDES_CONTEXT-FUNCTION: FUNCTION-local type
SYDES_CONTEXT-METHOD : METHOD-local type
IDX_CONTEXT_NAME
For user-defined types only:
With a local context: The name of the FORM or FUNCTION, whose type was defined. The name of the associated program is then the first entry in the name table.
With a global context: The name of the program in which the type was defined.
IDX_EDIT_MASK
Conversion routine from the ABAP-Dictionary, is in accordance with the addition EDIT MASK at simple DESCRIBE.
IDX_HELP_ID
Help-Id when referencing to fields from the ABAP-Dictionary
LENGTH
Internal length, corresponds to the addition LENGTH at simple DESCRIBE
OUTPUT_LENGTH
Output length, corresponds to the addition OUTPUT-LENGTH at simple DESCRIBE
DECIMALS
Number of decimal digits, corresponds to the addition DECIMALS at simple DESCRIBE
TYPE
ABAP-Type, corresponds to the addition TYPE at simple DESCRIBE
TABLE_KIND
A table type is stored here for the components which represent an internal table. The same values are returned as with the variant DESCRIBE TABLE itab KIND k. Components which do not represent a table get the return value set to SYDES_KIND-UNDEFINED (see type group SYDES).
Example
Example definition of the complex data type EMPLOYEE_STRUC:
PROGRAM DESCTEST.
TYPES: BEGIN OF name_struc,
         first TYPE c LENGTH 20,
         last   TYPE c LENGTH 20,
       END OF name_struc,
       BEGIN OF absence_time_struc,
         day        TYPE d,
         from       TYPE t,
         to         TYPE t,
       END OF absence_time_struc,
       phone_number TYPE n LENGTH 20,
       BEGIN OF employee_struc,
         id         LIKE sbook-customid,
         name       TYPE name_struc,
         BEGIN OF address,
           street TYPE c LENGTH 30,
           zipcode TYPE n LENGTH 4,
           place   TYPE c LENGTH 30,
         END OF address,
         salary_per_month TYPE p LENGTH 10 DECIMALS 3,
         absent           TYPE STANDARD TABLE OF absence_time_struc
                               WITH NON-UNIQUE DEFAULT KEY,
         phone            TYPE STANDARD TABLE OF phone_number
                               WITH NON-UNIQUE DEFAULT KEY,
       END OF employee_struc.
You can determine the structure of the type EMPLOYEE_STRUC by collecting the type group SYDES as follows:
TYPE-POOLS: sydes.
DATA: employee TYPE employee_struc,
      td       TYPE sydes_desc.
DESCRIBE FIELD employee INTO td.
The following table shows a few selected columns of the type description table TD-TYPES. For a better overview, the names of the columns IDX_NAME, IDX_UERR_TYPE and IDX_EDIT_MASK have been shortened:
    |FROM| TO |BACK|NAME|UTYP|EMSK|TYPE
|--||||||--
1 | 2 | 7 | 0 | 0 | 2 | 0 | v
2 | 0 | 0 | 1 | 6 | 0 | 4 | N
3 | 8 | 9 | 1 | 7 | 5 | 0 | u
4 | 10 | 12 | 1 | 8 | 0 | 0 | u
5 | 0 | 0 | 1 | 9 | 0 | 0 | P
6 | 13 | 13 | 1 | 11 | 0 | 0 | h
7 | 17 | 17 | 1 | 12 | 0 | 0 | h
8 | 0 | 0 | 3 | 13 | 0 | 0 | C
9 | 0 | 0 | 3 | 14 | 0 | 0 | C
10 | 0 | 0 | 4 | 15 | 0 | 0 | C
11 | 0 | 0 | 4 | 16 | 0 | 0 | N
12 | 0 | 0 | 4 | 17 | 0 | 0 | C
13 | 14 | 16 | 6 | 0 | 18 | 0 | u
14 | 0 | 0 | 13 | 20 | 0 | 0 | D
15 | 0 | 0 | 13 | 21 | 0 | 0 | T
16 | 0 | 0 | 13 | 22 | 0 | 0 | T
17 | 0 | 0 | 7 | 0 | 0 | 0 | N
Please note that the entries in rows 6 and 7 represent internal tables (ABAP-Type h). There is always an entry for the corresponding row type (rows 13 and 17) to an internal table.
The indices in the rows 5 to 7 refer to entries in the name table TD-NAMES. If you look, e.g., at row 3, you find the corresponding component name in TD-NAMES from row 7 (NAME) onward and the corresponding user type from row 5 (NAME_STRUC) onward.
In the name table TD-NAMES you find the following entries. Note that the names SALARY_PER_MONTH and ABSENCE_TIME_STRUC are stored in two parts:
    |CONTINUE|NAME                   |CONTINUE|NAME
|--|     -||--
1 |        |DESCTEST            12 |        |PHONE
2 |        |EMPLOYEE_STRUC      13 |        |FIRST
3 |        |SBOOK-CUSTOMID      14 |        |LAST
4 |        |==ALPHA             15 |        |STREET
5 |        |NAME_STRUC          16 |        |ZIPCODE
6 |        |ID                  17 |        |PLACE
7 |        |NAME                18 |   *    |ABSENCE_TIME_ST
8 |        |ADDRESS             19 |        |RUC
9 |   *    |SALARY_PER_MONT     20 |        |DAY
10 |        |H                   21 |        |FROM
11 |        |ABSENT              22 |        |TO

Maximum record length in internal table?

Is there a maximum record length in an internal table? Please note: My question is NOT related to table space. I'm referring only to the length of an individual record (A.K.A. row length).
I am using a work area to insert data into an internal table. Both the work area and internal table are defined by the same structure.
The structure has a total length of 672 bytes. For the sake of this discussion I'll point out that at the end of the structure, bytes 669, 670, 671, and 672 are four separate fields of 1 character each.
When viewing the work area record in the debugger I'm seeing all the fields and all the values. When viewing the internal table in the debugger after a record is inserted, the internal table ends with the field defined at Byte 670. The internal table does not include the two fields defined at Bytes 671 and 672.
Am I to assume from the above explanation that the length of a record ( A.K.A. row) in an internal table cannot exceed 670 bytes?
Thank you.

Manish,
False alarm! While, technically, you didn't answer my question, your request for code ended up helping me answer my own question.
To provide you with some code I wrote a simple test program using the record layout referred to above, with a DO loop to put some records into the internal table, followed by a LOOP AT, with accompanying WRITE statements to display the contents of the internal table and demonstrate that the last two fields weren't being stored.
However, when I ran the test program, the last two fields were being displayed.
It was at that point, when stepping through the debugger that I noticed the scroll arrows above the last column of my internal table that allowed me to scroll to the right and see my final two fields.
Apparently, because of the large number of fields in my internal table I had reached the default display length of the debugger. While I was obviously aware of the scroll bar found at the bottom of the display, I had never worked with an internal table of that width in the past and hadn't even noticed the scroll arrows above the last column before.
Thanks for taking the time to respond helping me get to the solution.

@Inserting Records in an Internal Table

Hi,
How can I Insert records in an internal table..such that i can insert the records somewhere in the middle based on the entry in a field?

INSERT wa INTO TABLE itab INDEX idx .
Effect
This variant can only be used for standard tables and sorted tables. Each line line_spec to be inserted into the line before the table index idx and the table index of the following lines is increased by one. A data object of the type i is expected for idx.
If idx contains a value equal to the number of the existing table lines plus one, the new line is appended as the last line in the internal table. If idx contains a greater value, no line is inserted and sy-subrc is set to 4.
An exception that cannot be handled is raised when:
idx contains a value less than or equal to 0
A line to be inserted would cause a duplicate entry in tables with a unique table key
A line to be inserted would disrupt the sort order of sorted tables
Within a LOOP loop, you can omit the addition INDEX. Each line to be inserted is inserted before the current table line of the LOOP loop. However, if the current line is deleted in the same loop pass, the response is undefined.

Delete records in a internal table

I Have an ALV in which I have selected several lines to delete (icon "-").
The method get_selected_rows returns the index of the selected lines.
In a loop I try to delete the lines of the internal table by the index. But I have a problem because when I delete a line, the index number is updated, therefore the second record that I try to delete doesn´t work because the index has changed.
does there exist the possibility that the index is not updated?
Thanks

hi
try to delete like this
loop at itab
delete itab
endloop
it deletes all the records in the internal table
outside of the loop
delete itab index 2 -
> it deletes the record of index 2
put it into the while or do while
i =1.
while i < 5
i = i+ 1.
delete itab index i.
endwhile.
it deletes 5 records in the internal table

Summarizing records in a internal table

hi
what is meant by summarizing records in an internal table
vamsi

HI
please go through this:
u will get some idea.
Appending Summarized Lines
The following statement allows you to summate entries in an internal table:
COLLECT <wa> INTO <itab>.
<itab> must have a flat line type, and all of the fields that are not part of the table key must have
a numeric type (F, I, or P). You specify the line that you want to add in a work area that is
compatible with the line type.
When the line is inserted, the system checks whether there is already a table entry that matches
the key. If there is no corresponding entry already in the table, the COLLECT statement has the
same effect as inserting the new line [Page 282]. If an entry with the same key already exists, the
COLLECT statement does not append a new line, but adds the contents of the numeric fields in
the work area to the contents of the numeric fields in the existing entry.
You should only use the COLLECT statement if you want to create summarized tables. If you
use other statements to insert table entries, you may end up with duplicate entries.
Lines are added to internal tables as follows:
Standard tables
If the COLLECT statement is the first statement to fill the standard table, the system
creates a temporary hash administration that identifies existing entries in the table. The
hash administration is retained until another statement changes the contents of key fields
or changes the sequence of the lines in the internal table. After this, the system finds
existing entries using a linear search. The runtime for this operation increases in linear
relation to the number of existing table entries. The system field SY-TABIX contains the
index of the line inserted or modified in the COLLECT statement.
Sorted tables
The system uses a binary search to locate existing lines. The runtime for the operation
increases logarithmically with the number of existing lines. The system field SY-TABIX
contains the index of the line inserted or modified in the COLLECT statement.
Hashed tables
The system finds existing lines using the hash algorithm of the internal table. After the
COLLECT statement, the system field SY-TABIX has the value 0, since hashed tables
have no linear index.
Example
DATA: BEGIN OF LINE,
COL1(3) TYPE C,
COL2(2) TYPE N,
COL3 TYPE I,
END OF LINE.
DATA ITAB LIKE SORTED TABLE OF LINE
WITH NON-UNIQUE KEY COL1 COL2.
BC - ABAP Programming SAP AG
Appending Summarized Lines
286 April 2001
LINE-COL1 = 'abc'. LINE-COL2 = '12'. LINE-COL3 = 3.
COLLECT LINE INTO ITAB.
WRITE / SY-TABIX.
LINE-COL1 = 'def'. LINE-COL2 = '34'. LINE-COL3 = 5.
COLLECT LINE INTO ITAB.
WRITE / SY-TABIX.
LINE-COL1 = 'abc'. LINE-COL2 = '12'. LINE-COL3 = 7.
COLLECT LINE INTO ITAB.
WRITE / SY-TABIX.
LOOP AT ITAB INTO LINE.
WRITE: / LINE-COL1, LINE-COL2, LINE-COL3.
ENDLOOP.
Thanks
Shiva

Calcullating no. of records in an internal table based on condition

Hi,
i have several records in an internal table. i need to calculate the number of records which meets a condition. is there any simple logic to find the records which meet the required criteria apart from looping into the internal table.
your help would be appreciated.
Thanks,
kranthi.

Hi,
U can use sy-dbcnt after the select querry.
DBCNT Number of elements in edited dataset with DB operations
WRITE: /12 'Number of selected records:', SY-DBCNT CENTERED.
REPORT ZZZ_TEST1 .
Tables: mara.
Types: begin of ty_mara,
matnr like mara-matnr,
end of ty_mara.
DATA: i_mara TYPE STANDARD TABLE OF ty_mara.
DATA: v_cnt like sy-dbcnt.
SELECT-OPTIONS: s_matnr FOR MARA-matnr.
SELECT matnr from mara into table i_mara.
if sy-subrc = 0.
v_cnt = sy-dbcnt.
WRITE: /12 'Number of selected records:', v_cnt CENTERED.
endif.
Hope this helps u.
Thanks & Regards,
Judith.

Count number of records in a internal table

Similar Messages

Maybe you are looking for