topic Re: declaring varaiable in Application Development and Automation Discussions

declaring varaiable

Former Member — Wed, 04 Apr 2007 15:30:41 GMT

HI,

Which one is the best practice of declaring variable and why?

vbeln like vbak-vbeln

vbeln type vbeln.

does declaring LIKE will effect the performance of the program?

Re: declaring varaiable

RichHeilman — Wed, 04 Apr 2007 15:33:15 GMT

Not sure that it matters. I believe it to be personal preference when using the table name and field instead of the data element directly.

vbeln type vbak-vbeln    <-  using table name and field

vbeln type vbeln           <- using data element.

Regards,

Rich Heilman

Re: declaring varaiable

Former Member — Wed, 04 Apr 2007 15:33:53 GMT

Hi!

Declaring will not affect the program runtime.

You can use the way you like better.

Regards

Tamá

Re: declaring varaiable

Former Member — Wed, 04 Apr 2007 19:51:49 GMT

Hi,

you can use LIKE to refer to any object that has been declared using DATA or a similar statement, and is visible in the current context. The object only has to have been declared. It is irrelevant whether the data object already exists in memory when you make the LIKE reference.

In principle, the local data objects in the same program are visible. As with local data types, there is a difference between local data objects in procedures and global data objects. Data objects defined in a procedure obscure other objects with the same name that are declared in the global declarations of the program.

TYPE:

Example: TYPE <type>

to refer to any data type <type> that is already known at this point in the program

When you refer to known data types using the TYPE addition, the visibility of the data types is important.

The predefined ABAP types (C, D, F, I, N, P, T, and X) are always visible. You cannot declare types with the same names as these data types, either in the program or in the ABAP Dictionary.

When we talk about the visibility of local data types in the program, we must differentiate between local data types in procedures and global data types. Data types defined in a procedure obscure other objects with the same name that are declared in the global declarations of the program. All local data types in a program obscure data types with the same names in the ABAP Dictionary. This also applies to data types from type groups.

In the ABAP Dictionary, different visibility rules apply to standalone data types and the data types stored in type groups. Data types in type groups obscure standalone data types with the same names. However, this should be an exceptional situation. All data types in the ABAP Dictionary should be in the same namespace. When you create a standalone data type, the system displays a warning if the name begins with the name of a type group followed by an underscore. Equally, you cannot create a type group if there is already a standalone data type with the same name followed by an underscore.

Regards

Sudheer

Re: declaring varaiable

Former Member — Wed, 04 Apr 2007 22:56:43 GMT

Performance wise there is not much of a difference but SAP is moving away from LIKE in OO context.

Re: declaring varaiable

Former Member — Thu, 05 Apr 2007 04:48:50 GMT

Hi Neha,

Bith the declarations are helpful and also best performance wise.

But for a huge program, we go for the TYPES declaration as it holds the reusability concept unlike the LIKE declaration. So in some kind, we can say that a little bit of performance can be improved using TYPES rather than LIKE in our program.

Hope this resolves your query.

Reward all the helpful answers.

Regards

Re: declaring varaiable

Former Member — Thu, 05 Apr 2007 07:42:43 GMT

I feel there will not be any performance difference while execution. If at all there can be any diffence, then it should be during the intermediate code generation. Both these codes will result in same ABAP intermediate codes and will be executed by the ABAP engine in same fashion.