topic Re: TABLES statement in report program in Application Development and Automation Discussions

TABLES statement in report program

Former Member — Mon, 11 Feb 2008 09:17:48 GMT

Hi,

Is there any performance issue in using TABLES statement in report program? Because I have got an review point from QA insisting me to avoid TABLES statement. Is it recommended by SAP to avoid TABLES statement in report program?

Thanks in advance.

Regards,

Balaji Viswanath.

Re: TABLES statement in report program

Former Member — Mon, 11 Feb 2008 09:20:45 GMT

Hi,

Tables statement actually creates field string with the given type and with the same name. This tables statement is going to ignored in next versions i.e. it is an obsolete statement ok

plzz reward if it is usefull to u

plzz dont forget to reward...

Re: TABLES statement in report program

kiran_k8 — Mon, 11 Feb 2008 09:23:39 GMT

Balaji,

If we are using a select-option for a field in the selection screen then the declaration of that particular table is mandatory,in the rest of all cases it is not.

delcaration of the table in the tabels declaration is mandatory.

tables: mara.

select-option s_matnr for mara-matnr.

K.Kiran.

Re: TABLES statement in report program

Former Member — Mon, 11 Feb 2008 09:26:20 GMT

Work table areas declared with TABLES behave like the data declared with the addition COMMON PART, meaning the data are used by the programs of a program group.

Table work areas declared with TABLES can be declared in subroutines and function modules. However, this is not recommended. A table work area declared in a procedure is not local but belongs to the context of a framework program. The table work area can be viewed starting from the declaration in the framework program and lives as long as the framework program. In contrast to normal program-global data, the content of the table work areas declared in subroutines and function modules is stored temporarily when these subroutines and function modules are called. Value assignments that were made during runtime of the procedure are preserved until the procedure is completed. When exiting the procedure, the table work areas are filled with the contents that they contained when the procedure was called. Table work areas declared in procedures behave like global data to which the statement LOCAL is applied in the procedure.

The declaration of common data areas for different programs is usually carried out in an include program, which is then integrated in all the programs involved. The use of common data areas in otherwise independent programs can be very problematic, with regard to both the maintainability and the functions. Therefore, common data areas should no longer be used. The parameter interfaces of procedures are available for exchanging data between programs.