Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

table in OO context

Former Member
0 Likes
1,618

Hi all.

please tell my why table with header line is not supported by OO context.

i want to fetch some the data from database table and display it on the output screen how to do this.

Regards

Prajwal.k

1 REPLY 1
Read only

Former Member
0 Likes
558

> Hi all.

> please tell my why table with header line is not

> supported by OO context.

>

Check this extract from SAP help

http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb36a1358411d1829f0000e829fbfe/content.htm

Using the header line as a work area means that you can use shorter statements; however, they are not necessarily easier to understand, since you cannot immediately recognize the origin and target of the assignment. Furthermore, the fact that the table and its header line have the same name can cause confusion in operations with entire internal tables. To avoid confusion, you should use internal tables with differently-named work areas.

Also check this

http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb367a358411d1829f0000e829fbfe/content.htm

When you use internal tables with header lines, you must remember that the header line and the body of the table have the same name. If you have an internal table with header line and you want to address the body of the table, you must indicate this by placing brackets after the table name (<itab>[]). Otherwise, ABAP interprets the name as the name of the header line and not of the body of the table. You can avoid this potential confusion by using internal tables without header lines. In particular, internal tables nested in structures or other internal tables must not have a header line, since this can lead to ambiguous expressions