topic Re: difference b/w Like and Type in Application Development and Automation Discussions

difference b/w Like and Type

Former Member — Mon, 18 Jun 2007 07:24:00 GMT

ERNAM like likp-ERNAM OR

ERNAM type ERNAM

I know the above both statements works same, but can I know when we have to use like and type, what is exact difference in both.

Akshitha.

Re: difference b/w Like and Type

Former Member — Mon, 18 Jun 2007 07:29:33 GMT

Hi,

For all practical purposes there are the same. The only additional advantage with types is that you can define your own types(including complex ones) in the data dictionary and reuse them accross various programs.

But within a program if two variables are defined one using LIKE and another using TYPE, both referring to the same field, then there is no difference.

If I include a type pool within a program, then I can define my variables only using TYPE to refer to any type defined in that pool. I cannot use LIKE in this scenario. Also, if I want to use native types like C, N, etc, I cannot use LIKE there either. I can use LIKE ABC only if ABC is in the database or if ABC is defined previously in the same program.

I can use TYPE ABC, if ABC is defined in database as a TYPE and included in the program with the statement TYPE-POOLS. I can use it, if it is the native types. I can use it, if it is already defined in the dictionary as a structure/table or structure/table field, or even if it is defined as a data element or a domain. So I can declare a variable V_BUKRS TYPE BUKRS, but I cannot define a variable V_BUKRS LIKE BUKRS.

But if I intend to use V_BUKRS to store company code, I will prefer to declare it as V_BUKRS LIKE T001-BUKRS, only because if tomorrow for some reason, the definition of T001-BUKRS changes to a data element for example, BUKRS_N(say DEC 4) instead of the data element BUKRS(CHAR 4) that it refers to now, I don't have to change my programs because I am referring to the table field and inhereting its properties. Whereas, had I declared my V_BUKRS TYPE BUKRS and the table now changed to BUKRS_N, I will be forced to change my program as there will be a type incompatability.

2. try this code (just copy paste)

report abc.

types : char50(50) type c.

*----

type.

data : d1 type c, "--- native

d2 type n, "--- native

d25 type char50 , "----

User defined data type

d3 type bukrs, "---- data element / domain

d4 type persno, "---- data element / domain

d5 type t001, "---- table

d99 type c

data :

*l1 like c "----

Not Allowed

*l2 like n "----

Not Allowed

*l25 like char50 , "----

User defined data type

*l3 like bukrs "----

Not Allowed

*l4 like persno, "----

Not Allowed

l5 like t001 , "---- table

l99 like pa0001

Regards

Re: difference b/w Like and Type

Former Member — Mon, 18 Jun 2007 08:35:07 GMT

Type

If you declare a variable with type , it will not occupy the memory initially.

If you declare a variable with type , it will occupy the memory initially.

Thanks

venkat

Re: difference b/w Like and Type

Former Member — Mon, 18 Jun 2007 08:37:06 GMT

difference between type like and type

Re: difference b/w Like and Type

Former Member — Mon, 18 Jun 2007 08:53:06 GMT

When you define a type no memory is allocated where as for a structure memory is allocated as soon as it is defined.

Convert the code you have provided and see what happens

TYPES: BEGIN OF tI_EKKO,
EBELN LIKE EKKO-EBELN,
AEDAT LIKE EKKO-AEDAT,
BUKRS LIKE EKKO-BUKRS,
BSART LIKE EKKO-BSART,
LIFNR LIKE EKKO-LIFNR,
END OF tI_EKKO.
 
DATA: BEGIN OF I_EKKO,
EBELN LIKE EKKO-EBELN,
AEDAT LIKE EKKO-AEDAT,
BUKRS LIKE EKKO-BUKRS,
BSART LIKE EKKO-BSART,
LIFNR LIKE EKKO-LIFNR,
END OF I_EKKO.

break-point.

now execute the program and at the breakpoint try to check value of I_EKKO and tI_EKKO. ONLY I_EKKO will be allocated meomory tI_EKKO will not be.

reward points if it is usefulll ....

Girish