Slow mass insert on base table

I have a table with a text index. If there are mass inserts into the table (e.g. 1Mio rows), the inserts are very slow.
The inserts take around 5min without index. The inserts take 2.5hours with index though sync mode is manual.
the index looks like
CREATE INDEX ui_t_ind on userinterface (searchtx)
   indextype is ctxsys.context
        PARAMETERS ('
                SECTION GROUP ctxsys.auto_section_group
                LEXER               german_lexer
                MEMORY           100000000
                SYNC (MANUAL)'
        );How could I improve the performance of the mass insert?

Hi,
so it looks you are on memory limits. Is it possible for you to decrease the SGA when inserting and increase the memory for the index. I have in my system also a table with over 5M document (biggest 600M), and when reindexing I do this trick, I set the memory for the index to 2GB from normally 128MB and decrease the SGA. This makes the creation of the index from over 6 hours to just 2 hours (it is done in parallel, the table is parallel).
Another option could be to partition the table (if not already done), so you could also parallel index.
You use Append (that is good), but after how many rows do you a commit? Or is it all or nothing?
Herald ten Dam
http://htendam.wordpress.com

Similar Messages

Insert data base table

Hi....
Iam having five records in my database tables.... with 5 fields.... now iam added a new field to that table...
I want to insert entries into that fielf through program..
Suggest me logic...
Thank you,
Naveen.I

hi,
check this sample code.
TABLES : zgm_table.
data : it_data type standard table of zgm_table,
wa_data type zgm_table.
wa_data-name = 'ABC'.
wa_data-city = 'JAPAN'.
wa_data-role = 'ASSOCIATE'.
wa_data-salary = 26000.
append wa_data to it_data.
modify zgm_table from table it_data.
IF sy-subrc = 0.
MESSAGE 'records created succesfully' TYPE 'S'.
ENDIF.
or
wa_data-name = 'ABC'.
wa_data-city = 'JAPAN'.
wa_data-role = 'ASSOCIATE'.
wa_data-salary = 38000.
append wa_data to it_data.
update zgm_table from table it_data.
reward points if hlpful.

Adding 2 more rows to a select without inserting rows to base table

hello all,
i have a below simple select statement which is querying a table.
select * from STUDY_SCHED_INTERVAL_TEMP
where STUDY_KEY = 1063;
but here is the situations. As you can see its returning 7 rows. But i need to add
2 more rows..with everything else default value or what exist... except adding 2 more rows.
i cannot insert into base table. I want my end results to increment by 2 days in
measurement_date_Taken to 01-apr-09....so basically measurement_date_taken should
end at study_end_Date...
IS THAT EVEN POSSIBLE WITHOUT INSERTING ROWS INTO THE TABLE AND JUST PLAYIHY AROUND WITH
THE SELECT STATEMENT??
sorry if this is confusing...i am on 10.2.0.3
Edited by: S2K on Aug 13, 2009 2:19 PM

Well, I'm not sure if this query looks as good as my lawn, but seems to work anyway ;)
I've used the 'simplified version', but the principle should work for your table to, S2K.
As Frank already pointed out (and I stumbled upon it while clunging): you just select your already existing rows and union them with the 'missing records', you calculate the number of days you're 'missing' based on the study_end_date:
MHO%xe> alter session set nls_date_language='AMERICAN';
Sessie is gewijzigd.
Verstreken: 00:00:00.01
MHO%xe> with t as ( -- generating your data here, simplified by me due to cat and lawn
2 select 1063 study_key
3 ,      to_date('01-MAR-09', 'dd-mon-rr') phase_start_date
4 ,      to_date('02-MAR-09', 'dd-mon-rr') measurement_date_taken
5 ,      to_date('01-APR-09', 'dd-mon-rr') study_end_date
6 from dual union all
7 select 1063, to_date('03-MAR-09', 'dd-mon-rr') , to_date('04-MAR-09', 'dd-mon-rr') , to_date('01-APR-09', 'dd-mon-rr') from dual union all
8 select 1063, to_date('03-MAR-09', 'dd-mon-rr') , to_date('09-MAR-09', 'dd-mon-rr') , to_date('01-APR-09', 'dd-mon-rr') from dual union all
9 select 1063, to_date('03-MAR-09', 'dd-mon-rr') , to_date('14-MAR-09', 'dd-mon-rr') , to_date('01-APR-09', 'dd-mon-rr') from dual union all
10 select 1063, to_date('03-MAR-09', 'dd-mon-rr') , to_date('19-MAR-09', 'dd-mon-rr') , to_date('01-APR-09', 'dd-mon-rr') from dual union all
11 select 1063, to_date('22-MAR-09', 'dd-mon-rr') , to_date('23-MAR-09', 'dd-mon-rr') , to_date('01-APR-09', 'dd-mon-rr') from dual union all
12 select 1063, to_date('22-MAR-09', 'dd-mon-rr') , to_date('30-MAR-09', 'dd-mon-rr') , to_date('01-APR-09', 'dd-mon-rr') from dual
13 ) -- actual query:
14 select study_key
15 ,      phase_start_date
16 ,      measurement_date_taken
17 ,      study_end_date
18 from   t
19 union all
20 select study_key
21 ,      phase_start_date
22 ,      measurement_date_taken + level -- or rownum
23 ,      study_end_date
24 from ( select study_key
25         ,      phase_start_date
26         ,      measurement_date_taken
27         ,      study_end_date
28         ,      add_up
29         from (
30                select study_key
31                ,      phase_start_date
32                ,      measurement_date_taken
33                ,      study_end_date
34                ,      study_end_date - max(measurement_date_taken) over (partition by study_key
35                                                                          order by measurement_date_taken ) add_up
36                ,      lead(measurement_date_taken) over (partition by study_key
37                                                          order by measurement_date_taken ) last_rec
38                from   t
39              )
40         where last_rec is null
41       )
42 where rownum <= add_up
43 connect by level <= add_up;
STUDY_KEY PHASE_START_DATE    MEASUREMENT_DATE_TA STUDY_END_DATE
      1063 01-03-2009 00:00:00 02-03-2009 00:00:00 01-04-2009 00:00:00
      1063 03-03-2009 00:00:00 04-03-2009 00:00:00 01-04-2009 00:00:00
      1063 03-03-2009 00:00:00 09-03-2009 00:00:00 01-04-2009 00:00:00
      1063 03-03-2009 00:00:00 14-03-2009 00:00:00 01-04-2009 00:00:00
      1063 03-03-2009 00:00:00 19-03-2009 00:00:00 01-04-2009 00:00:00
      1063 22-03-2009 00:00:00 23-03-2009 00:00:00 01-04-2009 00:00:00
      1063 22-03-2009 00:00:00 30-03-2009 00:00:00 01-04-2009 00:00:00
      1063 22-03-2009 00:00:00 31-03-2009 00:00:00 01-04-2009 00:00:00
      1063 22-03-2009 00:00:00 01-04-2009 00:00:00 01-04-2009 00:00:00
9 rijen zijn geselecteerd.If there's a simpler way (in SQL), I hope others will join and share their example/ideas/thoughts.
I have a feeling that this is using more resources than needed.
But I've got to cut the daisies first now, they interfere my 'lawn-green-ess' ;)

Count difference b/w forecast interface table(success rec) and base table

Hi all
We did forecast conversion.
We got wrong count while comparing count of successful loaded records of interface table(based on process_flag=5) and records inserted in base table .
I used below querys
1) to count the records successfully loaded into base table based on MRP_FORECAST_INTERFACE
select count (* ) from MRP_FORECAST_INTERFACE where TO_CHAR( last_update_date,'DD-MON-YYYY HH24:MI:SS') between
'20-MAR-2012 06:08:05' AND '20-MAR-2012 14:06:33'
and process_status=5 -- shows 859022
2) records hitted the base table at the same time
SELECT count (* ) FROM MRP_FORECAST_DATES where last_update_date >sysdate-2 --851451
I refer this document http://docs.oracle.com/cd/A85683_01/acrobat/mrptrm.pdf
In that it written like this If records process_status =5 in MRP_FORECAST_INTERFACE table then the planning manager successfully loaded into base table..
But why this count is different? Can any one help me on this...

Hi all
We did forecast conversion.
We got wrong count while comparing count of successful loaded records of interface table(based on process_flag=5) and records inserted in base table .
I used below querys
1) to count the records successfully loaded into base table based on MRP_FORECAST_INTERFACE
select count (* ) from MRP_FORECAST_INTERFACE where TO_CHAR( last_update_date,'DD-MON-YYYY HH24:MI:SS') between
'20-MAR-2012 06:08:05' AND '20-MAR-2012 14:06:33'
and process_status=5 -- shows 859022
2) records hitted the base table at the same time
SELECT count (* ) FROM MRP_FORECAST_DATES where last_update_date >sysdate-2 --851451
I refer this document http://docs.oracle.com/cd/A85683_01/acrobat/mrptrm.pdf
In that it written like this If records process_status =5 in MRP_FORECAST_INTERFACE table then the planning manager successfully loaded into base table..
But why this count is different? Can any one help me on this...

Making mass change to Oracle Apps base table

I have requirement where I have to do a mass updates/inserts to an Oracle Apps table (BOM_Inventory_Components). I have been told by my senior programmers that Oracle does not like direct updates or inserts to the Base tables in Oracle Apps.
Anyone knows of a standard practice of updating/inserting records into Base tables in Oracle Apps?

I have seen and done lot of projects where we do direct table update but we do have Metalink support and we do inform them and involve them into regours conference call and than we are proceding direct table update.
the trick is oracle always as package where you can fine related update procedure so by passing neccesary parameters you can update the table.
Regards
Prashant Pathak

Inserting into a base table of a materialized view takes lot of time.......

Dear All,
I have created a materialized view which refreshes on commit.materialized view is enabled query rewrite.I have created a materialized view log on the base table also While inserting into the base table it takes lot of time................Can u please tell me why?

Dear Rahul,
Here is my materialized view..........
create materialized view mv_test on prebuilt table refresh force on commit
enable query rewrite as
SELECT P.PID,
SUM(HH_REGD) AS HH_REGD,
SUM(INPRO_WORKS) AS INPRO_WORKS,
SUM(COMP_WORKS) AS COMP_WORKS,
SUM(SKILL_WAGE) AS SKILL_WAGE,
SUM(UN_SKILL_WAGE) AS UN_SKILL_WAGE,
SUM(WAGE_ADVANCE) AS WAGE_ADVANCE,
SUM(MAT_AMT) AS MAT_AMT,
SUM(DAYS) AS DAYS,
P.INYYYYMM,P.FIN_YEAR
FROM PROG_MONTHLY P
WHERE SUBSTR(PID,5,2)<>'PP'
GROUP BY PID,P.INYYYYMM,P.FIN_YEAR;
Please help me if query enable rewrite does any performance degradation......
Thanks & Regards
Kris

How to insert data from different internal table into a data base table

hi all,
I want to insert a particular field in an internal table to a field in a data base table.Note that the fields in the internal table and database table are not of the same name since i need to insert data from different internal tables.can some one tell me how to do this?
in short i want to do something like the foll:
INSERT INTO ZMIS_CODES-CODE VALUE '1'.
*INSERT INTO ZMIS_CODES-COL1 VALUE DATA_MTD-AUFNR .(zmis_codes is the db table and data_mtd is the int.table)

REPORT ZINSERT.
tables kna1.
data: itab LIKE KNA1.
data lv_kUNAG LIKE KNA1-KUNNR.
lv_kuNAG = '0000010223'.
ITAB-kuNNR = lv_kuNAG.
ITAB-name1 = 'XYZ'.
INSERT INTO KNA1 VALUES ITAB.
IF SY-SUBRC = 0.
WRITE:/ 'SUCCESS'.
ELSE.
WRITE:/ 'FAILED'.
ENDIF.
Here lv_kunag is ref to kna1 kunnr passed in different name
In internal table .
Try and let me know if this logic dint work.

Data from 2 database blocks insert into the same base table?

Hello,
I have canvas C_NEW. On this canvas, items from 3 blocks are usable by the user.
1. Block NEW_HEAD: 3 items say X1,X2,X3
2. Block NEW : multi record text fields say Y1 thru Y10. Also a scrollbar.
3. Block NEW_ACTION: 6 buttons say B1 thru B6 (One of them is N_OK which is the item in question)
both the blocks NEW, NEW_HEAD are db blocks and have the same base table say BT. When the users click on the N_OK (after filling out the data in the NEW_HEAD block and then NEW in that order) I need the data from both the NEW, NEW_HEAD to go into the BT. Currently only the data from the NEW is going into BT. Fields in the BT table which correspond to the fields X1,X2,X3 in the NEW_HEAD remain null after clicking the N_OK button. I put commit_form in the N_OK code since both the blocks are db blocks( and as suggested by folks, it is easier to issue a commit_form than do a lot more work in writing my own SQL).
How can I achive this?
Thanks,
Chiru

I tried doing what you suggested by putting the following code in the program unit which gets called when_button_pressed.
PROCEDURE P_SAVE IS
v_lc_no number;
v_lc_seq number;
v_dmg_allow number;
BEGIN
Go_Block('B_new_head');
v_lc_no:= :B_new_head.N_LC_NO;
v_lc_seq:= :B_new_head.N_LC_SEQ;
v_dmg_allow:= :B_new_head.N_LC_DMG_ALLOW;
Go_Block('B_new');
FIRST_RECORD;
LOOP
     emessage('before insert'||v_lc_no||'-'||v_lc_seq||'-'||:B_new.order_no);
INSERT INTO ct_lc_import(
    LC_NUMBER,
    LC_SEQ,
    DAMAGE_ALLOWANCE,
    ORDER_NO,
    QTY_SHIPPED,
    UNIT_PRICE,
    DRAFT_AMOUNT,
    TICKET_DEDUCTION,
    SHIPMENT_PENALTY,
    TOTAL_DEBIT,
    DEBIT_DATE)
    VALUES (v_lc_no,
            v_lc_seq,
            v_dmg_allow,
            :B_new.order_no,
            :B_new.qty_shipped,
            :B_new.unit_price,
            :B_new.draft_amount,
            :B_new.ticket_deduction,
            :B_new.shipment_penalty,
            :B_new.total_debit,
            :B_new.debit_date);
   commit;
NEXT_RECORD;
   if :SYSTEM.LAST_RECORD='TRUE' then
         emessage('last record');
         EXIT;
   end if;
--NEXT_RECORD;
END LOOP;
EXCEPTION
   when FORM_TRIGGER_FAILURE then
      raise;
   when OTHERS then
      emessage(SQLERRM);
      raise FORM_TRIGGER_FAILURE;
END;But I can't see the records in the table eventhough the message pops up with the values before inserting the 1st record. It then exits. I would think it would atleast insert the very first record into the the table at the least.
Thanks,
Chiru

Insert records into non base table

Hi
I would like to insert records into a table when a button is clicked. The table is a non base table. I am trying to save records displayed in a form into a history table which is not part of the form. I am using the following code stored in a program unit then called when the button is pressed. It doesn't generate any error but the records are not inserted. Can anyone please help.
hist_id := 1;
cust_name := :CUSTOMER.cust_name;
loan_date := :LOAN.loan_date;
return_date := LOAN.return_date;
FORMS_DDL('INSERT INTO LOAN_HISTORY VALUES'||hist_id||','||cust_name||','||loan_date||','||return_date);

Why do you need forms_ddl built in for a DML statement to be used in form?
U can directly use insert.
hist_id := 1;
cust_name := :CUSTOMER.cust_name;
loan_date := :LOAN.loan_date;
return_date := LOAN.return_date;
INSERT INTO LOAN_HISTORY VALUES (hist_id,cust_name,loan_date,return_date);
It should work perfectly.

How to Insert-Select and Updade base table

Hi All,
How is the best way to do this?
I have a table A that has 1million rows.
I need to Insert-Select into table B from a Group by on table A,
and Update all rows in table A that were used into Insert with a flag.
(select a hundred from A and insert 10 thousands into B)
What to do?
1-Update table A with flag before Insert-Select?
2-Insert-Select group by into table B, before Update?
3-Another way?
Thanks in advance,
Edson

Either way. But you may find that updating the source flag first and then using that flag as part of your where clause when extracting rows to put in the destination table is a bit faster.
In any case, you will commit only once after all of the work is done.

Constantly inserting into large table with unique index... Guidance?

Hello all;
So here is my world. We have central to our data monitoring system an oracle database running Oracle Standard One (please don't laugh... I understand it is comical) licensing.
This DB is about 1.7 TB of small record data.
One table in particular (the raw incoming data, 350gb, 8 billion rows, just in the table) is fed millions of rows each day in real time by two to three main "data collectors" or what have you. Data must be available in this table "as fast as possible" once it is received.
This table has 6 columns (one varchar usually empty, a few numerics including a source id, a timestamp and a create time).
The data is collect in chronological order (increasing timestamp) 90% of the time (though sometimes the timestamp may be very old and catch up to current). The other 10% of the time the data can be out of order according to the timestamp.
This table has two indexes, unique (sourceid, timestamp), and a non unique (create time). (FYI, this used to be an IOT until we had to add the second index on create time, at which point a secondary index on create time slowed the IOT to a crawl)
About 80% of this data is removed after it ages beyond 3 months; 20% is retained as "special" long term data (customer pays for longer raw source retention). The data is removed using delete statements. This table is never (99.99% of the time) updated. The indexes are not rebuilt... ever... as a rebuild is about a 20+ hour process, and without online rebuilds since we are standard one, this is just not possible.
Now what we are observing is that the inserts into this table
- Inserts are much slower based on a "wider" cardinality of the "sourceid" of the data being inserted. What I mean is that 10,000 inserts for 10,000 sourceid (regardless of timestamp) is MUCH, MUCH slower than 10,000 inserts for a single sourceid. This makes sense to me, as I understand it that oracle must inspect more branches of the index for uniqueness, and more different physical blocks will be used to store the new index data. There are about 2 million unique sourceId across our system.
- Over time, oracle is requesting more and more ram to satisfy these inserts in a timely matter. My understanding here is that oracle is attempting to hold the leafs of these indexes perpetually buffers. Our system does have a 99% cache hit rate. However, we are seeing oracle requiring roughly 10GB extra ram per quarter to 6 months; we're at about 50gb of ram just for oracle already.
- If I emulate our production load on a brand new, empty table / indexes, performance is easily 10x to 20x faster than what I see when I do the same tests with the large production copies of data.
We have the following assumption: Partitioning this table based on good logical grouping of sourceid, and then timestamp, will help reduce the work required by oracle to verify uniqueness of data, reducing the amount of data that must be cached by oracle, and allow us to handle our "older than 3 month" at a partition level, greatly reducing table and index fragmentation.
Based on our hardware, its going to be about a million dollar hit to upgrade to Enterprise (with partitioning), plus a couple hundred thousand a year in support. Currently I think we pay a whopping 5 grand a year in support, if that, total oracle costs. This is going to be a huge pill for our company to swallow.
What I am looking for guidance / help on, should we really expect partitioning to make a difference here? I want to get that 10x performance difference back we see between a fresh empty system, and our current production system. I also want to limit oracles 10gb / quarter growing need for more buffer cache (the cardinality of sourceid does NOT grow by that much per quarter... maybe 1000s per quarter, out of 2 million).
Also, please I'd appreciate it if there were no mocking comments about using standard one up to this point :) I know it is risky and insane and maybe more than a bit silly, but we make due with what we have. And all the credit in the world to oracle that their "entry" level system has been able to handle everything we've thrown at it so far! :)
Alright all, thank you very much for listening, and I look forward to hear the opinions of the experts.

Hello,
Here is a link to a blog article that will give you the right questions and answers which apply to your case:
http://jonathanlewis.wordpress.com/?s=delete+90%25
As far as you are deleting 80% of your data (old data) based on a timestamp, then don't think at all about using the direct path insert /*+ append */ as suggested by one of the contributors to this thread. The direct path load will not re-use any free space made by the delete. You have two indexes:
(a) unique index (sourceid, timestamp)
(b) index(create time)
Your delete logic (based on arrival time) will smatch your indexes as far as you are always deleting the left hand side of the index; it means you will have what we call a right hand index - In other words, the scattering of the index key per leaf block is certainly catastrophic (there is an oracle iternal function named sys_op_lidbid that will allow you to verify this index information). There is a fairly chance that your two indexes will benefit from a coalesce as already suggested:
           ALTER INDEX indexname COALESCE;This coalesce should be investigated to be done on a regular basis (may be after each 80% delete) You seem to have several sourceid for one timestamp. If the answer is yes you should think about compressing this index
    create index indexname (sourceid, timestamp) compress;
or
    alter index indexname rebuild compress;     You will do it only once. Your index will have a smaller size and may be more efficient than it is actually. The index compression will add an extra CPU work during an insert but it might help improving the overal insert process.
Best Regards
Mohamed Houri

How to stored data after clicking checkbox in data base table

REPORT ZT                                      .
TYPE-pools: slis.
tables:mkpf,mseg,mard,COWB_COMP,ZTABLE.
Types:BEGIN OF tp_data,
     mblnr LIKE mseg-mblnr,
     matnr LIKE mseg-matnr,
     werks LIKE mard-werks,
     lgort LIKE mard-lgort,
     lgpbe LIKE mard-lgpbe,
     charg LIKE mseg-charg,
     bwart LIKE mseg-bwart,
     budat LIKE mkpf-budat,
     menge LIKE mseg-menge,
     meins LIKE mseg-meins,
     kostl LIKE mseg-kostl,
     aufnr LIKE mseg-aufnr,
     rsnum LIKE mseg-rsnum,
     endkz like COWB_COMP-endkz,
END OF tp_data,
tp_tbl_data TYPE STANDARD TABLE OF tp_data.
MODIFIED*******************
DATA: WA TYPE TP_DATA.
MODIFIED*******************
*data: t_data like Y00_MM_ISSUE_DAT occurs 0 with header line.
Constants
Data objects (variable declarations and definitions)
Report data to be shown.
DATA: it_data TYPE STANDARD TABLE OF tp_data.
MODIFIED*******************
DATA : V_REPID LIKE SY-REPID.
MODIFIED*******************
Heading of the report.
DATA: t_heading TYPE slis_t_listheader.
*========================== Selection Screen
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS:smblnr FOR mseg-mblnr MODIF ID m1,
              smatnr FOR mseg-matnr MODIF ID m2,
              swerks FOR mard-werks MODIF ID m3,
              slgort FOR mard-lgort MODIF ID m4,
              slgpbe FOR mard-lgpbe MODIF ID m5,
              scharg FOR mseg-charg MODIF ID m6,
              sbwart FOR mseg-bwart MODIF ID m7,
              skostl FOR mseg-kostl MODIF ID m8,
              saufnr FOR mseg-aufnr MODIF ID m9,
              srsnum FOR mseg-rsnum MODIF ID m10.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-002.
PARAMETERS:pre RADIOBUTTON GROUP radi USER-COMMAND ucomm DEFAULT 'X',
          pse RADIOBUTTON GROUP radi,
          bps RADIOBUTTON GROUP radi.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE text-003.
PARAMETER:layout TYPE i.
SELECTION-SCREEN END OF BLOCK b3.
MODIFIED*******************
INITIALIZATION.
V_REPID = sy-repid.
MODIFIED*******************
*=========================== Event Blocks
AT selection-SCREEN.
start-OF-selection.
PERFORM get_data USING it_data.
END-OF-selection.
PERFORM build_alv USING it_data t_heading.
*=========================== Subroutines
*&      Form get_data
      Gets the information to be shown in the report.
FORM get_data USING t_data TYPE tp_tbl_data.
SELECT msegmblnr msegmatnr mardwerks mardlgort mard~lgpbe
msegcharg msegbwart mkpf~budat
   msegmenge msegmeins msegkostl msegaufnr mseg~rsnum
INTO CORRESPONDING FIELDS OF TABLE t_data
FROM mseg
JOIN mard ON mardmatnr EQ msegmatnr
              JOIN mkpf ON msegmblnr EQ mkpfmblnr
              WHERE mseg~matnr IN smatnr.
ENDFORM.                    " get_data
*&      Form build_alv
      Builds and display the ALV Grid.
FORM build_alv USING t_data TYPE tp_tbl_data
     t_heading TYPE slis_t_listheader.
ALV required data objects.
DATA: w_title   TYPE lvc_title,
       w_comm    TYPE slis_formname,
       w_status TYPE slis_formname,
       x_layout TYPE slis_layout_alv,
       t_event    TYPE slis_t_event,
       t_fieldcat TYPE slis_t_fieldcat_alv,
       t_sort     TYPE slis_t_sortinfo_alv.
REFRESH t_fieldcat.
REFRESH t_event.
REFRESH t_sort.
CLEAR x_layout.
CLEAR w_title.
Field Catalog
PERFORM set_fieldcat2 USING:
       1 'MBLNR' 'MBLNR' 'MSEG' space space space space space space
space space space space space space t_fieldcat ,
       2 'MATNR' 'MATNR' 'MSEG' space space space space space space
space space space space space space t_fieldcat ,
       3 'WERKS' 'WERKS' 'MARD' space space space space space space
space space space space space space t_fieldcat,
       4 'LGORT' 'LGORT' 'MARD' space space space space space space
space space space space space space t_fieldcat ,
       5 'LGPBE' 'LGPBE' 'MARD' space space space space space space
space space space space space space t_fieldcat ,
       6 'CHARG' 'CHARG' 'MSEG' space space space space space space
space space space space space space t_fieldcat ,
       7 'BWART' 'BWART' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       8 'BUDAT' 'BUDAT' 'MKPF' space space space space space space
space space space space space space t_fieldcat,
       9 'MENGE' 'MENGE' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       10 'MEINS' 'MEINS' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       11 'KOSTL' 'KOSTL' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       12 'AUFNR' 'AUFNR' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       13 'RSNUM' 'RSNUM' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
   14 'ENDKZ' 'ENDKZ' 'COWB_COMP' space space 'select' 'Select this row' 'Sel' 'Select this row' space space space 'X' 'X' space t_fieldcat.
Layout
x_layout-zebra = 'X'.
Top of page heading
PERFORM set_top_page_heading USING t_heading t_event.
Events
PERFORM set_events USING t_event.
GUI Status
w_status = ''.
User commands
w_comm   = 'USER_COMMAND'.
Order
Example
PERFORM set_order USING '<field>' 'IT_DATA' 'X' space space t_sort.
PERFORM set_order USING 'MBLNR' 'IT_DATA' 'X' space 'X' t_sort.
PERFORM set_order USING 'EBELN' 'IT_DATA' 'X' space 'X' t_sort.
PERFORM set_order USING 'EBELP' 'IT_DATA' 'X' space space t_sort.
Displays the ALV grid
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
   i_callback_program       = V_REPID
   it_fieldcat              = t_fieldcat
   is_layout                = x_layout
   it_sort                  = t_sort
   i_callback_pf_status_set = w_status
   i_callback_user_command = w_comm
   i_save                   = 'X'
   it_events                = t_event
   i_grid_title             = w_title
TABLES
   t_outtab                 = t_data
EXCEPTIONS
   program_error            = 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.                    " build_alv.
*&      Form set_top_page_heading
      Creates the report headings.
FORM set_top_page_heading USING t_heading TYPE slis_t_listheader
     t_events TYPE slis_t_event.
DATA: x_heading TYPE slis_listheader,
       x_event   TYPE LINE OF slis_t_event.
Report title
CLEAR t_heading[].
CLEAR x_heading.
x_heading-typ = 'H'.
x_heading-info = 'Reporte Prueba'(001).
APPEND x_heading TO t_heading.
Program name
CLEAR x_heading.
x_heading-typ = 'S'.
x_heading-KEY = 'Program: '.
x_heading-info = sy-repid.
APPEND x_heading TO t_heading.
User who is running the report
CLEAR x_heading.
x_heading-typ = 'S'.
x_heading-KEY = 'User: '.
x_heading-info = sy-uname.
APPEND x_heading TO t_heading.
Date of execution
CLEAR x_heading.
x_heading-typ = 'S'.
x_heading-KEY = 'Date: '.
WRITE sy-datum TO x_heading-info.
APPEND x_heading TO t_heading.
Time of execution
CLEAR x_heading.
x_heading-typ = 'S'.
x_heading-KEY = 'Time: '.
WRITE sy-uzeit TO x_heading-info.
APPEND x_heading TO t_heading.
Top of page event
x_event-name = slis_ev_top_of_page.
x_event-FORM = 'TOP_OF_PAGE'.
APPEND x_event TO t_events.
ENDFORM.
*&      Form set_events
      Sets the events for ALV.
      The TOP_OF_PAGE event is alredy being registered in
      the set_top_page_heading subroutine.
FORM set_events USING t_events TYPE slis_t_event.
DATA: x_event   TYPE LINE OF slis_t_event.
Example
clear x_event.
x_event-name = .
x_event-form = .
append x_event to t_event.
ENDFORM.
*&      Form set_order
      Adds an entry to the order table.
FORM set_order USING p_fieldname p_tabname p_up p_down p_subtot
     t_sort TYPE slis_t_sortinfo_alv.
DATA: x_sort TYPE slis_sortinfo_alv.
CLEAR x_sort.
x_sort-fieldname = p_fieldname.
x_sort-tabname   = p_tabname.
x_sort-UP = p_up.
x_sort-down = p_down.
x_sort-subtot = p_subtot.
APPEND x_sort TO t_sort.
ENDFORM.                    "set_order
*&      Form set_fieldcat2
      Adds an entry to the field catalog.
FORM set_fieldcat2 USING p_colpos p_fieldname p_ref_fieldname
p_ref_tabname
     p_outputlen p_noout
     p_seltext_m p_seltext_l p_seltext_s p_reptext_ddic p_ddictxt
     p_hotspot p_showasicon p_checkbox p_edit
     p_dosum
     t_fieldcat TYPE slis_t_fieldcat_alv.
DATA: wa_fieldcat TYPE slis_fieldcat_alv.
CLEAR wa_fieldcat.
General settings
wa_fieldcat-fieldname = p_fieldname.
wa_fieldcat-col_pos = p_colpos.
wa_fieldcat-no_out = p_noout.
wa_fieldcat-HOTSPOT = p_hotspot.
wa_fieldcat-CHECKBOX = p_checkbox.
wa_fieldcat-ICON = p_showasicon.
wa_fieldcat-do_sum = p_dosum.
Set reference fieldname, tablenam and rollname.
If p_ref_tabname is not given, the ref_fieldname given is a data
*element.
If p_ref_tabname is given, the ref_fieldname given is a field of a
*table. In case ref_fieldname is not given, it is copied from the
*fieldname.
IF p_ref_tabname IS INITIAL.
   wa_fieldcat-rollname =   p_ref_fieldname.
ELSE.
   wa_fieldcat-ref_tabname = p_ref_tabname.
   IF p_ref_fieldname EQ space.
     wa_fieldcat-ref_fieldname =   wa_fieldcat-fieldname.
   ELSE.
     wa_fieldcat-ref_fieldname =   p_ref_fieldname.
   ENDIF.
ENDIF.
Set output length.
IF NOT p_outputlen IS INITIAL.
   wa_fieldcat-outputlen = p_outputlen.
ENDIF.
Set text headers.
IF NOT p_seltext_m IS INITIAL.
   wa_fieldcat-seltext_m = p_seltext_m.
ENDIF.
IF NOT p_seltext_l IS INITIAL.
   wa_fieldcat-seltext_l = p_seltext_l.
ENDIF.
IF NOT p_seltext_s IS INITIAL.
   wa_fieldcat-seltext_s = p_seltext_s.
ENDIF.
IF NOT p_reptext_ddic IS INITIAL.
   wa_fieldcat-reptext_ddic = p_reptext_ddic.
ENDIF.
IF NOT p_ddictxt IS INITIAL.
   wa_fieldcat-ddictxt = p_ddictxt.
ENDIF.
Set as editable or not.
IF NOT p_edit IS INITIAL.
   wa_fieldcat-INPUT     = 'X'.
   wa_fieldcat-EDIT     = 'X'.
ENDIF.
APPEND wa_fieldcat TO t_fieldcat.
ENDFORM.                   "set_fieldcat2
*&      Form top_of_page
      Called on top_of_page ALV event.
      Prints the heading.
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
     i_logo             = 'TRVPICTURE04'
   it_list_commentary = t_heading.
ENDFORM.                    " alv_top_of_page
*&      Form user_command
      Called on user_command ALV event.
      Executes custom commands.
FORM user_command USING r_ucomm     LIKE sy-ucomm
     rs_selfield TYPE slis_selfield.
case sy-ucomm.
WHEN '&DATA_SAVE'.
LOOP AT IT_DATA INTO WA WHERE ENDKZ = 'X'.
   IF WA-ENDKZ = 'X'.
*******MODIFIED*********************************
U DELETE THIS CODE N USER UR INSERT CODE TO CHECK
SY-MSGV1 = WA-MBLNR.                              " U CAN DELETE
SY-MSGV2 = WA-MATNR.                              " U CAN DELETE
MESSAGE ID 'BC_BOR' TYPE 'I' NUMBER '888'          " U CAN DELETE
        WITH SY-MSGV1 SY-MSGV2. " U CAN DELETE
*******MODIFIED*********************************
   INSERT ZTABLE.
   ENDIF.
endloop.
ENDCASE.
ENDFORM.                    "user_command
this is my code, database will stored in fields only.data is empty,
how to slove that one,send any sugestion.

Hi Lakshmi,
       Can u explain briefly what is ur requirement. U mean to say that after clicking the checkbox in data base table or Screen?
Regards,
Jayaram...

Data Not loaded from ap_invoice_lines_interface to the base table

Hi ,
Please I'm working on Interface which load invoices from Cobol system to oracle , anyway procedure is working on fine & all data is loaded to the interface as i'm inserting 4 attributes which is DFF on the invoice line level
Now when i ran the import program all data is loaded to the base table except one of the attributes isnot loaded .
will anyone tell me what is the reason or how can i trace that ..........
Thanks In Advance

Dear All ,,,,
Please i got it's a matter of size of the attribute1 segment i increased it ,,,,,,,,,but now the issue that data is saved in the base table but not showing in the screen
will you please help me in that
Edited by: miro_feps on May 21, 2012 1:01 AM

How to insert data into table control

hi experts,,
i have inserted data into data base table through table control .
now i want to insert data into table control through database table.
how to delete data from table control for selected row

Hi
go through this link.
http://www.****************/Tutorials/ABAP/TableControl/Demo.htm

Data should get inserted in all tables if i enter the form field only once

Hi, I have a new question again.
There are 5 tables in a database, that is t1, t2, t3, t4 & t5. the first 4 table has one common column, known as lc_no. I have build the form using the form builder. In that form, there is a 1 text field for lc_no. I have not started to code anything as yet in the form because everything with respect to it is working fine and even the data is getting inserted. But the problem is that, when i enter the data in the form, the lc_no gets loaded in only one table. I want the data to get inserted in all the tables. What should i code? How should i start off? I'm very new to this & don't exactly know how do i start with it ?
Thank You. Can you help as i have not yet started to code in this form.
Oracle9i Enterprise Edition Release 9.2.0.1.0.
oracle forms 6i.

Let us say table one have lc_no, other columen
Table 2 have LC-no , other columsn
Table 3 have lc-no , other column,
Now in form(which has table1 as base table)
In PRe-Insert write like below
Insert into table2 (lc_no) values (:table1.lc_no) here tabel1 should be block name in form.
Insert into table3 (lc_no) values (:table1.lc_no)
................and so on .. to other table.
So, now when user commits the form, the lc_no will be available in all the other tables..

Slow mass insert on base table

Similar Messages

Maybe you are looking for