5 Comments

• 
  steve oldner

  # May 8th, 2013 at 9:14 am

  Yes, I have noticed all the hard work you have put into the site over the years. Very impressive! Haven’t thought about being a guest author, since I generally copy your code!

  Anyway, thanks for the blog and all the work you have put into it.

• 
  Naimesh Patel

  # May 8th, 2013 at 10:19 am

  Hello Steve, Thanks for your kind words 🙂

• 
  Abhi

  # May 11th, 2013 at 8:44 am

  Hi Naimesh,

  Great Work. Need to appreciate you for the effort you are keeping for the site.

  I have a question for you – old topic
  1) when to go for – for all entries or inner join(i have 1 answer that inner join should be used for maximum of 3 tables)
  2) is there any conditions/prerequisite to think before using Hashed Internal tables

• 
  Aashrith

  # May 13th, 2013 at 11:40 am

  Dear Abhi,

  Regarding question 2,

  SAP advises using the Hashed Internal Table if you expect to have large amount of data in the internal table and you will be accessing the data only through key access.

• 
  Naimesh Patel

  # May 13th, 2013 at 1:42 pm

  Hello Abhi,

  Regarding #1 – It always depends on the number Tables and optimal access path to execute the Join. You would see some amazing results by having as many as 6-8 tables which has a optimal access path as it has mandatory fields with concrete values which would result in a good join. If you try to break this join using the SELECT & LOOP, you may end up spending more time to get to the dataset.

  But on the other side, if you have a table which doesn’t follow the optimal access path, the same query may take longer runtime.

  Regarding #2 – Usage of hashed table, I agree with comment from Ashrith.
  From SAP help: See section Hashed Table in Choosing a Table Type

  Hashed tables
  This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.

  Thanks,
  Naimesh Patel