Base Table dropped

Hi,
Someone dropped a base table .Anyone please help how to check who had dropped it and from which terminal
it got dropped
Thanks,
Kr

Someone dropped a base tableDo you know table name...?
Anyone please help how to check who had dropped it and from which terminal it got droppedIs Auditing enabled in your database...?
What is the version of the database...?

Similar Messages

How to Compare Data length of staging table with base table definition

Hi,
I've two tables :staging table and base table.
I'm getting data from flatfiles into staging table, as per requirement structure of staging table and base table(length of each and every column in staging table is 25% more to dump data without any errors) are different for ex :if we've city column with varchar length 40 in staging table it has 25 in base table.Once data is dumped into staging table I want to compare actual data length of each and every column in staging table with definition of base table(data_length for each and every column from all_tab_columns) and if any column differs length I need to update the corresponding row in staging table which also has a flag called err_length.
so for this I'm using cursor c1 is select length(a.id),length(a.name)... from staging_table;
cursor c2(name varchar2) is select data_length from all_tab_columns where table_name='BASE_TABLE' and column_name=name;
But we're getting data atonce in first query whereas in second cursor I need to get each and every column and then compare with first ?
Can anyone tell me how to get desired results?
Thanks,
Mahender.

This is a shot in the dark but, take a look at this example below:
SQL> DROP TABLE STAGING;
Table dropped.
SQL> DROP TABLE BASE;
Table dropped.
SQL> CREATE TABLE STAGING
2 (
3          ID              NUMBER
4 ,       A               VARCHAR2(40)
5 ,       B               VARCHAR2(40)
6 ,       ERR_LENGTH      VARCHAR2(1)
7 );
Table created.
SQL> CREATE TABLE BASE
2 (
3          ID      NUMBER
4 ,       A       VARCHAR2(25)
5 ,       B       VARCHAR2(25)
6 );
Table created.
SQL> INSERT INTO STAGING VALUES (1,RPAD('X',26,'X'),RPAD('X',25,'X'),NULL);
1 row created.
SQL> INSERT INTO STAGING VALUES (2,RPAD('X',25,'X'),RPAD('X',26,'X'),NULL);
1 row created.
SQL> INSERT INTO STAGING VALUES (3,RPAD('X',25,'X'),RPAD('X',25,'X'),NULL);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT * FROM STAGING;
        ID A                                        B                                        E
         1 XXXXXXXXXXXXXXXXXXXXXXXXXX               XXXXXXXXXXXXXXXXXXXXXXXXX
         2 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXX
         3 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXX
SQL> UPDATE STAGING ST
2 SET     ERR_LENGTH = 'Y'
3 WHERE   EXISTS
4          (
5                  WITH    columns_in_staging AS
6                  (
7                          /* Retrieve all the columns names for the staging table with the exception of the primary key column
8                           * and order them alphabetically.
9                           */
10                          SELECT COLUMN_NAME
11                          ,       ROW_NUMBER() OVER (ORDER BY COLUMN_NAME) RN
12                          FROM    ALL_TAB_COLUMNS
13                          WHERE   TABLE_NAME='STAGING'
14                          AND     COLUMN_NAME != 'ID'
15                          ORDER BY 1
16                  ),      staging_unpivot AS
17                  (
18                          /* Using the columns_in_staging above UNPIVOT the result set so you get a record for each COLUMN value
19                           * for each record. The DECODE performs the unpivot and it works if the decode specifies the columns
20                           * in the same order as the ROW_NUMBER() function in columns_in_staging
21                           */
22                          SELECT ID
23                          ,       COLUMN_NAME
24                          ,       DECODE
25                                  (
26                                          RN
27                                  ,       1,A
28                                  ,       2,B
29                                  ) AS VAL
30                          FROM            STAGING
31                          CROSS JOIN      COLUMNS_IN_STAGING
32                  )
33                  /*      Only return IDs for records that have at least one column value that exceeds the length. */
34                  SELECT ID
35                  FROM
36                  (
37                          /* Join the unpivoted staging table to the ALL_TAB_COLUMNS table on the column names. Here we perform
38                           * the check to see if there are any differences in the length if so set a flag.
39                           */
40                          SELECT STAGING_UNPIVOT.ID
41                          ,       (CASE WHEN ATC.DATA_LENGTH < LENGTH(STAGING_UNPIVOT.VAL) THEN 'Y' END) AS ERR_LENGTH_A
42                          ,       (CASE WHEN ATC.DATA_LENGTH < LENGTH(STAGING_UNPIVOT.VAL) THEN 'Y' END) AS ERR_LENGTH_B
43                          FROM    STAGING_UNPIVOT
44                          JOIN    ALL_TAB_COLUMNS ATC     ON ATC.COLUMN_NAME = STAGING_UNPIVOT.COLUMN_NAME
45                          WHERE   ATC.TABLE_NAME='BASE'
46                  )       A
47                  WHERE   COALESCE(ERR_LENGTH_A,ERR_LENGTH_B) IS NOT NULL
48                  AND     ST.ID = A.ID
49          )
50 /
2 rows updated.
SQL> SELECT * FROM STAGING;
        ID A                                        B                                        E
         1 XXXXXXXXXXXXXXXXXXXXXXXXXX               XXXXXXXXXXXXXXXXXXXXXXXXX                Y
         2 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXX               Y
         3 XXXXXXXXXXXXXXXXXXXXXXXXX                XXXXXXXXXXXXXXXXXXXXXXXXXHopefully the comments make sense. If you have any questions please let me know.
This assumes the column names are the same between the staging and base tables. In addition as you add more columns to this table you'll have to add more CASE statements to check the length and update the COALESCE check as necessary.
Thanks!

Dropping base table of materialized view

HI please let me know what happens if i drop the base table of a materialized view? does the MV remain valid with data?

Hi,
Well, it's easy to test yourself.
SQL> select count(*) from t1;
COUNT(*)
       100
SQL> desc t1
Name                                      Null?    Type
ID                                                 NUMBER(10)
SQL> create materialized view t1_mv as select * from t1;
Materialized view created.
SQL> select count(*) from t1_mv;
COUNT(*)
       100
SQL> drop table t1 purge;
Table dropped.
SQL> select count(*) from t1_mv;
COUNT(*)
       100
SQL> desc t1_mv
Name                                      Null?    Type
ID                                                 NUMBER(10)
SQL> select object_type, status from user_objects where object_name = 'T1_MV';
OBJECT_TYPE         STATUS
TABLE               VALID
MATERIALIZED VIEW   INVALID
SQL> select * from t1_mv where rownum < 5;
        ID
         1
         2
         3
         4
SQL>I think the answer is very clear.
Asif Momen
http://momendba.blogspot.com

What are the Target Base Tables for FA_TAX_INTERFACE table?

Hi,
We are using "upload tax book interface" program to update the Tax Book informaiton.
For this we wanted to know all the Target Base Tables for FA_TAX_INTERFACE table (Specially for the ATTRIBUTE1-ATTRIBUTE15 columns of the interface table).
Kindly request you to help on this.
Thanks & Regards,
Satvik Patel

Well, what are you reconciling to? You are looking at something that seems to be different from your data extract, so what is that thing? My trouble shooting process is to take an asset that seems to be wrong and reconcile from the report/screen data to the extract data. You have to figure out what Oracle program is involved and what kind of SQL that the program is doing and what tables it is looking at. This could be an Oracle program error. I just ran into a problem on the Payables Posted Invoice Register report, where the total did not match my extract total. Turns out the report was wrong. If I had table records with a date/time stamp value (instead of just a date stamp value) in the accounting date field for the TO ACCOUNTING DATE value in my report request selection, those records were being dropped from the report. I reported this to Oracle support and found out that there is a patch to fix the problem (happens when cancelling an invoice) and a data script to follow to fix the historical data. So you have to keep an open mind. Yes, trying to find a reconciling issue can be very painful.
My reaction is that you are looking at the right tables. There is also a FA_DISTRIBUTION_HISTORY table that you may want to look into, that links back to the FA_DEPRN_DETAIL table. Maybe your issue lies there. At least something to look at.
John Dickey

Convertion of Base tables to Material views while executing dbms_refreshes

Hi all,
I have a typical type of problem. We have a daily task of database activities like monitoring the space, refreshing Material views etc and currently using While doing refreshing the materialized views (using dbms.refresh) All master tables are become MV's in the database.This is a serious issue has to be solved asap.
Also I find the materialized views got some data's in it. Now I want to get my master tables back to original.
I have an idea to drop all the respective base tables, materialized view and recreate the same once again.
But Is there any other alternate method there to get back my materialized views converted to base tables???
Can someone help me how to do the same????
Thanks in advance.
Regards
Dinesh

While doing refreshing the materialized views (using dbms.refresh)
All master tables are become MV's in the database?????
So strange that I'd say that's not possible. How did you check that ? and which command did you execute exactly ?

Changes of a base table PK/unique index

After alter a new column to a base table PK on the server, recreate the snapshot and run MGP the new unique index value did not update table C$ALL_INDEXES in client database conscli.odb. After sync two unique indexes were created for current table in lite.odb, one new and one old that still remains in table C$ALL_INDEXES in the client database conscli.odb.
Please, help me resolve this problem!

Drop and recreate the publication item using the APIs, then reset the metadata. That should fix the issue.

Using DAC for implementation of two change capture views on same base table

Hello
We have a need to create 2 views (V_INS_CLAIM & V1_INS_CLAIM) on a single table (S_INS_CLAIM) using DAC & Image tables.
The V_INS_CLAIM will be used to load ODS on a hourly basis and
The V1_INS_CLAIM will be used to load DataMart on a daily basis.
For this purpose, we propose using the following approach:
1) Create 2 separate containers - one for ODS and one for Datamart.
2) Use a separate image table suffix (for the same table) on each container e.g.
- Use image suffix 51 on S_INS_CLAIM for the ODS container (will result in image tables having suffix 51)
- Use image suffix 61 on S_INS_CLAIM for the Datamart container (will result in image tables having suffix 61)
3) In the ODS container, the change capture process would create a view V_INS_CLAIM using
the base table S_INS_CLAIM and the I/R/D tables using image suffix 51
For this folder the 'Drop and Create Change Capture Views Always' flag will be set to True
All views for this container will be created with the prefix "V_"
4) For the Datamart container, we propose to set the flag 'Drop and Create Change Capture Views Always' to False.
This would ensure that DAC never drops/creates the view (assuming that the view was already created by the ODS container)
For creating the change capture views, we propose to create the views using sql procedures.
All views for this container will be created with the prefix "V1_"
The above procedure would ensure that we have distinct views created for each target (ODS & Datamart), which are refreshed at different intervals.
Alternatively, instead of creating 2 views with different names in the SIEBEL schema,
we could create 2 schemas - one for ODS and the other for Datamart and create the change capture
views separately in each schema (using separate I/R/D image tables - as mentioned above).
Please let me know which of the above 2 approaches would work and supported by DAC and which would be the better option ?
Thanks

1.) Wrong forum. Go here: Business Intelligence Applications
2.) Soft delete or hard delete? Sound to me like you want to get rid of teh records. I.e. deleting history.
3.) Normal upsert mapping swon't do, you'll need delete mappings (depending on #2)

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 stored data after clicking check box save in data base table

TABLES:mseg,mard,mkpf.
TYPE-POOLS:slis.
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.
DATA:BEGIN OF itab OCCURS 0,
     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,
     checkbox TYPE c,
     END OF itab.
DATA: gt_fieldcat TYPE slis_t_fieldcat_alv,
       gw_fieldcat TYPE slis_fieldcat_alv,
       gt_layout TYPE slis_layout_alv.
START-OF-SELECTION.
SELECT msegmblnr msegmatnr mardwerks mardlgort mardlgpbe msegcharg msegbwart mkpfbudat
    msegmenge msegmeins msegkostl msegaufnr mseg~rsnum
INTO TABLE itab FROM
          mseg JOIN mard ON mardmatnr EQ msegmatnr
               JOIN mkpf ON msegmblnr EQ mkpfmblnr
               WHERE mseg~matnr IN smatnr.
IF sy-subrc EQ 0.
    SORT itab BY matnr.
    PERFORM display_alv_output.
ENDIF.
*&      Form display_alv_output
      text
--> p1        text
<-- p2        text
FORM display_alv_output.
REFRESH gt_fieldcat.
gw_fieldcat-fieldname = 'MBLNR'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 1.
gw_fieldcat-seltext_m = 'material document'.
gw_fieldcat-key = 'x'.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'MATNR'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 2.
gw_fieldcat-seltext_m = 'material'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'WERKS'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 3.
gw_fieldcat-seltext_m = 'plant'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'LGORT'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 4.
gw_fieldcat-seltext_m = 'storage location'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'LGPBE'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 5.
gw_fieldcat-seltext_m = 'storage bin'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'CHARG'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 6.
gw_fieldcat-seltext_m = 'Batch number'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'BWART'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 7.
gw_fieldcat-seltext_m = 'Movement Type (Inventory Management)'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'BUDAT'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 8.
gw_fieldcat-seltext_m = 'Posting Date in the Document'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'MENGE'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 9.
gw_fieldcat-seltext_m = 'QUANTITY'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'MEINS'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 10.
gw_fieldcat-seltext_m = 'Basic unit of measure'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'KOSTL'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 11.
gw_fieldcat-seltext_m = 'Cost center'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'AUFNR'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 12.
gw_fieldcat-seltext_m = 'Order Number'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'RSNUM'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 13.
gw_fieldcat-seltext_m = 'Number of Reservation / Depe'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-col_pos = 14.
gw_fieldcat-fieldname = 'CHECKBOX'.
gw_fieldcat-seltext_m = 'Compltd'.
gw_fieldcat-checkbox = 'X'.
gw_fieldcat-edit = 'X'.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
    I_CALLBACK_PROGRAM                = 'ZREPORT'
    IS_LAYOUT                         = gt_layout
    IT_FIELDCAT                       = gt_fieldcat
   TABLES
     t_outtab                          = itab
EXCEPTIONS
    PROGRAM_ERROR                     = 1
    OTHERS                            = 2.
ENDFORM.                    " display_alv_output
this is mycode .
send me replay.

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...

View's base table ?

how do i knw the views base table...
i can view text from user_source
but i there any dictionary table which show view name and base table name..?

Hmm , jsut a note to mention that you may use , v$fixed_view_definition also.
For example,
SQL> select view_definition
2 from v$fixed_view_definition where view_name=’V$LOG’;
VIEW_DEFINITION
select   GROUP# , THREAD# , SEQUENCE# , BYTES , MEMBERS , ARCHIVED , STATUS , FI
RST_CHANGE# , FIRST_TIME from GV$LOG where inst_id = USERENV(’Instance’)
SQL> select view_definition
2 from v$fixed_view_definition where view_name=’GV$LOG’;
VIEW_DEFINITION
select le.inst_id, le.lenum, le.lethr, le.leseq, le.lesiz*le.lebsz, ledup, decod
e(bitand(le.leflg,1),0,’NO’,'YES’), decode(bitand(le.leflg,24), 8, ‘CURRENT’,
                         16,’CLEARING’,                            24,’CLEARING_
CURRENT’,        decode(sign(leseq),0,’UNUSED’,        decode(sign((to_number(rt
.rtckp_scn)-to_number(le.lenxs))*        bitand(rt.rtsta,2)),-1,’ACTIVE’,'INACTI
VE’))), to_number(le.lelos), to_date(le.lelot,’MM/DD/RR HH24:MI:SS’,'NLS_CALENDA
R=Gregorian’) from x$kccle le, x$kccrt rt where le.ledup!=0 and le.lethr=rt.rtnu
m and le.inst_id = rt.inst_id
SQL>HTH
Aman....

ORA-01776: cannot modify more than one base table through a join view

I have created EO based on a database view than consists of two tables, and only one is updateable.
When I try to update a row using EO, I got a following message: "ORA-01776-cannot modify more than one base table through a join view"
In Forms, this issue is resolved by setting "Query Only" property of non-updateable items to "True".
Is it possible to do something like that in ADF BC?
Thanks

Thanks for answer.
When I set "updateable" property to "Never", that attribute is protected from any change.
I'm sorry for incomplete usecase.
I have set up a list of value on that attribute, because it is a lookup field for another table and I need to get an ID from that table.
Basically, I need that attribute to be updateble for BC, but not for database.
Edited by: MarioK on Oct 13, 2011 9:28 AM

Cannot modify more than one base table through a join view

hi guys, my current problem is that i have a datablock based on a view, now all the fields bar 1 are updateable, but this one field that is obtained through a join is displayed, the user can enter data in this field which then pupulates other fields which are required, but this specific field should not be updated. Is there an option to state this as i keep getting the error:
cannot modify more than one base table through a join view
Any help would be greatly appreciated, thanks.

the user can enter data in this field which then pupulates other fields So, using the value of "this field" you then query the rest of the fields? Can you show us the code you use to populate the rest of the fields?
but this specific field should not be updatedHave you tried setting the "Query Only" property of the field to "Yes" and the other DML properties (Ins, Upd, Del) to No?
Also, what is your Forms version?
Thanks,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

Create a materized view without primary key constraint on the base table?

Hi
I tried to create a materized view but I got this error:
SQL> CREATE MATERIALIZED VIEW TABLE1_MV REFRESH FAST
START WITH
to_date('04-25-2009 03:00:13','MM-dd-yyyy hh24:mi:ss')
NEXT
sysdate + 1
AS
select * from TABLE1@remote_db
SQL> /
CREATE MATERIALIZED VIEW TABLE1_MV REFRESH FAST
ERROR at line 1:
ORA-12014: table 'TABLE1' does not contain a primary key constraint.
TABLE1 in remote_db doesn't have a primary key constraint. Is there anyway that I can create a materized view on a base table which doesn't have a primary key constraint?
Thanks
Liz

Hi,
Thanks for your helpful info. I created a materialized view in the source db with rowid:
SQL> CREATE MATERIALIZED VIEW log on TABLE1 with rowid;
Materialized view log created.
Then I created a MV on the target DB:
CREATE MATERIALIZED VIEW my_schema.TABLE1_MV
REFRESH FAST
with rowid
START WITH
to_date('04-25-2009 03:00:13','MM-dd-yyyy hh24:mi:ss')
NEXT
sysdate + 1
AS
select * from TABLE1@remote_db
SQL> /
CREATE MATERIALIZED VIEW my_schema.TABLE1_MV
ERROR at line 1:
ORA-12018: following error encountered during code generation for
"my_schema"."TABLE1_MV"
ORA-00942: table or view does not exist
TABLE1 exists in remote_db:
SQL> select count(*) from TABLE1@remote_db;
COUNT(*)
9034459
Any clue what is wrong?
Thanks
Liz

Assigning a Value to a Base Table BLock Field

hi,
I have a form in which a block is a base table block . i need to change the value of a field. currently it shows the value of a field from the Table on which the block is based . I need to change the value of that field to display some other value of another table.
i have a written select statement like this
select name into vname from ws_emp where ecode = 101
then i have assigned to this base table field
:bt_person.ti_v_name := vname;
this i have created in the base table blocks Post query
but it is not assigning value
pls correct me and suggest me if there is any other better method to do this
Sarav

That SHOULD work in the Post-Query trigger of the block, but doing that is never a good idea. By replacing a base-table field with any value, it causes Forms automatic processing to lock the row immediately, so no other person running your form can call up the same data. And it causes Forms to think you need to update the record, so the record's status is changed to 'CHANGED' from 'QUERY'.
It would be better to create a non-base-table field in the block, and put the name into that field.

Base Table dropped

Similar Messages

Maybe you are looking for