How to see the constraints defined on table?

Hi i want to know how can i view a constraint defined on table. Like which is the foreign key and so on.
how can i do it ? is there any sql command?

Hi,
use the below Queries:
SELECT * FROM user_constraints
SELECT * FROM user_cons_columns
SELECT * FROM all_constraints
SELECT * FROM all_cons_columns
SELECT * FROM dba_constraints
SELECT * FROM DBA_cons_columns
Regards
K.Rajkumar

Similar Messages

SOST - transmission requests- How to see the log in a table

We see the messages and the log in SOST for a background job.
We want to see the log contents in a related table.
We checked table SOOD but can not see the log details.
Is there any way to see / extract log details by giving the user ID , created date and job name?
Regards,

Hi
If you are using the Extending classic, you can see the output details in the SOST. suppose if you want to check whether the PO send to vendor or not viea email.
BR
Satish

How to see the Table Names & Field Names by other than F1 help

Hi Experts
   How to see the Table Names & Field Names by other than F1 help, & How to see the List of MM Table Names.
Rgds

The only option to see the active table/ field name is through F1 --> Technical Information. Apart from this, you can use any 3rd part application like GUIex (INbuilt in SAP ECC 6.0 ... can be activated by clicking on the tri-color button on the top right), but you need technical knowledge to understand the information. As far consolidated list of MM tables is concerned, SAP don;t provide you the same at one place, it experience and knowledge which help you in this regard. For your immediate reference MM tables are as under :
EBAN - Purchase Requisition
EBKN - Purchase Requisition Account Assignment
EBUB   - Index for Stock Transport Requisitions for Materi
EINA    - Purchasing Info Record: General Data
EINE     - Purchasing Info Record: Purchasing Organization D
EIPA     - Order Price History: Info Record
EKAB   - Release Documentation
EKAN   - Vendor Address: Purchasing Document
EKBE    - History per Purchasing Document
EKBEH - Removed PO History Records
EKBZ    - History per Purchasing Document: Delivery Costs
EKBZH - History per Purchasing Document: Delivery Costs
EKEH    - Scheduling Agreement Release Documentation
EKEK    - Header Data for Scheduling Agreement Releases
EKES     - Vendor Confirmations
EKET     - Scheduling Agreement Schedule Lines
EKETH   - Scheduling Agreement Schedules: History Tables
EKKI      - Purchasing Condition Index
EKKN    - Account Assignment in Purchasing Document
EKKO    - Purchasing Document Header
EKPA     - Partner Roles in Purchasing
EKPB     - "Material Provided" Item in Purchasing Document
EKPO    - Purchasing Document Item
EKPV    - Shipping-Specific Data on Stock Tfr. for Purch. D
EKRS    - ERS Procedure: Goods (Merchandise) Movements to b
EKUB    - Index for Stock Transport Orders for Material
EORD    - Purchasing Source List
EQUK    - Quota File: Header

Reg: how to see the Assets in Tables

HI all,
How to see the assets in internal tables
regards
JK Rao

Hi,
ANAR     Asset Types
ANAT     Asset type text
ANEK     Document Header Asset Posting
ANEP     Asset Line Items
ANEV     Asset downpymt settlement
ANKT     Asset classes- Description
ANLA     Asset Master Record Segment
ANLB     Depreciation terms
ANLC     Asset Value Fields
ANLH     Main asset number
reward pts if useful
regds

How to switch off the constraints of database tables

hi
how can i switch off the constraints of database tables?

But do remember that if once you disable to constraints, enter some data and then try to enable again. If there is some conflicting data, Oracle is going to cry and will not allow you to enable the constraints.
Sidhu

Reg: how to see the vendor details and general ledger details in tables

HI all
how to see the vendor details and general ledger details in tables.
regards
JK Rao

General ledger transactions are available in following table;
1. BKPF & BSEG
2. BSIS - Open Items
3. BSAS - Cleared Itesm
For vendor
1. BSIK - Open Items
2. BSAK - Cleared Items
For Customers
1 BSID - Open Items
2. BSAD - Cleared Items
Regards
Rakesh Pawaskar

How to see the table in se11 that has been created in oracle 10g directly

hi,
how to see the table in se11 that has been created at SQL> prompt in oracle 10g directly ?
is there any procedure to attache directly created table into sap ?

I think you have to create it in SE11 first. Although you can probably use native SQL to access it from an ABAP program.
Rob

How to see the logic in an existing range partition table of a database.

Hi I need to see the logic used in a Range partitioned table in a database.
I need this because i need to create a db similar to this.
This is a live database.
Version used :10.2.0.3.0
How can i seee this
Cheers,
Kunwar

How to get that.
For example if i want to see the script for a table. I get this eror
SQL> select dbms_metadata.get_ddl('TABLE','x) from dual;
ERROR:
ORA-31603: object "x" of type TABLE not found in schema "SYS"
ORA-06512: at "SYS.DBMS_METADATA", line 1546
ORA-06512: at "SYS.DBMS_METADATA", line 1583
ORA-06512: at "SYS.DBMS_METADATA", line 1901
ORA-06512: at "SYS.DBMS_METADATA", line 2792
ORA-06512: at "SYS.DBMS_METADATA", line 4333
ORA-06512: at line 1
And i dont know the login details of that user..

How to delete the data from partition table

Hi all,
Am very new to partition concepts in oracle..
here my question is how to delete the data from partition table.
is the below query will work ?
delete from table1 partition (P_2008_1212)
we have define range partition ...
or help me how to delete the data from partition table.
Thanks
Sree

874823 wrote:
delete from table1 partition (P_2008_1212)This approach is wrong - as Andre pointed, this is not how partition tables should be used.
Oracle supports different structures for data and indexes. A table can be a hash table or index organised table. It can have B+tree index. It can have bitmap indexes. It can be partitioned. Etc.
How the table implements its structure is a physical design consideration.
Application code should only deal with the logical data structure. How that data structure is physically implemented has no bearing on application. Does your application need to know what the indexes are and the names of the indexes,in order to use a table? Obviously not. So why then does your application need to know that the table is partitioned?
When your application code starts referring directly to physical partitions, it needs to know HOW the table is partitioned. It needs to know WHAT partitions to use. It needs to know the names of the partitions. Etc.
And why? All this means is increased complexity in application code as this code now needs to know and understand the physical data structure. This app code is now more complex, has more moving parts, will have more bugs, and will be more complex to maintain.
Oracle can take an app SQL and it can determine (based on the predicates of the SQL), which partitions to use and not use for executing that SQL. All done totally transparently. The app does not need to know that the table is even partitioned.
This is a crucial concept to understand and get right.

Regarding how to delete the record in internal table

Hi experts ,
how to delete the record in intarnal table after validating the data,
if record contains invalid fields?
i am giving my code see this and give me the answer?
loop at it_data into wa_data .
Validate Cost Center
    READ TABLE it_kostl INTO wa_kostl WITH KEY kostl = wa_data-kostl BINARY SEARCH.
    IF sy-subrc NE 0.
      PERFORM update_error_log USING wa_data
                                     text-004.
    ENDIF.
Validate source file material ( material number )
loop at it_mara into wa_mara .
read table it_ausp into wa_ausp with key atwrt = wa_data-i_matnr .
           if sy-subrc NE 0 .
   PERFORM update_error_log USING wa_data
                                       text-002.
delete it_data-objek .
     else.
read table it_mara into wa_mara with key matnr = wa_ausp-objek .
       if sy-subrc EQ 0 .
       wa_data-objek = wa_mara-matnr.
       wa_data-matkl = wa_mara-matkl.
     ENDIF.
     Modify it_data from wa_data .
endif.
*endloop.
Validate unit of measure (unit)
    READ TABLE it_t006 INTO wa_t006 WITH KEY msehi = wa_data-unit .
    IF sy-subrc NE 0.
      PERFORM update_error_log USING wa_data
                                     text-003.
    endif.
Validate delivery location ( storage location )
    READ TABLE it_lgort INTO wa_lgort WITH KEY del_loc = wa_data-del_loc.
    IF sy-subrc NE 0.
      PERFORM update_error_log USING wa_data
                                     text-001.
         if wa_data-flag ='x' .
      delete it_data from wa_data .
    endif.
    ENDIF.
endloop.

Hi Naren,
First get the index number of the IT_data table and store it in one variable whose declaration like this.
data: tabix type sy-tabix.
while reading the internal table it_data set the tabix variable.
tabix = sy-tabix.
Instead of the above use below one.
Delete it_data-objek
Use the Below statement it will delete the row from the internal table.
Delete it_data-objek index tabix
Thanks,
Chidanand

How to see lock status of a table ?

Hi,
My question is : how to see the lock status of a table ?
and how to lock a table except run the FM ENQUEUE_TABLENAME?
Is there any transcation that can lock a table ?
thx in advance.

Hi Vincent
Via transaction SM12 we can check the lock entries at a particular point of time...
Kind Regards
Eswar

Get Error while update the User defined row table through DSK Code

Hi experts,
I have got an error while updating the user row defined table.
Error is - "Invalid row"
I have created one master table "@CBF_FARM " and Child table "@CBF_FAR1"
First i inserted 5 record in the child table so in my my child table there are 5 Line id (1,2,3,4,5 one for each row).
after that i delete 2 rows (3rd & 4th row) from child table now in my child table there are 3 rows( Line id 1, 2, 5). Please See attachment.
Now i am updating the last record of child table through Code (Line id is 5) from other form, then i got error invalid row.
Following Code used for updating the user defined child table.
SAPbobsCOM.GeneralService oGeneralService1 = null;
                                SAPbobsCOM.GeneralData oGeneralData1 = null;
                                SAPbobsCOM.GeneralDataParams oGeneralParams1 = null;
                                SAPbobsCOM.CompanyService sCmp1 = null;
                                SAPbobsCOM.GeneralData oChild1 = null;
                                SAPbobsCOM.GeneralDataCollection oChildren1 = null;
                                sCmp1 = clsAddOn.LDNA_Company.GetCompanyService();
                                oGeneralService1 = sCmp1.GetGeneralService("CBF_FARM");
                                // Get UDO record
                                oGeneralParams1 = ((SAPbobsCOM.GeneralDataParams)(oGeneralService1.GetDataInterface(SAPbobsCOM.GeneralServiceDataInterfaces.gsGeneralDataParams)));
                                oGeneralParams1.SetProperty("Code", oForm.Items.Item("edtFarmCd").Specific.Value);
                                oGeneralData1 = oGeneralService1.GetByParams(oGeneralParams1);
                                // Add lines on UDO Child Table
                                oChildren1 = oGeneralData1.Child("CBF_FAR1");
                                // Create data for rows in the child table
                                SAPbouiCOM.Item oItem = oForm.Items.Item("cmbShed");
                                oCombo = oItem.Specific;
                                string ShedCode = oCombo.Selected.Value;
                                ldna_Rec = clsAddOn.LDNA_Company.GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset);
                                string strQuery1 = "select LineId from [@CBF_FAR1] where U_ShedCd = " + ShedCode;
                                ldna_Rec.DoQuery(strQuery1);
                                oChild1 = oChildren1.Item(ldna_Rec.Fields.Item("LineId").Value - 1);
                                oChild1.SetProperty("U_Status", "Ready For Schedule");
                                //Update the UDO Record
                                oGeneralService1.Update(oGeneralData1);
Please Help me it is an urgent requirement,
-Regards
Vikas

hi.
Error is - "Invalid row"
Now i am updating the last record of child table through Code (Line id is 5) from other form, then i got error invalid row.
As per my knowledge
What i understood is you have 5 lines and you are going to be update 5th line
am i correct..
while u are updating the line in child table
you have to consider like this..
line number         u have to update like
1                                        0
2                                        1
3                                        2
4                                        3
5                                        4
which means in child table treat
line 1 as 0
line 2 as 1
line 5 as 4
If you want to update the line 5 u have to mention 4 th line

How to see the result

hi every body...
i want to get the result of any table..
for ex: select * from dept;
the o/p should be like(10~Accounts~new york)
for this i wrote this code.... it run sucessfully;
my prob is how to see the Result..
declare
tn varchar2(35);
sqlstmt varchar2(2000);
rc sys_refcursor;
begin
tn := '&tn';
sqlstmt := 'select * from '||tn;
open rc for sqlstmt;
end;
post u r comments,Hints and suggestion...

post u r comments,Hints and suggestion...
SQL> var rc refcursor
SQL> begin
2     open :rc for 'select * from &tn';
3 end;
4 /
Enter value for tn: emp
old   2:    open :rc for 'select * from &tn';
new   2:    open :rc for 'select * from emp';
PL/SQL procedure successfully completed.
SQL> print rc
     EMPNO ENAME      JOB              MGR HIREDATE         SAL       COMM     DEPTNO
      7369 SPENCER    CLERK           7902 17-DEC-80        800                    20
      7499 VERREYNNE SALESMAN        7698 20-FEB-81       1600        300         30
      7521 VAN WIJK   SALESMAN        7698 22-FEB-81       1250        500         30
      7566 MAINGUY    MANAGER         7839 02-APR-81       2975                    20
      7654 KISHORE    SALESMAN        7698 28-SEP-81       1250       1400         30
      7698 BARRY      MANAGER         7839 01-MAY-81       2850                    30
      7782 BOEHMER    MANAGER         7839 09-JUN-81       2695                    10
      7788 PADFIELD   ANALYST         7566 09-DEC-82       3000                    20
      7839 SCHNEIDER PRESIDENT            17-NOV-81       5500                    10
      7844 GASPAROTTO SALESMAN        7698 08-SEP-81       1500          0         30
      7876 CAVE       CLERK           7788 12-JAN-83       1100                    20
      7900 CLARKE     CLERK           7698 03-DEC-81        950                    30
      7902 JAFFAR     ANALYST         7566 03-DEC-81       3000                    20
      7934 ROBERTSON CLERK           7782 23-JAN-82       1430                    10
       109 JOMAR                                                                   30
      8800 VISWARAYAR INTERN          7934 03-OCT-82          0                    10
16 rows selected.
SQL> Cheers, APC
Blog : http://radiofreetooting.blogspot.com/

How to see the MM invoice changes in sap?

Hi
How to see the MM invoice changes in sap ?

Dear Prashant,
When ever we perform LIV and is blocked for payment (due to price variance or other variance) is stored on table RBKP_BLOCKED
Now when we release it through t. Code MRBR that time its get deleted from RBKP_BLOCKED
So you can always track it :
Go to ->SE16 ->Enter table name CDHDR -.>Table contents (F7)
In the selection screen enter
OBJECTCLAS as INCOMINGINVOICE
OBJECTID as =Invoice no+year (e.g 51056066022011 where is 5105606602 invoice no 2011 is year)
TCODE as MRBR
->Execute
You will find the details when it was released Date ,Time, User ID etc
Edited by: redriver on Dec 26, 2011 2:23 PM

How to increase the length of internal table dynamically

How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
The requirement code :
types: begin of t_data,
         form          like zscr_data_hdr-form,
         werks         like zscr_data_hdr-werks,
         matnr         like zscr_data_hdr-matnr,
         verid         like zscr_data_hdr-verid,
         lot           like zscr_data_hdr-lot,
         lot_qty       like zscr_data_hdr-lot_qty,
         udate         like zscr_data_hdr-udate,
         utime         like zscr_data_hdr-utime,
         zuser         like zscr_data_hdr-zuser,
         processed     like zscr_data_hdr-processed,
         defect        like zscr_defect_data-defect,
         vornr         like zscr_route_data-vornr,
         fld1          like zscr_defect_data-defect_val,
         fld2          like zscr_defect_data-defect_val,
         fld3          like zscr_defect_data-defect_val,
         fld4          like zscr_defect_data-defect_val,
         fld5          like zscr_defect_data-defect_val,
         fld6          like zscr_defect_data-defect_val,
         fld7          like zscr_defect_data-defect_val,
         fld8          like zscr_defect_data-defect_val,
         fld9          like zscr_defect_data-defect_val,
         fld10         like zscr_defect_data-defect_val,
         fld11         like zscr_defect_data-defect_val,
         fld12         like zscr_defect_data-defect_val,
         fld13         like zscr_defect_data-defect_val,
         fld14         like zscr_defect_data-defect_val,
         fld15         like zscr_defect_data-defect_val,
         fld16         like zscr_defect_data-defect_val,
         fld17         like zscr_defect_data-defect_val,
         fld18         like zscr_defect_data-defect_val,
         fld19         like zscr_defect_data-defect_val,
         fld20         like zscr_defect_data-defect_val,
         fld21         like zscr_defect_data-defect_val,
         fld22         like zscr_defect_data-defect_val,
         fld23         like zscr_defect_data-defect_val,
         fld24         like zscr_defect_data-defect_val,
         fld25         like zscr_defect_data-defect_val,
         fld26         like zscr_defect_data-defect_val,
         fld27         like zscr_defect_data-defect_val,
         fld28         like zscr_defect_data-defect_val,
         fld29         like zscr_defect_data-defect_val,
         fld30         like zscr_defect_data-defect_val,
         fld31         like zscr_defect_data-defect_val,
         fld32         like zscr_defect_data-defect_val,
         fld33         like zscr_defect_data-defect_val,
         fld34         like zscr_defect_data-defect_val,
         fld35         like zscr_defect_data-defect_val,
         fld36         like zscr_defect_data-defect_val,
         fld37         like zscr_defect_data-defect_val,
         fld38         like zscr_defect_data-defect_val,
         fld39         like zscr_defect_data-defect_val,
         fld40         like zscr_defect_data-defect_val,
         fld41         like zscr_defect_data-defect_val,
         fld42         like zscr_defect_data-defect_val,
         fld43         like zscr_defect_data-defect_val,
         fld44         like zscr_defect_data-defect_val,
         fld45         like zscr_defect_data-defect_val,
         fld46         like zscr_defect_data-defect_val,
         fld47         like zscr_defect_data-defect_val,
         fld48         like zscr_defect_data-defect_val,
         fld49         like zscr_defect_data-defect_val,
         fld50         like zscr_defect_data-defect_val,
         fld51         like zscr_defect_data-defect_val,
         fld52         like zscr_defect_data-defect_val,
         fld53         like zscr_defect_data-defect_val,
         fld54         like zscr_defect_data-defect_val,
         fld55         like zscr_defect_data-defect_val,
         fld56         like zscr_defect_data-defect_val,
         fld57         like zscr_defect_data-defect_val,
         fld58         like zscr_defect_data-defect_val,
         fld59         like zscr_defect_data-defect_val,
         fld60         like zscr_defect_data-defect_val,
         fld61         like zscr_defect_data-defect_val,
         fld62         like zscr_defect_data-defect_val,
         fld63         like zscr_defect_data-defect_val,
         fld64         like zscr_defect_data-defect_val,
         fld65         like zscr_defect_data-defect_val,
         fld66         like zscr_defect_data-defect_val,
         fld67         like zscr_defect_data-defect_val,
         fld68         like zscr_defect_data-defect_val,
         fld69         like zscr_defect_data-defect_val,
         fld70         like zscr_defect_data-defect_val,
         fld71         like zscr_defect_data-defect_val,
         fld72         like zscr_defect_data-defect_val,
         fld73         like zscr_defect_data-defect_val,
         fld74         like zscr_defect_data-defect_val,
         fld75         like zscr_defect_data-defect_val,
         fld76         like zscr_defect_data-defect_val,
         fld77         like zscr_defect_data-defect_val,
         fld78         like zscr_defect_data-defect_val,
         fld79         like zscr_defect_data-defect_val,
         fld80         like zscr_defect_data-defect_val,
         fld81         like zscr_defect_data-defect_val,
         fld82         like zscr_defect_data-defect_val,
         fld83         like zscr_defect_data-defect_val,
         fld84         like zscr_defect_data-defect_val,
         fld85         like zscr_defect_data-defect_val,
         fld86         like zscr_defect_data-defect_val,
         fld87         like zscr_defect_data-defect_val,
         fld88         like zscr_defect_data-defect_val,
         fld89         like zscr_defect_data-defect_val,
         fld90         like zscr_defect_data-defect_val,
         fld91         like zscr_defect_data-defect_val,
         fld92         like zscr_defect_data-defect_val,
         fld93         like zscr_defect_data-defect_val,
         fld94         like zscr_defect_data-defect_val,
         fld95         like zscr_defect_data-defect_val,
         fld96         like zscr_defect_data-defect_val,
         fld97         like zscr_defect_data-defect_val,
         fld98         like zscr_defect_data-defect_val,
         fld99         like zscr_defect_data-defect_val,
         fld100         like zscr_defect_data-defect_val,
         fld101         like zscr_defect_data-defect_val,
         fld102         like zscr_defect_data-defect_val,
         fld103         like zscr_defect_data-defect_val,
         fld104         like zscr_defect_data-defect_val,
         fld105         like zscr_defect_data-defect_val,
         fld106         like zscr_defect_data-defect_val,
         fld107         like zscr_defect_data-defect_val,
         fld108         like zscr_defect_data-defect_val,
         fld109         like zscr_defect_data-defect_val,
         fld110         like zscr_defect_data-defect_val,
         fld111         like zscr_defect_data-defect_val,
         fld112         like zscr_defect_data-defect_val,
         fld113         like zscr_defect_data-defect_val,
         fld114         like zscr_defect_data-defect_val,
         fld115         like zscr_defect_data-defect_val,
         fld116         like zscr_defect_data-defect_val,
         fld117         like zscr_defect_data-defect_val,
         fld118         like zscr_defect_data-defect_val,
         fld119         like zscr_defect_data-defect_val,
         fld120         like zscr_defect_data-defect_val,
         fld121         like zscr_defect_data-defect_val,
         fld122         like zscr_defect_data-defect_val,
         fld123         like zscr_defect_data-defect_val,
         fld124         like zscr_defect_data-defect_val,
         fld125         like zscr_defect_data-defect_val,
         fld126         like zscr_defect_data-defect_val,
         fld127         like zscr_defect_data-defect_val,
         fld128         like zscr_defect_data-defect_val,
         fld129         like zscr_defect_data-defect_val,
         fld130         like zscr_defect_data-defect_val,
         fld131         like zscr_defect_data-defect_val,
         fld132         like zscr_defect_data-defect_val,
         fld133         like zscr_defect_data-defect_val,
         fld134         like zscr_defect_data-defect_val,
         fld135         like zscr_defect_data-defect_val,
         dayst         like zscr_data_hdr-dayst,
       end of t_data.
In this fld1 to fld135 are defined in internal table.
But if the number of fields are more than 135 then the program is going to short dump.
Some times fld1 to fid170 or more fields will be there in my internal table.
Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

Hi
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Max

How to see the constraints defined on table?

Similar Messages

Maybe you are looking for