Internal table aggregation

HI SDN,
I am bringing the data into internal table like this
TYPES: BEGIN OF ty_EKAB,
          i_CONTRACT LIKE /BIC/AZPUR_OAP00-CONTRACT,
          i_CONT_ITEM LIKE /BIC/AZPUR_OAP00-CONT_ITEM,
          i_ZNET_VAL LIKE /BIC/AZPUR_OAP00-/BIC/ZNET_VAL,
          i_ZORDR_QTY LIKE /BIC/AZPUR_OAP00-/BIC/ZORDR_QTY,
          END OF ty_EKAB.
          DATA: IT_EKAB TYPE SORTED TABLE OF ty_EKAB
                WITH NON-UNIQUE KEY i_CONTRACT i_CONT_ITEM ,
                WA_EKAB TYPE ty_EKAB.
          SELECT CONTRACT CONT_ITEM /BIC/ZNET_VAL /BIC/ZORDR_QTY INTO
          TABLE IT_EKAB FROM /BIC/AZPUR_OAP00.
and Data looks like this
4600000000 00040              54,635.00                   1.000
4600000000 00040              40,365.00                   1.000
4600000002 00010                   0.00                   0.000
4600000002 00010              91,200.00                   1.000
4600000002 00010              31,554.00                   1.000
My question : Is there any statement on Internal table which aggregate the values with same CONTRACT CONT_ITEM .
Thanks

some ways to perform
- Loop at the internal table and use [COLLECT|https://www.sdn.sap.com/irj/scn/advancedsearch?query=collect&cat=sdn_all] statement into another table of same structure (also look help.sap.com at [Appending Summarized Lines|http://help.sap.com/erp2005_ehp_03/helpdata/EN/fc/eb36d5358411d1829f0000e829fbfe/frameset.htm])
- Sort the internal table and APPEND to another table using [SUM in a AT END OF|https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_all&query=sumATEND+OF&adv=false&sortby=cm_rnd_rankvalue] block (also look help.sap.com at [Processing Table Entries in Loops|http://help.sap.com/erp2005_ehp_03/helpdata/EN/fc/eb381a358411d1829f0000e829fbfe/frameset.htm])
- use a GROUP BY clause in your [SELECT INTO TABLE|https://www.sdn.sap.com/irj/scn/advancedsearch?cat=sdn_all&query=selectINTOTABLEGROUPBY&adv=false&sortby=cm_rnd_rankvalue] (also look help.sap.com at [Reading Data|http://help.sap.com/erp2005_ehp_03/helpdata/EN/fc/eb3983358411d1829f0000e829fbfe/frameset.htm])
Regards

Similar Messages

Using aggregation in ABAP code for internal table

I have written following code to get cumulative amount on a date but i have to hit database for each record.
Can't I use some function similar to SUM for doing the same thing on internal table??It would increase my performance.
code is:
    SELECT SUM( DEB_CRE_LC ) FROM /BIC/AZFIAR_O500
     INTO LV_BALMONTH   WHERE   DEBITOR = LV_DEBITOR AND
    CALMONTH GE LV_STARTMONTH AND CALMONTH LE LV_LASTCALMON.
I want to put ZFIAR data to internal table and read and do SUM thing..is it possible?? withotut usiong loop.
regards,
rakesh

Hi Rajesh,
types : begin of ty_tab,
            date type dats,
            DEB_CRE_LC   type .....     " delare type & is the filed need to summerized
            end of ty_tab,
data: itab type standard table of ty_tab.
SELECT date
              SUM( DEB_CRE_LC ) as DEB_CRE_LC FROM /BIC/AZFIAR_O500
              INTO corresponding fields of itab
              where CALMONTH GE LV_STARTMONTH AND CALMONTH LE LV_LASTCALMON
              group by date.   " date is the field available in your ODS/transparent table
simulate the above code in your program...
Hope this will work..

Join 2 internal tables

Hello,
i have to join the whole content of a table with the content of a aggregated table. i "moved" the content of the 2 dictionary tables into 2 internal tables and i want to join these 2 internal tables now.
first of all, is it generally possible to join 2 internal tables, for example with a read or loop statement?!
at second, i know how i would solve the problem in oracle 10g, but it looks like that open-sql supports not the same features like orcale. knows anyone of you how i can rebuild the following oracle statement in abap.
select a.id, a.col1, b.col2
from table_a as a, (select id, sum(col2) as col2 from table_c group by id) as b where a.id = b.id order by 1
thx

Hello Markus
ABAP open sql ahould be something like
select aid acol1 sum( b~col2 )
from table_a as a
join table_c as b
on aid = bid
group by b~id
not sure abour the order by; don't know oracle syntax exactly.
Try!
Regards,
Clemens

Internal Table and Structures

Hi,
I am a beginer. I know how to create a structure and how to create an internal table using ABAP/4. My problem is, i don't understand where to use internal table and structure, also i find myself very confused about the explicit work areas.
Plese someone show me a program by explaining all of this clearly.

Hi
Internal tables are the core of ABAP. They are like soul of a body. For any program we use
internal tables extensively. We can use Internal tables like normal data base tables only, but the
basic difference is the memory allocated for internal tables is temporary. Once the program is
closed the memory allocated for internal tables will also be out of memory.
But while using the internal tables, there are many performance issues to be considered. i.e which
type of internal table to be used for the program..like standard internal table, hashed internal
table or sorted internal table etc..
Internal tables
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.
Creating Internal Tables
Like other elements in the ABAP type concept, you can declare internal tables as abstract data
types in programs or in the ABAP Dictionary, and then use them to define data objects.
Alternatively, you can define them directly as data objects. When you create an internal table as a
data object, you should ensure that only the administration entry which belongs to an internal
table is declared statically. The minimum size of an internal table is 256 bytes. This is important if an
internal table occurs as a component of an aggregated data object, since even empty internal
tables within tables can lead to high memory usage. (In the next functional release, the size of the
table header for an initial table will be reduced to 8 bytes). Unlike all other ABAP data objects, you
do not have to specify the memory required for an internal table. Table rows are added to and
deleted from the table dynamically at runtime by the various statements for adding and deleting
records.
You can create internal tables in different types.
You can create standard internal table and then make it sort in side the program.
The same way you can change to hashed internal tables also.
There will be some performance issues with regard to standard internal tables/ hashed internal
tables/ sorted internal tables.
Internal table types
This section describes how to define internal tables locally in a program. You can also define internal tables globally as data types in the
ABAP Dictionary.
Like all local data types in programs , you define internal tables using the TYPES statement. If you do not refer to an existing table type
using the TYPE or LIKE addition, you can use the TYPES statement to construct a new local internal table in your program.
TYPES <t> TYPE|LIKE <tabkind> OF <linetype> [WITH <key>]
[INITIAL SIZE <n>].
After TYPE or LIKE, there is no reference to an existing data type. Instead, the type constructor occurs:
<tabkind> OF <linetype> [WITH <key>]
The type constructor defines the table type <tabkind>, the line type <linetype>, and the key <key> of the internal table <t>.
You can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.
Table type
You can specify the table type <tabkind> as follows:
Generic table types
INDEX TABLE
For creating a generic table type with index access.
ANY TABLE
For creating a fully-generic table type.
Data types defined using generic types can currently only be used for field symbols and for interface parameters in procedures . The generic
type INDEX TABLE includes standard tables and sorted tables. These are the two table types for which index access is allowed. You cannot
pass hashed tables to field symbols or interface parameters defined in this way. The generic type ANY TABLE can represent any table. You
can pass tables of all three types to field symbols and interface parameters defined in this way. However, these field symbols and
parameters will then only allow operations that are possible for all tables, that is, index operations are not allowed.
Fully-Specified Table Types
STANDARD TABLE or TABLE
For creating standard tables.
SORTED TABLE
For creating sorted tables.
HASHED TABLE
For creating hashed tables.
Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for
standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
Line type
For the line type <linetype>, you can specify:
Any data type if you are using the TYPE addition. This can be a predefined ABAP type, a local type in the program, or a data type from the
ABAP Dictionary. If you specify any of the generic elementary types C, N, P, or X, any attributes that you fail to specify (field length, number
of decimal places) are automatically filled with the default values. You cannot specify any other generic types.
Any data object recognized within the program at that point if you are using the LIKE addition. The line type adopts the fully-specified data
type of the data object to which you refer. Except for within classes, you can still use the LIKE addition to refer to database tables and
structures in the ABAP Dictionary (for compatibility reasons).
All of the lines in the internal table have the fully-specified technical attributes of the specified data type.
Key
You can specify the key <key> of an internal table as follows:
[UNIQUE|NON-UNIQUE] KEY <col1> ... <col n>
In tables with a structured line type, all of the components <coli> 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|NON-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|NON-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 <n>
This size does not belong to the data type of the internal table, and does not affect the type check. You can use the above addition to
reserve memory space for <n> table lines when you declare the table object.
When this initial area is full, the system makes twice as much extra space available up to a limit of 8KB. Further memory areas of 12KB each
are then allocated.
You can usually leave it to the system to work out the initial memory requirement. The first time you fill the table, little memory is used. The
space occupied, depending on the line width, is 16 <= <n> <= 100.
It only makes sense to specify a concrete value of <n> if you can specify a precise number of table entries when you create the table and
need to allocate exactly that amount of memory (exception: Appending table lines to ranked lists). This can be particularly important for
deep-structured internal tables where the inner table only has a few entries (less than 5, for example).
To avoid excessive requests for memory, large values of <n> are treated as follows: The largest possible value of <n> is 8KB divided by the
length of the line. If you specify a larger value of <n>, 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.
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.
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.
Internal table objects
Internal tables are dynamic variable data objects. Like all variables, you declare them using the DATA statement. You can also declare static
internal tables in procedures using the STATICS statement, and static internal tables in classes using the CLASS-DATA statement. This
description is restricted to the DATA statement. However, it applies equally to the STATICS and CLASS-DATA statements.
Reference to Declared Internal Table Types
Like all other data objects, you can declare internal table objects using the LIKE or TYPE addition of the DATA statement.
DATA <itab> TYPE <type>|LIKE <obj> [WITH HEADER LINE].
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 (<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.
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 <itab> TYPE|LIKE <tabkind> OF <linetype> WITH <key>
[INITIAL SIZE <n>]
[WITH HEADER LINE].
As when you define a table type , the type constructor
<tabkind> OF <linetype> WITH <key>
defines the table type <tabkind>, the line type <linekind>, and the key <key> of the internal table <itab>. Since the technical attributes of
data objects are always fully specified, the table must be fully specified in the DATA statement. You cannot create generic table types (ANY
TABLE, INDEX TABLE), only fully-typed tables (STANDARD TABLE, SORTED TABLE, HASHED TABLE). You must also specify the key and whether
it is to be unique (for exceptions, refer to Special Features of Standard Tables).
As in the TYPES statement, you can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.
You can create an internal table with a header line using the WITH HEADER LINE addition. The header line is created under the same
conditions as apply when you refer to an existing table type.
DATA ITAB TYPE HASHED TABLE OF SPFLI
WITH UNIQUE KEY CARRID CONNID.
The table object ITAB has the type hashed table, a line type corresponding to the flat structure SPFLI from the ABAP Dictionary, and a
unique key with the key fields CARRID and CONNID. The internal table ITAB can be regarded as an internal template for the database table
SPFLI. It is therefore particularly suitable for working with data from this database table as long as you only access it using the key.

Structure & Internal Tables

What is the difference between Structure & Internal Tables,
Regards.

Hi chidambar,
to say simply the internal table can have data within it but a structure is that which can be used by an internal table to define its columns ,it cannot have data on its own
coming to thoery this may help you,but dont confuse more with the theory
Structures
A structure is a sequence of any elementary types, reference types, or complex data types.
You use structures in ABAP programs to group work areas that logically belong together. Since the elements of a structure can have any data type, structures can have a large range of uses. For example, you can use a structure with elementary data types to display lines from a database table within a program. You can also use structures containing aggregated elements to include all of the attributes of a screen or control in a single data object.
The following terms are important when we talk about structures:
Nested and non-nested structures
Flat and deep structures
A nested structure is a structure that contains one or more other structures as components. Flat structures contain only elementary data types with a fixed length (no internal tables, reference types, or strings). The term deep structure can apply regardless of whether the structure is nested or not. Nested structures are flat so long as none of the above types is contained in any nesting level.
Any structure that contains at least one internal table, reference type, or string as a component (regardless of nesting) is a deep structure. Accordingly, internal tables, references, and strings are also known as deep data types. The technical difference between deep structures and all others is as follows. When you create a deep structure, the system creates a pointer in memory that points to the real field contents or other administrative information. When you create a flat data type, the actual field contents are stored with the type in memory. Since the field contents are not stored with the field descriptions in the case of deep structures, assignments, offset and length specifications and other operations are handled differently from flat structures.
Internal Tables
Internal tables consists of a series of lines that all have the same data type. Internal tables are characterized by:
The line type, which can be any elementary type, reference type, or complex data type.
The key identifies table rows. It is made up of the elementary fields in the line. The key can be unique or non-unique.
The access method determines how ABAP will access individual table entries. There are three access types, namely unsorted tables, sorted index tables and hash tables. For index tables, the system maintains a linear index, so you can access the table either by specifying the index or the key.
Hashed tables have no linear index. You can only access hashed tables by specifying the key. The system has its own hash algorithm for managing the table.
You should use internal tables whenever you need to use structured data within a program. One imprint use is to store data from the database within a program.
plz reward if helpful,
plz get back to me for further queries.
thanks and regards,
srikanth tulasi.

Sy-tabix for internal table in smartform

Hi friends,
How to capture the sy-tabix value for the entries in an internal table which has been looped into the loop of table node of a smartform?? I need to print something immedaitely after the end of the table
For every record the value of sy-tabix is showing 1 !!
Advance Thanks
Aadarsh

Hi Aadarsh,
Give ur sy-tabix at the end of the loop.
loop at itab.
//table node populations.
endloop.
give a seperate loop for this.
loop at itab.
sy-tabix.
endloop
get the total no and print it after the table.
If u r using do loop then give sy-index.
Hope tihs helps u,
Regards,
Nagarajan.
Message was edited by: Nagarajan Kumarappan

Regarding Exporting and Importing internal table

Hello Experts,
I have two programs:
1) Main program: It create batch jobs through open_job,submit and close job.Giving sub program as SUBMIT.
I am using Export IT to memory id 'MID' to export internal table data to sap memory in the subprogram.
The data will be processed in the subprogram and exporting data to sap memory.I need this data in the main program(And using import to get the data,but it is not working).
Importing IT1 from memory id 'MID' to import the table data in the main program after completing the job(SUBMIT SUBPROGRAM AND RETURN).
Importing is not getting data to internal table.
Can you please suggest something to solve this issue.
Thank you.
Regards,
Anand.

Hi,
This is the code i am using.
DO g_f_packets TIMES.
* Start Immediately
       IF NOT p_imm IS INITIAL .
         g_flg_start = 'X'.
       ENDIF.
       g_f_jobname = 'KZDO_INHERIT'.
       g_f_jobno = g_f_jobno + '001'.
       CONCATENATE g_f_jobname g_f_strtdate g_f_jobno INTO g_f_jobname
                                              SEPARATED BY '_'.
       CONDENSE g_f_jobname NO-GAPS.
       p_psize1 = p_psize1 + p_psize.
       p_psize2 = p_psize1 - p_psize + 1.
       IF p_psize2 IS INITIAL.
         p_psize2 = 1.
       ENDIF.
       g_f_spname = 'MID'.
       g_f_spid = g_f_spid + '001'.
       CONDENSE g_f_spid NO-GAPS.
       CONCATENATE g_f_spname g_f_spid INTO g_f_spname.
       CONDENSE g_f_spname NO-GAPS.
* ... (1) Job creating...
       CALL FUNCTION 'JOB_OPEN'
         EXPORTING
           jobname          = g_f_jobname
         IMPORTING
           jobcount         = g_f_jobcount
         EXCEPTIONS
           cant_create_job = 1
           invalid_job_data = 2
           jobname_missing = 3
           OTHERS           = 4.
       IF sy-subrc <> 0.
         MESSAGE e469(9j) WITH g_f_jobname.
       ENDIF.
* (2)Report start under job name
       SUBMIT (g_c_prog_kzdo)
              WITH p_lgreg EQ p_lgreg
              WITH s_grvsy IN s_grvsy
              WITH s_prvsy IN s_prvsy
              WITH s_prdat IN s_prdat
              WITH s_datab IN s_datab
              WITH p1      EQ p1
              WITH p3      EQ p3
              WITH p4      EQ p4
              WITH p_mailid EQ g_f_mailid
              WITH p_psize EQ p_psize
              WITH p_psize1 EQ p_psize1
              WITH p_psize2 EQ p_psize2
              WITH spid     EQ g_f_spid
              TO SAP-SPOOL WITHOUT SPOOL DYNPRO
              VIA JOB g_f_jobname NUMBER g_f_jobcount AND RETURN.
*(3)Job closed when starts Immediately
       IF NOT p_imm IS INITIAL.
         IF sy-index LE g_f_nojob.
           CALL FUNCTION 'JOB_CLOSE'
             EXPORTING
               jobcount             = g_f_jobcount
               jobname              = g_f_jobname
               strtimmed            = g_flg_start
             EXCEPTIONS
               cant_start_immediate = 1
               invalid_startdate    = 2
               jobname_missing      = 3
               job_close_failed     = 4
               job_nosteps          = 5
               job_notex            = 6
               lock_failed          = 7
               OTHERS               = 8.
           gs_jobsts-jobcount = g_f_jobcount.
           gs_jobsts-jobname = g_f_jobname.
           gs_jobsts-spname   = g_f_spname.
           APPEND gs_jobsts to gt_jobsts.
         ELSEIF sy-index GT g_f_nojob.
           CLEAR g_f_flg.
           DO.                         " Wiating untill any job completion
             LOOP AT gt_jobsts into gs_jobsts.
               CLEAR g_f_status.
               CALL FUNCTION 'BP_JOB_STATUS_GET'
                 EXPORTING
                   JOBCOUNT                         = gs_jobsts-jobcount
                   JOBNAME                          = gs_jobsts-jobname
                IMPORTING
                   STATUS                           = g_f_status
*            HAS_CHILD                        =
*          EXCEPTIONS
*            JOB_DOESNT_EXIST                 = 1
*            UNKNOWN_ERROR                    = 2
*            PARENT_CHILD_INCONSISTENCY       = 3
*            OTHERS                           = 4
               g_f_mid = gs_jobsts-spname.
               IF g_f_status = 'F'.
                 IMPORT gt_final FROM MEMORY ID g_f_mid .
                 FREE MEMORY ID gs_jobsts-spname.
                 APPEND LINES OF gt_final to gt_final1.
                 REFRESH gt_prlist.
                 CALL FUNCTION 'JOB_CLOSE'
                   EXPORTING
                     jobcount             = g_f_jobcount
                     jobname              = g_f_jobname
                     strtimmed            = g_flg_start
                   EXCEPTIONS
                     cant_start_immediate = 1
                     invalid_startdate    = 2
                     jobname_missing      = 3
                     job_close_failed     = 4
                     job_nosteps          = 5
                     job_notex            = 6
                     lock_failed          = 7
                     OTHERS               = 8.
                 IF sy-subrc = 0.
                   g_f_flg = 'X'.
                   gs_jobsts1-jobcount = g_f_jobcount.
                   gs_jobsts1-jobname = g_f_jobname.
                   gs_jobsts1-spname   = g_f_spname.
                   APPEND gs_jobsts1 TO gt_jobsts.
                   DELETE TABLE gt_jobsts FROM gs_jobsts.
                   EXIT.
                 ENDIF.
               ENDIF.
             ENDLOOP.
             IF g_f_flg = 'X'.
               CLEAR g_f_flg.
               EXIT.
             ENDIF.
           ENDDO.
         ENDIF.
       ENDIF.
       IF sy-subrc <> 0.
         MESSAGE e539(scpr) WITH g_f_jobname.
       ENDIF.
       COMMIT WORK .
     ENDDO.

How to select the data from a Maintainance View into an internal table

Hi All,
Can anybody tell me how to select the data from a Maintainance View into an internal table.
Thanks,
srinivas.

HI,
You can not retrieve data from A mentenance view.
For detail check this link,
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm
Regards,
Anirban

Creating XML file from ABAP internal table data....

Hello,
I am fethcing data froma custom table and I have to write data in XMl format. Following is the XML format in which I want data. Is there any function module iN SAP which will help me in writing data from internal table to XML file ?
<batch>
<invoice>
    <StatusCode>10</StatusCode>
    <paymentamount>122.00</paymentamount>
     <ReferenceNumber>70980934</ReferenceNumber>
</invoice>
<invoice>
     <StatusCode>90</StatusCode>
    <paymentamount>122.00</paymentamount>
     <ReferenceNumber>70980934</ReferenceNumber>
</invoice>
<control>
    <InvoiceCount>2</InvoiceCount>
</control>
</batch>
Please help.
Regards,
Jainam.

I suggest you look into "simple transformations". That's SAP's most recent technology for such purposes, as far as I know.
http://help.sap.com/abapdocu_70/en/ABENABAP_ST.htm
Thomas

Need suggestion in uploading dynamic excel file to corresponding columns of internal table

Hi Friends,
I have an excel file which doesn't have standard template. Just the users will key in their header (in row1 ) and followed by item details in excel and upload to internal table. Now by doing some internal developments in program I need to place the values in corresponding fields.
Let me explain with some examples.
1. I have an internal table
data : begin of itab occurs 0,
                   f1,
                   f2,
                   f3,
                   f4,
                   f5,
          end of itab.
2. I have excel file as below
3 . Now i need to fill my internal table itab as below
Need to be placed in corresponding fields.
4. When I used GUI_UPLOAD FM it updates internal table as
Please give me suggestion on how to achieve it.
Thanks in advance.

Hi Kumar,
use a temporary table to get excel values and then parse them to a second table with the format you want.
This is pretty basic.
regards,
Edgar

How to populate data in dynamic internal table

Hi Expert,
fyi. My dynamic internal table field is created base on data selected. Eg. select table qpcd has 5 records. These 5 recods will become fieldname to my dynamic internal table. My dynamic internal table will be
...itab
      01
      02
      03
      04
      05
The 5 records from qpcd is populated in another table call viqmel. I need to find the occurance of each code in viqmel and populate the number of occurance in itab in each of column. The final dynamic itab will be like this
table itab
01       02     03    04     05   -
> field name
2         0        1     0       1    -
> data
my source code like below
Report ZPLYGRND2.
TABLES: mara, makt.
TYPE-POOLS: slis, sydes.
DATA:it_fcat TYPE slis_t_fieldcat_alv,
     is_fcat LIKE LINE OF it_fcat,
     ls_layout TYPE slis_layout_alv.
DATA: it_fieldcat TYPE lvc_t_fcat,
      is_fieldcat LIKE LINE OF it_fieldcat.
DATA: new_table TYPE REF TO data,
      new_line TYPE REF TO data,
      ob_cont_alv TYPE REF TO cl_gui_custom_container,
      ob_alv TYPE REF TO cl_gui_alv_grid,
      vg_campos(255) TYPE c,
      i_campos LIKE TABLE OF vg_campos,
      vg_campo(30) TYPE c,
      vg_tables(60) TYPE c.
types : begin of t_qpcd,
         codegruppe like qpcd-codegruppe,
         code like qpcd-code,
        end of t_qpcd.
data:wa_qpcd type t_qpcd,
     i_qpcd type standard table of t_qpcd initial size 0.
FIELD-SYMBOLS: <l_table> TYPE table,
               <l_line> TYPE ANY,
               <l_field> TYPE ANY.
select * into corresponding fields of wa_qpcd from qpcd
where katalogart = 'D'
and   codegruppe = 'OOT01'.
append wa_qpcd to i_qpcd.
endselect.
loop at i_qpcd into wa_qpcd.
is_fcat-fieldname = wa_qpcd-code.
APPEND is_fcat TO it_fcat.
endloop.
LOOP AT it_fcat INTO is_fcat.
    is_fieldcat-fieldname = is_fcat-fieldname.
    is_fieldcat-ref_field = is_fcat-ref_fieldname.
    is_fieldcat-ref_table = is_fcat-ref_tabname.
    APPEND is_fieldcat TO it_fieldcat.
ENDLOOP.
*... Create the dynamic internal table
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
        it_fieldcatalog = it_fieldcat
    IMPORTING
        ep_table = new_table.
if sy-subrc = 0.
endif.
*... Create a new line
ASSIGN new_table->* TO <l_table>.
CREATE DATA new_line LIKE LINE OF <l_table>.
ASSIGN new_line->* TO <l_line>.
LOOP AT <l_table> INTO <l_line>.
ENDLOOP.

hello dear i m giving u a code in this a dynamic table is made on the basis of table in database , and u can download this data correct it , see it, or even change it....and upload in tht table help full if u dont know the table name...in advance.
also the code to populate data in dynamic table is in this code like:
SELECT * FROM (MTABLE_N)
INTO CORRESPONDING FIELDS OF TABLE <FS_ITAB> .
look at the whole program .hope this solve ur problem thanks.
REPORT ZTESTA MESSAGE-ID ZIMM    .
TYPES : DATA_OBJECT TYPE REF TO DATA.
DATA : MITAB TYPE REF TO DATA .
TYPE-POOLS : SLIS .
DATA : IT_FIELDCAT TYPE STANDARD TABLE OF SLIS_FIELDCAT_ALV
WITH HEADER LINE .
DATA : IT_FIELDCATALOG TYPE LVC_T_FCAT .
DATA : WA_FIELDCATALOG TYPE LVC_S_FCAT .
DATA : I_STRUCTURE_NAME LIKE DD02L-TABNAME .
DATA : I_CALLBACK_PROGRAM LIKE SY-REPID .
DATA : DYN_LINE TYPE DATA_OBJECT .
FIELD-SYMBOLS : <FS_ITAB> TYPE STANDARD TABLE .
DATA : TABLE_NAME_IS_VALID TYPE C .
DATA : DYNAMIC_IT_INSTANTIATED TYPE C .
CONSTANTS BUTTONSELECTED TYPE C VALUE 'X' .
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(29) T_TABL.
PARAMETERS : MTABLE_N LIKE RSRD1-TBMA_VAL
MATCHCODE OBJECT DD_DBTB_16 OBLIGATORY .
DATA CHECKTABLED.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(29) T_FILE.
PARAMETERS : MFILENAM LIKE RLGRAP-FILENAME .
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(29) T_DOWN.
PARAMETERS : P_DOWNLD RADIOBUTTON GROUP GRP1
USER-COMMAND M_UCOMM .
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(29) T_CHKF.
PARAMETERS : P_CHKFIL RADIOBUTTON GROUP GRP1 .
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(29) T_UPLD.
PARAMETERS : P_UPLOAD RADIOBUTTON GROUP GRP1 .
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(29) T_SHOW.
PARAMETERS : P_SHOW_T RADIOBUTTON GROUP GRP1 .
SELECTION-SCREEN END OF LINE.
AT SELECTION-SCREEN OUTPUT .
PERFORM CHECK_FILENAME .
AT SELECTION-SCREEN.
IF SY-UCOMM = 'ONLI'.
    CHECKTABLED = MTABLE_N+0(1).
    IF CHECKTABLED NE 'Z'.
      MESSAGE I017.
      LEAVE TO SCREEN 1000.
    ENDIF.
    IF SY-UNAME NE 'KAMESH.K'.
      MESSAGE I023 WITH SY-UNAME.
      LEAVE TO SCREEN 1000.
    ENDIF.
ENDIF.
IF SY-UCOMM = 'PRIN'.
    CHECKTABLED = MTABLE_N+0(1).
    IF CHECKTABLED NE 'Z'.
      MESSAGE I017.
      LEAVE TO SCREEN 1000.
    ENDIF.
    IF SY-UNAME NE 'KAMESH.K'.
      MESSAGE I023 WITH SY-UNAME.
      LEAVE TO SCREEN 1000.
    ENDIF.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR MFILENAM .
PERFORM F4_FOR_FILENAME .
INITIALIZATION .
T_TABL = 'Table Name' .
T_FILE = 'File Name' .
T_DOWN = 'Download Table' .
T_CHKF = 'Check File to Upload' .
T_UPLD = 'Upload File' .
T_SHOW = 'Show Table Contents' .
START-OF-SELECTION .
PERFORM CHECK_TABLE_NAME_IS_VALID .
END-OF-SELECTION .
IF TABLE_NAME_IS_VALID EQ ' ' .
    MESSAGE I398(00) WITH 'INVALID TABLE NAME' .
ELSE .
    PERFORM INSTANTIATE_DYNAMIC_INTERNAL_T .
    CHECK DYNAMIC_IT_INSTANTIATED = 'X' .
    CASE BUTTONSELECTED .
      WHEN P_DOWNLD .
        PERFORM SELECT_AND_DOWNLOAD .
      WHEN P_CHKFIL .
        PERFORM CHECK_FILE_TO_UPLOAD .
      WHEN P_UPLOAD .
        PERFORM UPLOAD_FROM_FILE .
      WHEN P_SHOW_T .
        PERFORM SHOW_CONTENTS .
    ENDCASE .
ENDIF .
FORM CHECK_TABLE_NAME_IS_VALID.
DATA MCOUNT TYPE I .
TABLES DD02L .
CLEAR TABLE_NAME_IS_VALID .
SELECT COUNT(*) INTO MCOUNT FROM TADIR
WHERE PGMID = 'R3TR'
AND OBJECT = 'TABL'
AND OBJ_NAME = MTABLE_N .
IF MCOUNT EQ 1 .
    CLEAR DD02L .
    SELECT SINGLE * FROM DD02L WHERE TABNAME = MTABLE_N .
    IF SY-SUBRC EQ 0.
      IF DD02L-TABCLASS = 'TRANSP' .
        TABLE_NAME_IS_VALID = 'X' .
      ENDIF .
    ENDIF.
ENDIF .
ENDFORM. " CHECK_TABLE_NAME_IS_VALID
FORM SELECT_AND_DOWNLOAD.
CLEAR : <FS_ITAB> .
SELECT * FROM (MTABLE_N)
INTO CORRESPONDING FIELDS OF TABLE <FS_ITAB> .
PERFORM CHECK_FILENAME.
CALL FUNCTION 'WS_DOWNLOAD'
       EXPORTING
            FILENAME                = MFILENAM
            FILETYPE                = 'DAT'
       TABLES
            DATA_TAB                = <FS_ITAB>
       EXCEPTIONS
            FILE_OPEN_ERROR         = 1
            FILE_WRITE_ERROR        = 2
            INVALID_FILESIZE        = 3
            INVALID_TYPE            = 4
            NO_BATCH                = 5
            UNKNOWN_ERROR           = 6
            INVALID_TABLE_WIDTH     = 7
            GUI_REFUSE_FILETRANSFER = 8
            CUSTOMER_ERROR          = 9
            OTHERS                  = 10.
IF SY-SUBRC EQ 0.
    MESSAGE I398(00) WITH 'Table' MTABLE_N
    'successfully downloaded to '
    MFILENAM .
ENDIF.
ENDFORM. " SELECT_AND_DOWNLOAD
FORM UPLOAD_FROM_FILE.
DATA : ANS TYPE C .
DATA : LINES_OF_ITAB TYPE I .
DATA : MSY_SUBRC TYPE I .
CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
       EXPORTING
            TEXTLINE1 = 'Are you sure you wish to upload'
            TEXTLINE2 = 'data from ASCII File to DB table '
            TITEL     = 'Confirmation of Data Upload'
       IMPORTING
            ANSWER    = ANS.
IF ANS = 'J' .
    PERFORM CHECK_FILENAME.
    CLEAR MSY_SUBRC .
    CALL FUNCTION 'WS_UPLOAD'
         EXPORTING
              FILENAME                = MFILENAM
              FILETYPE                = 'DAT'
         TABLES
              DATA_TAB                = <FS_ITAB>
         EXCEPTIONS
              CONVERSION_ERROR        = 1
              FILE_OPEN_ERROR         = 2
              FILE_READ_ERROR         = 3
              INVALID_TYPE            = 4
              NO_BATCH                = 5
              UNKNOWN_ERROR           = 6
              INVALID_TABLE_WIDTH     = 7
              GUI_REFUSE_FILETRANSFER = 8
              CUSTOMER_ERROR          = 9
              OTHERS                  = 10.
    MSY_SUBRC = MSY_SUBRC + SY-SUBRC .
    IF SY-SUBRC EQ 0.
      DESCRIBE TABLE <FS_ITAB> LINES LINES_OF_ITAB .
      IF LINES_OF_ITAB GT 0 .
        MODIFY (MTABLE_N) FROM TABLE <FS_ITAB> .
        MSY_SUBRC = MSY_SUBRC + SY-SUBRC .
      ENDIF .
    ENDIF.
    IF MSY_SUBRC EQ 0 .
      MESSAGE I398(00) WITH LINES_OF_ITAB
      'Record(s) inserted in table'
      MTABLE_N .
    ELSE .
      MESSAGE I398(00) WITH
      'Errors occurred No Records inserted in table'
      MTABLE_N .
    ENDIF .
ENDIF .
ENDFORM. " UPLOAD_FROM_FILE
FORM F4_FOR_FILENAME.
CALL FUNCTION 'WS_FILENAME_GET'
       EXPORTING
            DEF_PATH         = 'C:\'
            MASK             = ',.,..'
            MODE             = '0'
       IMPORTING
            FILENAME         = MFILENAM
       EXCEPTIONS
            INV_WINSYS       = 1
            NO_BATCH         = 2
            SELECTION_CANCEL = 3
            SELECTION_ERROR = 4
            OTHERS           = 5.
ENDFORM. " F4_FOR_FILENAME
FORM CHECK_FILENAME.
IF MFILENAM IS INITIAL
AND NOT ( MTABLE_N IS INITIAL )
AND P_SHOW_T NE BUTTONSELECTED.
    CONCATENATE 'C:\'
    MTABLE_N '.TXT' INTO MFILENAM.
ENDIF .
ENDFORM. " CHECK_FILENAME
FORM INSTANTIATE_DYNAMIC_INTERNAL_T.
CLEAR DYNAMIC_IT_INSTANTIATED .
I_STRUCTURE_NAME = MTABLE_N .
CLEAR IT_FIELDCAT[] .
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
       EXPORTING
            I_STRUCTURE_NAME       = I_STRUCTURE_NAME
       CHANGING
            CT_FIELDCAT            = IT_FIELDCAT[]
       EXCEPTIONS
            INCONSISTENT_INTERFACE = 1
            PROGRAM_ERROR          = 2
            OTHERS                 = 3.
IF SY-SUBRC EQ 0.
    LOOP AT IT_FIELDCAT .
      CLEAR WA_FIELDCATALOG .
      MOVE-CORRESPONDING IT_FIELDCAT TO WA_FIELDCATALOG .
      WA_FIELDCATALOG-REF_FIELD = IT_FIELDCAT-FIELDNAME .
      WA_FIELDCATALOG-REF_TABLE = MTABLE_N .
      APPEND WA_FIELDCATALOG TO IT_FIELDCATALOG .
    ENDLOOP .
    CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
    EXPORTING
    IT_FIELDCATALOG = IT_FIELDCATALOG
    IMPORTING
    EP_TABLE = MITAB .
    ASSIGN MITAB->* TO <FS_ITAB> .
    DYNAMIC_IT_INSTANTIATED = 'X' .
ENDIF.
ENDFORM. " INSTANTIATE_DYNAMIC_INTERNAL_T
FORM SHOW_CONTENTS.
CLEAR : <FS_ITAB> .
SELECT * FROM (MTABLE_N)
INTO CORRESPONDING FIELDS OF TABLE <FS_ITAB> .
I_CALLBACK_PROGRAM = SY-REPID .
CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
       EXPORTING
            I_CALLBACK_PROGRAM = I_CALLBACK_PROGRAM
            IT_FIELDCAT        = IT_FIELDCAT[]
       TABLES
            T_OUTTAB           = <FS_ITAB>
       EXCEPTIONS
            PROGRAM_ERROR      = 1
            OTHERS             = 2.
ENDFORM. " SHOW_CONTENTS
FORM CHECK_FILE_TO_UPLOAD.
PERFORM CHECK_FILENAME.
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            FILENAME                = MFILENAM
            FILETYPE                = 'DAT'
       TABLES
            DATA_TAB                = <FS_ITAB>
       EXCEPTIONS
            CONVERSION_ERROR        = 1
            FILE_OPEN_ERROR         = 2
            FILE_READ_ERROR         = 3
            INVALID_TYPE            = 4
            NO_BATCH                = 5
            UNKNOWN_ERROR           = 6
            INVALID_TABLE_WIDTH     = 7
            GUI_REFUSE_FILETRANSFER = 8
            CUSTOMER_ERROR          = 9
            OTHERS                  = 10.
IF SY-SUBRC EQ 0.
    I_CALLBACK_PROGRAM = SY-REPID .
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
         EXPORTING
              I_CALLBACK_PROGRAM = I_CALLBACK_PROGRAM
              IT_FIELDCAT        = IT_FIELDCAT[]
         TABLES
              T_OUTTAB           = <FS_ITAB>
         EXCEPTIONS
              PROGRAM_ERROR      = 1
              OTHERS             = 2.
ENDIF .
ENDFORM. " CHECK_FILE_TO_UPLOAD
Message was edited by:
        SAURABH SINGH
        SENIOR EXECUTIVE
        SAMSUNG INDIA ELECTRONICS LTD.,NOIDA

How to upload a file in application server to an internal table

Hi,
      I am asked to upload a file from application server to internal table. Can you please suggest me the ways to do it or the function module which helps to browse the application server file names.
I have done a program. But its giving problem in searching the files from application server. I am pasting my code for ur review. Please tell me which part i have to correct or suggest me some other ways to do it.
*& Report ZUPLOAD1
REPORT ZUPLOAD1.
type-pools: truxs.
parameters: p_upl_ps radiobutton group g1 default 'X', "upload from pres. server
             p_path type rlgrap-filename,
             p_upl_as radiobutton group g1,   "upload from appln server
             <b>p_dir LIKE filepath-pathintern DEFAULT 'Y_ABAP',
             p_file LIKE filepath-pathintern lower case,</b>
             p_test as checkbox.
constants: c_x value 'X',
           c_tab type c value cl_abap_char_utilities=>horizontal_tab.
types: ty_data(1000) type c.    "structure to hold legacy data
data: i_data type standard table of ty_data. "internal table of ty_data
types: begin of stritab,
      land1 type v_t604-land1, "structure of legacy file.
      stawn type v_t604-stawn,
      bemeh type v_t604-bemeh,
      impma type v_t604-impma,
      minol type v_t604-minol,
      end of stritab.
data: gi_itab type standard table of stritab, "internal table of legacy file
      gw_itab type stritab. "work area
data: i_raw type truxs_t_text_data,
      v_fullpath type string.
at selection-screen on value-request for p_path.
if p_upl_ps = c_x. "if presentation server is selected
perform get_file.
else.            "if application server is selected
perform set_file_path.
perform upload_from_server.
perform split_data.
endif.
form get_file.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
PROGRAM_NAME        = SYST-CPROG
DYNPRO_NUMBER       = SYST-DYNNR
FIELD_NAME          = ' '
IMPORTING
   FILE_NAME           = p_path.     "getting the file name of pres server
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
EXPORTING
I_FIELD_SEPERATOR          =
    I_LINE_HEADER              = 'X'              "converting excel to sap and filling in
    I_TAB_RAW_DATA             = i_raw      "internal table
    I_FILENAME                 = p_path
TABLES
    I_TAB_CONVERTED_DATA       = gi_itab
EXCEPTIONS
   CONVERSION_FAILED          = 1
   OTHERS                     = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endform.
form set_file_path.                 "Getting the file path of application server
data: lv_file type p_file.
      lv_file = p_file.
      CALL FUNCTION 'FILE_GET_NAME_USING_PATH'
        EXPORTING
        CLIENT                           = SY-MANDT
          LOGICAL_PATH                     = p_dir
        OPERATING_SYSTEM                 = SY-OPSYS
        PARAMETER_1                      = ' '
        PARAMETER_2                      = ' '
        PARAMETER_3                      = ' '
        USE_BUFFER                       = ' '
          FILE_NAME                        = lv_file
        USE_PRESENTATION_SERVER          = ' '
        ELEMINATE_BLANKS                 = 'X'
       IMPORTING
         FILE_NAME_WITH_PATH              = v_fullpath
       EXCEPTIONS
         PATH_NOT_FOUND                   = 1
         MISSING_PARAMETER                = 2
         OPERATING_SYSTEM_NOT_FOUND       = 3
         FILE_SYSTEM_NOT_FOUND            = 4
         OTHERS                           = 5
      IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
endform.
form upload_from_server.
data: lv_msg type string,
      lw_data type ty_data.
open dataset v_fullpath for input message lv_msg in text mode encoding default.
if sy-subrc <> 0.
message lv_msg type 'i'.
stop.
endif.
do.
read dataset v_fullpath into lw_data.
if sy-subrc <> 0.
write:/5 'Error in processign data set'.
exit.
endif.
append lw_data to i_data.
enddo.
close dataset v_fullpath.
if sy-subrc <> 0.
write: /5 'Error closing dataset'.
endif.
endform.
form split_data.
data: lw_data type ty_data.
data: lw_itab type stritab.
data: begin of ty_itab,
      land1 type v_t604-land1,
      stawn type v_t604-stawn,
      bemeh type v_t604-bemeh,
      impma type v_t604-impma,
      minol type v_t604-minol,
      end of ty_itab.
loop at i_data into lw_data.
split lw_data at c_tab into
      ty_itab-land1
      ty_itab-stawn
      ty_itab-bemeh
      ty_itab-impma
      ty_itab-minol.
lw_itab-land1 = ty_itab-land1.
lw_itab-stawn = ty_itab-stawn.
lw_itab-bemeh = ty_itab-bemeh.
lw_itab-impma = ty_itab-impma.
lw_itab-minol = ty_itab-minol.
append lw_itab to gi_itab.
endloop.
endform.
start-of-selection.
loop at gi_itab into gw_itab.
write: /5 'COUNTRY', 'IMPORT CODE', 'SUP UNIT', 'FIRST UOM', 'SECOND UOM',
       /5 gw_itab-land1, gw_itab-stawn,gw_itab-bemeh,gw_itab-impma,gw_itab-minol.
endloop.
end-of-selection.
I hope problem must be in p_dir and p_file which are in bold.. Kindly help me out. Thanks in advance.

see the following ex:
*&      Form SUB_GET_FILEPATH
      text
--> p1        text
<-- p2        text
FORM SUB_GET_FILEPATH .
    GFILE = 'D:\SAP_INT\INBOUND\INBOX'. "Path
ENDFORM.                    " SUB_GET_FILEPATH
*&      Form SUB_GET_FILE
      text
--> p1        text
<-- p2        text
FORM SUB_GET_FILE .
DATA: P_FDIR(200) TYPE C.
DATA: IT_FILEDIR1 TYPE STANDARD TABLE OF TY_FILEDIR WITH HEADER LINE.
P_FDIR = GFILE.
CALL FUNCTION 'RZL_READ_DIR_LOCAL'
    EXPORTING
      NAME     = P_FDIR
    TABLES
      FILE_TBL = IT_FILEDIR.
REFRESH : IT_FILEDIR1.
LOOP AT IT_FILEDIR.
    IF IT_FILEDIR-NAME(4) = 'ZINC' OR IT_FILEDIR-NAME(4) = 'zinc'.
      MOVE IT_FILEDIR-NAME TO IT_FILEDIR1-NAME.
      APPEND IT_FILEDIR1.
    ENDIF.
ENDLOOP.
IF IT_FILEDIR1[] IS INITIAL.
    STOP.
ENDIF.
LOOP AT IT_FILEDIR1.
    REFRESH: I_TAB.
    CLEAR: I_TAB.
    NAME = IT_FILEDIR1-NAME.
    CONCATENATE: GFILE '\' NAME INTO G_FILE.
    OPEN DATASET G_FILE FOR INPUT IN TEXT MODE
                                     ENCODING DEFAULT
                                     IGNORING CONVERSION ERRORS.
    IF SY-SUBRC EQ 0.
      CONCATENATE 'FILENAME : ' G_FILE INTO I_MSG1.
      APPEND I_MSG1.
      DO.
        READ DATASET G_FILE INTO RECORD.
        IF SY-SUBRC = 0.
          SPLIT RECORD AT ',' INTO I_TAB-BUKRS I_TAB-EBELN
              I_TAB-BLDAT I_TAB-XBLNR I_TAB-LIFNR I_TAB-AMOUNT
              I_TAB-CURR I_TAB-BUSAREA
              I_TAB-BKTXT I_TAB-DMBTR I_TAB-MENGE I_TAB-SRNO.
          MOVE-CORRESPONDING I_TAB TO I_TAB1.
        ELSE.
          EXIT.
        ENDIF.
        APPEND I_TAB1.
        CLEAR: I_TAB, I_TAB1.
      ENDDO.
    ENDIF.
    CLOSE DATASET G_FILE.

Use 3 internal table in GUI_Download

Hello expert,
i have 3 internal table: gt_header, gt_body and gt_footer. how can i used all 3 in gui_download fm. here is my sample code:
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      filename              = gv_file_name
      filetype              = 'ASC'
    TABLES
      data_tab              = gt_header.
here i can only pass one internal table.
Help please?

Hi Hassim,
Maybe you can declare another internal table, with all fields is type C and length as you wanted.
Loop those three itabs, append to this new itab. then call this FM download.
regards,
Archer

IMPORT Statement Issue (Internal Table)

Hi All,
I am using an IMPORT statement to get all the data from other report's internal table. Now whenever this (the other report's internal table) is changed (for field addition, etc), my report throws a dump. Hence, everytime I have to add these fields in my program as well.
Is there any way by which I can include the whole internal table of that report in my program just like
'INCLUDE STRUCTURE VBRK'.
Thanks in advance

Hi, CHeck this code related to your problem..This will helpful to you...
I have done this program earlier..I hope it will helpful to u..
This programa calling the other program to import the data..
Check it out...
*" Tables declarations.................................................
TABLES:
spfli.
*" Type declarations...................................................
Type declaration of the structure to hold data from table SPFLI     *
TYPES:
BEGIN OF type_s_spfli,
    carrid LIKE spfli-carrid,          " Carrier Id
    connid LIKE spfli-connid,          " Connection Number
    cityfrom LIKE spfli-cityfrom,      " City from
    cityto LIKE spfli-cityto,          " City to
    airpfrom LIKE spfli-airpfrom,      " Airport from
    airpto LIKE spfli-airpto,          " Airport to
    countryfr LIKE spfli-countryfr,    " Country from
    countryto LIKE spfli-countryto,    " Country to
END OF type_s_spfli.
Data Declaration...................................................*
     Field String To Hold Flight Details Record from SPFLI          *
DATA
fs_spfli TYPE type_s_spfli.
Data Declaration...................................................*
     Internal Table To Hold Flight Details Records from SPFLI       *
DATA
t_spfli LIKE STANDARD TABLE OF fs_spfli.
TYPES:
BEGIN OF types_s_itab,
    carrid LIKE sflight-carrid,        " Carrier id
    connid LIKE sflight-connid,        " Connection number
    fldate LIKE sflight-fldate,        " Flight date
END OF types_s_itab.
Data Declaration...................................................*
     Field String To Hold Flight Details Record from SFLIGHT        *
DATA
fs_itab TYPE types_s_itab.
Data Declaration...................................................*
     Internal Table To Hold Flight Details Records from SFLIGHT     *
DATA
t_itab LIKE STANDARD TABLE OF fs_itab.
*" Type declarations...................................................
Type declaration of the structure to hold data from table SBOOK     *
TYPES:
BEGIN OF type_s_sbook,
   carrid LIKE sbook-carrid,           " Carrier Id
   connid LIKE sbook-connid,           " Connection Number
   fldate LIKE sbook-fldate,           " Flight date
   bookid LIKE sbook-bookid,           " Booking number
   loccuram LIKE sbook-loccuram,       " Local currency
   loccurkey LIKE sbook-loccurkey,
   order_date LIKE sbook-order_date,   " Booking date
END OF type_s_sbook.
Data Declaration...................................................*
     Field String To Hold Flight Details Record from BOOK           *
DATA
fs_sbook TYPE type_s_sbook.
Data Declaration...................................................*
     Internal Table To Hold Flight Details Records from SBOOK       *
DATA
t_sbook LIKE STANDARD TABLE OF fs_sbook.
DATA
w_checkbox.                          " Checkbox
SELECT-OPTIONS:
s_carr FOR spfli-carrid.             " Carrier id range
                      START-OF-SELECTION EVENT                      *
START-OF-SELECTION.
PERFORM selectq.
                      END-OF-SELECTION EVENT                        *
END-OF-SELECTION.
SET PF-STATUS 'YH1314_030502'.
PERFORM display_basic.
AT USER-COMMAND.
PERFORM ucomm.
*&    Form selectq
    This subroutine retreive data from SPFLI table
There are no interface parameters to be passed to this subroutine.
FORM selectq .
SELECT carrid                        " Carrier id
         connid                        " Connection number
         cityfrom                      " City from
         cityto                        " City to
         airpfrom                      " Airport from
         airpto                        " Airport to
         countryfr                     " Country from
         countryto                     " Country to
         INTO CORRESPONDING FIELDS OF TABLE t_spfli
         FROM spfli
         WHERE carrid IN s_carr.
ENDFORM.                               " Selectq
*&      Form display_basic
    This subroutine displays data from internal table
There are no interface parameters to be passed to this subroutine.
FORM display_basic .
LOOP AT t_spfli INTO fs_spfli.
    WRITE:
      / w_checkbox AS CHECKBOX,
        fs_spfli-carrid,
        fs_spfli-connid,
        fs_spfli-cityfrom,
        fs_spfli-cityto,
        fs_spfli-airpfrom,
        fs_spfli-airpto,
        fs_spfli-countryfr,
        fs_spfli-countryto.
ENDLOOP.                             " LOOP AT T-SPFLI INTO...
ENDFORM.                               " Display_basic
*&      Form UCOMM
This subroutine for at user-command event
There are no interface parameters to be passed to this subroutine.
FORM ucomm .
RANGES :
    r_carr FOR spfli-carrid,
    r_conn FOR spfli-connid,
    r_carrid FOR sflight-carrid,
    r_connid FOR sflight-connid,
    r_fldate FOR sflight-fldate.
CASE sy-ucomm.
    WHEN 'DISPLAY'.
      DATA:
        lw_lines TYPE i,
        lw_lineno TYPE i VALUE 3.
      DESCRIBE TABLE t_spfli LINES lw_lines.
      DO lw_lines TIMES.
        READ LINE lw_lineno FIELD
             VALUE w_checkbox   INTO w_checkbox
                   fs_spfli-carrid INTO fs_spfli-carrid
                   fs_spfli-connid INTO fs_spfli-connid.
        IF sy-subrc = 0.
          IF w_checkbox = 'X'.
            r_carr-sign = 'I'.
            r_carr-option = 'EQ'.
            r_carr-low = fs_spfli-carrid.
            APPEND r_carr.
            r_conn-sign = 'I'.
            r_conn-option = 'EQ'.
            r_conn-low = fs_spfli-connid.
            APPEND r_conn.
          ENDIF.                       " IF W_CHECKBOX = 'X'
        ENDIF.                         " IF SY-SUBRC = 0
        ADD 1 TO lw_lineno.
      ENDDO.                           " DO LW_LINES TIMES
      SUBMIT yh1314_030502_call
        WITH s_carr IN r_carr
        WITH s_conn IN r_conn
         AND RETURN.
      IMPORT t_itab FROM MEMORY ID 'YH1314'.
      LOOP AT t_itab INTO fs_itab.
        r_carrid-sign = 'I'.
        r_carrid-option = 'EQ'.
        r_carrid-low = fs_itab-carrid.
        APPEND r_carrid.
        r_connid-sign = 'I'.
        r_connid-option = 'EQ'.
        r_connid-low = fs_itab-connid.
        APPEND r_connid.
        r_fldate-sign = 'I'.
        r_fldate-option = 'EQ'.
        r_fldate-low = fs_itab-fldate.
        APPEND r_fldate.
      ENDLOOP.                         " LOOP AT T_ITAB INTO.....
      SELECT carrid                    " Carriee Id
             connid                    " Connection number
             fldate                    " Flight date
             bookid                    " Booking number
             loccuram                  " Local Currency
             order_date                " Booking date
         INTO CORRESPONDING FIELDS OF TABLE t_sbook
         FROM sbook
         WHERE carrid IN r_carrid AND
               connid IN r_connid AND
               fldate IN r_fldate.
      IF SY-SUBRC NE 0.
        MESSAGE 'NO RECORDS FOUND'(006) TYPE 'S'.
      ENDIF.                           " IF SY-SUBRC NE 0
      LOOP AT t_sbook INTO fs_sbook.
        AT FIRST.
          WRITE: /5 'Carrier Id'(001),
                 20 'Conn Id'(002),
                 35 'Flight date'(003),
                 50 'Book Id'(004),
                 65 'Local Currency'(005).
        ENDAT.                         " AT FIRST
        WRITE: /5 fs_sbook-carrid,
               20 fs_sbook-connid,
               35 fs_sbook-fldate,
               50 fs_sbook-bookid,
               65 fs_sbook-loccuram CURRENCY fs_sbook-loccurkey.
      ENDLOOP.                         " LOOP AT T_SBOOK INTO.....
ENDCASE.                             " CASE SY-UCOMM
ENDFORM.                               " UCOMM
Regards
Kiran

Can not insert or update [TABLE] from internal table in method

I've faced a problem with OO abap. I've tried to insert into [ TABLE ] from internal table, but i've got error msg after i compiled.
"An explicit work area is necessary in the OO context. Use "INSERT wa INTO [TABLE] itab""
After i changed to loop in work area and INSERT INTO [TABLE] VALUES gw_data., everything is fine, can compile and run.
This is error code.
METHOD set_data_to_table.
    REFRESH gi_data.
    CLEAR gi_data.
    IF gi_file[] IS NOT INITIAL.
* Set data for modify table
      LOOP AT gi_file INTO gw_file.
        MOVE-CORRESPONDING gw_file TO gw_data.
        me->conversion_input( EXPORTING im_vendor = gw_data-vendor
                              CHANGING ch_vendor = gw_data-vendor ).
        APPEND gw_data TO gi_data.
      ENDLOOP.
      INSERT [TABLE] FROM TABLE gi_data.
*      LOOP AT gi_data INTO gw_data.
*        INSERT INTO [TABLE] VALUES gw_data.
*        IF sy-subrc = 0.
*          COMMIT WORK.
*        ELSE.
*          ROLLBACK WORK.
*        ENDIF.
*      ENDLOOP.
    ELSE.
      MESSAGE 'No data found' TYPE 'I'.
    ENDIF.
ENDMETHOD.                    "set_data_to_table

Hi Matthew,
I think there is no difference in database insert between OO and non-OO.
The correct syntax according to ECC600 online documentation is
[Inserting Several Lines|http://help.sap.com/saphelp_erp2005vp/helpdata/en/fc/eb3a6d358411d1829f0000e829fbfe/content.htm]
To insert several lines into a database table, use the following:
INSERT target FROM TABLE itab \[ACCEPTING DUPLICATE KEYS].
This writes all lines of the internal table itabto the database table in one single operation. If one or more lines cannot be inserted because the database already contains a line with the same primary key, a runtime error occurs. You can prevent the runtime error occurring by using the addition ACCEPTING DUPLICATE KEYS.
Whenever you want to insert more than one line into a database table, it is more efficient to work with an internal table than to insert the lines one by one.
I think the syntax
INSERT my_dbtable FROM TABLE gi_data.
should work, your suggestion may lead to syntax error.
Regards,
Clemens

Internal table aggregation

Similar Messages

Maybe you are looking for