‎2008 Aug 05 1:43 PM
Hi,
I want function module to get the plantwise invoices.
Currently i want to write query on VBRK for invoices and for plant details i need to write query on VBRP.
For large data it takes more time.
So can anybody tell me regarding this?
Regards,
Deepak.
‎2008 Aug 05 1:53 PM
Hi...
Following are some performance tuning conditions....
and better to go for for all entries method.. because it links the tables at application layer level..
Use Select Single when only one row is expected
Use Select Where rather than Selectu2026Check
Use Select with aggregate functions (SUM, MAX, MINu2026)
Use a View instead of nested Selects
Use Select column specific instead of select * for few fields
Use Selectu2026Into Table rather than Select...Move Corru2026Apend
Use Join extension with Select if possible
Use special operators (CO, CA, CS) rather than code your own
Use Delete Adjacent Duplicates rather than manual processing
Specify key fields for Readu2026Binary Search
Use Loop At Where rather than Loop Atu2026Check
Copy Internal Tables with TAB_DEST() = TAB_SRC()
Specify the sort key as restrictively as possible
Use Append To, Insert Into, Collect Into rather than Move
Compare tables with If Tab1() = Tab2()u2026
Use Delete ITAB Whereu2026 instead of Loop At ITAB Whereu2026Delete..
Use Case statements instead of If-constructions
Use Call Functions wisely, Performs use less memory
Use While instead of Do Exit
Use Type I for Indices
Keep Occurs clause realistic or use 0
Use COMMIT WORK as appropriate to free the Data Base and preserve work
Avoid:
Using Shift inside a While-loop
Leaving unneeded declarations in your program
Using Move-corresponding for just a few fields
Excessive nested includes within function calls
Using DB field names if the value will be changed
Using Occurs clause if only the header is needed
All the best!!
Thanks,
Naveen Inuganti.
‎2008 Aug 05 1:51 PM
Hi
Check for this FM WLF_INVOICE_CHECK_WERKS if it suits your requirement.
Thanks
Sudharshan
‎2008 Aug 05 1:53 PM
Hi...
Following are some performance tuning conditions....
and better to go for for all entries method.. because it links the tables at application layer level..
Use Select Single when only one row is expected
Use Select Where rather than Selectu2026Check
Use Select with aggregate functions (SUM, MAX, MINu2026)
Use a View instead of nested Selects
Use Select column specific instead of select * for few fields
Use Selectu2026Into Table rather than Select...Move Corru2026Apend
Use Join extension with Select if possible
Use special operators (CO, CA, CS) rather than code your own
Use Delete Adjacent Duplicates rather than manual processing
Specify key fields for Readu2026Binary Search
Use Loop At Where rather than Loop Atu2026Check
Copy Internal Tables with TAB_DEST() = TAB_SRC()
Specify the sort key as restrictively as possible
Use Append To, Insert Into, Collect Into rather than Move
Compare tables with If Tab1() = Tab2()u2026
Use Delete ITAB Whereu2026 instead of Loop At ITAB Whereu2026Delete..
Use Case statements instead of If-constructions
Use Call Functions wisely, Performs use less memory
Use While instead of Do Exit
Use Type I for Indices
Keep Occurs clause realistic or use 0
Use COMMIT WORK as appropriate to free the Data Base and preserve work
Avoid:
Using Shift inside a While-loop
Leaving unneeded declarations in your program
Using Move-corresponding for just a few fields
Excessive nested includes within function calls
Using DB field names if the value will be changed
Using Occurs clause if only the header is needed
All the best!!
Thanks,
Naveen Inuganti.