Why Obsolete Statements

[Former Member]

Hi,

What are the problems we need to face while using obsolete statements in a program.

Is there any other options insted of Import and export of memory ids comes under the obsolute statements?

DATA:lv_run_id TYPE XXXX_run_id,

lv_memrunid TYPE c LENGTH 11 VALUE 'XXXX_RUNID'.

GET PARAMETER ID 'ACC_SYSTEM' FIELD lv_accsys.

*--- For RunId we use a memory ID

IMPORT lv_run_id FROM MEMORY ID lv_memrunid.

Last statement is an obsolete statement . is there any other way ? for getting the parameter id.

.........Gopeekrishnan

[Former Member · Accepted solution]

hi,

suppose you want a parameter id for MATNR in that case

you goto MARA table and double click the component of matnr and double click it , you will get a popup in that go to further characteristics.

regards,

manohar.

[manuel_bassani · Accepted solution]

Hi,

Your last statement is obsolete.

IMPORT lv_run_id FROM MEMORY ID lv_memrunid.

correct is:

IMPORT lv_run_id = lv_run_id FROM MEMORY ID lv_memrunid.

implicit field names are no more allowed.

From F1 help:

*****************************************

Reason:

The use of implicit names may lead to errors. The specified names are to be understood as field identifications in the cluster. With the implicit method, the specified identifications are used literally when data clusters are exported, i.e., including offset/length specifications or preceding selectors. When clusters are imported in a different context, these identifications must be known and must be specified identically. Because of the similarity to method and function module calls, the use of the equals sign (=) emphasizes that formal parameters appear on the left and actual parameters on the right. The expressions FROM and TO are also additionally used to specify where data is stored.

*****************************************

Regards, Manuel