topic Re: Extended Program Check, TABLES statement obsolete in Application Development and Automation Discussions

Extended Program Check, TABLES statement obsolete

Former Member — Thu, 03 May 2012 09:28:18 GMT

Hi,

I am using a field from "DD02L" in my parameters and therefore have declared the table using TABLES statement.

When I do an EPC on my program, it gives me the following under Programming Guidelines(Warnings) :-

"TABLES statement (DD02L) is obsolete

Cannot be suppressed using a pragma or pseudo-comment"

What is the alternative to this statement?.

I am working ECC 6 Ehp5.

Re: Extended Program Check, TABLES statement obsolete

Former Member — Thu, 03 May 2012 09:36:21 GMT

Why dont you use the data element of the table for your parameter?

Re: Extended Program Check, TABLES statement obsolete

Former Member — Thu, 03 May 2012 09:38:33 GMT

If by parameters, you mean to say , selection screen parameters,why you need Tables Statement to define parameter. You can directly do it like:

Parameters p_tab type dd02l-tabname.

Kindly let me know if I understood your requirement incorrectly.

Re: Extended Program Check, TABLES statement obsolete

Kartik2 — Thu, 03 May 2012 09:43:01 GMT

Dear Asshrith HG,

When you use the statement TABLES, then an internal table with header line will get declared and sice internal tables with header lines are obsolete you are getting that error message.

As suggested you can use the data element directly. Data element for that field is TABNAME.

Declare a variable of type TABNAME and use it in your program. Thank you.

Regards,

kartik

Re: Extended Program Check, TABLES statement obsolete

former_member209818 — Thu, 03 May 2012 09:43:48 GMT

You can direct refer to the Data Element of the field which you want to refer and accordingly you can adjust your Parameter declaration. For that you do not need to use TABLES statement.

Table statement actually allows you to use a structure with the same name and hence it creates a conflict in a Obj Oriented scenario. Hence that statement is made Obsolete.

Re: Extended Program Check, TABLES statement obsolete

ThomasZloch — Thu, 03 May 2012 09:44:11 GMT

TABLES statement is obsolete because it declares a work area of the same name as the DB table, thus leading to ambiguous code, similar topic as internal tables with header lines, also obsolete.

Better declare separate work areas for the relevant DB tables for the use in the SELECT statements.

Thomas

Re: Extended Program Check, TABLES statement obsolete

Private_Member_49934 — Thu, 03 May 2012 10:05:35 GMT

For parameters you don't need TABLES statement You can directly refer using TABLE-FIELDNAM or Data element name. LIke

parameters : p_matnr type matnr.

If you are trying to create select option the you may create an auxilarry variable for the same.

data : gv_matnr type matnr.

select-options : so_matnr for gv_matnr.

Re: Extended Program Check, TABLES statement obsolete

RaymondGiuseppi — Thu, 03 May 2012 10:09:40 GMT

TABLES should only be used when fields are used in a dynpro, else declare a workarea of type database name. (ex: DATA: vbap TYPE vbap.)

Regards,

Raymond

Re: Extended Program Check, TABLES statement obsolete

Former Member — Thu, 03 May 2012 10:18:01 GMT

Thanks all for your quick & valuable replies.