Value not moved to work are of the internal table

HI
I have one internal table declared with occurs 2500.
i am selecting the values from a z table into this internal table.
now i want to move the values in the table to another internal table for download.here except one field all the other fields are moving to the new internal table.When i debugged i could see the value in the internal table but its not getting moved to work area of that internal table (or the header line).
I could not see the value when i use itab[]-field in debugger mode instead when i use itab[1]-field i could see that field value.
please do suggest.

There is no need to move your data from one internal table to another with fixed structure. All you need to do is take each row's components skipping the column you don't want to download and concatenate this to some string. Then append to string table and download it. Sample:
"let's say your column is on 3rd place in the table
data l_row_string type string.
data lt_string_tab type table of string.
Loop at itab assigning <wa>.
do.
    check sy-index ne 3. "skip this column
    assign component sy-index of structure <wa> to <comp>.
    if sy-subrc = 0.
      CONCATENATE l_row_string <comp> INTO l_row_string SEPARATED BY cl_abap_char_utilities=>horizontal_tab.
    else.
      "no more component in row
      append l_row_string to lt_string_tab.
      clear l_row_string.
      exit.
    endif.
enddo.
endloop.
Now all you need is to downlaod your lt_string_tab as your text file (extension TXT).
Regards
Marcin

Similar Messages

How to merge work areas of same internal table

Hi Experts,
I have a requirement to merge two work areas into 3rd work area where all 3 belonging to same internal table like example below.
        person | activity | location |
wa1: 001     |    A       |              |
        person | activity | location |
wa2: 001     |              | xyz       |
after merging the value in wa3 should be as follows:
         person | activity | location |
wa3: 001      |    A       | xyz       |
I am looking for a ABAP command or FM to perform this task. Please help me on the same.
Many Thanks,
Vijay

Hello,
Try this:
Field-symbols: <lfs_wa1> type line of lit1,
                 <lfs_wa2> type line of lit2.
sort lit2 by field1 ascending.
loop at lit1 assigning <lfs_wa1>.
    read table lit2 with key field1 = <lfs_wa1>-field1 assigning <lfs_wa2> binary search.
    clear wa3.
    wa3-field1 = <lfs_wa2>-field1.
    wa3-field2 = <lfs_wa2>-field2.
    wa3-field3 = <lfs_wa2>-field3.
    append wa3 to lit3.
endloop.
Use sorted internal tables, field symbols and binary search for better performance. In case when different fields in both work areas may be populated for each row, you need to implement some check and move logic inside loop instead of simple value assignment. I assume that the key value is always there for both tables you want to merge.
best regards,
Marcin
Edited by: Marcin Makowski on Oct 20, 2010 7:16 PM
Edited by: Marcin Makowski on Oct 20, 2010 7:17 PM

ALV Report: How to pass the variable in Work area to the FM ? Please help !

I want to pass the field in the work area which contains the floating point numbers to FM 'FLTP_CHAR_CONVERSION_FROM_SI'. This the correct FM, I have tested.
If I specify the field with Tab name in FM , It says its not an internal table with header line.
Please help me, How should can I proceed further and pass the field to FM and get it back in work area.
And an other issue is I want to sum the particular field in the output.
Is there a way to do using 'PF-STATUS', if so how ? or what is the alternative for this ?
Please help me with my issues.
I'm new to ALV reports.
Thanks in Advance !

Hi,
For your FM issue, i think you are trying to pass the field in the FM as ITAB-field, while you should be taking the data in the work area first and then pass this work area in the FM as WA_ITAB-field.
I hope this will resolve your prob.
I mean loop at the table and take the values into work area, update the internal table with changed value. This way by the end of loop you will have all your fields converted.
Please explain a little more about your second doubt, it is unclear(to me atleast).
Edited by: DeepakNagar on Jul 28, 2011 6:08 PM

Difference betwen the internal tables

Hai friends,
           Pls give me the types of internal tables and their   differences .and its usage by example.
regrds,
Prashanth.

Internal tables
Definition
Data structure that exists only at program runtime.
An internal table is one of two structured data types in ABAP. It can contain any number of identically structured rows, with or without a header line.
The header line is similar to a structure and serves as the work area of the internal table. The data type of individual rows can be either elementary or structured.
Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.
Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects . A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object.
Internal Tables as Data Types
Internal tables and structures are the two structured data types in ABAP. The data type of an internal table is fully specified by its line type, key, and table type.
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.
Key
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.
If a table has a structured line type, its default key consists of all of its non-numerical columns that are not references or themselves internal tables. 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.
The user-defined key can contain any columns of the internal table that are not references or themselves internal tables. 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.
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 not. 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.
Generic Internal Tables
Unlike other local data types in programs, you do not have to specify the data type of an internal table fully. Instead, you can specify a generic construction, that is, the key or key and line type of an internal table data type may remain unspecified. You can use generic internal tables to specify the types of field symbols and the interface parameters of procedures. You cannot use them to declare data objects.
Internal Tables as Dynamic Data Objects
Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.
Choosing a Table Type
The table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most frequently executed.
Standard tables
This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.
Sorted tables
This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.
Hashed tables
This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.
Special Features of Standard Tables
Unlike sorted tables, hashed tables, and key access to internal tables, which were only introduced in Release 4.0, standard tables already existed several releases previously. Defining a line type, table type, and tables without a header line have only been possible since Release 3.0. For this reason, there are certain features of standard tables that still exist for compatibility reasons.
Standard Tables Before Release 3.0
Before Release 3.0, internal tables all had header lines and a flat-structured line type. There were no independent table types. You could only create a table object using the OCCURS addition in the DATA statement, followed by a declaration of a flat structure:
DATA: BEGIN OF .
The effect of the OCCURS addition is to construct a standard table with the data type
They can also be replaced by the following statements:
Standard Tables From Release 4.0
When you create a standard table, you can use the following forms of the TYPES and DATA statements. The addition INITIAL SIZE is also possible in all of the statements. The addition WITH HEADER LINE is possible in the DATA statement.
Standard Table Types
Generic Standard Table Type:
TYPES TYPE|LIKE TABLE OF TYPE|LIKE TABLE OF
                       WITH TYPE|LIKE TABLE OF TYPE|LIKE TABLE OF TYPE|LIKE TABLE OF
                       WITH .
Here, the LIKE addition refers to an existing table object in the same program. The TYPE addition can refer to an internal type in the program declared using the TYPES statement, or a table type in the ABAP Dictionary.
You must ensure that you only refer to tables that are fully typed. Referring to generic table types (ANY TABLE, INDEX TABLE) or not specifying the key fully is not allowed (for exceptions, refer to Special Features of Standard Tables).
The optional addition WITH HEADER line declares an extra data object with the same name and line type as the internal table. This data object is known as the header line of the internal table. You use it as a work area when working with the internal table (see Using the Header Line as a Work Area). 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 ([]). 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.
                  TYPES VECTOR TYPE SORTED TABLE OF I WITH UNIQUE KEY TABLE LINE.
DATA: ITAB TYPE VECTOR,
      JTAB LIKE ITAB WITH HEADER LINE.
MOVE ITAB TO JTAB.   <- Syntax error!
MOVE ITAB TO JTAB[].
The table object ITAB is created with reference to the table type VECTOR. The table object JTAB has the same data type as ITAB. JTAB also has a header line. In the first MOVE statement, JTAB addresses the header line. Since this has the data type I, and the table type of ITAB cannot be converted into an elementary type, the MOVE statement causes a syntax error. The second MOVE statement is correct, since both operands are table objects.
Declaring New Internal Tables
You can use the DATA statement to construct new internal tables as well as using the LIKE or TYPE addition to refer to existing types or objects. The table type that you construct does not exist in its own right; instead, it is only an attribute of the table object. You can refer to it using the LIKE addition, but not using TYPE. The syntax for constructing a table object in the DATA statement is similar to that for defining a table type in the TYPES statement.
DATA ]
As when you define a table type, the type constructor
of an internal table as follows:
UNIQUE KEY belong to the key as long as they are not internal tables or references, and do not contain internal tables or references. Key fields can be nested structures. The substructures are expanded component by component when you access the table using the key. The system follows the sequence of the key fields.
UNIQUE KEY TABLE LINE
If a table has an elementary line type (C, D, F, I, N, P, T, X), you can define the entire line as the key. If you try this for a table whose line type is itself a table, a syntax error occurs. If a table has a structured line type, it is possible to specify the entire line as the key. However, you should remember that this is often not suitable.
UNIQUE DEFAULT KEY
This declares the fields of the default key as the key fields. If the table has a structured line type, the default key contains all non-numeric columns of the internal table that are not and do not contain references or internal tables. If the 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.
Specifying a key is optional. If you do not specify a key, the system defines a table type with an arbitrary key. You can only use this to define the types of field symbols and the interface parameters of procedures. For exceptions, refer to Special Features of Standard Tables.
The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions:
·     You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically.
·     You must always specify the UNIQUE option when you create a hashed table.
Initial Memory Requirement
You can specify the initial amount of main memory assigned to an internal table object when you define the data type using the following addition:
INITIAL SIZE , the system calculates a new value so that n times the line width is around 12KB.
Examples
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
1. TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
The program defines a table type ITAB. It is a sorted table, with line type of the structure LINE and a unique key of the component COLUMN1.
2. TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY                      TABLE LINE.
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
TYPES: BEGIN OF DEEPLINE,
FIELD TYPE C,
TABLE1 TYPE VECTOR,
TABLE2 TYPE ITAB,
END OF DEEPLINE.
TYPES DEEPTABLE TYPE STANDARD TABLE OF DEEPLINE
WITH DEFAULT KEY.
The program defines a table type VECTOR with type hashed table, the elementary line type I and a unique key of the entire table line. The second table type is the same as in the previous example. The structure DEEPLINE contains the internal table as a component. The table type DEEPTABLE has the line type DEEPLINE. Therefore, the elements of this internal table are themselves internal tables. The key is the default key - in this case the column FIELD. The key is non-unique, since the table is a standard table.
Specifying the Type of Formal Parameters
Formal parameters can have any valid ABAP data type. You can specify the type of a formal parameter, either generically or fully, using the TYPE or LIKE addition. If you specify a generic type, the type of the formal parameter is either partially specified or not specified at all. Any attributes that are not specified are inherited from the corresponding actual parameter when the subroutine is called. If you specify the type fully, all of the technical attributes of the formal parameter are defined with the subroutine definition.
The following remarks about specifying the types of parameters also apply to the parameters of other procedures (function modules and methods).
If you have specified the type of the formal parameters, the system checks that the corresponding actual parameters are compatible when the subroutine is called. For internal subroutines, the system checks this in the syntax check. For external subroutines, the check cannot occur until runtime.
By specifying the type, you ensure that a subroutine always works with the correct data type. Generic formal parameters allow a large degree of freedom when you call subroutines, since you can pass data of any type. This restricts accordingly the options for processing data in the subroutine, since the operations must be valid for all data types. For example, assigning one data object to another may not even be possible for all data types. If you specify the types of subroutine parameters, you can perform a much wider range of operations, since only the data appropriate to those operations can be passed in the call. If you want to process structured data objects component by component in a subroutine, you must specify the type of the parameter.
Specifying Generic Types
The following types allow you more freedom when using actual parameters. The actual parameter need only have the selection of attributes possessed by the formal parameter. The formal parameter adopts its remaining unnamed attributes from the actual parameter.
     Check for actual parameters
No type specificationTYPE ANY     The subroutine accepts actual parameters of any type. The formal parameter inherits all of the technical attributes of the actual parameter.
TYPE C, N, P, or X     The subroutine only accepts actual parameters with the type C, N, P, or X. The formal parameter inherits the field length and DECIMALS specification (for type P) from the actual parameter.
TYPE TABLE     The system checks whether the actual parameter is a standard internal table. This is a shortened form of TYPE STANDARD TABLE (see below).
TYPE ANY TABLE     The system checks whether the actual parameter is an internal table. The formal parameter inherits all of the attributes (line type, table type, key) from the actual parameter.
TYPE INDEX TABLE     The system checks whether the actual parameter is an index table (standard or sorted table). The formal parameter inherits all of the attributes (line type, table type, key) from the actual parameter.
TYPE STANDARD TABLE     The system checks whether the actual parameter is a standard internal table. The formal parameter inherits all of the attributes (line type, key) from the actual parameter.
TYPE SORTED TABLE     The system checks whether the actual parameter is a sorted table. The formal parameter inherits all of the attributes (line type, key) from the actual parameter.
TYPE HASHED TABLE     The system checks whether the actual parameter is a hashed table. The formal parameter inherits all of the attributes (line type, key) from the actual parameter.
Note that formal parameters inherit the attributes of their corresponding actual parameters dynamically at runtime, and so they cannot be identified in the program code. For example, you cannot address an inherited table key statically in a subroutine, but you probably can dynamically.
TYPES: BEGIN OF LINE,
        COL1,
        COL2,
      END OF LINE.
DATA: WA TYPE LINE,
      ITAB TYPE HASHED TABLE OF LINE WITH UNIQUE KEY COL1,
      KEY(4) VALUE 'COL1'.
WA-COL1 = 'X'. INSERT WA INTO TABLE ITAB.
WA-COL1 = 'Y'. INSERT WA INTO TABLE ITAB.
PERFORM DEMO USING ITAB.
FORM DEMO USING P TYPE ANY TABLE.
READ TABLE P WITH TABLE KEY (KEY) = 'X' INTO WA.
ENDFORM.
The table key is addressed dynamically in the subroutine. However, the static address
READ TABLE P WITH TABLE KEY COL1 = 'X' INTO WA.
is syntactically incorrect, since the formal parameter P does not adopt the key of table ITAB until runtime.
Assigning Internal Tables :
Like other data objects, you can use internal tables as operands in a MOVE statement
MOVE , including the data in any nested internal tables. The original contents of the target table are overwritten.
If you are using internal tables with header lines, remember that the header line and the body of the table have the same name. If you want to address the body of the table in an assignment, you must place two brackets () after the table name.
DATA: BEGIN OF line,
        col1(1) TYPE c,
        col2(1) TYPE c,
      END OF line.
DATA: etab LIKE TABLE OF line WITH HEADER LINE,
      ftab LIKE TABLE OF line.
line-col1 = 'A'. line-col2 = 'B'.
APPEND line TO etab.
MOVE etab[] TO ftab.
LOOP AT ftab INTO line.
WRITE: / line-col1, line-col2.
ENDLOOP.
The output is:
A B
The example creates two standard tables ETAB and FTAB with the line type of the structure LINE. ETAB has a header line. After filling ETAB line by line using the APPEND statement, its entire contents are assigned to FTAB. Note the brackets in the statement.
DATA: ftab TYPE SORTED TABLE OF f
           WITH NON-UNIQUE KEY table_line,
      itab TYPE HASHED TABLE OF i
           WITH UNIQUE KEY table_line,
      fl   TYPE f.
DO 3 TIMES.
INSERT sy-index INTO TABLE itab.
ENDDO.
ftab = itab.
LOOP AT ftab INTO fl.
WRITE: / fl.
ENDLOOP.
The output is:
1.000000000000000E+00
2.000000000000000E+00
3.000000000000000E+00
FTAB is a sorted table with line type F and a non-unique key. ITAB is a hashed table with line type I and a unique key. The line types, and therefore the entire tables, are convertible. It is therefore possible to assign the contents of ITAB to FTAB. When you assign the unsorted table ITAB to the sorted table FTAB, the contents are automatically sorted by the key of FTAB.
In Unicode systems, the following conversion is not allowed:
DATA: BEGIN OF iline,
        num TYPE i,
      END OF iline,
      BEGIN OF fline,
        num TYPE f,
      END OF fline,
      itab LIKE TABLE OF iline,
      ftab LIKE TABLE OF fline.
DO 3 TIMES.
iline-num = sy-index.
APPEND iline-num TO itab.
ENDDO.
ftab = itab.
loop AT ftab INTO fline.
WRITE: / fline-num.
ENDLOOP.
In a non-Unicode system, the output may look something like this:
        6.03823403895813E-154
        6.03969074613219E-154
        6.04114745330626E-154
Here, the line types of the internal tables ITAB and FTAB are structures each with one component of type I or F. The line types are convertible, but not compatible. Therefore, when assigning ITAB to FTAB, the contents of Table ITAB are converted to type C fields and then written to FTAB. The system interprets the transferred data as type F fields, so that the results are meaningless. In Unicode systems, you are not allowed to convert numeric fields to fields of type C.
Initializing Internal Tables
Like all data objects, you can initialize internal tables with the
CLEAR .
statement. This statement restores an internal table to the state it was in immediately after you declared it. This means that the table contains no lines. However, the memory already occupied by the memory up until you cleared it remains allocated to the table.
If you are using internal tables with header lines, remember that the header line and the body of the table have the same name. If you want to address the body of the table in a comparison, you must place two brackets () after the table name.
CLEAR , LT, <).
If you are using internal tables with header lines, remember that the header line and the body of the table have the same name. If you want to address the body of the table in a comparison, you must place two brackets () after the table name.
The first criterion for comparing internal tables is the number of lines they contain. The more lines an internal table contains, the larger it is. If two internal tables contain the same number of lines, they are compared line by line, component by component. If components of the table lines are themselves internal tables, they are compared recursively. If you are testing internal tables for anything other than equality, the comparison stops when it reaches the first pair of components that are unequal, and returns the corresponding result.
DATA: BEGIN OF LINE,
COL1 TYPE I,
COL2 TYPE I,
END OF LINE.
DATA: ITAB LIKE TABLE OF LINE,
             JTAB LIKE TABLE OF LINE.
DO 3 TIMES.
LINE-COL1 = SY-INDEX.
LINE-COL2 = SY-INDEX ** 2.
APPEND LINE TO ITAB.
ENDDO.
MOVE ITAB TO JTAB.
LINE-COL1 = 10. LINE-COL2 = 20.
APPEND LINE TO ITAB.
IF ITAB GT JTAB.
WRITE / 'ITAB GT JTAB'.
ENDIF.
APPEND LINE TO JTAB.
IF ITAB EQ JTAB.
WRITE / 'ITAB EQ JTAB'.
ENDIF.
LINE-COL1 = 30. LINE-COL2 = 80.
APPEND LINE TO ITAB.
IF JTAB LE ITAB.
WRITE / 'JTAB LE ITAB'.
ENDIF.
LINE-COL1 = 50. LINE-COL2 = 60.
APPEND LINE TO JTAB.
IF ITAB NE JTAB.
WRITE / 'ITAB NE JTAB'.
ENDIF.
IF ITAB LT JTAB.
WRITE / 'ITAB LT JTAB'.
ENDIF.
The output is:
ITAB GT JTAB
ITAB EQ JTAB
JTAB LE ITAB
ITAB NE JTAB
ITAB LT JTAB
This example creates two standard tables, ITAB and JTAB. ITAB is filled with 3 lines and copied to JTAB. Then, another line is appended to ITAB and the first logical expression tests whether ITAB is greater than JTAB. After appending the same line to JTAB, the second logical expression tests whether both tables are equal. Then, another line is appended to ITAB and the third logical expressions tests whether JTAB is less than or equal to ITAB. Next, another line is appended to JTAB. Its contents are unequal to the contents of the last line of ITAB. The next logical expressions test whether ITAB is not equal to JTAB. The first table field whose contents are different in ITAB and JTAB is COL1 in the last line of the table: 30 in ITAB and 50 in JTAB. Therefore, in the last logical expression, ITAB is less than JTAB.
Sorting Internal Tables
You can sort a standard or hashed table in a program. To sort a table by its key, use the statement
SORT ASCENDING .
The statement sorts the internal table ASCENDING
             BY ASCENDING
                 ASCENDING .
The table is now sorted by the specified components : T for standard table, S for sorted table, and H for hashed table.
DATA: BEGIN OF LINE,
         COL1 TYPE I,
         COL2 TYPE I,
      END OF LINE.
DATA ITAB LIKE HASHED TABLE OF LINE WITH UNIQUE KEY COL1
                                    INITIAL SIZE 10.
DATA: LIN TYPE I,
      INI TYPE I,
      KND TYPE C.
DESCRIBE TABLE ITAB LINES LIN OCCURS INI KIND KND.
WRITE: / LIN, INI, KND.
DO 1000 TIMES.
LINE-COL1 = SY-INDEX.
LINE-COL2 = SY-INDEX ** 2.
INSERT LINE INTO TABLE ITAB.
ENDDO.
DESCRIBE TABLE ITAB LINES LIN OCCURS INI KIND KND.
WRITE: / LIN, INI, KND.
The output is:
         0         10 H
     1,000         10 H
Here, a hashed table ITAB is created and filled. The DESCRIBE TABLE statement is processed before and after the table is filled. The current number of lines changes, but the number of initial lines cannot change.
INSERT LINE INTO TABLE ITAB.
LINE-TEXT = 'Moller'.
CONVERT TEXT LINE-TEXT INTO SORTABLE CODE LINE-XTEXT.
INSERT LINE INTO TABLE ITAB.
LINE-TEXT = 'Miller'.
CONVERT TEXT LINE-TEXT INTO SORTABLE CODE LINE-XTEXT.
INSERT LINE INTO TABLE ITAB.
SORT ITAB.
PERFORM LOOP_AT_ITAB.
SORT ITAB BY XTEXT.
PERFORM LOOP_AT_ITAB.
SORT ITAB AS TEXT.
PERFORM LOOP_AT_ITAB.
FORM LOOP_AT_ITAB.
LOOP AT ITAB INTO LINE.
    WRITE / LINE-TEXT.
ENDLOOP.
SKIP.
ENDFORM.
This example demonstrates alphabetical sorting of character fields. The internal table ITAB contains a column with character fields and a column with corresponding binary codes that are alphabetically sortable. The binary codes are created with the CONVERT statement (see Converting to a Sortable Format). The table is sorted three times. First, it is sorted binarily by the TEXT field. Second, it is sorted binarily by the XTEXT field. Third, it is sorted alphabetically by the TEXT field. Since there is no directly corresponding case in English, we have taken the results from a German text environment:
Miller
Moller
Muller
Möller
Miller
Moller
Möller
Muller
Miller
Moller
Möller
Muller
After the first sorting, 'Möller' follows behind 'Muller' since the internal code for the letter 'ö' comes after the code for 'u'. The other two sorts are alphabetical
The binary sort by XTEXT has the same result as the alphabetical sorting by the field TEXT.
Regards,
Amit
Reward all helpful replies.

Confused with the internal table

Hello,
I am getting confused again by the usage of work space for an internal table.
Say for example I have a internal table itab that is defined as:
DATA:ITAB TYPE STANDARD TABLE OF Txxx.
Then I define a work space for the internal table.
DATA:WS_ITAB LIKE ITAB.
Now say for example, I would like to fill in some data to this internal table, can I do:
WS_ITAB-FIELD1 = 3.
APPEND WS_ITAB INTO ITAB INDEX 1.
where FIELD1 is a valid field in Txxx?
If not, how should I accomplish my goal? Thanks a lot!

Yes, you have the right idea. When working with work areas it is a good idea to define them like line of itab. This way, anytime itab changes, the wa will also be updated.
DATA: ITAB TYPE STANDARD TABLE OF Txxx.
<b>data: wa like line of itab</b>.
You can add a line to your internal table by filling the work area and appending to the internal table.
wa-fld1 = 'A'.
wa-fld2 = 'B'.
wa-fld3 = 'C'.
append wa to itab.
You can insert into a specific index by using INSERT.
Insert wa into itab index 1.
Regards,
Rich heilman

How to Pass the Internal table of a report to Smart Form

Hi Experts,
I have one report in which from selection screen i am getting the values from the users, and upon that values i am filling data in to the internal table.
Now i want to pass that internal table data to the smart form
and print that data in the smart form.
So could you pls give me some pseudo code or any steps to achieve it.
Thanks & Regards,
DS

Hi DS,
First of all you need to create a SF and then need to call the FM generated by the FM in your report.
In the SF in the form interface>tables tab>mention the name of the table and its type structure.
Pls note that a new structure has to be created as the same type of your internal table which holds the data.
And the import and export parameters as just the same as in a FM.
Now after you create and activate your SF a FM will be generated (wen u execute your SF you will be taken to this SE37 screen with the name of FM so no probs..)
You can call this FM in your report. Hope this helps.
Ex:
say itab has your final data, and you also want to export a variable var1 to the SF.
after your normal report operations end, call the FM and pass on these data.
say your FM name is FM1.
call function FM1
exporting
var1 = var1
tables
itab1 = itab1.
pls note that in the SF also i gave the same names, it is not mandatory to give the same names.
and as you want to print a table in the smartforms, you need to create a table in the smart forms and then display the data which is quite simple.
Hope this helps...
if you need any further explanations, pls revert...
Regards,
Narendra.
Reward points if helpful!!!

Need to delete Table Contents for the list of tables in the internal table.

Hi All,
I have req where in I have the list of table in an internal table and delete the contents of the tables which are in the internal table.
I need to delete the contents of the table using Native SQL statements. Else I can use function modules to delte the contents of table.
Thanks in advance. Appriciable if you can revert as soon as possible at all.
Thanks and Regards,
Raj.
Edited by: Thomas Zloch on Mar 11, 2010 1:56 PM

Hi,
You can try using truncate statement in native sql.
EXEC SQL.
TRUNCATE TABLE ABC.
ENDEXEC.

Cannot see the system folder(private work area) in the dependency manager

Hi
I am not able to see the 'system folder'(private work area) in the dependency manager tool.
I have captured the user schema in this folder, and want to see dependency information of objects in it.
Please Help.
Thanks

Hi Guru,
Please go through SAP note # 1333684 and configure accordingly.
Also, follow the note # 1042993, if problem is not getting resolved.
Thanks
Pavan

Red box Highlighting the entire work area of the Block diagram

I have a thin red box highlighting the entire work are of the block diagram...I've checked for breakpoints but dont see any. I run the code and after completion the entire work area turns black for a couple seconds and then the red box flashes and the continue button on the tool bar is hightlighted. Any assistance would be great
tks

This is indeed a breakpoint.
You should be able to clear it by selecting your breakpoint tool from the tools palette and clicking outside of your main code area.
When your breakpoint tool is going to set a breakpoint, the tool is filled in with black. When is is going to clear a breakpoint, it is not filled.
You can also search for breakpoints from the Edit menu Find function. Click the Select Object icon goto Others and select Breakpoint. This will find all your breakpoints. Sometimes they get set by mistake and you don't know it.
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

I just loaded some July pictures into my PC iCloud photos upload folder, but I do not see them with my iPad. Are they not shared because they are past the 30 day window, or is there a different issue?

I just loaded some July pictures into my PC iCloud photos upload folder, but I do not see them with my iPad. Are they not shared because they are past the 30 day window, or is there a different issue?

Generally I would not use Facebook for sharing any photos, it compresses the photos substantially, and when you have shadows and dark colours you get visible "bands" where there should be subtle gradients, ie at sunsets and sunrises.
It sounds like you are using two methods to upload to Facebook:
1. Sharing from within Aperture, which basically syncs Facebook with your Aperture album, so any changes made at either end gets synced, hence the deletions from Albums, although the original file should still be in your library, just removed rom the album. It is like a playlist in iTunes.
2. Exporting pics and uploading to Facebook from the browser.
I am not sure how method 1 gets compressed, but I know that uploading hi-res jpegs to Facebook using method 2 results in poor quality images.
I wouldn't even bother comparing option 1 or 2, and they will both be poor images once you view them on Facebook, as opposed to viewing uploaded images on proper image sharing / hosting sites.
Your problem is not with Aperture, it is using Facebook for showing your work.
If you export pics form Aperture at high res jpegs or TIFFs your images will be fine.
If you insist to use Facebook as your way to share your work, then your workflow should be this:
1. Right click images you want to share.
2. Select Export version.
3. Export as 100% size and ensure the export settings are set at 100% quality.
4. Upload this pic into Facebook.
This will get you the best image size and resolution on Facebook.
See how you go.

"Not using a pattern recognized by the GSA table invalidation mechanism" warning (many-to-many items relationships)

Hello.
I'm getting such warnings on server startup:
12:57:33,241 WARN [StoreRepository] Warning - table: store_user appears in item descriptors: store and user but not using a pattern recognized by the GSA table invalidation mechanism. Cached values from this table will not be updated when user's properties are modified. These properties for this table are: [storeUsers]
12:57:33,241 WARN [StoreRepository] Missing a src id property in item-descriptor user's table named store_user whose column-names are store_id
12:57:33,242 WARN [StoreRepository] Missing a dst id property in item-descriptor store's table named store_user whose column-names are user_id
12:57:33,242 WARN [StoreRepository] Missing a dst multi property in item-descriptor store's table named store_user whose column-name is store_id
12:57:33,242 WARN [StoreRepository] Warning - table: store_user appears in item descriptors: user and store but not using a pattern recognized by the GSA table invalidation mechanism. Cached values from this table will not be updated when store's properties are modified. These properties for this table are: [userStores]
12:57:33,243 WARN [StoreRepository] Missing a src id property in item-descriptor store's table named store_user whose column-names are user_id
12:57:33,243 WARN [StoreRepository] Missing a dst id property in item-descriptor user's table named store_user whose column-names are store_id
12:57:33,243 WARN [StoreRepository] Missing a dst multi property in item-descriptor user's table named store_user whose column-name is user_id
Here's repository definition file:
<item-descriptor name="user" id-space-name="user" display-name="User" display-property="name">
<table name="user_tbl" type="primary" id-column-name="user_id">
       <property name="id" column-name="user_id" data-type="string" display-name="Id">
            <attribute name="uiwritable" value="false" />
            <attribute name="propertySortPriority" value="-1" />
       </property>
       <property name="name" column-name="user_name" data-type="string" display-name="Name">
            <attribute name="propertySortPriority" value="-1" />
       </property>
</table>
<table name="store_user" type="multi" id-column-names="user_id" multi-column-name="store_id">
       <property name="userStores" display-name="User Stores" data-type="map" column-names="email" component-data-type="string">
            <attribute name="propertySortPriority" value="-1" />
            <attribute name="uiwritable" value="false" />
       </property>
</table>
</item-descriptor>
<item-descriptor name="store" id-space-name="store" display-name="Store" display-property="name">
<table name="store_tbl" type="primary" id-column-name="store_id">
       <property name="id" column-name="store_id" data-type="string" display-name="Id">
            <attribute name="uiwritable" value="false" />
            <attribute name="propertySortPriority" value="-1" />
       </property>
       <property name="name" column-name="store_name" data-type="string" display-name="Name">
            <attribute name="propertySortPriority" value="-1" />
       </property>
</table>
<table name="store_user" type="multi" id-column-names="store_id" multi-column-name="user_id">
       <property name="userStores" display-name="User Stores" data-type="map" column-names="email" component-data-type="string">
            <attribute name="propertySortPriority" value="-1" />
            <attribute name="uiwritable" value="false" />
       </property>
</table>
</item-descriptor>
I'll appreciate it, if someone tell me what's wrong with my definition.
Thank you in advance,
Jurii.

Hi Jurii,
You are right about ATG docs do not have info about M-M that can fit into your requirement. So we have to give it a try :-)
Please try with the below definition to see it it works.
user_tbl and store_tbl - no changes
store_user table has three columns - user_id, store_id and email
<item-descriptor name="user" id-space-name="user" display-name="User" display-property="name">
<table name="user_tbl" type="primary" id-column-name="user_id">
       <property name="id" column-name="user_id" data-type="string" display-name="Id">
            <attribute name="uiwritable" value="false" />
            <attribute name="propertySortPriority" value="-1" />
       </property>
       <property name="name" column-name="user_name" data-type="string" display-name="Name">
            <attribute name="propertySortPriority" value="-1" />
       </property>
</table>
<table name="store_user" type="multi" id-column-names="user_id">
       <property name="store" display-name="Stores" data-type="set" column-names="store_id" component-item-type="store"/>
    <property name="email" display-name="User Store Email" data-type="set" column-names="email" component-data-type="string"/>
</table>
</item-descriptor>
<item-descriptor name="store" id-space-name="store" display-name="Store" display-property="name">
<table name="store_tbl" type="primary" id-column-name="store_id">
       <property name="id" column-name="store_id" data-type="string" display-name="Id">
            <attribute name="uiwritable" value="false" />
            <attribute name="propertySortPriority" value="-1" />
       </property>
       <property name="name" column-name="store_name" data-type="string" display-name="Name">
            <attribute name="propertySortPriority" value="-1" />
       </property>
</table>
<table name="store_user" type="multi" id-column-names="store_id">
       <property name="user" display-name="Users" data-type="set" column-names="user_id" component-item-type="user"/>
    <property name="email" display-name="User Store Email" data-type="set" column-names="email" component-data-type="string"/>
</table>
</item-descriptor>
Thanks,
Gopinath Ramasamy

INSERT works for only last record of the Internal table ...??

I am trying to insert data from an internal table JTAB to a Databse Table
in CRM. The name of the databse table in CRM is CRMD_PARTNER
For this i first declared an internal table JTAB with same structure as that of
the databse table CRMD_PARTNER
DATA: BEGIN OF JTAB OCCURS 0,
     INCLUDE STRUCTURE CRMD_PARTNER,
      END OF JTAB.
Then I filled my JTAB with the required entries. For filling the JTAB i am
getting data from couple of other tables and filling the internal table JTAB
     loop at ktab.
here i am filling values in JTAB and then i say APPEND JTAB.
        endloop.
     Till here every thing works well and my internal table JTAB has all values that
I need to insert to the CRMD_PARTNER table. Also my JTAB has vales for all primary key fields.
Now I write a condition like below.
if not jtab[] inital.
MODIFY CRMD_PARTNER from TABLE JTAB.
COMMIT WORK.
endif.
Here comes the problem...once this code is executed and once program totally executes...
i always see that only last record in JTAB is being inserted to the databse table CRMD_PARTNER.
When i check in the debugger ..i see that the loop is being executed only once
and the SY-TABIX of JTAB is being always set to the length of JTAB and
that is why only last record is being inseretd to the table CRMD_PARTNER.
Now what should i do ..to insert all records of JTAB to CRMD_PARTNER table?
is there a way i can restet the SY-TABIX and make the modify statement work for all records of JTAB?
Finally i hardcoded the values in JTAB then i dont have any problem and all records of JTAB are being
inserted into the database table.
only if i am dynamically fetching the values into JTAB(by Putting in loop..endloop statements and
pushing values to JTAB and APPENDING JTAB ) i have a problem .
in this case also my JTAB is being correctly filled with values ..but when i try to
insert theses values to CRMD_PARTNER with MODIFY stmt ..only always last record is being inserted.
i tried with INSERT instead of MODIFY and i am getting runtime error.
kindly pease help.
Regards,
Jessica Sam

yes a@s i am really struggling from last 3 days.
I actually want to create a sales order in CRM and want to
assign ship to party for each line item in a sales order in CRM
for that i used the standard bapi BAPI_BUSPROCESSND_CREATEMULTI and i am able
to create an order successfully, but i see that the ship toparty
that i give at header is being copied to each line item.
but this is not what is expected.
So finally i tracked in which table the ship to party gets stored in each line item
and then tried to insert the records directly into databse. and it worked
but only if i am hardcoding..but not when i am dynamically fecthing the values into JTAB for insertion,
Can yoy help ..if you have any idea why insert/modify is processing only last record?
any help will be highly appreciated.
Regards,
Jessica Sam

Runtime error:ABAP program lines are longer than the internal table

Hi all,
Below is the code I have written,when Iam running it Iam getting
'ABAP program lines are longer than the internal table' runtime error.How can I resolve it.
REPORT ZTEST1 NO STANDARD PAGE HEADING LINE-SIZE 255.
TABLES:MARC,CDHDR,CDPOS.
TYPE-POOLS:SLIS.
DATA:HEADER TYPE SLIS_T_FIELDCAT_ALV,
     WA TYPE SLIS_FIELDCAT_ALV,
     LAYOUT TYPE SLIS_LAYOUT_ALV.
TYPES:BEGIN OF MARC_TY,
        MATNR LIKE MARC-MATNR,
        WERKS LIKE MARC-WERKS,
        EKGRP LIKE MARC-EKGRP,
        MINBE LIKE MARC-MINBE,
        EISBE LIKE MARC-EISBE,
        MABST LIKE MARC-MABST,
       END OF MARC_TY.
TYPES:BEGIN OF MATNR1_TY,
        MATNR1 LIKE CDHDR-OBJECTID,
      END OF MATNR1_TY.
TYPES:BEGIN OF CDHDR_TY,
         OBJECTCLAS LIKE CDHDR-OBJECTCLAS,
         OBJECTID   LIKE CDHDR-OBJECTID,
         CHANGENR   LIKE CDHDR-CHANGENR,
         USERNAME   LIKE CDHDR-USERNAME,
         UDATE      LIKE CDHDR-UDATE,
        END OF CDHDR_TY.
TYPES:BEGIN OF CDPOS_TY,
         OBJECTCLAS LIKE CDPOS-OBJECTCLAS,
         OBJECTID   LIKE CDPOS-OBJECTID,
         CHANGENR   LIKE CDPOS-CHANGENR,
         TABNAME    LIKE CDPOS-TABNAME,
         FNAME      LIKE CDPOS-FNAME,
         CHNGIND    LIKE CDPOS-CHNGIND,
         VALUE_NEW LIKE CDPOS-VALUE_NEW,
         VALUE_OLD LIKE CDPOS-VALUE_OLD,
        END OF CDPOS_TY.
**************TABLE TYPES********************************************
TYPES: MARC_TAB   TYPE TABLE OF MARC_TY,
       MATNR1_TAB TYPE TABLE OF MATNR1_TY,
       CDHDR_TAB TYPE TABLE OF CDHDR_TY,
       CDPOS_TAB TYPE TABLE OF CDPOS_TY.
*******************INTERNAL TABLES************************************
DATA:MARC_ITAB   TYPE MARC_TAB,
     MATNR1_ITAB TYPE MATNR1_TAB,
     CDHDR_ITAB TYPE CDHDR_TAB,
     CDPOS_ITAB TYPE CDPOS_TAB.
****************WORK AREAS********************************************
DATA:MARC_WA   TYPE MARC_TY,
     MATNR1_WA TYPE MATNR1_TY,
     CDHDR_WA TYPE CDHDR_TY,
     CDPOS_WA TYPE CDPOS_TY.
*******************SELECTION-SCREEN***********************************
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETERS:PLANT LIKE MARC-WERKS.
SELECT-OPTIONS:MATERIAL FOR MARC-MATNR.
SELECT-OPTIONS:DATE FOR CDHDR-UDATE.
SELECTION-SCREEN END OF BLOCK B1.
START-OF-SELECTION.
SELECT MATNR
        WERKS
        EKGRP
        MINBE
        EISBE
        MABST
        FROM MARC INTO TABLE MARC_ITAB
        WHERE MATNR IN MATERIAL
        AND WERKS = PLANT.
CHECK MARC_ITAB[] IS NOT INITIAL.
LOOP AT MARC_ITAB INTO MARC_WA.
   MATNR1_WA-MATNR1 = MARC_WA-MATNR.
   APPEND MATNR1_WA TO MATNR1_ITAB.
   CLEAR MATNR1_WA.
ENDLOOP.
CHECK MATNR1_ITAB[] IS NOT INITIAL.
SELECT OBJECTCLAS
        OBJECTID
        CHANGENR
        USERNAME
        UDATE
        FROM CDHDR INTO TABLE CDHDR_ITAB
        FOR ALL ENTRIES IN MATNR1_ITAB
        WHERE OBJECTCLAS = 'MATERIAL'
        AND OBJECTID = MATNR1_ITAB-MATNR1
        AND UDATE IN DATE.
CHECK CDHDR_ITAB[] IS NOT INITIAL.
SORT CDHDR_ITAB[] DESCENDING BY OBJECTID CHANGENR.
DELETE ADJACENT DUPLICATES FROM CDHDR_ITAB[] COMPARING OBJECTID.
SELECT OBJECTCLAS
       OBJECTID
       CHANGENR
       TABNAME
       FNAME
       CHNGIND
       VALUE_NEW
       VALUE_OLD
       FROM CDPOS INTO CORRESPONDING FIELDS OF TABLE CDPOS_ITAB
       FOR ALL ENTRIES IN CDHDR_ITAB
       WHERE OBJECTCLAS = CDHDR_ITAB-OBJECTCLAS
       AND OBJECTID = CDHDR_ITAB-OBJECTID
       AND CHANGENR = CDHDR_ITAB-CHANGENR
       AND TABNAME = 'MARC'
       AND FNAME    IN ('MINBE','EISBE','MABST','LVORM')
       AND CHNGIND = 'U'.
CHECK CDPOS_ITAB[] IS NOT INITIAL.
*LOOP AT CDPOS_ITAB INTO CDPOS_WA.
WRITE: / CDPOS_WA-OBJECTCLAS,
         CDPOS_WA-OBJECTID,
         CDPOS_WA-CHANGENR,
         CDPOS_WA-TABNAME,
         CDPOS_WA-FNAME,
         CDPOS_WA-CHNGIND,
         CDPOS_WA-VALUE_NEW,
         CDPOS_WA-VALUE_OLD.
*ENDLOOP.
WA-SELTEXT_L = 'OBJECTCLAS'.
WA-COL_POS   = '1'.
WA-FIELDNAME = 'OBJECTCLAS'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '15'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'OBJECTID'.
WA-COL_POS   = '2'.
WA-FIELDNAME = 'OBJECTID'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '20'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'CHANGENR'.
WA-COL_POS   = '3'.
WA-FIELDNAME = 'CHANGENR'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '8'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'TABNAME'.
WA-COL_POS   = '4'.
WA-FIELDNAME = 'TABNAME'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '5'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'FNAME'.
WA-COL_POS   = '5'.
WA-FIELDNAME = 'FNAME'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '7'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'CHANGING'.
WA-COL_POS   = '6'.
WA-FIELDNAME = 'CHANGING'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '1'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'VALUE_NEW'.
WA-COL_POS   = '7'.
WA-FIELDNAME = 'VALUE_NEW'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '5'.
APPEND WA TO HEADER.
CLEAR WA.
WA-SELTEXT_L = 'VALUE_OLD'.
WA-COL_POS   = '8'.
WA-FIELDNAME = 'VALUE_OLD'.
WA-TABNAME   = 'CDPOS_ITAB'.
WA-OUTPUTLEN = '5'.
APPEND WA TO HEADER.
CLEAR WA.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
EXPORTING
    I_PROGRAM_NAME               = SY-REPID
    I_INTERNAL_TABNAME           = 'CDPOS_ITAB'
    I_CLIENT_NEVER_DISPLAY       = 'X'
    I_INCLNAME                   = SY-REPID
CHANGING
    CT_FIELDCAT                  = HEADER[]
EXCEPTIONS
IF SY-SUBRC <> 0.
ENDIF.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
    I_CALLBACK_PROGRAM                = SY-REPID
    IT_FIELDCAT                       = HEADER[]
TABLES
    T_OUTTAB                          = CDPOS_ITAB[]
IF SY-SUBRC <> 0.
ENDIF.

Your select querry on MARC is not matching with MARC_TY.
The field in the MARC table and MARC_TY should be same.
and also, when you are making select querry on CDPOS table
with all entries.
When ever you are using all entries select statement, you should check whether the internal table is having value.
you should check
if CDPOS_IT[] is not initial.
SELECT OBJECTCLAS
OBJECTID
CHANGENR
TABNAME
FNAME
CHNGIND
VALUE_NEW
VALUE_OLD
FROM CDPOS INTO CORRESPONDING FIELDS OF TABLE CDPOS_ITAB
FOR ALL ENTRIES IN CDHDR_ITAB
WHERE OBJECTCLAS = CDHDR_ITAB-OBJECTCLAS
AND OBJECTID = CDHDR_ITAB-OBJECTID
AND CHANGENR = CDHDR_ITAB-CHANGENR
AND TABNAME = 'MARC'
AND FNAME IN ('MINBE','EISBE','MABST','LVORM')
AND CHNGIND = 'U'.
endif.
Regards
Madhan D

Derived table 'tablename' is not updatable because a column of the derived table is derived or constant.

Hi Guys,
I have a With CTE table expression ,this cte gets the value from startdate and enddate
I need to insert this startdate and enddate into a table ,while inserting into table,i got the below error,
Derived table 'Datematrix' is not updatable because a column of the derived table is derived or constant.
below is the query i used,
declare @StartDate date='01/01/2013'
declare @EndDate date='12/31/2013'
;WITH Datematrix(AllocationDate)
As
SELECT @StartDate AS AllocationDate
UNION ALL
SELECT DATEADD(D,1,AllocationDate) AS AllocationDate
FROM Datematrix WHERE AllocationDate<@EndDate
Insert into Datematrix(AllocationDate)
select * from Datematrix
any guys update this solution.
Thanks
Bhupesh.R

;WITH Datematrix(AllocationDate)
As
SELECT @StartDate AS AllocationDate
UNION ALL
SELECT DATEADD(D,1,AllocationDate) AS AllocationDate
FROM Datematrix WHERE AllocationDate<@EndDate
Insert into Datematrix(AllocationDate)
select * from Datematrix
Hello,
Your CTE bases only on fix value = @StartDate , not on a table/view; here do you want to insert data to? This don't work in any way.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Summing the internal table values

Hi Experts,
I have requirement in report to add the values in the internal table based on document no.
for example
Document no         date                         Amount                Exchange Rate
190000012         05.04.2009                     100                                1
190000012         05.04.2009                     200                                1
190000012         05.04.2009                     300                                1
190000013         05.04.2009                     100                                1
190000013         05.04.2009                     200                                1
190000014         05.04.2009                     100                                1
If i use Collect or On change statements , the exchange rate is also adding
Document no         date                         Amount                Exchange Rate
190000012         05.04.2009                     600                                3
190000013         05.04.2009                     300                                2
190000014         05.04.2009                     100                                1
But i want to add only the amount field not the exchange rate .Please suggest me the best solutions.
I want to display as
Document no         date                         Amount                Exchange Rate
190000012         05.04.2009                     600                                1
190000013         05.04.2009                     300                                1
190000014         05.04.2009                     100                                1
Thanks in advance
satish

hi,
check this
Sort itab by documentno.
Loop at itab1.
on change of itab1-dcno.
clear total.
move itab1-docno to itab2-docno.
itab2-total = itab-amont.
move itab1-total to itab2-total.
move itab1-date to itab2-date.
move itab1-rate to itab2-rate.
flag = ' '.
append itab2.
clear itab2.
else.
itab2-total = itab2-total + itab-amont.
endon
Endloop.
it will work for adjest append statement according to the out put .
~linganna

Value not moved to work are of the internal table

Similar Messages

Maybe you are looking for