Application Development 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: 

Performance issue - in 4.7 ( previously worked in ECC 6 only)

Former Member
0 Kudos

Hi experts,

I have worked on ECC 6.0 and now i have got a new job and now working in 4.7 for support project. I feel it is very difficult after working in 6.0.

I have not used occurs 0, like etc.. statements in 6.0.

In 4.7 what are the things that i should consider to avoid performance issues.

plz guide me.

thanks in advance.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi sakthi sri,

As you are in Support project you will not do much coding rite,

If there a new program to develop write code as you do in ECC 6.0 and then do Extended check for that program then you will come to know what are Obsolete statements then you can rectify easily.

When it comes to Performance issue, wht ever you do in ECC 6.0 do as same in 4.7.

revert me for any info.

Regards,

Suneel G

8 REPLIES 8

Former Member
0 Kudos

You can check SE30 -> 'Tips & Tricks' to avoid performance issues, other than that there is no seperate procedure to avoid in 4.7.

0 Kudos

Hi satya,

working on tips and tricks too. thanks.

0 Kudos

Hi Sakthi,

I faced the same problem,. I am in support now for last 3 months...

So let me share some of the tips and tricks I follow...

In ECC 6.0 there is always less data... since the database may be from 2005 but not early than that...

But for 4.7 EE it may be from 1997 also... like mine...

Since of a huge database,,, some times the select statements you write will not work in PRD & QAS..

You will get Request Timed Out.

So you need to be more carefull at select statements,,, match as many as primary keys.. and learn Secondary indexes,,, and must should have a good idea on foreign key relations very well...

About the like or Occurs..etc. you dont worry about that,, that is very easy.... and if there is a modification you can write the code almost all like the ECC 6.0...

In SAP Wiki, there are performance tips & Coding procedures.. Lokk at that it will be help full...

Thanks & regards,

Dileep .C

0 Kudos

Also Try T-code ST05 (SQL Trace) for Peformance Analysis of SQL statements.

Thanks.

Former Member
0 Kudos

Hi sakthi sri,

As you are in Support project you will not do much coding rite,

If there a new program to develop write code as you do in ECC 6.0 and then do Extended check for that program then you will come to know what are Obsolete statements then you can rectify easily.

When it comes to Performance issue, wht ever you do in ECC 6.0 do as same in 4.7.

revert me for any info.

Regards,

Suneel G

0 Kudos

Thanks suneel.

previously I never use occurs 0 statement for itab declaration. here they are using. so i am confused whether to change it and will it affect the performance.

thanks.

0 Kudos

If you want to create internal table without header line then you no need to use Occurs 0, instead you need to use external work area.

If you are sure about the number of entries in the internal table then you can use Occurs n, (n is number of records), while creating internal table.

if you are not sure about the number of records of the internal table and if you dont want to use the separate work area then you will use Occurs 0.

It is same concept across all the versions, nothing to worry much.

0 Kudos

Hi sakthi sri,

please close the thread once answered or else continue with your doubts.

Regards,

Suneel G