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.

Similar Messages

Maximum record limit for internal table

hello all,
can any one tell me what is the maximum limit of internal table. i would like to add all records from bseg to internal table. so i can improve processing time.
thanks,
raj

hi,
Before Release 4.0A, ABAP stored the content of internal tables in a combination of main memory and file space. This means that the maximum size of all internal tables of all programs running on such an application server at one time is about 2 GB. With Release 4.0A or greater, this size decreases to about 500 MB. (Note that those values aren't fixed, but this is a good guide. This minimum of 500 MB is the lowest limit of the real value, which varies among different operating systems and even among different releases of the same operating system.)
It may sound strange that a newer release has a higher restriction on capacity. But it's a consequence of the fact that the contents of internal tables move from a reserved file to shared memory. When you process internal tables this way in Release 4.0A or greater, you pay for much better performance with a smaller potential size.
Regards,
Sourabh

SQL Loader-704: Internal error: Maximum record length must be = [10000000]

Hi,
running SQL*Loader (Release 8.1.7.2.1) causes an error "SQL*Loader-704: Internal error: Maximum record length must be <= [10000000]". This error occurs when SQLLoader is trying to load several thousand records into a database table. Each record is less than 250 bytes in length.
Any idea what could cause the problem?
Thanks in advance!
Ingo
And here's an extract from the log file generated by SQLLoader :
Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array: 1360 rows, maximum of 10485760 bytes
Continuation: none specified
Path used: Conventional
Table "SYSTEM"."BASICPROFILE$1", loaded from every logical record.
Insert option in effect for this table: APPEND
TRAILING NULLCOLS option in effect
Column Name Position Len Term Encl Datatype
UUID FIRST * O(X07) CHARACTER
DOMAINID NEXT * O(X07) CHARACTER
LASTMODIFIED NEXT * O(X07) DATE DD/MM/YYYY HH24:MI:SS
ANNIVERSARY NEXT * O(X07) CHARACTER
BIRTHDAY NEXT * O(X07) CHARACTER
COMPANYNAME NEXT * O(X07) CHARACTER
DESCRIPTION NEXT * O(X07) CHARACTER
FIRSTNAME NEXT * O(X07) CHARACTER
COMPANYNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
FIRSTNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
GENDER NEXT * O(X07) CHARACTER
HOBBIES NEXT * O(X07) CHARACTER
HONORIFIC NEXT * O(X07) CHARACTER
JOBTITLE NEXT * O(X07) CHARACTER
KEYWORDS NEXT * O(X07) CHARACTER
LASTNAME NEXT * O(X07) CHARACTER
LASTNAMETRANSCRIPTION NEXT * O(X07) CHARACTER
NICKNAME NEXT * O(X07) CHARACTER
PREFERREDLOCALE NEXT * O(X07) CHARACTER
PREFERREDCURRENCY NEXT * O(X07) CHARACTER
PROFESSION NEXT * O(X07) CHARACTER
SECONDLASTNAME NEXT * O(X07) CHARACTER
SECONDNAME NEXT * O(X07) CHARACTER
SUFFIX NEXT * O(X07) CHARACTER
TITLE NEXT * O(X07) CHARACTER
CONFIRMATION NEXT * O(X07) CHARACTER
DEFAULTADDRESSID NEXT * O(X07) CHARACTER
BUSINESSPARTNERNO NEXT * O(X07) CHARACTER
TYPECODE NEXT * O(X07) CHARACTER
OCA NEXT * O(X07) CHARACTER
SQL*Loader-704: Internal error: Maximum record length must be <= [10000000]

As a second guess, the terminator changes or goes missing at some point in the data file. If you are running on *NIX, try wc -l data_file_name. This will give a count of the number of lines (delimited by CHR(10) ) that are in the file. If this is not close to the number you expected, then that is your problem.
You could also try gradually working through the data file loading 100 records, then 200, then 300 etc. to see where it starts to fail.
HTH
John

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

How to delete records from dynamic internal table.

Hi Experts,
Need urgent help!!!
Issue is with Dynamic internal tables.
Below is code written by me :
FORM select_query USING Lw_tabnam
                  TYPE t682i-kotabnr.
DATA : lw_line TYPE REF TO data,
          lw_line1 TYPE REF TO data.
    CREATE DATA Lw_line    TYPE (lw_TABNAM).
    ASSIGN      Lw_line->* TO   <WA_tbl>.
    CREATE DATA LW_LINE    TYPE STANDARD TABLE OF (Lw_tabnam)
                           WITH NON-UNIQUE DEFAULT KEY.
    ASSIGN      Lw_line->* TO <TBL>.
    SELECT * FROM (Lw_tabnam)
             INTO CORRESPONDING FIELDS OF TABLE <TBL>
             WHERE (t_keys).
Endform.
code is working fine.
here even the table name and where condition are dynamic,everything is fine upto this point.
Now i have to delete some record from <TBL> based on some conditons.
     for ex : ( here lc_fieldname is KUNNR)
      loop at t_kunnr.
          lw_tabix = sy-tabix.
        Read table <tbl>
                with key (lc_fieldname) = t_kunnr-kunnr ASSIGNING <wa_tbl>.
        If sy-subrc = 0.
        *Delete
        delete <tbl> from <wa_tbl>
delete <tbl> index lw_tabix.
        Endif.
     Endloop.
The above delete statement doesn't work ,even we can't use index as it gives a syntax error " something related to "index is not allowed in standard table or hash table.
Can you help me ab't how to delete records in Dynamic internal table?
Other option that i am thinking of is to create a static table of type dynamic table.
means, data itab type standard table of <tbl> .I know the syntax is wrong ,however is there any way to do this?
Thanks in advance ,
If you have any suggestion ab't this then do let me know.
bye,
Gaurav.

Hi
I wrote this code and it works fine:
DATA LW_TABNAM(10) VALUE 'LFA1'.
DATA : LW_LINES TYPE REF TO DATA,
       LW_LINE TYPE REF TO DATA.
FIELD-SYMBOLS: <TABLE> TYPE TABLE,
               <WA>    TYPE ANY.
CREATE DATA LW_LINES TYPE TABLE OF (LW_TABNAM)
WITH NON-UNIQUE DEFAULT KEY.
ASSIGN LW_LINES->* TO <TABLE>.
CREATE DATA LW_LINE TYPE (LW_TABNAM).
ASSIGN LW_LINE->* TO <WA>.
DO 10 TIMES.
APPEND INITIAL LINE TO <TABLE>.
ENDDO.
SY-TABIX = 4.
DELETE <TABLE> INDEX SY-TABIX.
WRITE SY-SUBRC.
I hope it help you
Max

@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.

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 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.

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

Field length in internal table

hi,
how to selt field length in internal table?.
i have created on report the report out puts down load to using download function .
the out format is:
op1 op2   op3      op4
1     3       4
i want
op1   op2   op3       op4
1                3          4
how to set this please give sample code.

HI,
Give internal table like this.
DATA: BEGIN OF itab OCCURS 100,
            op1(04),
            op2(04),
op3(04),
op4(04),
      END OF itab.
So it will allocate space between 1, 3 and 4.
Reward if it useful.
Thanks.

Record count in internal table

i want to know record count for the records stored in
internal table.
do we have any system field to display record count?

Hi,
Try this:
Data: count_lines type i.
describe table my_table lines count_lines.
Regards,
Arjan

How to increase the length of internal table dynamically

How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
The requirement code :
types: begin of t_data,
         form          like zscr_data_hdr-form,
         werks         like zscr_data_hdr-werks,
         matnr         like zscr_data_hdr-matnr,
         verid         like zscr_data_hdr-verid,
         lot           like zscr_data_hdr-lot,
         lot_qty       like zscr_data_hdr-lot_qty,
         udate         like zscr_data_hdr-udate,
         utime         like zscr_data_hdr-utime,
         zuser         like zscr_data_hdr-zuser,
         processed     like zscr_data_hdr-processed,
         defect        like zscr_defect_data-defect,
         vornr         like zscr_route_data-vornr,
         fld1          like zscr_defect_data-defect_val,
         fld2          like zscr_defect_data-defect_val,
         fld3          like zscr_defect_data-defect_val,
         fld4          like zscr_defect_data-defect_val,
         fld5          like zscr_defect_data-defect_val,
         fld6          like zscr_defect_data-defect_val,
         fld7          like zscr_defect_data-defect_val,
         fld8          like zscr_defect_data-defect_val,
         fld9          like zscr_defect_data-defect_val,
         fld10         like zscr_defect_data-defect_val,
         fld11         like zscr_defect_data-defect_val,
         fld12         like zscr_defect_data-defect_val,
         fld13         like zscr_defect_data-defect_val,
         fld14         like zscr_defect_data-defect_val,
         fld15         like zscr_defect_data-defect_val,
         fld16         like zscr_defect_data-defect_val,
         fld17         like zscr_defect_data-defect_val,
         fld18         like zscr_defect_data-defect_val,
         fld19         like zscr_defect_data-defect_val,
         fld20         like zscr_defect_data-defect_val,
         fld21         like zscr_defect_data-defect_val,
         fld22         like zscr_defect_data-defect_val,
         fld23         like zscr_defect_data-defect_val,
         fld24         like zscr_defect_data-defect_val,
         fld25         like zscr_defect_data-defect_val,
         fld26         like zscr_defect_data-defect_val,
         fld27         like zscr_defect_data-defect_val,
         fld28         like zscr_defect_data-defect_val,
         fld29         like zscr_defect_data-defect_val,
         fld30         like zscr_defect_data-defect_val,
         fld31         like zscr_defect_data-defect_val,
         fld32         like zscr_defect_data-defect_val,
         fld33         like zscr_defect_data-defect_val,
         fld34         like zscr_defect_data-defect_val,
         fld35         like zscr_defect_data-defect_val,
         fld36         like zscr_defect_data-defect_val,
         fld37         like zscr_defect_data-defect_val,
         fld38         like zscr_defect_data-defect_val,
         fld39         like zscr_defect_data-defect_val,
         fld40         like zscr_defect_data-defect_val,
         fld41         like zscr_defect_data-defect_val,
         fld42         like zscr_defect_data-defect_val,
         fld43         like zscr_defect_data-defect_val,
         fld44         like zscr_defect_data-defect_val,
         fld45         like zscr_defect_data-defect_val,
         fld46         like zscr_defect_data-defect_val,
         fld47         like zscr_defect_data-defect_val,
         fld48         like zscr_defect_data-defect_val,
         fld49         like zscr_defect_data-defect_val,
         fld50         like zscr_defect_data-defect_val,
         fld51         like zscr_defect_data-defect_val,
         fld52         like zscr_defect_data-defect_val,
         fld53         like zscr_defect_data-defect_val,
         fld54         like zscr_defect_data-defect_val,
         fld55         like zscr_defect_data-defect_val,
         fld56         like zscr_defect_data-defect_val,
         fld57         like zscr_defect_data-defect_val,
         fld58         like zscr_defect_data-defect_val,
         fld59         like zscr_defect_data-defect_val,
         fld60         like zscr_defect_data-defect_val,
         fld61         like zscr_defect_data-defect_val,
         fld62         like zscr_defect_data-defect_val,
         fld63         like zscr_defect_data-defect_val,
         fld64         like zscr_defect_data-defect_val,
         fld65         like zscr_defect_data-defect_val,
         fld66         like zscr_defect_data-defect_val,
         fld67         like zscr_defect_data-defect_val,
         fld68         like zscr_defect_data-defect_val,
         fld69         like zscr_defect_data-defect_val,
         fld70         like zscr_defect_data-defect_val,
         fld71         like zscr_defect_data-defect_val,
         fld72         like zscr_defect_data-defect_val,
         fld73         like zscr_defect_data-defect_val,
         fld74         like zscr_defect_data-defect_val,
         fld75         like zscr_defect_data-defect_val,
         fld76         like zscr_defect_data-defect_val,
         fld77         like zscr_defect_data-defect_val,
         fld78         like zscr_defect_data-defect_val,
         fld79         like zscr_defect_data-defect_val,
         fld80         like zscr_defect_data-defect_val,
         fld81         like zscr_defect_data-defect_val,
         fld82         like zscr_defect_data-defect_val,
         fld83         like zscr_defect_data-defect_val,
         fld84         like zscr_defect_data-defect_val,
         fld85         like zscr_defect_data-defect_val,
         fld86         like zscr_defect_data-defect_val,
         fld87         like zscr_defect_data-defect_val,
         fld88         like zscr_defect_data-defect_val,
         fld89         like zscr_defect_data-defect_val,
         fld90         like zscr_defect_data-defect_val,
         fld91         like zscr_defect_data-defect_val,
         fld92         like zscr_defect_data-defect_val,
         fld93         like zscr_defect_data-defect_val,
         fld94         like zscr_defect_data-defect_val,
         fld95         like zscr_defect_data-defect_val,
         fld96         like zscr_defect_data-defect_val,
         fld97         like zscr_defect_data-defect_val,
         fld98         like zscr_defect_data-defect_val,
         fld99         like zscr_defect_data-defect_val,
         fld100         like zscr_defect_data-defect_val,
         fld101         like zscr_defect_data-defect_val,
         fld102         like zscr_defect_data-defect_val,
         fld103         like zscr_defect_data-defect_val,
         fld104         like zscr_defect_data-defect_val,
         fld105         like zscr_defect_data-defect_val,
         fld106         like zscr_defect_data-defect_val,
         fld107         like zscr_defect_data-defect_val,
         fld108         like zscr_defect_data-defect_val,
         fld109         like zscr_defect_data-defect_val,
         fld110         like zscr_defect_data-defect_val,
         fld111         like zscr_defect_data-defect_val,
         fld112         like zscr_defect_data-defect_val,
         fld113         like zscr_defect_data-defect_val,
         fld114         like zscr_defect_data-defect_val,
         fld115         like zscr_defect_data-defect_val,
         fld116         like zscr_defect_data-defect_val,
         fld117         like zscr_defect_data-defect_val,
         fld118         like zscr_defect_data-defect_val,
         fld119         like zscr_defect_data-defect_val,
         fld120         like zscr_defect_data-defect_val,
         fld121         like zscr_defect_data-defect_val,
         fld122         like zscr_defect_data-defect_val,
         fld123         like zscr_defect_data-defect_val,
         fld124         like zscr_defect_data-defect_val,
         fld125         like zscr_defect_data-defect_val,
         fld126         like zscr_defect_data-defect_val,
         fld127         like zscr_defect_data-defect_val,
         fld128         like zscr_defect_data-defect_val,
         fld129         like zscr_defect_data-defect_val,
         fld130         like zscr_defect_data-defect_val,
         fld131         like zscr_defect_data-defect_val,
         fld132         like zscr_defect_data-defect_val,
         fld133         like zscr_defect_data-defect_val,
         fld134         like zscr_defect_data-defect_val,
         fld135         like zscr_defect_data-defect_val,
         dayst         like zscr_data_hdr-dayst,
       end of t_data.
In this fld1 to fld135 are defined in internal table.
But if the number of fields are more than 135 then the program is going to short dump.
Some times fld1 to fid170 or more fields will be there in my internal table.
Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

Hi
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Max

Store the vital info from the absence quota record in an internal table

Hi experts,
I want to detrmine if the Absence records (PA2001 rec) deduction from date (PA2001-BEGDA) and absence to date (PA2001-ENDDA) are permissible for the validity period of the Absence Quota record (the PA2006 rec). If the quotas deduction from date, PA2006-DESTA, is greater than the PA2001-BEGDA, we then need to identify this absence quota record for change and change the deduction from date, PA2006-DESTA, to be the same as PA2001-BEGDA. Store the vital info from the absence quota record in an internal table and record the new date that the deduction from date that needs to be changed to. The changes will be made via a BDC session.
Please help me out...
Thanks,
Vicky

This looks possible if we code it in 'dynamic action' table, but the BDC may not read it during run time.
Do you still have this issue?
Thanks
Narasimha

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.

Maximum record length in internal table?

Similar Messages

Maybe you are looking for