Internal tables whose line type contains further internal tables

Hi,
can you please demonstrate through a code sniplet the follwing topics .
structures containing internal tables as components (deep structures)
Internal tables whose line type contains further internal tables.
Thx in advance
Regards
sas

Hi,
Check the code
TYPES : BEGIN OF t_gr,
          wrbtr TYPE ekbe-wrbtr,
          menge TYPE ekbe-menge,
          bwart TYPE ekbe-bwart,
         END OF t_gr.
DATA : i_gr    TYPE TABLE OF t_gr.
TYPES : BEGIN OF t_ekbe,
           ebeln TYPE ekbe-ebeln,
           ebelp TYPE ekbe-ebelp,
           *llggr LIKE i_gr,*
          END OF t_ekbe.
   DATA : i_ekbe      TYPE TABLE OF t_ekbe.
   SELECT ebeln
          ebelp
          wrbtr
          FROM ekbe
          INTO TABLE i_ekbe1
          FOR ALL ENTRIES IN i_data1
          WHERE ebeln = i_data1-ebeln   AND
                ebelp = i_data1-ebelp   AND
                  bewtp = c_e          AND
                ( bwart = c_101        OR
                  bwart = c_102        OR
                  bwart = c_103        OR
                  bwart = c_104 ).
loop at i_ekbe1 into wa_ekbe1.
wa_ekbe = wa_ekbe1.
wa_gr-wrbtr = wa_ekbe-wrbtr
append wa_gr to i_gr.
on change of wa_ekbe1-ebeln.
       *INSERT LINES OF i_gr INTO wa_ekbe-llggr INDEX 1.*
       *APPEND wa_ekbe TO i_ekbe.*
endon.
edloop.
the above code the ekbe table is having one move itab l_gr
l_gr is updated in each loop and and each change the i_ekbe is updated with one set of l_gr data as internal table line for i_ekbe.
regards,
Nandha

Similar Messages

Purpose of Row type, line type and Table Type..

Hi All,
Just Im started working with OOABAP. Whenever I open some structures, most of the components in the structures have the below three words. What is the exact difference b/w the below words. What is purpose those?
Row type, line type
Table type:
Please let me know.

hi,
Line Type
The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table.
Table type
The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.
Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether the key is to be UNIQUE or NON-UNIQUE. Standard tables and sorted tables are known generically as index tables.
Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.
The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key should be UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries. The uniqueness depends on the table access method.
At tables with structured row type, the standard key is formed from all character-type columns of the internal table. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty. At tables with non-structured row type, the standard key consists of the entire row. If the row type is also a table, an empty key is defined.
The user-defined key can contain any columns of the internal table that are no internal table themselves, and do not contain internal tables. References are allowed as table keys. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.
Internal tables are always completely specified regarding row type, key and access type
Hope this helps.

Sorting internal table with line types

Hi,
I have internal table juts for an example with four entries as below:
A[]
Line.....Line Types
444001.....P
New York...C
Evershine..B
Mary.......N
I want to sort the internal table with line types in order of lin types NBCP.
How can i do this ?
Please help.
Note: Above example is just with four entries, there might be internal table with ten entries and ten defined sorting order for line types.

Hi Tushar,
Please note that we can't changes the mandatory sequence of the address format as defined in the country specif address format. We can change the sequence of others fields by line_priority.
Try to change the address type :
ADDRESS_TYPE - Address type (from 3.0C)
There are three types of address:
Address type '1': addresses of firms or organizations; the address structure which is used in most SAP applications as 'Address'.
Address type '2': address of a person
Address type '3': work address, usually the address of a contact person in a company
Please use T/code "OY01"> Select Country> Example :AU"--> Display --> Select address key and press F1. You will find SAP 's Address format configuration .
sap help:
Formatting Routine Key for Printing Addresses
For printing addresses, there are country-specific routines which in each case copy the correct postal formatting of the address.
The three-character "Address Layout Key" for the recipient country controls which of the routines available for formatting addresses in the relevant country is used.
These routines are programmed into the ADDRESS_INTO_PRINTFORM function module.
They are based on different national and international guidelines and norms, including:
ISO 11180,
contracts of the World Postal Union (Seoul 1994),
international address samples from the World Postal Union
as well as the available rules of the individual countries.
Below you will find an overview of the country-specific formats currently implemented.
Customers can program their own formatting routines using a customer exit. The SZAD0001 SAP enhancement has been defined in the package SZAD for this (-> transaction CMOD).
General formatting rules
The following parameters are used depending on the transaction:
whether the company address (street/house number) or the P.O. Box address is printed if both exist,
how many lines are available for printing,
which is the sender country.
If there are not enough lines, then lines are left out according to a standard sequence.
The address format depends on whether the sender country is the same as, or different from, the recipient country. The country is always specified from abroad, either as a text name, or as an identification code of up to three characters (license plate code or country key).
Where the country name is written out in full, it is written in the language of the sender country. If a language is not specified for the sender country, or the sender country itself is not specified, the logon language is used instead.
Exception: the language for the country code can be explicitly overwritten by a parameter in the print program (e.g. when the country code for customs transit papers is always to be specified in a particular language, such as English). if the "Print country name in recipient language" flag is set in the print program, the recipient language is used.
Other language-dependent components such as the title and the word 'PO Box' are printed in the recipient language or the recipient country language. If this cannot be determined, the logon language is again used.
For all formats except Great Britain (006), Japan (013), and South Korea (017), the core of the address is formatted as follows (without empty lines, except for the compulsory empty line:)
title line (if applicable)
name block (differs depending on the address type, see below)
street address or PO Box
(compulsory empty line, if applicable)
city line with postal code
country code (if applicable)
The city line and the country name are always printed in upper case for foreign addresses (only for the complete address, not for short forms).
The name block generally consists of the following:
"Normal" addresses (address type SPACE and address type 1):
NAME1
NAME2
NAME3
NAME4
Personal addresses (address type 2):
Title of person and name of person
Business address with department and contact person (address type 3):
NAME1
NAME2
NAME3
NAME4
department
title of person and name of person
In addresses entered using Business Address Services (central address management) (see Release notes Central Address Management for Release 4.0 and Central Address Management for Release 4.5 ), the street address can comprise several lines (see Print street address), otherwise street and house number are maintained in the Street field.
Some countries do not have a compulsory empty line (see notes below). The city and district are printed in the city line, connected by a hyphen (exceptions: 004 USA, 006 Great Britain/Ireland, 013 Japan, 015 Germany, 017 South Korea, 019 Denmark), provided that the total length does not exceed 35 characters. If a different city is specified for the PO Box (PFORT), this is used in the PO Box address.
In all formats which use a country code (currently 001 European standard format 002 Italy, 011 Switzerland and 014 Austria ), the license plate code for that country is used. If this is not maintained, the country key in table T005 is used.
If the "Print country name in foreign addresses" flag is set for the sender country in table 005, the country code is not used; the country name is printed in the last line of the address.
Formats 004 (USA), 005 (Canada) and 008 (Singapore) contain a line ('F') for the function of the contact person in the company (if address type = '3'). This line comes immediately after the line 'N' (Name (and title) of the natural person).
In formats 002 (Italy), 004 (USA), 005 (Canada), 006 (Great Britain), 007 (Brazil) and Australia (009), the REGIO field (Region, State, Province, County) is formatted. For the USA, Canada, Brazil and Australia, the key from table T005S is used; for Great Britain the text name from table T005U.
In all countries for which no "Address structure key" is maintained, a standard format is used which corresponds to format "010".
Hope this may help you.
Lanka

Difference between line type and internal table?

Hi..
I wanted to know, what is the difference between Line type and Internal Table?

Hi,
Before the 4.7 release in SAP if we want to define an internal table we have to write the defination using the occurs statement and we need to define all the fields using INCLUDE STRUCTURE or indidually all the fields ine by one.
From 4.7 release of R/3 SAP introduced the Line type concept and it's part of the ABAP OOPS concept. for internal table defination we don't need to use the occur statements. Instead INCLUDE structure we need to create a Line type for that structure in Se11 and then we can define the internal table like :
DATA : ITAB TYPE TABLE OF <LINE_TYPE>.
Only thing is this table will be a table without header. So for internal table processing we need to define a work area structure of type line of line type . EX:
DATA: WA_ITAB TYPE LINE OF <LINE_TYPE>.
Hope this helps.
Thanks,
Greetson

Mapping Line type Data to table data

Hi,
I am trying to refer to a data element present in the line type of a table type which belongs to an import parameter of a smartform. How will i access the data element to use in the where clause of a select statement.
For Eg:
Import Parameter name: PARTNER_H
TYPE: CRMT_OUTPUT_PARTNER_H_COMT (table type)
The line type attached to this table type is CRMT_OUTPUT_PARTNER_H_COM.
This line type is the structure that contains the data element that i need to use. the details are as below:
Component: RELATION_PARTNER
Component type: BU_PARTNER_GUID
I have written a select statement as below:
SELECT SINGLE * from BUT000 into I_FS_BUT000 where
PARTNER_GUID = PARTNER_H-RELATION_H.
I have given the input parameter as PARTNER_H.
It throws me an error that "PARTNER_H" is a table without a header line and therefore has no component called "RELATION_H".
Is this the correct way to access the data element?Please help.

Hi Neena,
Since PARTNER_H is an internal table it may have multiple values. If you want only a single entry from BUT000, you ll have to determine which entry from PARTNER_H you need in select query.
If it is always going to have only a single value then , this will work :
data: wa_partner_h type line of CRMT_OUTPUT_PARTNER_H_COMT.
Read table partner_h into wa_partner_h index 1.
if sy-subrc is initial.
SELECT SINGLE * from BUT000 into I_FS_BUT000 where
PARTNER_GUID = WA_PARTNER_H-RELATION_H.
endif.
Regards,
Arun

Smartform Table Line types duplicate entries problem

Hi ,
I am getting one strange problem in Smartforms. i tried for information in SDN but i did not get any usefull ones.
I have created my main window with particular width. I created two different Line types. On particular condition i need use these line types.
First line item will have 6 columns in that one column is empty.
Second liitem will have 5 columns.
When i am generating the output, the last item data of the first line type is repeating twice, i.e with first line type and the second line type.
Can anyone give me the inputs to solve this.
Thanks,
Srinivas Bhavanam

Did you check SAP notes?
I don't understand what you get exactly:
For the last line of the internal table, you would like to get this:
A B C D E F
G H I J K
But you get that:
A B C D E F
A B C D E F
Did I understand correctly?
Did you use something special? (header, footer, conditions, ...)

Table Types and Line Type

What is the need of Table Types,
when there is Tables.
Even when iam using in the Abap Programs in se38..
iam not getting any difference..
Even i want to about the use of Line type
when there is the structure..
iam sap 4.7 they gave that Table type describe the structure and
functional attributes of an internal table.

Way: 1:
Go to SE84 --> Select ABAP Dict --> Table Types -->
Enter the short names like ORDER wih leading and ending * on the Table Types Field. ---> F8
This will bring all related entries of Table Types(Line Types) having ORDER has a part of its Name.
Way:2:
If you know the Table Name, then go SE11 --> Putch in the Table Name --> Press Display
Now put the cursor on the Table Name field, press CNTLSHFTF3, on the WHERE USED LIST Pop up, Select only the TABLE TYPE Option and press EXECUTE.
This will bring the Table Types and Line Types.
SAP Table Types
I. Transparent tables (BKPF, VBAK, VBAP, KNA1, COEP)
Allows secondary indexes (SE11->Display Table->Indexes)
Can be buffered (SE11->Display Table->technical settings) Heavily updated tables should not be buffered.
II. Pool Tables (match codes, look up tables)
Should be accessed via primary key or
Should be buffered (SE11->Display Table->technical settings)
No secondary indexes
Select * is Ok because all columns retrieved anyway
III. Cluster Tables (BSEG,BSEC) Should be accessed via primary key - very fast retrieval otherwise very slow
No secondary indexes
Select * is Ok because all columns retrieved anyway. Performing an operation on multiple rows is more efficient than single row operations. Therefore you still want to select into an internal table. If many rows are being selected into the internal table, you might still like to retrieve specific columns to cut down on the memory required.
Statistical SQL functions (SUM, AVG, MIN, MAX, etc) not supported
Can not be buffered
IV. Buffered Tables (includes both Transparent & Pool Tables)
While buffering database tables in program memory (SELECT into internal table) is generally a good idea for performance, it is not always necessary. Some tables are already buffered in memory. These are mostly configuration tables. If a table is already buffered, then a select statement against it is very fast. To determine if a table is buffered, choose the 'technical settings' soft button from the data dictionary display of a table (SE12). Pool tables should all be buffered.
Table Types : A table type describes the structure and functional attributes of an internal table in ABAP. In ABAP programs you can reference a table type TTYP defined in the ABAP Dictionary with the command
DATA : itab TYPE TTYP.
Reafer these links below for clear ideas.
http://help.sap.com/saphelp_nw04/helpdata/en/fb/f14736a1f0ad1fe10000009b38f839/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
Thanks
Allot points if this helps!

Difference between line type and table type

hi,
can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

hi,
Go through this blog, this might help you.
/people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
                        "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
In a BSP when we need to work with a table we must always do the following:
1, in the Types definitions create a structure:
                        types : begin of ts_reclist,
mso-bidi-        style='mso-tab-count:2'>                            receiver type somlreci1-receiver,
mso-bidi-        style='mso-tab-count:2'>                 style='mso-tab-count: 1'>             rec_type type somlreci1-rec_type,
mso-bidi-         style='mso-tab-count:2'>                            end of ts_reclist.
mso-bidi- <![if !supportEmptyParas]> <![endif]>
but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
class="MsoNormal">                         types : tt_reclist type table of ts_reclist.
class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
                       data: t_reclist type tt_reclist.
and creating the structure based upon the structure definiton:
<![if !supportEmptyParas]>   <![endif]>                         data: s_reclist type ts_reclist.
as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
                        s_reclist-receiver = '[email protected]'.   "<-- change address
mso-bidi- <![if !supportEmptyParas]> <![endif]>
mso-bidi-                         s_reclist-rec_type = 'U'.
and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
                        append s_reclist to t_reclist.
<![if !supportEmptyParas]> <![endif]>
the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1">           style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>
class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
                        EXPORTING
style='mso-tab-count:2'>                                    document_data = docdata
style='mso-tab-count:2'>                                    DOCUMENT_TYPE = 'RAW'
style='mso-tab-count:2'>                                    PUT_IN_OUTBOX = 'X'
style='mso-tab-count:2'>                                    COMMIT_WORK = 'X' "used from rel.6.10
                        TABLES
mso-bidi-font-size: style='mso-tab-count:2'>                                    receivers = t_reclist
class="style1"> <![if !supportEmptyParas]>   <![endif]>
<![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
<![if !supportEmptyParas]> when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.
Hope this helps, Do reward.

In "LOOP ... WHERE ..." the line type of the table must be statically defin

Hi All,
        I have written the code, for greater than (GJAHR) 2007 and restricted company codes ( table name = ZGLCCODE).
     Here I have written the following the code which is giving an error
In "LOOP ... WHERE ..." the line type of the table must be statically defin
ZGLCCODE Contains only restricted company codes.
Code is as follows
TABLES : ZGLCCODE.
DATA : LT_DATAPACKAGE TYPE TABLE OF DTFIGL_4.
DATA : LS_PACKAGE TYPE DTFIGL_4.
TYPES: BEGIN OF LS_TZGLCCODE,
       ZBUKRS type BUKRS,
        END OF LS_TZGLCCODE.
DATA : LT_ITZGLCCODE TYPE LS_TZGLCCODE OCCURS 0 WITH HEADER LINE.
DATA : LI_NUM TYPE I,
       LC_ZGJAHR TYPE BSEG-GJAHR VALUE '2007'.
SELECT ZBUKRS INTO TABLE LT_ITZGLCCODE FROM ZGLCCODE.
Note: "C_T_DATA" dynamic structure = "DTFIGL_4" structure
*- Remove from the DataSource Company Code -
LOOP AT C_T_DATA INTO LS_PACKAGE WHERE GJAHR GE '2007'.
READ TABLE LT_ITZGLCCODE WITH KEY ZBUKRS = LS_PACKAGE-BUKRS.
IF SY-SUBRC <> 0.
   APPEND LS_PACKAGE TO LT_DATAPACKAGE.
ENDIF.
CLEAR LS_PACKAGE.
ENDLOOP.
IF LT_DATAPACKAGE[] IS NOT INITIAL.
DESCRIBE TABLE LT_DATAPACKAGE LINES LI_NUM.
IF LI_NUM GT 0.
   REFRESH C_T_DATA.
   APPEND LINES OF LT_DATAPACKAGE TO C_T_DATA.
   REFRESH LT_DATAPACKAGE.
   FREE LT_DATAPACKAGE.
endif.
ELSE.
   REFRESH C_T_DATA.
ENDIF.
Please give me your valuable suggestions.
Thanks
Ganesh Reddy.

Hi Ganesh,
whatever you do, you can try like this:
1 - any code posted should be wrapped in \
then try something like this:
field-symbols:
<tabrec> type any,
<field>   type any.
sort ITZGLCCODE by bukrs.
LOOP AT C_T_DATA ASSIGNING <tabrec>.
ASSIGN component 'GJAHR' of structure <tabrec> to <field>.
check <field> <= 2007.
ASSIGN component 'BUKRS' of structure <tabrec> to <field>.
READ TABLE LT_ITZGLCCODE WITH KEY ZBUKRS = <field>
    BINARY SEARCH TRANSPORTING NO FIELDS. "speed up the volume.
IF SY-SUBRC 0.
    MOVE-CORRESPONDING <tabrec> to LS_PACKAGE.
    APPEND LS_PACKAGE TO LT_DATAPACKAGE.
ENDIF.
ENDLOOP.
Regards,
Clemens

Hash tables in combination with data references to the line type.

I'm having an issue with hash tables - in combination with reference variables.
Consider the following: (Which is part of a class) - it attempts to see if a particular id exists in a table; if not add it; if yes change it.
types: BEGIN OF TY_MEASUREMENT,
           perfid      TYPE zgz_perf_metric_id,
           rtime       TYPE zgz_perf_runtime,
           execount    TYPE zgz_perf_execount,
           last_start TYPE timestampl,
         END OF TY_MEASUREMENT.
METHOD START.
DATA: ls_measurement TYPE REF TO ty_measurement.
READ TABLE gt_measurements WITH TABLE KEY perfid = i_perfid reference into ls_measurement.
if sy-subrc <> 0.
    "Didn't find it.
    create data ls_measurement.
    ls_measurement->perfid = i_perfid.
    insert ls_measurement->* into gt_measurements.
endif.
GET TIME STAMP FIELD ls_measurements-last_start.
ls_measurement->execount = ls_measurement->execount + 1.
ENDMETHOD.
I get compile errors on the insert statement - either "You cannot use explicit index operations on tables with types HASHED TABLE" or "ANY TABLE".      It is possible that.
If I don't dereference the type then I get the error LS_MEASUREMENT cannot be converted to the line type of GT_MEASUREMENTS.
I'm not looking to solve this with a combination of references and work ares - want a reference solution.
Thanks!
_Ryan
Moderator message - Moved to the correct forum
Edited by: Rob Burbank on Apr 22, 2010 4:43 PM

I think it might work when you change it for
insert ls_measurement->* into TABLE gt_measurements.
For hashed table a new line here will be inserted according to given table key.
Regards
Marcin

Printing double line in Column label Box/Table Line Type of smartform

Hi,
In MAIN window, in ITEM table, the header box, (where column labels are printed), one double lines r printing!! it looks like (not exactly) instead of single line (________) its printing double lines (======), so, pls. let me know, Wht culd be the reason?
Thank you

Hi,
Check that if you used table borders in attributes of line types.
And also check if you are using sy-unline...
Regards,
Shankar.

How to get the line type of a table type

Hi,
i want to indetify the line type of a table type dynamically in my program. how to do?
For example:
data: lv_ttype type type ROLLNAME value 'PRXCTRLTAB'.
how to identify line type of lv_ttype in the program.
Thanks,
johnney.

Hello Johnney,
try like this...
types: begin of ty_itab,
            matnr like mara-matnr,
            werks like marc-werks,
            maktx like makt-maktx,
          end of g_t_itab.
data: g_t_itab type table of ty_itab.
data: <b>wa_itab like line of g_t_itab.</b> " This is line type... so called work area.
Reward If Helpful.
Regards
Sasidhar Reddy Matli.

How to perform a select op on a table whose name is contained by a variable

I am using Oracle SQL*Plus client.
declare
tablename_var varchar(10); LOOK HERE
date_var date;
begin
select sysdate
into date_var
from &tablename_var; LOOK HERE
dbms_output.put_line('The system date is '||date_var);
end;
The above code prompts the user to enter a value for the variable tablename_var, once the user enters 'dual' on prompt... The system date is given as output.
declare
tablename_var varchar(10):='dual'; LOOK HERE
date_var date;
begin
select sysdate
into date_var
from tablename_var; LOOK HERE
dbms_output.put_line('The system date is '||date_var);
end;
This code fails and gives an error. I understand. Engine interprets it as... trying to perform a select operation on a variable, and says a table or a view is expected.
Can someone please tell me what to do, to perform a select operation on a table whose name is contained by a variable, like above?

Hi,
Welcome to the forum!
You need Dynamic SQL if the table- or column names are variables.
Getting the current date isn't a good example; you could get that without a query simply by saying
date_var := SYSDATE;Also, SELECT ... INTO will raise an error if the query does not return exactly 1 row.
In the example below, let's get the latest entry_date from a given table:
For example:
declare
     tablename_var     varchar(10);
     date_var      date;
     sql_txt           VARCHAR2 (1000);
begin
     tablename_var := 'table_x;
     sql_txt := 'select MAX (entrydate)'
          || ' from ' || tablename_var;
     dbms_output.put_line (sql_txt || ' = sql_txt');    -- Not essential, but recommended
     EXECUTE IMMEDIATE sql_txt INTO date_var;
     dbms_output.put_line ('The latest entry_date is ' || date_var);
end;Dynamic SQL involves creating a string that contains the SQL statement. Displaying the string is purely optional, of course, but it's a very good idea when writing and de-bugging code. Remember to comment-out or delete the display before moving the code into Production.
For an exercise, make the column name a variable, instead of the hard-coded entry_date.
Edited by: Frank Kulash on Nov 5, 2009 9:20 AM

How to update a table whose column name contains an ampersand?

Hello,
I am needing to update a column whose column name contains an ampersand, and cannot figure out a way to do this. Option is not there to have the column name changed.
Ex:
UPDATE aircrafts
SET d&f = 1
WHERE aircraft_code = '737';
this returns an error of missing an = sign
I tried:
SET 'd'||'&'||'f' = 1
doesnt work
Any help is greatly appreciated.
Thanks,
Laura

SET DEFINE OFF
will stop interpreting the & sign as starting of a lexical parameter on the client.
Not sure if you have that issue there.
& might also be a not allowed character in normal column names (didn't test).
In that case you might need to put the column name in ".
+example+
{code}
UPDATE aircrafts
SET "d&f" = 1
WHERE aircraft_code = '737';
{code}
Be aware that in this case the column name must be spelled exactly like it was when the table was created.
Included upper/lower case.
{code}
UPDATE aircrafts
SET "D&F" = 1
WHERE aircraft_code = '737';
{code}

Urgent : How to modify the line type and table type

I am working on ALV Grid Control, i need to know how to modify the line type values to table type.
             ls_celltab-fieldname = 'ZSAVINGS '.
             ls_celltab-style = l_mode.
        INSERT ls_celltab INTO TABLE pt_celltab.
Here ls_celltab is line type and pt_celltab is table type.
Please give me the suggestion ASAP.
C.Bharath Kumar

Hi,
Here is the example
DATA: BEGIN OF LINE,
        LAND(3) TYPE C,
        NAME(10) TYPE C,
        AGE      TYPE I,
        WEIGHT   TYPE P DECIMALS 2,
      END OF LINE.
DATA ITAB LIKE SORTED TABLE OF LINE
          WITH NON-UNIQUE KEY LAND NAME AGE WEIGHT.
LINE-LAND = 'G'.   LINE-NAME   = 'Hans'.
LINE-AGE = 20.    LINE-WEIGHT = '80.00'.
INSERT LINE INTO TABLE ITAB.
LINE-LAND = 'USA'. LINE-NAME   = 'Nancy'.
LINE-AGE = 35.    LINE-WEIGHT = '45.00'.
INSERT LINE INTO TABLE ITAB.
Regards
Sudheer

Internal tables whose line type contains further internal tables

Similar Messages

Maybe you are looking for