Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Performance issue using COEP

former_member227596
Participant
0 Likes
426

Dear Abapers,

I m working on Costing data. When I open COEP file using All entries in internal table. Its takes very long time & maxmimum time limit excced & terminates.

Pl. help.

regards

Vikas

1 REPLY 1
Read only

Former Member
0 Likes
306

Hi vikas,

Can u send the code.

Regards

Suresh.D

and u can check below standards to improve performance:

 1. First remove occurs 0 and occurs 0,

use types and delcare structure.

then declare internal table.

ex-

types: begin of ty_lfa1,

kunnr like kna1-kunnr,'end of ty_kna1.

data : i_kna1 type standard table of ty_kna1 with header line.

 instead of inner join use for allentries.

 into corresponding fields of will decrease performance.

 delete adjacent duplicates from itab_final comparing matnr lgort.

place it outside the loop.

 before every select statenet check sy-subrc = 0.if sucessful the write another one.

 don’t' loop an internal table more than once.

and for better performane follow below points

Always check the driver internal tables is not empty, while using FOR ALL ENTRIES

Avoid for all entries in JOINS

Try to avoid joins and use FOR ALL ENTRIES.

Try to restrict the joins to 1 level only ie only for tables

Avoid using Select *.

Avoid having multiple Selects from the same table in the same object.

Try to minimize the number of variables to save memory.

The sequence of fields in 'where clause' must be as per primary/secondary index ( if any)

Avoid creation of index as far as possible

Avoid operators like <>, > , < & like % in where clause conditions

Avoid select/select single statements in loops.

Try to use 'binary search' in READ internal table. Ensure table is sorted before using BINARY SEARCH.

Avoid using aggregate functions (SUM, MAX etc) in selects ( GROUP BY , HAVING,)

Avoid using ORDER BY in selects

Avoid Nested Selects

Avoid Nested Loops of Internal Tables

Try to use FIELD SYMBOLS.

Try to avoid into Corresponding Fields of

Avoid using Select Distinct, Use DELETE ADJACENT

Go through the following Document

Message was edited by:

suresh dameruppula