Query request

Hi Experts
I would like some help from the experts on how to create a query to produce the following information:
I want to see any open sales orders that contain a product code that is not a Stocked Item.  I then only wish to see any that do not have a B2B purchase order linked to it.
Information required on the query is: -
u2022     S/O Number
u2022     BP Code
u2022     BP Name
u2022     S/O Posting Date
u2022     S/O Due Date
u2022     Item Number
u2022     Item Description
u2022     Free Text
u2022     Qty on S/O
u2022     Sales Employee
u2022     Owner
If it is possible you can display all orders and show in the last column of the query another heading (P/O Ref.)  This way any that do not have a B2B P/O will be blank.  If there is a P/O then I would like to have a drill down arrow in order to go into the P/O document. 
Thanks in advance
Jon Yen

Hi Jon,
Try this....
SELECT Distinct T0.[DocNum], T0.[CardCode], T0.[CardName], T0.[DocDate], T0.[DocDueDate], T1.[ItemCode],
T1.[Dscription], T1.[Quantity], T2.[SlpName] , T4.[firstName]+' '+T4.[lastName],T6.[DocNum] AS 'PO No.'
FROM ORDR T0
INNER JOIN RDR1 T1 ON T0.DocEntry = T1.DocEntry
INNER JOIN OITM T2 ON T1.ItemCode = T2.ItemCode
LEFT OUTER JOIN OSLP T3 ON T0.SlpCode = T3.SlpCode
LEFT OUTER JOIN OHEM T4 ON T0.empID = T4.OwnerCode
LEFT OUTER JOIN POR1 T5 ON T1.Docentry = T5.Baseentry and T1.LineNum=T5.Baseline
LEFT OUTER JOIN OPOR T6 ON T5.Docentry = T6.Docentry
WHERE T2.[InvntItem] = 'N' and  T0.[DocStatus] ='O'
Thanks
Sachin

Similar Messages

  • Content Tab: None of the fact tables are compatible with the query request

    Hi All,
    **One thing I am not clear yet of all my years with OBIEE is working with the content tab in BMM.**
    I have made a rpd the joins in physical layer as shown below:
    https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056545119428530
    And the BMM layer as:
    https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056519553812930
    Error I am getting when i run a request from the 3 columns from the selected 3 tables is:
    Dim - Comment Code Details
    Fact - Complaint
    Dim - Service Details
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14020] None of the fact tables are compatible with the query request Sr Num:[DAggr(Fact - Complaint.Sr Num by [ Dim - Service Details.Sr Cat Type Cd, Dim - Comment Code Details.Cmtcode name] )]. (HY000).
    I get no error for consistency.. I read everywhere and I know i need to set the appropriate aggregation levels in the various dims and facts LTS properties to help OBIEE understanding our model, but how to do that.. how do i decide... how should I approach, what should be the aggregation level, what details.
    When i click More button i see different options: Copy, Copy From, Get Levels, Check Level, what do these mean.
    Aggregation Content, group by - Logical Level or Column which one should i choose and how should I decide.
    Can anyone explain the Content Tab in details and from scratch with some example and why we get these errors.... I know many people who are well versed with many other things related to RPD but this. A little efforts of explaining from you guys will really be appreciated.
    Thanks in advance,
    Dev

    Hi Deepak,
    Option 1:
    My tables in physical layer are joined as below:
    D1--> F1 <--D2--> F2 <--D3
    Same way i model it in BMM
    D1--> F1 <-- D2--> F2 <--D3
    Here D1 is non Conformed Dimension for F2 and D3 is non Conformed dim for F1. Later create Dimensional hierarchies, I tried setting up the content levels
    I go Sources>content tab of Fact F1 I set
    Dimensions----------- Logical level
    D1---------------------- D1 Detail
    D2---------------------- D2 Detail
    D3---------------------- D3 Total
    then, I go Sources>content tab of Fact F2 I set
    Dimensions----------- Logical level
    D1---------------------- D1 Total
    D2---------------------- D2 Detail
    D3---------------------- D3 Detail
    Then, I also go in all the dimensions and set their content levels to Details, but it still gives me errors not sure where I am going wrong in setting the content levels.
    I need to know whether the way I have modeled it in BMM is right,
    Option 2:
    I can combine the two facts in a single Logical Fact or the above design should also work.
    (F1&F2)<--D1, D2 , D3 joined separately using complex logical joins.
    what will be the content tab details?
    Thanks,
    Dev

  • Essbase answers - None of the fact tables are compatible with the query request "member"

    Hi,
    I have modelled an Essbase database into the repository.
    If I pull the measure, period and year dimension in and filter on the year (member) and display the year (member) along with the period (alias) and measure it errors with =>
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request Fiscal Year.Fiscal Year Code. (HY000)
    However, all other things being equal if I change the year displayed to the alias then it works.
    Anyone tell me why??
    Is there a limitation that Essbase brings through that you cannot view what you filter on?
    thanks,
    Robert.

    Hi
    i have done the content level setting in each of the table, D1,F1 and F2(LTS), now i am getting the following error..
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Gl Sets Of Books) does not contain mapping for [Code Combinations.Code Combinations.Affiliate, GL Balances.GL Balances.Currency Code, GL Balances.GL Balances.PTD_Balance, Gl Sets Of Books.Gl Sets Of Books .SoB Name]. (HY000)
    Gl Balances : D1
    Code Commbination: F1
    Gl Sets Of Books : F2
    I have checked the joins in physical and BMM layer..all are fine..

  • Fact tables are compatible with the query request

    Hi,
    i am using 11g.In 10g working fine without any error.After migrate 10g into 11g below error will returning. What is the problem and How we will fix.Could you pls let me know.Thanks
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request FACT_AGENT_TIME_STATISTICS.FKEY. (HY000)
    SQL Issued: SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6, s_7, s_8, s_9, s_10 FROM ( SELECT 0 s_0, "Team Performance"."DIMENSION - LOCATION"."COUNTRY CODE" s_1, "Team Performance"."DIMENSION - TIME"."BUSINESS DATE" s_2, CASE WHEN "Team Performance"."DIMENSION - TEAM"."ROLE" ='TEAM LEADER' THEN 'Team Leader' ELSE "Team Performance"."DIMENSION - TEAM"."TEAM" END s_3, CASE WHEN '30 Mins Interval' ='15 Mins Interval' THEN "Team Performance"."DIMENSION - TIME"."15 Mins Interval" ELSE "Team Performance"."DIMENSION - TIME"."30 Mins Interval" END s_4, ((SUM("Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - ACD CALL HANDLING"+"Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - AFTER CALL WORK (ACW)")+SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AVAILABLE TIME"))/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_5, (SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AUX3 - TRAINING"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX4 - MEETING"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX5 - PROJECT"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX6 - COACHING")/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_6, (SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."STAFFED TIME")/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_7, COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE" s_8, MIN("Team Performance"."DIMENSION - TIME"."FULL DATE TIME") s_9, REPORT_AGGREGATE(((SUM("Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - ACD CALL HANDLING"+"Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - AFTER CALL WORK (ACW)")+SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AVAILABLE TIME"))/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") BY CASE WHEN '30 Mins Interval' ='15 Mins Interval' THEN "Team Performance"."DIMENSION - TIME"."15 Mins Interval" ELSE "Team Performance"."DIMENSION - TIME"."30 Mins Interval" END, CASE WHEN "Team Performance"."DIMENSION - TEAM"."ROLE" ='TEAM LEADER' THEN 'Team Leader' ELSE "Team Performance"."DIMENSION - TEAM"."TEAM" END) s_10 FROM "Team Performance" WHERE (("DIMENSION - TIME"."BUSINESS DATE" BETWEEN timestamp '2012-11-23 00:00:00' AND timestamp '2012-11-23 00:00:00') AND ("DIMENSION - LOCATION"."COUNTRY CODE" = 'US') AND ("DIMENSION - LOCATION".DEPARTMENT = 'CSG')) ) djm FETCH FIRST 65001 ROWS ONLY

    Back up your repository before following these steps:
    1 Reduce the problem report to minimum number of columns required to generate the error. This will usually identify which dimension and which fact are incompatible.
    2 Open the repository in the Administration tool and verify that the dimension and fact table join at the physical layer of the repository
    3 Verify that there is a complex join between the dimension and the fact in the business layer.
    4 Check the logical table sources for the fact table. At least one of them must have the Content tab set to a level in the hierarchy that represents the problem dimension. This is usually the detailed level.
    5 Check the logical table source Content tab for the dimension table. Unless there is a valid reason, this should be set to blank.
    6. Save any changes to the repository.

  • NQSError: 14020  : Fact Table Incompatible with Query Request

    Hi All,
    I am trying to add a new join to existing fact and dimension tables.
    These tables are already part of some star schemas.
    Now when I add the join , RPD doesn't show any consistency errors/warnings but when I create an analysis in OBIEE 11g, Measure from fact shows only null.
    When I looked at the log, the physical query just has a select statement querying the dimension table and following message :
    "COUNT converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request COUNT:[DAggr(CF_FACT1.COUNT by [ CD_DATE_4.DATE_KEY.. "
    Has anyone encountered similar problem ?   
    Few threads spoke about settign the content level but its not set for any date dimension we are using but it still works. Facing this problem only for the new join I am trying to add now.
    Thanks for any pointers
    Sujana                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Back up your repository before following these steps:
    1 Reduce the problem report to minimum number of columns required to generate the error. This will usually identify which dimension and which fact are incompatible.
    2 Open the repository in the Administration tool and verify that the dimension and fact table join at the physical layer of the repository
    3 Verify that there is a complex join between the dimension and the fact in the business layer.
    4 Check the logical table sources for the fact table. At least one of them must have the Content tab set to a level in the hierarchy that represents the problem dimension. This is usually the detailed level.
    5 Check the logical table source Content tab for the dimension table. Unless there is a valid reason, this should be set to blank.
    6. Save any changes to the repository.

  • Error: None of the fact tables are compatible with the query request

    Hi experts,
    I have one confirm dimension D1 and other two fact table F1 and F2 (F1 and F2 are connected to D1)
    when i create a report from D1 and F1 the report is running fine. But pull the column from F2 also in this report i am getting the following error
    None of the fact tables are compatible with the query request Code Combinations
    please suggest on the same.
    Regards,
    S

    Hi
    i have done the content level setting in each of the table, D1,F1 and F2(LTS), now i am getting the following error..
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Gl Sets Of Books) does not contain mapping for [Code Combinations.Code Combinations.Affiliate, GL Balances.GL Balances.Currency Code, GL Balances.GL Balances.PTD_Balance, Gl Sets Of Books.Gl Sets Of Books .SoB Name]. (HY000)
    Gl Balances : D1
    Code Commbination: F1
    Gl Sets Of Books : F2
    I have checked the joins in physical and BMM layer..all are fine..

  • None of the dimension tables are compatible with the query request

    Hi,
    i am experiencing the below error while querying columns alone from employee dimension (w_employee_d) in workforce profile SA. There is only one column in my report which is employee number coming from employee dimension. when i query other information like job, region, location etc i am not getting any error. the below error appears only when querying columns from employee dimension. the content tab level for the LTS of employee dimension is set to employee detail.
         View Display Error
    Odbc driver returned an error (SQLExecDirectW).
    Error Details
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14077] None of the dimension tables are compatible with the query request Dim - Employee.Employee Number. (HY000)
    SQL Issued: SELECT 0 s_0, "Human Resources - Workforce Profile"."Employee Attributes"."Employee Number" s_1 FROM "Human Resources - Workforce Profile" FETCH FIRST 65001 ROWS ONLY.
    couldn't able to know the exact reason. Any suggestions would be highly appreciated.
    Regards.

    hi user582149,
    It is difficult to answer you question with such a little amount of details. Could you specify:
    - how many facts/dimensions are you using in the query?
    - what is the structure of your Business Model?
    - which version of OBI are you using?
    - what does your log say?
    I hope to tell you more having the information above
    Cheers

  • "None of the fact tables are compatible with the query request " error

    I've got a situation where I have two facts(Fact_1, Fact_2) and three dimensions(dim_1,dim_2,dim_3) in 1 subject area. I've got dimension hierarchies setup for all the dimension tables.
    Dim_1 is one to many to Fact_1
    Dim_2 is one to many to Fact_2
    Dim_3 is one to many to both Fact_1 and Fact_2
    I've set up the content levels for the LTS for the Facts so that they are the lowest grain for dimensions they join to and the grand total grain for dimensions they do not join to.
    My rpd is consistent. When I run a report using an attribute from Dim_3 and Dim_1 or Dim_3 and Dim_2, the report comes back fine.
    But if I try to run a report using all three Dim tables, I get an error and the message "None of the fact tables are compatible with the query request ".
    First of all, is it possible to make a report using all three dimensions?
    Second, what's the best way to trouble shoot this error? Why are none of the fact tables compatible? I thought as long as the aggregation levels were set to grand total for non-shared dimensions, Answers would be able to create the report properly.
    Any advise would be greatly appreciated.
    Thanks!
    -Joe

    OBIEE is looking for a fact that can link ALL the dimensions together. This is also known as the implicit fact ... you don't have a fact that can relate all the dimensions - you have 2 facts that together they can. Perhaps you need to great a single logical fact that has both LTS for your physical facts and try it that way.
    Then you'd have Dim1, Dim 2, Dim3 all being able to join to Fact1 (which is made of physical facts 1 & 2).

  • Users are not able to query request submitted by other user .

    users are not able to query request submitted by some other user using the same responsibility .
    applications ver . 12.1.2

    I have just upgraded 11.5.10 to 12.1.3. I have followed doc ID 804296.1 so users can see out files within the same responsibility. But users still cannot see out files from other users. I really believe I have followed the doc completely. Any advice?
    SQL> select bug_number from ad_bugs where bug_number like '8671003';
    BUG_NUMBER
    8671003
    Also these are the steps I took per the doc:
    sysadmin >Functional Developer >Security > Objects
    Search on Database Object = FND_CONCURRENT_REQUESTS
    Click on Concurrent Requests.
    Click on Object Instance Sets tab.
    Click on Create Instance Set button.
    Name=Allow user to view other requests within same responsibility
    Code=XXFND_CONC_REQUESTS_01
    Description=Allow user to view other requests within same responsibility
    Predicate=
    &TABLE_ALIAS.request_id in (select cr.request_id from fnd_concurrent_requests cr where
    cr.responsibility_id = fnd_global.resp_id and cr.responsibility_application_id =
    fnd_global.resp_appl_id)
    Sysadmin >User Management >Roles and Role Inheritance
    Click Create Role button
    Catagory=Miscellaneous
    Role Code=UMX|XX_VIEW_OUTPUT
    Display Name=View Output For Same Responsibility
    Description=View Output For Same Responsibility
    Click Create Grant and "Save and Continue'
    Name=XX_VIEW_OUT
    Description=View output of other users in same resposibility
    Object=Concurrent Requests
    Click Next
    Data Content Type “Instance Set”
    Instance Set=Allow user to view other requests within same responsibility
    Click Next
    At the bottom
    Set=Request Operations
    Click Next> Finish
    Edited by: 893303 on Oct 26, 2011 6:53 AM

  • Unusual query request

    I have an unusual query request. Any comments are appreciated!
    For every column in the table, I need to count the distinct values, order the column names by descending and create 2 groups.
    Group 1:
    The columns that have the most distinct values.
    Group 2:
    The columns that have the fewest distinct values.
    Thanks

    Interesting but how do you determine what falls into GROUP 1 and what falls into GROUP 2. Is it a 50/50 split or what?
    This may be something for the SQL forum and I am sure there are a lot more elagant ways to do this. However, if it was a one time deal I would do it by brute force and off the top of my head I would do something like this.
    set heading off;
    set pagesize 0
    set linesize 200
    set echo off
    set feedback off;
    spool /tmp/selectioncount.sql
    select 'select count(distinct(column_name)) DISTCOUNT,'''||column_name||
    ''' COLUMN_NAME FROM '||OWNER||'.'||TABLE_NAME||';'
    FROM DBA_TAB_COLUMNS where table_name like 'MYTABLE';
    spool off;
    spool /tmp/results.lst
    @/tmp/selectioncount.sql
    spool off
    I would then edit /tmp/results.lst to get rid of any extraneous information like the sql prompts and then use the UNIX commands sort and split the results based on the first column.
    Again, not elegant...1 time shot.
    But done and overwith.
    Regards
    Tim

  • SQL query requested to pull one field out of multiple records

    Post Author: ralph.devlin
    CA Forum: Data Connectivity and SQL
    We use Track IT to manage our ticket base. We have parent work orders and child assignments that I am trying to report on. What I want to do is create a view, or even if this can be done in a formula, is pull data from the main work order, which in our scnerio and accorindg to the database diagrapm is WORKORDERTYPEID = 0, It will pull the TASKS.RESPONS field from that WO. Then it will compare the TASKS.PARETNWOID to WOID and if WORKORDERTYPEID = 1 then it needs to return the TASKS/RESPONS field of that record, and there may be three records or so. Then What I may need it to do is organize it maybe into seperate columns so I can add each one to Crystal keeping in mind that it will need to link those records to main WOID of the parent so it will display on one line. Any ideas
    Ralph

    Post Author: ralph.devlin
    CA Forum: Data Connectivity and SQL
    Ok I tried that and it seemed to work fine, here is an aexample of the data returned
    168458
    Lane, Carrie
    Ralph Devlin
    Ralph Devlin
    168458
    PHX - Training Room
    SM - 8th Fl Conf Room
    NULL
    NULL
    168458
    6/20/2008 3:30:00 PM
    Video Conference
    0
    168458
    Lane, Carrie
    Ralph Devlin
    Luis Estrada
    168458
    PHX - Training Room
    SM - 8th Fl Conf Room
    NULL
    NULL
    168458
    6/20/2008 3:30:00 PM
    Video Conference
    1
    Using the last column which is the workordertypeid, I was able to elimate the first row of data, which is the parent work order, but see how it is returning the technician name twice, where the second row returns me as the primary and then the technician on the assignment WO as well, which I want. In Crystal I have it only selecting the rows with the 1 is the last column, since those rows have the data arranged how I want them to be.
    Once issue that just arose, is what if we only had one work order that we wanted to report on in the subreport. since the WO will get a 0 in the last column, it will never be selected in the report. Is there a way to either us a statement that selects it if it is the only WO listed compared by the WOID field, or if there is a way in SQL, to get what is showing in row 2 to be the only row returned back so I can then show all work orders regardless if they are an assignment
    Here is my current SQL query
    SELECT     T1.WOID, T1.REQUEST, T1.RESPONS, T2.RESPONS AS Addtech, T2.PARENTWOID, T1.LOOKUP2, T1.TaskLookup3, T1.TaskLookup4, T1.TaskLookup5,                       T1.WO_NUM, T1.DUEDATE, T1.WOTYPE3, T2.WorkOrderTypeIdFROM         dbo.TASKS AS T1 LEFT OUTER JOIN                      dbo.TASKS AS T2 ON T2.PARENTWOID = T1.WOID

  • "None of the fact tables are compatible with the query request"

    Hi guys,
    I have a weird issue. Previously fine working Subject area started to give this error after migration. The issue is happening when I select a column from dimension and try to display it. Also, I can't get to the list of values in filter I get "Error retrieving choices" error. One dimension is working fine though, and when a column from it is selected, it displays other column just fine. I checked physical layer, primary keys, mappings in the BMM, LTS sources, Connection Pool settings. Everything looks legit. For few hours it was working fine, and now it's giving this issue. Anyone knows what the cause could be. The search I've conducted revealed that this is a data mapping issue - however, all my layers seem to be in check. Thanks

    hi user582149,
    It is difficult to answer you question with such a little amount of details. Could you specify:
    - how many facts/dimensions are you using in the query?
    - what is the structure of your Business Model?
    - which version of OBI are you using?
    - what does your log say?
    I hope to tell you more having the information above
    Cheers

  • 10g Feature Query/Request

    Is it possible to set the tab size to different amounts for different file types? For instance, I like my Java source code to have a relatively large indentation, as I believe this enhances readability. However, XML files tend to have much deeper nesting, and therefore a large tab size quickly results in having to scroll the document to the right to see the innermost content. Anything nested this deeply in source code is probably bad code and should be refactored, but this happens all the time in UIX, for example, since almost every tag needs an additional 'contents' tag.
    I can only find one global tab size setting in the 'Code Editor' properties. If there isn't currently any way to set this size differently for individual file types, please consider this feature for future releases.

    You can tell Apple your wishes directly using this link: http://www.apple.com/feedback/iphone.html

  • Feature query/request:Home button functionality (triple & quadruple clicks)

    Hi all,
    I severely lack the ability to bind the triple-click on the home button on my iPhone 3GS to something useful. For me, that would be to access the "add new inbox item" in Omnifocus. For others, it could be opening the voice memos app and starting to record audio. Is it possible to enable this functionality (accessing app specific functionality, with bonus points for doing this when the iPhone is locked) without resorting to jailbreak? Is this functionality something anyone else would find welcome?
    Oh, and in the perfect world, a quadruple click would start a recording of audio, inside a new inbox item within Omnifocus. This is an accessibility settings that would make my iPhone and its workflow more accessible to me.

    You can tell Apple your wishes directly using this link: http://www.apple.com/feedback/iphone.html

  • Richiesta query , request query

    Salve ,
    avrei un problema dovrei estrarre da un package che contiene delle procedure tutti i dblink presenti avendo come risultato la seguente tabella :
    Nome Package | Nome Procedura | Dblink (presente nel procedura) |
    Grazie
    Scusate per l'inglese
    Hi, I would have a problem I should extract from a package that it contains some procedures all the present dblinks having as resulted the following chart :
    Name Package | Name Procedure | Dblink (it foresees in the procedure) |
    Thank you
    You excuse for the English

    Following table has the details of the data base link available in the database.
    SQL> select * from dictionary where table_name like '%LINK%'
      2  /
    TABLE_NAME           COMMENTS
    USER_DB_LINKS        Database links owned by the user
    DBA_DB_LINKS         All database links in the database
    ALL_DB_LINKS         Database links accessible to the user
    V$DBLINK             Synonym for V_$DBLINK
    GV$DBLINK            Synonym for GV_$DBLINKNot sure if you are looking for this..
    Thanks,
    Karthick.

Maybe you are looking for