Find if there is any common record in two internal tables

hi,
I have two internal tables of same structure... say A and B.
I need to know if there are any common lines in them.
one way is to loop in any one of them and keep executing a read on the other.
can anyone suggest a better way.
thanks,
Arindam.

Hi Arindam,
To find common records in two internal tables, they can be compared
If INT_DATA1 EQ INT_DATA2.
endif.
The first criterion for comparing internal tables is the number of lines they contain. If two internal tables contain the same number of lines, they are compared line by line, component by component.
If the internal tables contain the same number of records and are sorted on the same key, the comparison stops at the line where the records are not common. For example, if the number of common records is 4, the comparison stops at the 5th line and sy-tabix becomes 5.
Hope it helps.
Regards,
Nupur

Similar Messages

Pick Common records from 2 internal tables

Hi,
I have 2 similar internal tables it_bseg1 (contain records based on the Posting Date BUDAT of document) & it_bseg2 (contain records based on the Customer Code KUNNR). Both these tables contains some common records. And I want these common records only. So please tell me to get the common records in the easiest way.
Regards,
Vishal

Hi,
There must be atleast one common field for these two internal tables to get the common records.
If you identify the common field then you can use this logic.
Loop at it_bseg1 into wa_bseg1.
Read table bseg2 into wa_bseg2 with key <commonfield > = wa_itab1-<commonfield>.
If sy-subrc eq 0.
Append wa_bseg1 to it_bseg3.
Endif.
Endloop.
Now it_bseg3 contains the common records.
If there is no use of it_bseg1 in your further development then you can do teh logic without declaring third internal table it_bseg3.
Loop at it_bseg1 into wa_bseg1.
Read table bseg2 into wa_bseg2 with key <commonfield > = wa_itab1-<commonfield>.
If sy-subrc ne 0.
delete it_bseg1 where <commonfield> = wa_itab1-<commonfield>.
Endif.
Endloop.
Now it_bseg1 contains teh common records of it_bseg1 and it_bseg2.
Hope this will help.
Regards,
Swarna Munukoti.
Edited by: Swarna Munukoti on Sep 3, 2008 2:05 PM

How to get records into two internal tables from 1 internal table?

VERME                                                                     LGPLA
252.000 EA 300     0149A                                  410     0149
276.000 EA 300     0149A                                  410     0107
516.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
I have above records in my one internal table ITAB.
I want to divide these records in to two internal tables ITAB1 and ITAB2. and this is based on LGPLA and VERME.
If there is same LGPLA (last column) and different VERME (1st column) available, then it should append ITAB1
Otherwise it should append ITAB2.
ITAB1 should contain ,
516.000 EA 300     0149A                                  400     3013
ITAB2 should contain ,
252.000 EA 300     0149A                                  410     0149
276.000 EA 300     0149A                                  410     0107
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
528.000 EA 300     0149A                                  400     3013
I have tried with this code
Loop at itab.
IF lv_prev_lgpla = wa-lgpla and lv_prev_verme <> wa-verme.
      APPEND wa TO itab1.
else.
      APPEND wa TO itab2.
endif.
lv_prev_lgpla = wa-vlpla.
lv_prev_verme = wa-anfme.
Endloop.
But it contains,
516.000 EA 300     0149A                                  400     3013
in table ITAB2 which I dont want.
Points rewarded soon.
Regards,
Ronn

Dear Ronny,
i am gining the solution below.But would request you to change your ITAB STRUCTURE LIKE THIS BEFORE USING THE CODE
VERME LGPLA
252.000 EA 300 0149A 0149 410
276.000 EA 300 0149A 0107 410
516.000 EA 300 0149A 3013 400
528.000 EA 300 0149A 3013 400
528.000 EA 300 0149A 3013 400
528.000 EA 300 0149A 3013 400
528.000 EA 300 0149A 3013 400
528.000 EA 300 0149A 3013 400
528.000 EA 300 0149A 3013 400
then do as follows.
SORT ITAB BY LGPLA VERME.
LOOP AT ITAB INTO WITAB.
W_INDEX = SY-TABIX.
here take all the abOve fields in temp fieds.
LW_VERME = WITAB-VERME..AND SO ON.
AT END OF LGPLA.
   MOVE: all LW fields to work area of ITAB1
   APPEND work area of ITAB1 TO ITAB1.
   DELETE ITAB INDEX W_INDEX
ENDAT.
ENDLOOP.
Basically what u r doing here is thet u r using processing event.
So whenerv VERME changes this event will be triggered.
Just try this out...something like this only will be he logic.
Please let me know further

How to delete the matching records from two internal tables

Hi ,
I have two internal tables say A and B of the same type. If A has 10 records and B has 4 records , I want to delete the 4 records in B from A .
loop at B into wa .
delete A where key = wa - key .
endloop.
takes a long time if the table B is huge. how can I improve the performance.
Thanks.
Gayathri

Hi Gayathri,
You could try field-symbols. It reduces the data transfer from the internal table B to the work area.
field-symbols <fs_itab_b> like line of B.
loop at B assigning <fs_itab_b>.
delete A where key = <fs_itab_b>?-key.
endloop.
Regards,
<a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=zwcc%2fwm4ups%3d">anand Mandalika</a>.

Need logic to retrieve common fields in two internal tables

Hi,
I need to get the common data from the internnal table IT_BSEG and IT_ZFI_CSHLW_DIRE tables please help me out in sorting out this porblem.
the fields in IT_BSEG are Account number,Profit center,company code,document type etc.
where as the fields in IT_CSHFLW_DIRE are Account number from,Account number to,company code from,company code to and profit center.
so how to check whether a record which is in It_BSEG,exists in IT_CSHFLW_DIRE..?
Thanks,
Kumar

Solution 1.
LOOP AT ITAB1.
LOOP AT ITAB2
WHERE ( ACCOUNT_FROM LE ITAB1-ACCOUNT AND
               ACCOUNT_TO GE ITAB1-ACCOUNT )
      AND (COMPANY_FROM LE ITAB1-COMPANY AND
               COMPANY_TO      GE ITAB1-COMPANY
       AND (PROFIT_CENTER EQ LE ITAB1-PROFIT_CENTER ).
<Your logic>.
ENDLOOP.
ENDLOOP.
soultions 2.
RANGES: COMPANY_CODE FOR <Your data dictionary reference>
                ACCOUNT             FOR <Your data dictionary reference>.
LOOP AT ITAB2.
REFRESH: COMPANY_CODE, ACCOUNT.
CLEAR: COMPANY_CODE, ACCOUNT.
MOVE: I TO COMPANY_CODE-SIGN,
            I TO ACCOUNT-SIGN.
MOVE: BT TO COMPANY_CODE-OPTION,
            BT TO ACCOUNT-OPTION.
MOVE: ITAB2-COMPANY_FROM   TO COMPANY_CODE-LOW,
             ITAB2-ACCOUNT_FROM    TO ACCOUNT-LOW.
MOVE: ITAB2-COMPANY_TO   TO COMPANY_CODE-HIGH.
             ITAB2-ACCOUNT_TO    TO ACCOUNT-HIGH.
APPEND: COMPANY_CODE, ACCOUNT.
LOOP AT ITAB1 WHERE ACCOUNT IN ACCOUNT         "<----range
                              AND company      IN company_code    "<----range
                              AND profit_center eq ITAB2-PROFIT_CENTER.
*<You code>
ENDLOOP.
ENDLOOP.
Please note both approach have different <b>bussines logic</b>.
It depends on your bussiness logic which table data you are looking in which table.
Regards,
A.Singh

How to append records between two internal tables

hi all,
im trying to append from an internal table to another internal table with same structure. i tried the following but it overwrites previous contents of i_dest:
move i_src to i_dest
thanks,
sid

hey u try to move it record by record
<b>itab2 = itab.
append itab2.</b>
This should work I guess
just check the code below, if u want to move the whole itab into itab2 then use <b>itab2[] = itab.</b>
<b>loop at it_pgm.
read table itab with key obj_name = it_pgm-pgm_name.
if sy-subrc = 0.
    itab_final-obj_name = itab-obj_name.
    itab_final-func_spec = itab-func_spec.
    itab_final-func_area = itab-func_area.
    itab_final-dev_class = itab-dev_class.
    append itab_final.
else.
   itab_alt-pgm_name = it_pgm-pgm_name.
   append itab_alt.
endif.</b>
please reward points if found helpful

Get the Common from Two Internal Tables with same structure

Hi ,
I need to get the Common data from Two Internal Tables with same structure with using the looping method.
For e.g.
I have two internal table say ITAB1 and ITAB2.
ITAB1 has values A,B,C,D,E,F
ITAB2 has values A,H,B,Y,O
Output at runtime should be : A,B

Hi mohit,
1. If u want to compare all fields,
   for matching purpose,
   then we can do like this.
2.
report abc.
data : a like t001 occurs 0 with header line.
data : b like t001 occurs 0 with header line.
loop at a.
LOOP AT B.
    IF A = B.
      WRITE :/ 'SAME'.
    ENDIF.
endloop.
ENDLOOP.
regards,
amit m.

Find whether there is any text frame in given co-ordinates

Hi there,
I'm using adobe indesign 2.0.2 and vb 6.
I want to find whether there is any text frame existing in the given co-ordinates.
Please help.
Thanx
Robin

You need to tackle this the other way around: get references to all the text frames (on the spread, I suppose) and compare their coordinates with those of interest.
Dave

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.

Help needed to get unique record from an internal table

Hi Everybody,
I have to get unique record from an internal table. i know we can use read statement with key condition .
But the problem is i have to use some relational operators like GE or LE.
eg
read table itab into wa with key width GE itab-widthfrom
                                                   width LE itab-widthto
                                                   machno eq itab-machno.
Its giving me error when I use the operators GE , LE.( I think since it can't find a unique record with those relational
operators in the with key statement)
Is there any other way to get unique record from internal table without using the loop?
Thanks,
Sunny

Using the read statement you will need some kind of loop. For example.
DO.
READ TABLE......
WITH KEY ......
                    READ = SPACE
IF SY-SUBRC EQ 0
TABLE-READ = 'X'.
MODIFY TABLE
ADD 1 TO W_FOUND.
ELSE
EXIT.
ENDIF
ENDDO.
IF W_FOUND EQ 1.
...record is unique.
ENDIF.

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

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

How to get common datas from two int.tables

hi,
please tell me , how to i will get the common datas between two int. tables
& place them in third int. table.
give me syntax.
regards
subhasis.

Hi Subhasis,
<b>SORT :</b></u>
SORT itab.
Extras:
1. ... BY f1 f2 ... fn
2. ... ASCENDING
3. ... DESCENDING
4. ... AS TEXT
5. ... STABLE
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Field symbols not allowed as sort criterion.
Effect
The entries in the internal table are sorted in ascending order using the key from the table definition (DATA, TYPES).
Addition 1
... BY f1 f2 ... fn
Effect
Uses the sort key defined by the sub-fields f1, f2, ..., fn of the table itab instead of the table key. The fields can be of any type; even number fields and tables are allowed.
You can also specify the sort fields dynamically in the form (name). If name is blank at runtime, the sort field is ignored. If itab is a table with a header line, you can also use a field symbol pointing to the header line of itab as a dynamic sort criterion. A field symbol that is not assigned is ignored. If a field symbol is assigned, but does not point to the header line of the internal table, a runtime error occurs.
If the line type of the internal table contains object reference variables as components, or the entire line type is a reference variable, you can use the attributes of the object to which a reference is pointing in a line as sort criteria (see Attributes of Objects as the Key of an Internal Table.
You can address the entire line of an internal table as the key using the pseudocomponent TABLE_LINE. This is particularly relevant for tables with a non-structured line type when you want to address the whole line as the key of the table (see also Pseudocomponent TABLE_LINE With Internal Tables).
If you use one of the additions 2 to 5 before BY, it applies to all fields of the sort key by default. You can also specify these additions after each individual sort field f1, f2, ..., fn. For each key field, this defines an individual sort rule which overrides the default.
Addition 2
... ASCENDING
Effect
Sorts in ascending order. This is also the default if no sort order is specified directly after SORT. For this reason, it is not necessary to specify ASCENDING explicitly as the default sort order.
With the addition BY, you can also specify ASCENDING directly after a sort field to define ascending order explicitly as the sort sequence for this field.
Addition 3
... DESCENDING
Effect
Sorts in descending order. If the addition comes right after SORT, DESCENDING is taken as the default for all fields of the sort key.
With the addition BY, you can also specify DESCENDING directly after a sort field.
Addition 4
... AS TEXT
Effect
Text fields are sorted appropriate to the locale. This means that the relative order of characters is defined according to the text environment being used.
When an internal mode is opened (in other words, when a roll area is opened), the text environment is automatically set to the logon language specified in the user master record. If necessary, however, you can change the text environment explicitly in your program by using a SET-LOCALE statement.
If the addition comes directly after itab, locale-specific rules are used for all fields of the sort key where the type of these fields is C or W. After the sort, the sequence of entries usually does not match the sequence which results otherwise, without using the addition AS TEXT, i.e. with binary sorting.
With the addition BY, you can also specify AS TEXT directly after a sort field, provided it is of type C or W, or a structured type. Otherwise, a runtime error occurs. In sort fields with a structured type, AS TEXT only affects subcomponents with type C or W.
In case of an invalid character, a SYSLOG message is written, and the respective record is inserted at the end.
Note
Please keep the rules for site-specific sorting in mind.
Example
Sort a name table with different keys:
TYPES: BEGIN OF PERSON_TYPE,
         NAME(10)   TYPE C,
         AGE        TYPE I,
         COUNTRY(3) TYPE C,
       END OF PERSON_TYPE.
DATA: PERSON TYPE STANDARD TABLE OF PERSON_TYPE WITH
                  NON-UNIQUE DEFAULT KEY INITIAL SIZE 5,
      WA_PERSON TYPE PERSON_TYPE.
WA_PERSON-NAME    = 'Muller'. WA_PERSON-AGE = 22.
WA_PERSON-COUNTRY = 'USA'.
APPEND WA_PERSON TO PERSON.
WA_PERSON-NAME    = 'Moller'. WA_PERSON-AGE = 25.
WA_PERSON-COUNTRY = 'FRG'.
APPEND WA_PERSON TO PERSON.
WA_PERSON-NAME    = 'Möller'. WA_PERSON-AGE = 22.
WA_PERSON-COUNTRY = 'USA'.
APPEND WA_PERSON TO PERSON.
WA_PERSON-NAME    = 'Miller'. WA_PERSON-AGE = 23.
WA_PERSON-COUNTRY = 'USA'.
APPEND WA_PERSON TO PERSON.
SORT PERSON.
Now, the sequence of the table entries is as follows:
Miller 23 USA
Moller 25 FRG
Muller 22 USA
Möller 22 USA
If, for example, you apply German sort rules where the umlaut comes directly after the letter 'o' in the sort, the data record beginning with 'Möller' would not be in the right place in this sequence. It should come second.
Provided a German-language locale is set (e.g. sorting is according to German grammatical rules, see also SET LOCALE), you can sort the names according to German rules as follows:
SORT PERSON BY NAME AS TEXT.
Now, the sequence of table entries is as follows:
Miller 23 USA
Moller 25 FRG
Möller 22 USA
Muller 22 USA
Further examples:
SORT PERSON DESCENDING BY COUNTRY AGE NAME.
Now, the sequence of table entries is as follows:
Miller 23 USA
Möller 22 USA
Muller 22 USA
Moller 25 FRG
SORT PERSON DESCENDING BY AGE ASCENDING NAME AS TEXT.
Now, the sequence of table entries is as follows:
Muller 22 USA
Möller 22 USA
Miller 23 USA
Moller 25 FRG
Addition 5
... STABLE
Effect
Uses a stable sort, that is, the relative sequence of entries that have the same sort key remains unchanged.
Unlike additions 2 to 4, you cannot use this addition directly after a sort field.
Notes
General:
The number of sort fields is restricted to 250.
The sort process is only stable if you use the STABLE addition. Otherwise, a predefined sequence of fields used to sort a list is not usually retained.
It does not make sense to use the SORT command for a SORTED TABLE. If the table type is statically declared, the system returns a syntax error if you try to SORT the table. If the table type is not statically declared (for example, because the table was passed to a FORM routine as an INDEX TABLE in a parameter), and the system can interpret the SORT statement as an empty operation, it ignores the statement. This is the case when the key in the BY clause corresponds to the beginning of the table key. Otherwise, a runtime error occurs.
To delete all duplicate entries from a sorted internal table (e.g. just after SORT), you can use the DELETE ADJACENT DUPLICATES FROM itab statement.
When using the addition AS TEXT, the sequence of entries after the sort does not usually match the sequence resulting from a binary sort, i.e. if the addition AS TEXT is not specified. The consequence of this is that after the SORT, you are not allowed to access with the READ TABLE itab ... BINARY SEARCH statement.
If you still want to access data sorted apppropriate to the locale with a binary search, you can do this by including an additional component in the table where you can explictly store the data formatted using the CONVERT TEXT ... INTO SORTABLE CODE statement. This is also recommended for performance reasons if you have to re-sort the table several times according to locale-specific criteria.
If the internal table has more than 2^19 lines or is larger than 12 MB, the system sorts it physically using an external auxiliary file. You can specify the directory in which the file should be created using the SAP profile parameter DIR_SORTTMP. By default, the system uses the SAP data directory (SAP profile parameter DIR_DATA).
Notes
Performance:
The runtime required to sort an internal table increases with the number of entries and the length of the sort key.
Sorting an internal table with 100 entries with a 50 byte key requires about 1300 msn (standardized microseconds). Using a 30-byte key, the runtime is about 950 msn.
If one of the specified sort criteria is itself an internal table, SORT may sometimes take much longer.
The runtime increases if you use a stable sort.
Physical sorting reduces the runtime required for subsequent sequential processing.
Reward If Useful.
Regards,
Chitra

To compare two internal tables and delete records

Hi friends,
    I have to compare two internal tables and should delete the records which is not present in both the tables. Reply me as soon as possible.
Thanks.

Hi Nagarajan,
1. I don't think there is any direct (one-shot statement)
    way to achieve this.
    one has to do by writing some logic.
2. Loop at ITAB1.
     Read table ITAB2 with key Field1 = ITAB1-Field1.
     If sy-subrc <> 0.
     delete ITAB1.
     endif.
   Endloop.
Do the same again with ITAB2.
   Loop at ITAB2.
     Read table ITAB1 with key Field1 = ITAB2-Field1.
     If sy-subrc <> 0.
     delete ITAB2.
     endif.
   Endloop.
3. If any better way is found, i will let u know.
Hope it helps.
Regards,
Amit M.

How to collect similar record from the internal table

I need to collect exact matched records from 1 internal table to another internal table by searching 5 fields. I need to have records which are exactly matched for 5 fields. i have written a code wich is mention below it gave me only similar records but not 100% matched record.. would you like to help me. any correction, suggetion,. Will be great help to me.

To get exact match of 5 records, do as follows.
Check whether internal table gives only one record or not after READ statement.If internal table gives more than one entry for READ then the results will be improper.
I think there is no need of READ statement on same internal table within LOOP. I commented the same in code.
sort i_bp_p by title initials name_last idnumber idtype f50code rbcode. "acc_num.
loop at i_bp_p into wa_i_bp_p.
*lv_tabix = sy-tabix.
*read table i_bp_p index lv_tabix into wa_i_bp_p.read table i_but0id into wa_but0id with key idnumber = wa_i_bp_p-idnumber
idtype = wa_i_bp_p-idtype binary search.
if sy-subrc = 0.
read table i_but000 into wa_but000 with key title = wa_i_bp_p-title
initials = wa_i_bp_p-initials
name_last = wa_i_bp_p-name_last binary search.
if sy-subrc = 0.
read table i_but0is into wa_but0is with key f50code = wa_i_bp_p-f50code
rbcode = wa_i_bp_p-rbcode binary search.
if sy-subrc = 0.
move-corresponding wa_i_bp_p to i_bp_p100.
append i_bp_p100.
endif.
endif.
endif.
endloop.
sort i_bp_p100 by partner.
loop at i_bp_p100.
write : /10 i_bp_p100-partner,
20 i_bp_p100-title,
30 i_bp_p100-initials,
40 i_bp_p100-name_last,
53 i_bp_p100-idnumber,
70 i_bp_p100-idtype,
85 i_bp_p100-rbcode,
95 i_bp_p100-f50code.
endloop.
sort i_bp_p by title initials name_last idnumber idtype f50code rbcode. "acc_num.
loop at i_bp_p into wa_i_bp_p.
lv_tabix = sy-tabix.
read table i_bp_p index lv_tabix into wa_i_bp_p.
if sy-subrc = 0.
read table i_but0id into wa_but0id with key idnumber = wa_i_bp_p-idnumber
idtype = wa_i_bp_p-idtype binary search.
if sy-subrc = 0.
read table i_but000 into wa_but000 with key title = wa_i_bp_p-title
initials = wa_i_bp_p-initials
name_last = wa_i_bp_p-name_last binary search.
if sy-subrc = 0.
read table i_but0is into wa_but0is with key f50code = wa_i_bp_p-f50code
rbcode = wa_i_bp_p-rbcode binary search.
if sy-subrc = 0.
move-corresponding wa_i_bp_p to i_bp_p100.
append i_bp_p100.
endif.
endif.
endif.
endif.
endloop.

Find if there is any common record in two internal tables

Similar Messages

Maybe you are looking for