How to use table maintance generator

Hi Friends,
I wanted to add more data in predefined table. For that table maintance is allowed with restriction. So anybody will tell me how to proceed for adding more data in table.
Regards,
Salil

Hi Ajay,
Thanks for ur valuable reply. But i m unable to make entry by both ways. Suppose i m going through se11. How i can judge authorization group & function group.
I m using crm table. I dont know the authorization group for that table as well as function group. May i choose any thing by F4 & then create entries???
Regards,
Salil

Similar Messages

Add a new record in database table without using table maintance generator

Hi Expart ,
Plz. tell me how to add new record in database table without using table maintance ganerator ....give me one ex.
Regards
Bhabani

Hi,
The other way to safely handle the modification of tables is through is by programs that can be done with SE38 or SE80.
To insert into database table we use INSERT statement :
1. To insert a single line into a database table, use the following:
INSERT INTO <target> VALUES <wa>.
INSERT <target> FROM <wa>.
2. To insert a several lines into a database table, use the following:
INSERT <target> FROM TABLE <itaba>.
Or even we can use MODIFY statementas this single statement is used to insert as well as update the records of database table.
MODIFY <target> FROM <wa>.
or MODIFY <target> FROM TABLE <itab>.
thanx.
Edited by: Dhanashri Pawar on Sep 10, 2008 12:25 PM
Edited by: Dhanashri Pawar on Sep 10, 2008 12:30 PM

....how to create table maintanence generator for a z table and how to use

Hi...
3....how to create table maintanence generator for a z table and how to use that for transfering a selected records to one server to another server.
thanks and regards,
k.swaminath reddy

Hi,
Table maintanance Generator is used to manually
input values using transaction sm30.The Table Maintenance Generator is used to create table maintenance program to add, modify or delete records in the database table. This can be accessed using transaction SE54 or in SE11 using the menu Utilities->Table Maintenance Generator
<b>
Follow below steps</b>
go to se11 check table maintanance check box under
attributes tab
utilities-table maintanance Generator->
create function group and assign it under
function group input box.
also assign authorization group default &NC& .
select standard recording routine radio in table
table mainitainence generator to move table
contents to quality and production by assigning
it to request.
select maintaience type as single step.
maintainence screen as system generated numbers
this dialog box appears when you click on create
button
save and activate table
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ed2d446011d189700000e8322d00/content.htm
One step, two step in Table Maintenance Generator
Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.
Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.
please check the link for getting information about table maintenance generator !
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=use%20of%20table%20maintenance%20generator&cat=sdn_all
http://www.sapdevelopment.co.uk/tips/tips_tabmaint_tcode.htm
http://www.sap-img.com/abap/create-a-table-maintance-program-for-a-z-table.htm
Regards,
Priyanka.

How to create table.maint.generator and enduser should use using ztcode

Hi,
can any one guide me how to create table maintanence generator and after creating,enduser must use using ztcode.
any help can be appreciated.
Thanks & Regards,
Sandeep.

Hi,
Table Maintenance generator is required to do Manual entries in the Table. If the requirement is to update the table only programmatically and not manually then table maint. generator is not required.
Manual entries in table can be maintained ( New record can be inserted / existing can be modified ) using transaction SM 30, if the table maintenance for the table is generated.
How to activate Table maint.
Goto SE11 and open the table.
Click UTILITIES -> Table Maint. Generator, Enter the details and click on Save. Then activate the table.
chk a sample 1.
refer.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/abap/how%20to%20implement%20events%20in%20table%20maintenance.doc
some more helps
Check out this thread:
table maintenance
http://help.sap.com/saphelp_erp2005/helpdata/en/a7/513520407a11d1893b0000e8323c4f/frameset.htm - a link for basics on Table Maintenance.
Also, Check out this weblog on table maintenance:
/people/sudheer.cheedella/blog/2006/02/20/extracting-data-in-table-maintenance
<b>how to create a a T-code of that</b>
Go to se93.
Then create the new T.code.
Under that select parameter Transaction.
Then give the sm30 in the t.code in default values tab.
check the checkbox skip initial screen.
in classification tab.
click checkbox inherit gui attributes..
Now below..
In the default values..
WRITE
viewname = give ur table name.
show = X
save and check it once...
now u can able to call ur table through ur new t.code...
rgds
anver
if hlped pls mark points

Reg : Tcode for table maintance generator

Hello,
I have created the Tcode for Table maintance generator of a table using SE93 which directly goes to the table maintaince generator. My requirement is if i open the tcode i need to display the custom selection screen before going to the table maintaince generator. How do i do it. please can give me the steps to fulfil the above req.
regards
haritha

Check below thread will be useful to you.
Re: Sending Payment Advice as Email to Vendors
For more information:
Search sdn with key words tcode + table maintainence generator
Regards

How to use table control in LSMW

Hello All,
I have requirement to use LSMW , in my using transaction have table control ,I need to pass values in table control . how to use table control in LSMW .Can any one give me the solution for this.
Best regards,
Satya.

Note: The recording function records a fixed screen sequence. It cannot be used for migrating data containing a variable number of items or for transactions with dynamic screen sequences!
Tip: It is possible to create a recording via SHDB, generate a program out of this recording, and adopt the program to your needs and registrate the program to be able to use it in LSMW.
Thats means, for creation of project and WBS Elements is not possible through
1. LSMW-BDC (For both CJ01 and CJ20n)
2. LSMW-BAPI (Method: Maintain is not listed )
3. LSME-Standard Batch Direct Input.
Its possible through programmatically(SE38.) either using BAPI Or BDC.
Thanks,

Regarding table maintance generator

hi experts,
when ever i use sm30 for the particular table for feeding the data it si showing this error:::: The maintenance dialog for YHREMPSUBGRP is incomplete or not defined..what is the reason behind this as i already activated the function group zsap_hr_incv which i m using in the table maintance generator for the table yhrempsubgrp.,,plz help me.

Hi Ravi,
Did you finished, the following steps? Please check again.
go to se11 check table maintanance check box under
attributes tab
utilities-table maintanance Generator->
create function group and assign it under
function group input box.
also assign authorization group default &NC& .
select standard recording routine radio in table
table mainitainence generator to move table
contents to quality and production by assigning
it to request.
select maintaience type as single step.
maintainence screen as system generated numbers
this dialog box appears when you click on create
button
save and activate table
Thanks,

How to create table maintainenece Generator

hi all
       I dont know how to create table maintainence generator after creating the table.
I have created the table.
After that how to maintain the table.
What is the use of table maintainence generator.
Thanks

Hi Muthu,
Through table maintenance you can direct add new entries in your table. For that u need to follow some steps.
Step1 : Click Delivery and Maintenance tab in your table and select "Display/Maintenance Allowed"
Step2 : Utilities--->Table maint generator
Step3 : Give Authorization Group - &NC&
Step4 : Function group - Any ( You can give ur table name also ) This Function Group will genrate automatically.
Step5 : Maintenance type - Select first radio button "One Step"
Step6 : Maint. Screen No. - Overview screen as 1
                                              Single screen       as 0
Step7 : Click on Create button on application tool bar
Step8 : just save in your package.
Step8 : Create transaction code for the same . Environment----->transaction code
Step9 : Give any t.code name and click on create button. You will get a popup where you have to choose last radio button "Transaction with parameter"
Step10 : Give the transaction name - SM30 and check Inherit GUI Attribute"
Step11 : GUI Support - check all the check boxes.
Step12 : Name of screen field           Values
                VIEWNAME -                   Table name and
                UPDATE      -                      X
Finally u can this t.code and add new entries in ur table directly.
Regards,
Amit Nanda
SAP Consultant

How to use Table valued MSSQL function in OBIEE

Hi all,
Can some one help me to understand how to use table valued function in OBIEE? I want to use a table valued function (MSSQL function, with some input parameter), in the physical layer to pull the data?
I know for MSSQL Stored Procedure we can write as
EXEC SP_NAME @Parameter = 'VLUEOF(NQ_SESSION.Variablename)'
but now I have a table valued function in the query window I can get the data as
select * from myfunction(parametervalue)
In physical layer of OBIEE I have tried as
select * from myfunction('VLUEOF(NQ_SESSION.Variablename)'), but I'm getting error as the NQ_SESSION variable doesn't have a value , but actually I have initialized the variable but still Im getting error.
Can some one help me to solve this.
Thanks,
Mithun

Follow this link and try yourself. let me know for issues
Substring instr issue in obiee
Appreciate if you mark
Edited by: Srini VEERAVALLI on Feb 20, 2013 8:13 AM

How to use table control in bdc, plz somebody tell me.

Hi Gurus,
Ples tell me
how to use table control in bdc, plz somebody tell me.
And send Sample CODE also. Thnaks in advance.

hi,
Table control / step loop in BDC
Steploop and table contol is inevitable in certain transactions. When we run BDC for such transactions, we will face the situation: how many visible lines of steploop/tablecontrol are on the screen?
Although we can always find certain method to deal with it, such as function code 'NP', 'POPO', considering some extreme situation: there is only one line visible one the screen, our BDC program should display an error message. (See transaction 'ME21', we you resize your screen to let only one row visible, you can not enter mutiple lines on this screen even you use 'NP')
we can determine the number of visible lines on Transaction Screen from our Calling BDC program.
Demo ABAP code has two purposes:
1. how to determine number of visible lines and how to calculte page number;
(the 'calpage' routine has been modify to meet general purpose usage)
2. using field symbol in BDC program, please pay special attention to the difference
in Static ASSIGN and Dynamic ASSIGN.
Step1: go to screen painter to display the screen 121, then we can count the fixed line on this screen, there is 7 lines above the steploop and 2 lines below the steploop, so there are total 9 fixed lines on this screen. This means except these 9 lines, all the other line is for step loop.
Then have a look at steploop itselp, one entry of it will occupy two lines.
(Be careful, for table control, the head and the bottom scroll bar will possess another two fixed lines, and there is a maximum number for table line)
Now we have : FixedLine = 9
LoopLine = 2(for table control, LoopLine is always equal to 1)
Step2: go to transaction itself(ME21) to see how it roll page, in ME21, the first line of new page is always occupied by the last line of last page, so it begin with index '02', but in some other case, fisrt line is empty and ready for input.
Now we have: FirstLine = 0
or FirstLine = 1 ( in our case, FirstLine is 1 because the first line of new page is fulfilled)
Step3: write a subroutine calcalculating number of pages
(here, the name of actual parameter is the same as formal parameter)
global data: FixedLine type i, " number of fixed line on a certain screen
LoopLine type i, " the number of lines occupied by one steploop item
FirstLine type i, " possbile value 0 or 1, 0 stand for the first line of new " scrolling screen is empty, otherwise is 1
Dataline type i, " number of items you will use in BDC, using DESCRIBE to get
pageno type i, " you need to scroll screen how many times.
line type i, " number of lines appears on the screen.
index(2) type N, " the screen index for certain item
begin type i, " from parameter of loop
end type i. " to parameter of loop
*in code sample, the DataTable-linindex stands for the table index number of this line
form calpage using FixedLine type i (see step 1)
LoopLine type i (see step 1)
FirstLine type i (see step 2)
DataLine type i ( this is the item number you will enter in transaction)
changing pageno type i (return the number of page, depends on run-time visible line in table control/ Step Loop)
changing line type i.(visible lines one the screen)
data: midd type i,
vline type i, "visible lines
if DataLine eq 0.
Message eXXX.
endif.
vline = ( sy-srows - FixedLine ) div LoopLine.
*for table control, you should compare vline with maximum line of
*table control, then take the small one that is min(vline, maximum)
*here only illustrate step loop
if FirstLine eq 0.
pageno = DataLine div vline.
if pageno eq 0.
pageno = pageno + 1.
endif.
elseif FirstLine eq 1.
pageno = ( DataLine - 1 ) div ( vline - 1 ) + 1.
midd = ( DataLine - 1 ) mod ( vline - 1).
if midd = 0 and DataLine gt 1.
pageno = pageno - 1.
endif.
endif.
line = vline.
endform.
Step4 write a subroutine to calculate the line index for each item.
form calindex using Line type i (visible lines on the screen)
FirstLine type i(see step 2)
LineIndex type i(item index)
changing Index type n. (index on the screen)
if FirstLine = 0.
index = LineIndex mod Line.
if index = '00'.
index = Line.
endif.
elseif FirstLine = 1.
index = LineIndex mod ( Line - 1 ).
if ( index between 1 and 0 ) and LineIndex gt 1.
index = index + Line - 1.
endif.
if Line = 2.
index = index + Line - 1.
endif.
endif.
endform.
Step5 write a subroutine to calculate the loop range.
form calrange using Line type i ( visible lines on the screen)
DataLine type i
FirstLine type i
loopindex like sy-index
changing begin type i
end type i.
If FirstLine = 0.
if loopindex = 1.
begin = 1.
if DataLine <= Line.
end = DataLine.
else.
end = Line.
endif.
elseif loopindex gt 1.
begin = Line * ( loopindex - 1 ) + 1.
end = Line * loopindex.
if end gt DataLine.
end = DataLine.
endif.
endif.
elseif FirstLine = 1.
if loopindex = 1.
begin = 1.
if DataLine <= Line.
end = DataLine.
else.
end = Line.
endif.
elseif loop index gt 1.
begin = ( Line - 1 ) * ( loopindex - 1 ) + 2.
end = ( Line - 1 ) * ( loopindex - 1 ) + Line.
if end gt DataLine.
end = DataLine.
endif.
endif.
endif.
endform.
Step6
using field sysbol in your BDC, for example: in ME21, but you should calculate each item will correponding to which index in steploop/Table Control
form creat_bdc.
field-symbols: , , .
data: name1(14) value 'EKPO-EMATN(XX)',
name2(14) value 'EKPO-MENGE(XX)',
name3(15) value 'RM06E-SELKZ(XX)'.
assign: name1 to ,
name2 to ,
name3 to .
do pageno times.
if sy-index gt 1
*insert scroll page ok_code"
endif.
perform calrange using Line DataLine FirstLine sy-index
changing begin end.
loop at DataTable from begin to end.
perform calindex using Line FirstLine DataTable-LineIndex changing Index.
name1+11(2) = Index.
name2+11(2) = Index.
name3+12(2) = Index.
perform bdcfield using DataTable-matnr.
perform bdcfield using DataTable-menge.
perform bdcfield using DataTable-indicator.
endloop.
enddo.
example 1
BDC table control is an area on the screen in which you can display data in tabular form. You process it using a loop. Table controls are comparable to step loop tables. While a table control consists of a single definition row, step loop blocks may extend over more than one row. Table controls are more flexible than step loops, and are intended to replace them
When you need to handle a scenario like in sales order,it may contain more than one material,if you have more than one material We have to use table control,it will have number of columns and number of rows.
Table controls allow you to enter, display, and modify tabular data easily on the screen
Check this code,
PARAMETERS: file1 LIKE rlgrap-filename.
*Internal Table Declarations
DATA: BEGIN OF itab OCCURS 0,
matnr(18) TYPE c, "MaterialNumber
werks(4) TYPE c, "Plant
vdatu(10) TYPE c, "Valid From Date
bdatu(10) TYPE c, "Valid To Date
lifnr(10) TYPE c, "Vendor Number
ekorg(4) TYPE c, "Purchasing Organization
feskz TYPE c, "Fixed
autet TYPE c, "MRP Indicator
END OF itab.
DATA: bdcdata LIKE TABLE OF bdcdata WITH HEADER LINE.
*VARIABLES Declarations
DATA: wa1 LIKE LINE OF itab. "Workarea for ITAB
DATA: n TYPE i, "Check
count TYPE i.
DATA: cnt(2), "Counter
wa(15). "Workarea to hold concatenatedvalue
DATA v_msg(100).
DATA: flag.
DATA: file TYPE string.
*Initialization event
INITIALIZATION.
*At-selection-screen event
*To provide Input help for file name
AT SELECTION-SCREEN ON VALUE-REQUEST FOR file1.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
IMPORTING
file_name = file1.
*START-OF-SELECTION EVENT
START-OF-SELECTION.
MOVE file1 TO file.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = file
filetype = 'ASC'
has_field_separator = 'X'
TABLES
data_tab = itab
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
*To populate BDCDATA and start data transfer
LOOP AT itab .
To validate Plant range
IF itab-werks = '1000' OR itab-werks = '2000'
OR itab-werks = '1008'.
AT NEW werks.
CLEAR: n.
cnt = 1.
PERFORM bdc_dynpro USING 'SAPLMEOR' '0200'.
PERFORM bdc_field USING 'BDC_CURSOR'
'EORD-MATNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'EORD-MATNR'
itab-matnr.
PERFORM bdc_field USING 'EORD-WERKS'
itab-werks.
PERFORM bdc_dynpro USING 'SAPLMEOR' '0205'.
CONCATENATE 'EORD-EKORG(' cnt ')' INTO wa.
PERFORM bdc_field USING 'BDC_CURSOR'
wa.
PERFORM bdc_field USING 'BDC_OKCODE'
'=BU'.
ENDAT.
IF n = 12.
READ TABLE bdcdata WITH KEY fval = '=BU'.
bdcdata-fval = '=NS'.
MODIFY bdcdata INDEX sy-tabix TRANSPORTING fval.
PERFORM bdc_dynpro USING 'SAPLMEOR' '0205'.
PERFORM bdc_field USING 'BDC_CURSOR'
'EORD-VDATU(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=BU'.
cnt = 2.
n = 2.
ENDIF.
CONCATENATE 'EORD-VDATU(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-vdatu.
CONCATENATE 'EORD-BDATU(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-bdatu.
CONCATENATE 'EORD-LIFNR(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-lifnr.
CONCATENATE 'EORD-EKORG(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-ekorg.
CONCATENATE 'RM06W-FESKZ(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-feskz.
CONCATENATE 'EORD-AUTET(' cnt ')' INTO wa.
PERFORM bdc_field USING wa
itab-autet.
IF n <> 12.
n = cnt.
ENDIF.
cnt = cnt + 1.
AT END OF werks.
CALL TRANSACTION 'ME01' USING bdcdata
UPDATE 'S'
MODE 'A'.
CLEAR:bdcdata,bdcdata[].
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
id = sy-msgid
lang = 'EN'
no = sy-msgno
v1 = sy-msgv1
v2 = sy-msgv2
v3 = sy-msgv3
v4 = sy-msgv4
IMPORTING
msg = v_msg.
WRITE:/ v_msg.
CLEAR: bdcdata,bdcdata[],flag.
ENDAT.
ENDIF.
ENDLOOP.
Start new screen *
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
ENDFORM.
Insert field values
FORM bdc_field USING fnam fval.
IF NOT fval IS INITIAL.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDIF.
CLEAR wa.
ENDFORM.
Sample code 2
THis is example to upload the Bank details of the Vendor which has the TC.
REPORT zprataptable2
NO STANDARD PAGE HEADING LINE-SIZE 255.
DATA : BEGIN OF itab OCCURS 0,
i1 TYPE i,
lifnr LIKE rf02k-lifnr,
bukrs LIKE rf02k-bukrs,
ekorg LIKE rf02k-ekorg,
ktokk LIKE rf02k-ktokk,
anred LIKE lfa1-anred,
name1 LIKE lfa1-name1,
sortl LIKE lfa1-sortl,
land1 LIKE lfa1-land1,
akont LIKE lfb1-akont,
fdgrv LIKE lfb1-fdgrv,
waers LIKE lfm1-waers,
END OF itab.
DATA : BEGIN OF jtab OCCURS 0,
j1 TYPE i,
banks LIKE lfbk-banks,
bankl LIKE lfbk-bankl,
bankn LIKE lfbk-bankn,
END OF jtab.
DATA : cnt(4) TYPE n.
DATA : fdt(20) TYPE c.
DATA : c TYPE i.
INCLUDE bdcrecx1.
START-OF-SELECTION.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
filename = 'C:\first1.txt'
filetype = 'DAT'
TABLES
data_tab = itab.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
filename = 'C:\second.txt'
filetype = 'DAT'
TABLES
data_tab = jtab.
LOOP AT itab.
PERFORM bdc_dynpro USING 'SAPMF02K' '0100'.
PERFORM bdc_field USING 'BDC_CURSOR'
'RF02K-KTOKK'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'RF02K-LIFNR'
itab-lifnr.
PERFORM bdc_field USING 'RF02K-BUKRS'
itab-bukrs.
PERFORM bdc_field USING 'RF02K-EKORG'
itab-ekorg.
PERFORM bdc_field USING 'RF02K-KTOKK'
itab-ktokk.
PERFORM bdc_dynpro USING 'SAPMF02K' '0110'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFA1-LAND1'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'LFA1-ANRED'
itab-anred.
PERFORM bdc_field USING 'LFA1-NAME1'
itab-name1.
PERFORM bdc_field USING 'LFA1-SORTL'
itab-sortl.
PERFORM bdc_field USING 'LFA1-LAND1'
itab-land1.
PERFORM bdc_dynpro USING 'SAPMF02K' '0120'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFA1-KUNNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0130'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFBK-BANKN(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ENTR'.
cnt = 0.
LOOP AT jtab WHERE j1 = itab-i1.
cnt = cnt + 1.
CONCATENATE 'LFBK-BANKS(' cnt ')' INTO fdt.
PERFORM bdc_field USING fdt jtab-banks.
CONCATENATE 'LFBK-BANKL(' cnt ')' INTO fdt.
PERFORM bdc_field USING fdt jtab-bankl.
CONCATENATE 'LFBK-BANKN(' cnt ')' INTO fdt.
PERFORM bdc_field USING fdt jtab-bankn.
IF cnt = 5.
cnt = 0.
PERFORM bdc_dynpro USING 'SAPMF02K' '0130'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFBK-BANKS(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=P+'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0130'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFBK-BANKN(02)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ENTR'.
ENDIF.
ENDLOOP.
PERFORM bdc_dynpro USING 'SAPMF02K' '0130'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFBK-BANKS(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ENTR'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0210'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFB1-FDGRV'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'LFB1-AKONT'
itab-akont.
PERFORM bdc_field USING 'LFB1-FDGRV'
itab-fdgrv.
PERFORM bdc_dynpro USING 'SAPMF02K' '0215'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFB1-ZTERM'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0220'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFB5-MAHNA'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_dynpro USING 'SAPMF02K' '0310'.
PERFORM bdc_field USING 'BDC_CURSOR'
'LFM1-WAERS'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'LFM1-WAERS'
itab-waers.
PERFORM bdc_dynpro USING 'SAPMF02K' '0320'.
PERFORM bdc_field USING 'BDC_CURSOR'
'RF02K-LIFNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=ENTR'.
PERFORM bdc_dynpro USING 'SAPLSPO1' '0300'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=YES'.
PERFORM bdc_transaction USING 'XK01'.
ENDLOOP.
PERFORM close_group.
Header file:
1 63190 0001 0001 0001 mr bal188 b in 31000 a1 inr
2 63191 0001 0001 0001 mr bal189 b in 31000 a1 inr
TC file:
1 in sb 11000
1 in sb 12000
1 in sb 13000
1 in sb 14000
1 in sb 15000
1 in sb 16000
1 in sb 17000
1 in sb 18000
1 in sb 19000
1 in sb 20000
1 in sb 21000
1 in sb 22000
2 in sb 21000
2 in sb 22000
Regards

How to use table control in bdc briefly?

how to use table control in bdc briefly in description manner ?

Hi friend,
here i am giving exm. code of table control.see if help full to u.
REPORT zxk_01
       NO STANDARD PAGE HEADING LINE-SIZE 255.
include bdcrecx1.
TYPES : BEGIN OF ty_data,
       line(100) TYPE c,
       END OF ty_data.
PARAMETERS: p_pcfile   LIKE ibipparms-path DEFAULT 'D:\NKS.TXT'.
DATA : g_filename    TYPE string.
TYPES : BEGIN OF ty_file,
        lifnr(16) TYPE c,                             " vendor
        bukrs(4) TYPE c,                             "company code
        ktokk(4)   TYPE c,                             " Acc grp
        anred(15) TYPE c,                             " Title
        name1(35) TYPE c,                             " name
        sortl(10) TYPE c,                             " search term
        stras(35) TYPE c,                             " street
        ort01(35) TYPE c,                             " city
        ort02(35) TYPE c,                             " district
        land1(3) TYPE c,                              " country
        pfach(10) TYPE c,                             " PO BOx
        spras(2) TYPE c,                             " language
        kunnr(10) TYPE c,                             " Customer
        vbund(6) TYPE c,                              " trading partner
        banks(3) TYPE c,                              " BANK COUNTRY
        bankl(15) TYPE c,                             " BANK KEY
        bankn(18) TYPE c,                             " BANK ACC
        koinh(60) TYPE c,                             " ACC HOLDER
        bkont(2) TYPE c,                              " CK
        bvtyp(4) TYPE c,                              " BNKT
        bkref(20) TYPE c,                             " REFERENCE DETAILS
        namev(35)   TYPE c,                                 " first NAME
        name2(35)   TYPE c,                                 " NAME
        telf1(16) TYPE c,                                   " TELEPHONE
        abtnr(4) TYPE c,                                   " DEPTT
        pafkt(2) TYPE c,                                   " FUNCTION
        akont(10) TYPE c,                             " REC ACCOUNT
        zuawa(3) TYPE c,                             " SORT KEY
        lnrze(10) TYPE c,                             "HEAD OFFICE
        fdgrv(10) TYPE c,                             " CASH MGMT GRP,
        frgrp(4) TYPE c,                             " RELEASE GRP
        zterm(4) TYPE c,                             " PAY TERMS
        togru(4) TYPE c,                             " TOLERENCE GRP,
        reprf,                                        "CHECK DOUBLE INV
        zwels(10) TYPE c,                            " PAYMENTS METHODS
        zahls,                                       " PAYMENTS BLOCK
        hbkid(5) TYPE c,                             " house bank
        zgrup(2) TYPE c,                             " grouping key
        mahna(4) TYPE c,                             " dunn procedure
        mansp,                                       " DUNNING BLOCK'
        gmvdt(10) TYPE c,                            " LEGAL DONE PROCEDURE
        lfrma(10) TYPE c,                            " DUNN RECEPIENT
        madat(10) TYPE c,                            " LAST DUNNED
        mahns(1) TYPE c,                         " dunning level
        mgrup(2) TYPE c,                            " grouping key
        busab(2) TYPE c,                             "dunning clerk
       END OF ty_file.
DATA : BEGIN OF it_xk01 OCCURS 0,
       lifnr(16) TYPE c,                             " vendor
       bukrs(4) TYPE c,                             "company code
       ktokk(4)   TYPE c,                             " Acc grp
       anred(15) TYPE c,                             " Title
       name1(35) TYPE c,                             " name
       sortl(10) TYPE c,                             " search term
       stras(35) TYPE c,                             " street
       ort01(35) TYPE c,                             " city
       ort02(35) TYPE c,                             " district
       land1(3) TYPE c,                              " country
       pfach(10) TYPE c,                             " PO BOx
       spras(2) TYPE c,                             " language
       kunnr(10) TYPE c,                             " Customer
       vbund(6) TYPE c,                              " trading partner
       akont(10) TYPE c,                             " REC ACCOUNT
       zuawa(3) TYPE c,                             " SORT KEY
       lnrze(10) TYPE c,                             "HEAD OFFICE
       fdgrv(10) TYPE c,                             " CASH MGMT GRP,
       frgrp(4) TYPE c,                             " RELEASE GRP
       zterm(4) TYPE c,                             " PAY TERMS
       togru(4) TYPE c,                             " TOLERENCE GRP,
       reprf,                                        "CHECK DOUBLE INV
       zwels(10) TYPE c,                            " PAYMENTS METHODS
       zahls,                                       " PAYMENTS BLOCK
       hbkid(5) TYPE c,                             " house bank
       zgrup(2) TYPE c,                             " grouping key
       mahna(4) TYPE c,                             " dunn procedure
       mansp,                                       " DUNNING BLOCK'
       gmvdt(10) TYPE c,                            " LEGAL DONE PROCEDURE
       lfrma(10) TYPE c,                            " DUNN RECEPIENT
       madat(10) TYPE c,                            " LAST DUNNED
       mahns(1) TYPE c,                         " dunning level
       mgrup(2) TYPE c,                            " grouping key
       busab(2) TYPE c,                             "dunning clerk
       END OF it_xk01.
     internal table for bank detaiils
DATA : BEGIN OF it_bank OCCURS 0,
       banks(3) TYPE c,                              " BANK COUNTRY
       bankl(15) TYPE c,                             " BANK KEY
       bankn(18) TYPE c,                             " BANK ACC
       koinh(60) TYPE c,                             " ACC HOLDER
       bkont(2) TYPE c,                              " CK
       bvtyp(4) TYPE c,                              " BNKT
       bkref(20) TYPE c,                             " REFERENCE DETAILS
       lifnr(16) TYPE c,                             " vendor
      xezer,                                        " CHECK
       END OF it_bank.
INTERNAL TABLE FOR CONTACT PERSON
TYPES : BEGIN OF ty_cust,
       lifnr(16) TYPE c,
       namev(35)   TYPE c,                                 " first NAME
       name1(35)   TYPE c,                                 " NAME
       telf1(16) TYPE c,                                   " TELEPHONE
       abtnr(4) TYPE c,                                   " DEPTT
       pafkt(2) TYPE c,                                   " FUNCTION
       END OF ty_cust.
INTERNAL TABLES DECLARATION
DATA : it_bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE,
       it_bdcmsgcoll LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE,
       it_file TYPE TABLE OF ty_file,
       it_data TYPE TABLE OF ty_data,
       it_cust TYPE TABLE OF ty_cust.
   WORK AREAS FOR TYPES
DATA : wa_xk01 LIKE it_xk01,
       wa_data TYPE ty_data,
       wa_file TYPE ty_file,
       wa_bank LIKE it_bank,
       wa_cust TYPE ty_cust.
*CALL METHOD cl_gui_frontend_services=>gui_upload
   EXPORTING
     filename = lt_file
     filetype = 'ASC'
   CHANGING
     data_tab = iT_DATA.
IF sy-subrc <> 0.
ENDIF.
g_filename = p_pcfile.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    filename                      = g_filename "'D:\TESTDATA1_XK01.txt'
   filetype                      = 'TXT'
    has_field_separator           = 'X'
HEADER_LENGTH                 = 0
   read_by_line                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
    replacement                   = ' '
CHECK_BOM                     = ' '
VIRUS_SCAN_PROFILE            =
NO_AUTH_CHECK                 = ' '
IMPORTING
FILELENGTH                    =
HEADER                        =
TABLES
    data_tab                      = it_file
EXCEPTIONS
   file_open_error               = 1
   file_read_error               = 2
   no_batch                      = 3
   gui_refuse_filetransfer       = 4
   invalid_type                  = 5
   no_authority                  = 6
   unknown_error                 = 7
   bad_data_format               = 8
   header_not_allowed            = 9
   separator_not_allowed         = 10
   header_too_long               = 11
   unknown_dp_error              = 12
   access_denied                 = 13
   dp_out_of_memory              = 14
   disk_full                     = 15
   dp_timeout                    = 16
   OTHERS                        = 17
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT it_file INTO wa_file .
ON CHANGE OF WA_FILE-LIFNR.
wa_xk01-lifnr =   wa_file-lifnr.
wa_xk01-bukrs =   wa_file-bukrs.
wa_xk01-ktokk =   wa_file-ktokk.
wa_xk01-anred = wa_file-anred.
wa_xk01-name1 = wa_file-name1.
wa_xk01-sortl = wa_file-sortl.
wa_xk01-stras = wa_file-stras.
wa_xk01-ort01 = wa_file-ort01.
wa_xk01-ort02 = wa_file-ort02.
wa_xk01-land1 = wa_file-land1.
wa_xk01-pfach = wa_file-pfach.
wa_xk01-spras = wa_file-spras.
wa_xk01-kunnr = wa_file-kunnr.
wa_xk01-vbund = wa_file-vbund.
wa_xk01-akont = wa_file-akont.
wa_xk01-zuawa = wa_file-zuawa.
wa_xk01-lnrze = wa_file-lnrze.
wa_xk01-fdgrv = wa_file-fdgrv.
wa_xk01-frgrp = wa_file-frgrp.
wa_xk01-zterm = wa_file-zterm.
wa_xk01-togru = wa_file-togru.
wa_xk01-reprf = wa_file-reprf.
wa_xk01-zwels = wa_file-zwels.
wa_xk01-zahls = wa_file-zahls.
wa_xk01-hbkid = wa_file-hbkid.
wa_xk01-zgrup = wa_file-zgrup.
wa_xk01-mahna = wa_file-mahna.
wa_xk01-mansp = wa_file-mansp.
wa_xk01-gmvdt = wa_file-gmvdt.
wa_xk01-lfrma = wa_file-lfrma.
wa_xk01-madat = wa_file-madat.
wa_xk01-mahns = wa_file-mahns.
wa_xk01-mgrup = wa_file-mgrup.
wa_xk01-busab = wa_file-busab.
   APPEND wa_xk01 TO it_xk01.
   CLEAR : WA_XK01.
CONTINUE.
   ENDON.
IF WA_FILE-BANKS NE ''.
wa_bank-lifnr = wa_file-lifnr.
wa_bank-banks = wa_file-banks.
wa_bank-bankl = wa_file-bankl.
wa_bank-bankn = wa_file-bankn.
wa_bank-koinh = wa_file-koinh.
wa_bank-bkont = wa_file-bkont.
wa_bank-bvtyp = wa_file-bvtyp.
wa_bank-bkref = wa_file-bkref.
wa_cust-lifnr = wa_file-lifnr.
wa_cust-namev = wa_file-namev.
wa_cust-name1 = wa_file-name2.
wa_cust-telf1 = wa_file-telf1.
wa_cust-abtnr = wa_file-abtnr.
wa_cust-pafkt = wa_file-pafkt.
APPEND wa_bank TO it_bank.
APPEND wa_cust TO it_cust.
APPEND wa_xk01 TO it_xk01.
CLEAR : wa_bank , wa_cust.
ENDIF.
ENDLOOP.
START-OF-SELECTION.
LOOP AT it_xk01 INTO wa_xk01.
    REFRESH it_bdcdata.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0100'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RF02K-KTOKK'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'RF02K-LIFNR'
                                   wa_xk01-lifnr.                                        " vendor
    PERFORM bdc_field       USING 'RF02K-BUKRS'
                                  wa_xk01-bukrs.                                        " company cpode
    PERFORM bdc_field       USING 'RF02K-KTOKK'
                                  wa_xk01-ktokk.                                        " Acc group
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0110'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFA1-SPRAS'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'LFA1-ANRED'
                                  wa_xk01-anred.                                          " title
    PERFORM bdc_field       USING 'LFA1-NAME1'
                                  wa_xk01-name1.                                        " name
    PERFORM bdc_field       USING 'LFA1-SORTL'
                                  wa_xk01-sortl.                                       " ' search term'
    PERFORM bdc_field       USING 'LFA1-STRAS'
                                  wa_xk01-stras.                                    "street'
    PERFORM bdc_field       USING 'LFA1-PFACH'
                                  wa_xk01-pfach.                                     " po box
    PERFORM bdc_field       USING 'LFA1-ORT01'
                                  wa_xk01-ort01.                                  " city
    PERFORM bdc_field       USING 'LFA1-ORT02'
                                  wa_xk01-ort02.                                       " district
    PERFORM bdc_field       USING 'LFA1-LAND1'
                                  wa_xk01-land1.                                         " country
    PERFORM bdc_field       USING 'LFA1-SPRAS'
                                  wa_xk01-spras.                                         " language
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0120'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFA1-VBUND'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'LFA1-KUNNR'                                   " customer
                                  wa_xk01-kunnr.
    PERFORM bdc_field       USING 'LFA1-VBUND'
                                  wa_xk01-vbund.                                       " trading partner
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFBK-BKREF(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ENTR'.
    DATA : fnam(20) TYPE c,
           int      TYPE c.
    MOVE 1 TO int.
    CLEAR wa_bank.
    LOOP AT it_bank INTO wa_bank WHERE lifnr = wa_xk01-lifnr.
      CONCATENATE 'LFBK-BANKS(' int ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                    wa_bank-banks.                                           " city
      CONCATENATE 'LFBK-BANKL(' int ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                    wa_bank-bankl.
      CONCATENATE 'LFBK-BANKN(' int ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                    wa_bank-bankn.
      CONCATENATE 'LFBK-KOINH(' int ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                    wa_bank-koinh.
      CONCATENATE 'LFBK-BKONT(' int ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                    wa_bank-bkont.
      CONCATENATE 'LFBK-BVTYP(' int ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                    wa_bank-bvtyp.
      CONCATENATE 'LFBK-BKREF(' int ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                   wa_bank-bkref.
      int = int + 1.
    ENDLOOP.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0130'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFBK-BANKS(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ENTR'.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0380'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'KNVK-PAFKT(05)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ENTR'.
    DATA : fnam1(20) TYPE c,
           cnt.
    cnt = 1.
    CLEAR : wa_cust.
    LOOP AT it_cust INTO wa_cust WHERE lifnr = wa_xk01-lifnr.
      CONCATENATE 'KNVK-NAMEV(' cnt ')' INTO fnam1.
      PERFORM bdc_field       USING fnam1
                                    wa_cust-namev.
      CONCATENATE 'KNVK-NAME1(' cnt ')' INTO fnam1.
      PERFORM bdc_field       USING fnam1
                                     wa_cust-name1.
      CONCATENATE 'KNVK-TELF1(' cnt ')' INTO fnam1.
      PERFORM bdc_field       USING fnam1
                                    wa_cust-telf1.
      CONCATENATE 'KNVK-ABTNR(' cnt ')' INTO fnam1.
      PERFORM bdc_field       USING fnam1
                                   wa_cust-abtnr.
      CONCATENATE 'KNVK-PAFKT(' cnt ')' INTO fnam1.
      PERFORM bdc_field       USING fnam1
                                    wa_cust-pafkt.
      cnt = cnt + 1.
    ENDLOOP.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0380'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'KNVK-NAMEV(01)'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=ENTR'.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0210'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFB1-FRGRP'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'LFB1-AKONT'
                                  wa_xk01-akont.                           " REC aCC
    PERFORM bdc_field       USING 'LFB1-ZUAWA'
                                   wa_xk01-zuawa.                                " SORT KEY
    PERFORM bdc_field       USING 'LFB1-LNRZE'
                                   wa_xk01-lnrze.                            " HEAD OFFICE
    PERFORM bdc_field       USING 'LFB1-FDGRV'
                                  wa_xk01-fdgrv.                              " CASH MGMT GRP
    PERFORM bdc_field       USING 'LFB1-FRGRP'
                                  wa_xk01-frgrp.                          " RELEASE GRP
    PERFORM bdc_field       USING 'LFB1-CERDT'
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0215'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFB1-ZGRUP'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'LFB1-ZTERM'
                                  wa_xk01-zterm.                            " PAYMENT TERMS'
    PERFORM bdc_field       USING 'LFB1-TOGRU'
                                   wa_xk01-togru.                            " TOLERENCE GRP
    PERFORM bdc_field       USING 'LFB1-REPRF'
                                   wa_xk01-reprf.                                " CHECK DOUBLE INV
    PERFORM bdc_field       USING 'LFB1-ZWELS'
                                   wa_xk01-zwels.                            " PAYMENT METHOD
    PERFORM bdc_field       USING 'LFB1-ZAHLS'
                                   wa_xk01-zahls.                                " PAYMENT BLOCK
    PERFORM bdc_field       USING 'LFB1-HBKID'
                                   wa_xk01-hbkid.                             " HOUSE BANK
    PERFORM bdc_field       USING 'LFB1-ZGRUP'
                                   wa_xk01-zgrup.                              " GROUPING KEY
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0220'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFB5-BUSAB'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'LFB5-MAHNA'
                                   wa_xk01-mahna.                           " DUNN PROCEDURE
    PERFORM bdc_field       USING 'LFB5-MANSP'
                                   wa_xk01-mansp.                              " DUNNING BLOCK
    PERFORM bdc_field       USING 'LFB5-LFRMA'
                                   wa_xk01-lfrma.                        " Dunn representative
    PERFORM bdc_field       USING 'LFB5-GMVDT'
                                   wa_xk01-gmvdt.                      " legal dunn proc
    PERFORM bdc_field       USING 'LFB5-MADAT'
                                   wa_xk01-madat.                      " last dunned
    PERFORM bdc_field       USING 'LFB5-MAHNS'
                                   wa_xk01-mahns.                               " dunn level
    PERFORM bdc_field       USING 'LFB5-BUSAB'
                                   wa_xk01-busab.                             " dunning clerk
    PERFORM bdc_field       USING 'LFB1-MGRUP'
                                   wa_xk01-mgrup.                             " grouping key
    CALL TRANSACTION 'XK01' USING it_bdcdata
                           MODE 'A'.
ENDLOOP.
Start new screen *
FORM bdc_dynpro USING program dynpro.
CLEAR it_bdcdata.
it_bdcdata-program = program.
it_bdcdata-dynpro = dynpro.
it_bdcdata-dynbegin = 'X'.
APPEND it_bdcdata.
ENDFORM.                    "BDC_DYNPRO
Insert field
FORM bdc_field USING fnam fval TYPE any.
CLEAR it_bdcdata.
it_bdcdata-fnam = fnam.
it_bdcdata-fval = fval.
APPEND it_bdcdata.
ENDFORM. "bdc_field
*perform close_group.

How to use table type in bulk collect

Hi experts,
How to use table type in bulk collect see the procedure used( oracle 10g)
and error is
PLS-00597: expression 'REQ_REC' in the INTO list is of wrong type
CREATE OR REPLACE PROCEDURE SAMPLE_SP IS
TYPE TYP_A AS OBJECT
( COLMN1 TABLE1.COLM1%TYPE,
COLMN2 TABLE1.COLM2%TYPE,
COLMN3 TABLE1.COLM3%TYPE
TYPE REC_A IS TABLE OF TYP_A;
REQ_REC A_REC;
CURSOR REQ_CUR IS SELECT COLM1,COLM2,COLM3 FROM TABLE1 WHERE <CONDITION>;
BEGIN
OPEN REQ_REC;
LOOP
EXIT WHEN REQ_REC%NOTFOUND;
FETCH REQ_REC BULK COLLECT INTO REQ_REC LIMIT 1000;
FOR I IN 1..REQ_REC.COUNT
LOOP
<insert statement>
END LOOP;
COMMIT;
END LOOP;
END SAMPLE_SP;
Many thanks,
Kalinga

ok but that is not an issue..
Hi experts,
How to use table type in bulk collect see the procedure used( oracle 10g)
and error is
PLS-00597: expression 'REQ_REC' in the INTO list is of wrong type
CREATE OR REPLACE PROCEDURE SAMPLE_SP IS
TYPE TYP_A AS OBJECT
( COLMN1 TABLE1.COLM1%TYPE,
COLMN2 TABLE1.COLM2%TYPE,
COLMN3 TABLE1.COLM3%TYPE
TYPE REC_A IS TABLE OF TYP_A;
REQ_REC A_REC;
CURSOR REQ_CUR IS SELECT COLM1,COLM2,COLM3 FROM TABLE1 WHERE <CONDITION>;
BEGIN
OPEN REQ_CUR;
LOOP
EXIT WHEN REQ_REC%NOTFOUND;
FETCH REQ_REC BULK COLLECT INTO REQ_REC LIMIT 1000;
FOR I IN 1..REQ_REC.COUNT
LOOP
<insert statement>
END LOOP;
COMMIT;
END LOOP;
END SAMPLE_SP;
Many thanks,
Kalinga
Message was edited by:
Kalinga

Button "Position" can't work in sm30 when use Table maintenance generator

Hello guys,
i have created a table and use 'Table Maintenance Generator' to generate the code. When i run sm30 and click the button 'Position', it can not work.
i enter '/h' to debug it and find the value'POSI' is not assigned to ok_code.
Some tables created before are OK. What's the matter with it?
Many Thanks

hello daniel,
there is very possibility that some inconsistency might be occured while generating table maintenance generator. So i would advice u to create ur table maintenance generator once more after deleting the current one.
Reward properly.

Reg:table maintance generator

hi,
i have one z table with 5 fields now i added another one field .
in sm30 previouly showing in header 5 fields description , but now why the new field description is not visible why???
i think it should automatically added ...
please help me regarding this issue.
thanks

hi,
for ur answer.
but i change again but no..the description (valution class) is not coming .
i just entered the bslnr field as standard into my z table.
but why its not displaying in my table maintance generator screen as a header..
any process is there??
please let me know.

What is the use of table maintance generator and how it is used ddic

hi dear friends
i would like to know about how the table maintaience generator is used in ddic .i have the step by step processor of that but i would like to know importance and advantages of it .

Nani,
With the help of the table maintenance generator, you are able to maintain the ENTRIES of the table in SM30 transaction.
It can be set in transaction SE11 - Tools - Table maintenance generator.
Table maintanance Generator is used to manually input values using transaction sm30
follow below steps
1) go to se11 check table maintanance check box under attributes tab
2) utilities-table maintanance Generator-> create function group and assign it under
function group input box. Also assign authorization group default &NC& .
3) select standard recording routine radio in table table mainitainence generator to move table
contents to quality and production by assigning it to request.
4) select maintaience type as single step.
5) maintainence screen as system generated numbers this dialog box appears when you click on create button
6) save and activate table
One step, two step in Table Maintenance Generator
Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.
Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.
SM30 is used for table maintenance(addition or deletion of records),
For all the tables in SE11 for which Table maintenance is selected , they can be maintained in SM30
Sm30 is used to maintain the table ,i.e to delete ,insert or modify the field values and all..
It creates the maintenance screen for u for the aprticular table as the maintenance is not allowed for the table..
In the SE11 delivery and maintenance tab, keep the maintenance allowed..
Then come to the SM30 and then enter the table name and press maintain..,
Give the authorization group if necessary and give the function group and then select maintenance type as one step and give the screen numbers as system specified..
Then create,,,
Then u will able to see the maintenance view for the table in which u can able to insert and delete the table values...
We use SM30 transaction for entering values into any DB table.
First we create a table in SE11 and create the table maintenance generator for that Table using (utilities-> table maintenance generator) and create it.
Then it will create a View.
After that from SM30, enter the table name and Maintain, create new entries, change the existing entries for that table.
For further help look into these links
http://help.sap.com/saphelp_46c/helpdata/EN/cf/21eb6e446011d189700000e8322d00/frameset.htm
http://help.sap.com/saphelp_bw30b/helpdata/en/69/c2516e4ba111d189750000e8322d00/content.htm
Table
Don't forget to reward if useful.....

How to use table maintance generator

Similar Messages

Maybe you are looking for