Shared Top Border

Enterprise Resource
Planning Portal

 

Advertise | Founder BLOG

ERPGenie.COM ABAP Tips and Tricks Database

THE ultimate
ERP website

 

Forums | Vote for us |

Google    Other Search Options

Home arrow Tips and Tricks arrow ABAP Reports arrow Internal Table Processing
Internal Table Processing PDF Print E-mail
User Rating: / 0
PoorBest 
Written by Anon.   
Friday, 09 March 2007
Custom reports often require large amounts of processing of internal tables.  The following techniques have worked well for large volume internal table processing. a) Modifying selected components through a mass modify

* Table TAB is filled with 100 entries. A line has two components, a   
* FLAG of typ C and an integer table INTTAB with 20 entries each.      
* The Flag is switched on for all 100 lines.

TAB-FLAG = 'X'.                                                         
MODIFY TAB TRANSPORTING FLAG                                            
                   WHERE FLAG IS INITIAL.

b) Modifying a huge internal table

It is recommended to have a READ … with Binary search on the table with Where condition and then Modify the records using 'Modify ….. index v_index."  In one of the cases, Modify with where condition took 1 hr 30 minutes, when changed to Modify .. index v_index it was reduced to 13 minutes.  This is very similar to the parallel cursor technique.

c) Appending through mass append

*Table TAB_SRC and TAB_DEST are both filled with 500 entries of 100 bytes
* each. TAB_SRC is appended line by line to TAB_DEST.

APPEND LINES OF TAB_SRC TO TAB_DEST.

d) Inserting one internal table into another internal table through mass insert

* Table TAB_SRC and TAB_DEST are both filled with 500 entries of 100 bytes   
* each. TAB_SRC is inserted line by line into TAB_DEST at index IDX

*    Let the kernel do the work
                                                                     
IDX = 250.                                                           
INSERT LINES OF TAB_SRC INTO TAB_DEST INDEX IDX.

e) Delete adjacent duplicates

* Table TAB_DEST is filled with 1000 entries of 100 bytes each and contains
* 500 pairs of duplicates

*    Let the kernel do the work

DELETE ADJACENT DUPLICATES FROM TAB_DEST COMPARING K.

Related Items:

 
< Prev   Next >

Google Search

Google Ads

Shared Bottom Border

Contact Us | Polls | Add URL | Contribute | Privacy | Terms | Feedback

Discussion Forum | BLOG | Consultants: Post your resume | Companies: Advertise on ERPGenie.COM | Post Job
Financials Consultant | Consultant Review | Gallia Consulting | Supply Chain Project | SAP Financials Forum
GenieHoldings.COM, Inc. | Genie Press | WorkflowGenie | ESAGenie | ERPTopSites | ABAP Tips and Tricks | SAP Solutions Database

EDIGenie | Searching Survivor