BASIS Tables

Hi Gurus,
I require the mane of table in which i can find the following information
1.)type of system (system info)
2.)client
3.)server model (like NT or UNIX)
4.)Instances
5.)Server Names
6.)Memory info
7.)Operating system
8.)SAP SID's
I only know 2 tables i.e, T000 and CVERS
Can anyone help for the rest.
Regards
Anthony D'souza

dear Anthony D'souza,
why using table, if there is tcode provided by SAP to monitor it all ?
here I show you the way
using TCode ST06 > detail analysis menu> HW info
it tells you system model, no. of CPU, disks, tapes, memory, network interface, disk config, swap utilization and kernel parameters
using TCode ST06 > detail analysis menu> Operating System Collector> Details On
it tells you OS type and version, hostname of your server,
SAP SID, client, program currently running and user ID can be seen on the bottom right corner of your GUI screen
hope it help you.
rgds,
alfonsus guritno

Similar Messages

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

Hi
I am trying to create a view.
Chosing a sap table fo ex: likp
and a customized table activated which is having a customized field with curr reference field as waerk of vbak (reference table).
Now while i am activating the view i have an error : the customized table is not a base table
please le tme know what is a base table and how can i successfully create my view .
thanks in advance
points will be awarded
vgmnm

Hi,
Try to create a view on normal application tables , and dont include any customizable table as base table in view creation. because those customizatable table can be maintained through SPRO only. So it wont allow you to include that in the view creation.
Regards,
Naveen

How to know who has created a particular record in the data base table

Hi All...
Can any one tell me how to track the information about who has entered the records in to the data base table....
Thanks in advance...

You could check the Created By and Created On fields if your tables contains these fields.
OR
You could check the table DBTABLOG if table logging is enabled for the table
OR
You could check the Change document tables CDHDR and CDPOS.
-Kiran
Please mark useful answers

Data is visible in base tables of BOM routing but not visible in front end

Hi,
Through BOM_RTG_PUB API I am populating routing data into base tables, it is successfull.. but that data is not visible in front end when i queried from front end..
i am getting error while i run API as......
An error occured while processing business object BOM_ITEM12 in organization MMO. Please check the data in this business object and re-run the import process.
Can any one help me in finding out what's wrong with this..
Thanks in advance..
Edited by: 875417 on Feb 6, 2012 10:49 PM

Your obeservation is correct, and expected behavior.
This behavior is useful when you have inputs that you would like to set as defaults for the user.
Obviously, if there is a value to be saved, it will require some memory to store the value.
If the input is left empty by default, that memory is made available again.
It may not be easy to think of a good use for this for a graph, but think about for numeric or string controls.
What if the user isnt sure how they should input a certain parameter or value?
You could store a default value so they could see how they should input their value.
Message Edited by Cory K on 09-15-2009 11:12 AM
Cory K

Creation of field in data base table

Hi,
I want to create a field in data base table , which holds the float values but i don't want to use the FLTP data type, why bcoz if i use this data type in selection screen of the table the the field is not appeqring, i dont want to go for the option QUAN bcoz there i need to define the ref table and ref field.
please explain what is the way to create this field.
regards
Krishna

Use NUMC
Awrd POints if useful
Bhupal

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.

CC&B 2.3.1 - Custom indexes for base tables

Hi,
We are seeing a couple of statements in the database that could improve its performance with new custom indexes on base tables. Questions are:
- can we create new indexes on base tables ?
- is there any recommendations about naming, characteristics and location for this indexes ?
- is there any additional step to do in CC&B in order to use the index (define metadata or ...) ?
Thanks.
Regards.

Hi,
if it necessary You can crate custom index.
In this situation You should follow naming convention from Database Design Standards:
Indexes
Index names are composed of the following parts:
+[X][C/M/T]NNN[P/S]+
+•     X – letter X is used as a leading character of all base index names prior to Version 2.0.0. Now the first character of product owner flag value should be used instead of letter X. For client specific implementation index in Oracle, use CM.+
+•     C/M/T – The second character can be either C or M or T. C is used for control tables (Admin tables). M is for the master tables. T is reserved for the transaction tables.+
+•     NNN – A three-digit number that uniquely identifies the table on which the index is defined.+
+•     P/S/C – P indicates that this index is the primary key index. S is used for indexes other than primary keys. Use C to indicate a client specific implementation index in DB2 implementation.+
Some examples are:
+•     XC001P0+
+•     XT206S1+
+•     XT206C2+
+•     CM206S2+
Warning! Do not use index names in the application as the names can change due to unforeseeable reasons
There is no additional metadata information for indexes in CI_MD* tables - because change of indexes does not influence generated Java code.
Hope that helps.
Regards,
Bartlomiej

BASIS Tables

Similar Messages

Maybe you are looking for