Difference between Table Maintenance and SE11

Hi all,
I want to know what is the difference between creating modifying table records using SM30 and creating modifying table records using SE11. As in Se11 itself we have the options for creating modifying Customer table records why we have to go for SM30.
Regards,
Kasi S

Check out these links
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_46c/helpdata/en/a7/5133ac407a11d1893b0000e8323c4f/frameset.htm
regards,
Santosh

Similar Messages

What is difference between table space and shchema

what is difference between table space and shchema ?

784633 wrote:
so each user has it own space of tables - schema ?yes, but let's clarify a bit ....
The "schema" is the collection of all objects owned by a particular user. So if user SCOTT creates two tables, EMP and DEPT, and a view EMP_RPT, and a procedure GET_MY_EMP, those objects (tables, views, procedures) collectively make up the SCOTT schema.
Those objects will be physically stored in a tablespace.
A tablespace is a named collection of data files. So tablespace USERS will be made up of one or more data files. A specific datafile can belong to one and only one tablespace. If a tablespace has more than one data file, oracle will manage those files as a collection invisible to the application - much like the OS or disk subsystem handles striping across multiple physical disks.
A specific object in the SCOTT schema can exist in only one tablespace, but not all objects of the schema have to be in the same tablespace. Likewise a tablespace can contain objects from multiple schemas.
and can one user to access tables of other users?As others have said - FRED can access tables belonging to SCOTT as long has SCOTT has granted that access to FRED.

Difference between table CKMLKEPH and transaction figure of CKM3

Hi Gurus,
Having an issue in material ledger transaction and table data.
There is a difference between table CKMLKEPH and transaction figure of CKM3 for couple of periods.
Single level price difference for raw material domestic figure coming in transaction CKM3 is not matching with CKMLKEPH table.
Can you advice the tentative reason of it.
Thanks in advance,
MC.

Hi MC,
MLHELP_CCS_CONS_CHECK which check the actual CCS and the program
MLHELP_SPRICE_CCS_INIT for the standard CCS.
These programs are provided by the ML Helpdesk tool via note 364368.
Although these reports are used by SAP Support you can execute them in
test mode to verify your CCS data.
Regards,Declan

Query on differences between table Icons and types in smartforms

Hello,
I have a question regarding the apparent differences between tables in smartforms.
I have noticed on some of the default smartforms that are supplied the table icon is the same as on the
'Create new session' button at the top of a Sap session window. The icon on a table that I am currently working on is like a 'spread sheet' design, a heading with columns, as shown in the current documentation. The way the two styles of tables work is different.
Is the difference down to the fact one was created in an older implementation of Sap?
The reason I ask is because the table I refered to initially, is easier when configuring cells.
Regards
Mike.

Hello Karthik
Thanks for taking the time to reply to my question.
The difference in the icons but with essentially the same function has always confused me since starting Smartforms.
Thank you for enlightening me.
I asked the question because the Complex node has a feature that I could have used. I have managed though to solve my problem using a table node.
Ten points awarded.
Best Regards
Mike Spear.

Difference between tables statement and by using type statement

Hi all,
I need to know the difference between the two of the below statements
Tables spfli.
and
data spfli type spfli with header line.
As far as i know both seem same to me.
Thanks in advance,
Bala.

>
Bala Shanmuga Priyan wrote:
> Hi all,
>
> I need to know the difference between the two of the below statements
>
>
Tables spfli.
this will create a work area (spfli), looks like DB table spfli, but the statement is obsolate
Bala Shanmuga Priyan wrote:
>
data spfli type spfli with header line.
this will result in a syntax error, because this would also create a work area, but they cannot have header lines, so you should leave the WITH HEADER LINE addition.
To create work area use:
DATA : gw_spfli TYPE spfli.
To create internal table:
DATA : gt_spfli TYPE TABLE OF spfli.

Difference between tables statement and work area

Hi
i would like know the difference between these statement.
tables: vttk.
data :itab type standard table of vttk,
wa_itab like line of vttk.
what will happen with the table statement keyword ???
whether any difference between the ouput created through tables and wa_itab statement???

Hi
HI,
INTERNAL Table and it's background:
===================================
Internal table acts as a container which is used to store the record sets. That is used to store the data fetched from the database table.
So due to performance reason every time access to database would not be so good and decrease the performance. So you just select the data from the database and store it in the intermediate table. This table is called INTERNAL TABLE. So it's an replica of the database. The design foes like this,
PRESENTATION SERVER <> APPLICATION SERVER <>
DATABASE SERVER.
So everytime gain accessing to database results in high resource usage and bad permformance.
So always play around with internal tables. So obviously the whenever you access the data in the INTERNAL TABLE, the application server will be used.
WORK AREA:
==========
When ever you loop at the internal table, the current record should be stored in a temporary work place. That is called WORK AREA.
LOOP AT ITAB INTO WORKAREA.
ENDLOOP.
ITAB :An internal table
WORKAREA:An instance of internal table
Go thru the link below
Internal tables
appending internal tables.
Reward if usefull

DIFFERENCE between Tabstrip control and tabstrin(with wizard)

difference between table control and table control wizard.
and what is all about custom control
give simple examples

Hi
Table Control
http://help.sap.com/saphelp_erp2005vp/helpdata/en/d1/802338454211d189710000e8322d00/frameset.htm
Table Control Wizard
http://help.sap.com/saphelp_erp2005vp/helpdata/en/d1/802338454211d189710000e8322d00/frameset.htm
Tab Strip
http://help.sap.com/saphelp_erp2005vp/helpdata/en/04/10f2469e0811d1b4700000e8a52bed/frameset.htm
Tab Strip wizard
http://help.sap.com/saphelp_erp2005vp/helpdata/en/04/10f2469e0811d1b4700000e8a52bed/frameset.htm
http://www.sapmaterial.com/tablecontrol_sap.html
Custom Controls
A custom control is an area on a screen. You create them in the Screen Painter, and, like all other screen objects, they have a unique name. You use custom controls to embed controls. A control is a software component on the presentation server, which can be either an ActiveX control or a JavaBean, depending on the SAPgui you are using. They allow you to perform tasks, such as editing texts, locally on the presentation server. The control is driven by the application logic, which still runs on the application server.
The SAP Control Framework
The controls on the presentation server and the ABAP application programs on the application server communicate using the Structure link SAP Control Framework. This is programmed in ABAP Objects, and contains a set of global classes that you can find in the Class Browser under Basis ® Frontend services. These classes encapsulate the communication between the application server and presentation server, which is implemented using Remote Function Call.
All application controls are encapsulated in a global class. You can find the SAP Basis controls in the Class Browser under Basis ® Frontend Services or Basis ® Component Integration. Programs that use controls on a screen work with the methods and events of the global classes that encapsulates them.
Container Controls
Before you can work with a custom control on a screen, you must assign a Structure link SAP Container Control to it. Container controls are instances of special global classes from the SAP Control Framework. The global class for custom controls is called CL_GUI_CUSTOM_CONTAINER. To link a custom control to a container control, pass the custom control name to the CONTAINER_NAME parameter of the container control constructor when you instantiate it.
As well as using custom containers, you can link controls to a screen using a SAP Docking Container. This is encapsulated in the global class CL_GUI_DOCKING_CONTAINER. The SAP Docking Container does not place the control within a screen. Instead, it attaches it to one of the four edges. You can nest containers. For example, you can use the SAP Splitter Container (classes CL_GUI_EASY_SPLITTER_CONTAINER or CL_GUI_SPLITTER_CONTAINER) within other containers. This allows you to split a custom control or docking control into more than one area, allowing you to embed more than one control.
One example,
program z.
Constants *
constants: c_me like trdir-cnam value 'VNDOVV',
c_myurl type scarr-url value
'http://www.brainbench.com/transcript.jsp?pid=147699',
c_width type i value 260,
c_height type i value 130.
Types *
types: begin of t_pgm,
year(4) type c,
name like trdir-name,
end of t_pgm,
begin of t_pgmkey,
id type i,
name like trdir-name,
end of t_pgmkey.
Data *
data: it_pgmkey type table of t_pgmkey.
Classes *
Definitions *
class screen_init definition create private.
public section.
class-methods init_screen returning value(this)
type ref to screen_init.
methods constructor.
private section.
class-data a_id type i.
data: splitter_h type ref to cl_gui_splitter_container,
splitter_v type ref to cl_gui_splitter_container,
picture type ref to cl_gui_picture,
tree type ref to cl_gui_simple_tree.
methods: fill_tree,
fill_picture.
endclass.
class screen_handler definition.
public section.
methods: constructor importing container
type ref to cl_gui_container,
handle_node_double_click
for event node_double_click
of cl_gui_simple_tree
importing node_key,
handle_picture_double_click
for event picture_dblclick
of cl_gui_picture.
private section.
data: html_viewer type ref to cl_gui_html_viewer,
editor type ref to cl_gui_textedit.
methods: fill_html,
fill_src importing programid type trdir-name.
endclass.
Implementations *
class screen_init implementation.
method init_screen.
data screen type ref to screen_init.
create object screen.
this = screen.
endmethod.
method constructor.
data: events type cntl_simple_events,
event like line of events,
event_handler type ref to screen_handler,
container_left type ref to cl_gui_container,
container_right type ref to cl_gui_container,
container_top type ref to cl_gui_container,
container_bottom type ref to cl_gui_container.
create object splitter_h
exporting
parent = cl_gui_container=>screen0
rows = 1
columns = 2.
call method splitter_h->set_border
exporting border = cl_gui_cfw=>false.
call method splitter_h->set_column_mode
exporting mode = splitter_h->mode_absolute.
call method splitter_h->set_column_width
exporting id = 1
width = c_width.
container_left = splitter_h->get_container( row = 1 column = 1 ).
container_right = splitter_h->get_container( row = 1 column = 2 ).
create object splitter_v
exporting
parent = container_left
rows = 2
columns = 1.
call method splitter_v->set_border
exporting border = cl_gui_cfw=>false.
call method splitter_v->set_row_mode
exporting mode = splitter_v->mode_absolute.
call method splitter_v->set_row_height
exporting id = 1
height = c_height.
container_top = splitter_v->get_container( row = 1 column = 1 ).
container_bottom = splitter_v->get_container( row = 2 column = 1 ).
create object picture
exporting parent = container_top.
create object tree
exporting parent = container_bottom
node_selection_mode =
cl_gui_simple_tree=>node_sel_mode_single.
create object event_handler
exporting container = container_right.
event-eventid = cl_gui_simple_tree=>eventid_node_double_click.
event-appl_event = ' '. "system event, does not trigger PAI
append event to events.
call method tree->set_registered_events
exporting events = events.
clear: event, events[].
event-eventid = cl_gui_picture=>eventid_picture_dblclick.
event-appl_event = ' '. "system event, does not trigger PAI
append event to events.
call method picture->set_registered_events
exporting events = events.
set handler: event_handler->handle_node_double_click for tree,
event_handler->handle_picture_double_click for picture.
call method: me->fill_picture,
me->fill_tree.
endmethod.
method fill_picture.
call method:
picture->load_picture_from_sap_icons exporting icon = '@J4@',
picture->set_display_mode
exporting display_mode = picture->display_mode_fit_center.
endmethod.
method fill_tree.
data: node_table type table of abdemonode,
node type abdemonode,
w_pgm type t_pgm,
w_cdat type rdir_cdate,
it_pgm type table of t_pgm,
w_pgmkey type t_pgmkey.
clear: a_id, it_pgmkey[].
select distinct name cdat from trdir into (w_pgm-name, w_cdat)
where cnam = c_me.
w_pgm-year = w_cdat(4).
append w_pgm to it_pgm.
clear w_pgm.
endselect.
sort it_pgm.
node-hidden = ' '. " All nodes are visible,
node-disabled = ' '. " selectable,
node-isfolder = 'X'. " a folder,
node-expander = ' '. " have no '+' sign for expansion.
loop at it_pgm into w_pgm.
at new year.
node-node_key = w_pgm-year.
clear node-relatkey.
clear node-relatship.
node-text = w_pgm-year.
node-n_image = ' '.
node-exp_image = ' '.
append node to node_table.
endat.
at new name.
add 1 to a_id.
node-node_key = w_pgmkey-id = a_id.
w_pgmkey-name = w_pgm-name.
node-relatkey = w_pgm-year.
node-relatship = cl_gui_simple_tree=>relat_last_child.
node-text = w_pgm-name.
node-n_image = '@0P@'.
node-exp_image = '@0P@'.
append w_pgmkey to it_pgmkey.
endat.
append node to node_table.
endloop.
call method tree->add_nodes
exporting table_structure_name = 'ABDEMONODE'
node_table = node_table.
endmethod.
endclass.
class screen_handler implementation.
method constructor.
create object: html_viewer exporting parent = container,
editor exporting parent = container
wordwrap_mode =
cl_gui_textedit=>wordwrap_at_fixed_position
wordwrap_position = 72.
call method: fill_html,
editor->set_readonly_mode exporting readonly_mode = 1.
endmethod.
method handle_node_double_click.
data: w_name type programm,
w_id type i,
w_year(4) type c,
w_pgmkey type t_pgmkey.
w_name = node_key+4.
w_id = w_name.
clear w_name.
read table it_pgmkey into w_pgmkey with key id = w_id
binary search.
if sy-subrc = 0.
w_name = w_pgmkey-name.
endif.
w_year = node_key(4).
if w_name is initial.
call method: fill_html,
html_viewer->set_visible exporting visible = 'X',
editor->set_visible exporting visible = ' '.
else.
call method: fill_src exporting programid = w_name,
editor->set_visible exporting visible = 'X',
html_viewer->set_visible exporting visible = ' '.
endif.
call method cl_gui_cfw=>flush.
endmethod.
method handle_picture_double_click.
call method: fill_html,
html_viewer->set_visible exporting visible = 'X',
editor->set_visible exporting visible = ' '.
call method cl_gui_cfw=>flush.
endmethod.
method fill_html.
call method html_viewer->show_url exporting url = c_myurl.
endmethod.
method fill_src.
types t_line(72) type c.
data src type table of t_line.
read report programid into src.
call method: editor->delete_text,
editor->set_text_as_r3table exporting table = src[].
endmethod.
endclass.
Data *
data this_screen type ref to screen_init.
Program execution *
load-of-program.
call screen 100.
Dialog Modules PBO *
module status_0100 output.
set pf-status 'SCREEN_100'.
set titlebar 'TIT_100'.
this_screen = screen_init=>init_screen( ).
endmodule.
Dialog Modules PAI *
module cancel input.
leave program.
endmodule.
Reward if usefull

Difference between line type and internal table?

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

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

Difference between current row and previous row in a table

Hi All,
I am having a problem with the query. Can some of please help me?
I need to get difference between current row and previous row in a table. I have a table, which have data like bellow.
TABLEX
================
Name Date Items
AAA 01-SEP-09 100
BBB 02-SEP-09 101
CCC 03-SEP-09 200
DDD 04-SEP-09 200
EEE 05-SEP-09 400
Now I need to get output like bellow...
Name Date Items Diff-Items
AAA 01-SEP-09 100 0
BBB 02-SEP-09 101 1
CCC 03-SEP-09 200 99
DDD 04-SEP-09 200 0
EEE 05-SEP-09 400 200
Can some one help me to write a query to get above results?
Please let me know if you need more information.
Thanks a lot in advance.
We are using Oracle10G(10.2.0.1.0).
Thanks
Asif

     , nvl (items - lag (items) over (order by dt), 0)like in
SQL> with test as
2 (
3 select 'AAA' name, to_date('01-SEP-09', 'dd-MON-rr') dt, 100 items from dual union all
4 select 'BBB' name, to_date('02-SEP-09', 'dd-MON-rr') dt, 101 items from dual union all
5 select 'CCC' name, to_date('03-SEP-09', 'dd-MON-rr') dt, 200 items from dual union all
6 select 'DDD' name, to_date('04-SEP-09', 'dd-MON-rr') dt, 200 items from dual union all
7 select 'EEE' name, to_date('05-SEP-09', 'dd-MON-rr') dt, 400 items from dual
8 )
9 select name
10       , dt
11       , items
12       , nvl (items - lag (items) over (order by dt), 0)
13    from test
14 ;
NAM DT             ITEMS NVL(ITEMS-LAG(ITEMS)OVER(ORDERBYDT),0)
AAA 01-SEP-09        100                                      0
BBB 02-SEP-09        101                                      1
CCC 03-SEP-09        200                                     99
DDD 04-SEP-09        200                                      0
EEE 05-SEP-09        400                                    200
SQL>

Difference between Data staging and Dimension Table ?

Difference between Data staging and Dimension Table ?

Data Staging:
Data extraction and transformation is done here.
Meaning that, if we have source data in flat file, we extract it and load into staging tables, we take care of nulls, we change datetime format etc.. and after such cleansing/transformation at then end, load it to Dim/Fact tables
Pros: Makes process simpler and easy and also we can keep track of data as we have data in staging
Cons: Staging tables need space hence need memory space
Dimension Table:
tables which describes/stores the attribute about specific objects
Below is star schema which has dimension storing information related to Product, Customer etc..
-Vaibhav Chaudhari

Hi guru's what is the difference between table and temlate in smartforms

hi guru's what is the difference between table and temlate in smartforms

Hi Vasu,
Template is used for proper allignment of data which table is used for displaying multiple data.
We can say Template is for static data and Table is for dynamic data.
Suppose we have a requirement in which we have to allign the customer address in such a way as shown below:-
Name- Vasu Company- WIPRO Location- Chennai
Desig- S/W Native - Mumbai
Then for proper allighnment we can create a template and split that into 3 columns and 2 rows and create text elements for each cell display a proper allighned data at the output.
When we include a template inside a loop it gives the same property as a table.
When we have mutiple data which is to be extended to the next page like when we display all employee details in a company we use table.
Table has 3 sections , HEADER, ITEM ,FOOTER
The header secntion will be executed once and it will loop at the item level. at the end footer will be executed.
Hope this gives u some idea..
Please reward if useful
Regards,
sunil kairam.

Difference between work area and internal tables.

Hi I wanna know the difference between work area and internal tables.
what happend if i give with out header line in internal table.
also how to assosiate work area to internal table in that scenario.

Hi Balaji..
The internal table is an ABAP runtime object which has two parts the Body and the header.
Whereas a work area cannot have a body.. It is mere a field or group of fields which can hold values at runtime..
In the SAP higher versions mySAP ERP, the use of tables with header line is made obsolete.. But there is absolutely no problem with the same..
Just think that when you define an internal table with occurs or with header line statement, the system automatically creates a workarea with this table, using which you can access the contents in the bosy of tyhe table.. You can read a record from the table body to this header or add a record in the header to the internal table body..
When you work with a table ITAB without a header line, you can not use statements like READ TABLE, APPEND, INSERT etc without giving an explicit work area..
Suppose i have an internal table like:
DATA : itab TYPE STANDARD TABLE OF t001.
This table will not have a header with it.
If you will use APPEND itab. The compilor will give error.
Here i will create a work area with same structure of the table.
DATA : e_wa TYPE t001.
Now i will write:
APPEND e_wa TO itab.
READ TABLE itab INTO e_wa WITH KEY xxxxxx
LOOP AT itab INTO e_wa... etc..
In a better approach we use Field symbols with such tables, instead of structures
FIELD-SYMBOLS: <fs_itab> TYPE t001.
So,
LOOP AT itab ASSIGNING <fs_itab>
READ TABLE itab ASSIGNING <fs_itab> etc.. However we can not use field symbols in few cases..
I hope this will help you..
Thanks and Best Regards,
Vikas Bittera.
**Points for usefull answers**

What is the difference between standard,sorted and hash table

can anyone say what is the difference between standard,sorted and hash tabl

Hi,
Standard Tables:
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Tables:
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship 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, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Tables:
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.
Regards,
Ferry Lianto

Difference between line type and table type

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

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

Difference between Info structure and Table

Hi Friends
I need to know difference between info structure and table (updating a table using a scheduled program),Which one of this is better and why?
Please help me to get the Pros and Cons of the two available approach.
Thanks
Mitesh

Hi,
No different, these are just transparent tables like any other. You can select data from them the same as any other transparent table.
Refer
https://forums.sdn.sap.com/click.jspa?searchID=4342729&messageID=1424611
https://forums.sdn.sap.com/click.jspa?searchID=4342729&messageID=3609095
Regards

Difference between Table Maintenance and SE11

Similar Messages

Maybe you are looking for