CURSOR_SHARING universe parameter

Does anyone know if the CURSOR_SHARING parameter is supported in a universe (BOXI R2 SP3, FP3.3)?  BOXI R2 is running on AIX, and the reporting and CMS databases are on Oracle 10g.  On the database side, CURSOR_SHARING is set to FORCE.  On the universe side, we want to set the CURSOR_SHARING value to EXACT.  Is this possible?

The solution to this is to add the following value to the ConnectInit parameter in the Universe Connection, "alter session set cursor_sharing=exact".  Don't use the double quotes in your value.

Similar Messages

  • Universe parameter

    Hi ALL,
    I would like to have more information about the universe parameter "BOUNDARY_WEIGHT_TABLE" (in the Designer). Is it a value between 0 and 9 only?? And if it can be more than 9 what's its effect in the reports from the related universe.
    Thank you for your support,
    Asma

    Hi Asma,
    Below is the information which you will get running through the documents:-
    Large tables in the From clause have to be wholly parsed even if they are filtered by a condition afterward. By setting the Boundary_Weight_Table parameter, designers can define a limit (in number of rows) to avoid this full parse. If the table size in rows is greater than the entered value, the table is declared as a subquery:
    FROM (SELECT col1, col2,...., coln FROM Table_Name WHERE
    simple condition)
    In the statement above, only the columns necessary for the query are retrieved and the condition in the inner statement limits the number of records to parse in the outer one.
    The above is self explanatory and I am not very sure what effect could it have if we give parameters outside the range but I should expect it not to accept the value outside the range.
    Cheers.

  • How to use @variable(bouser) in Universe to get BOE userid in Xcelsius

    Dear Expert,
    I have request that need to display BOE userid to displayed in Dashboard using Xcelsius,
    after searching in Internet, i found that it can be done by using @variable(bouser) in an object in the Universe, and use the object in Qaaws, but i don't how to use it.
    already tried insert /* @variable('BOUSER') */ in END_SQL universe parameter, but still no luck.
    my question is :
    how to use @variable(bouser) in universe? and then my Xcelsius can display the BOE userid?
    thanks in advance for any answer.
    I Using SAP Integration KIT to create universe from Query BEX
    Luqman
    Edited by: luqman hakim on Jun 29, 2010 4:03 PM

    >
    Didier Mazoue wrote:
    > Hi,
    >
    > You are mentioning that you are using SAP Integration Kit.
    > Does it mean that the source you are targeting is SAP BW?
    >
    > If it is the case, this is unfortunately not supported.
    > SAP BW MDX does not support calculated expressions that return string or date: this is a limitation of SAP BW engine.
    > This is one of the reason why a lot of user exit are used to address these needs.
    >
    > Regards
    > Didier
    Didier Mazoue 
    yes, my Data source is SAP BW, and connected to BOE via SAP INT KIT.
    It's too bad that SAP doesn't support so simple requirement.
    you said : user exit 
    are used to address these needs.
    so there are possibility to solve my problem.
    would you give me the logic of user exit?  which part I should create the user exit
    I'm quiet familiar with user exit in BW
    thanks

  • Universe export - data changes not reflecting in Report

    Hi
    The changes and the latest updates in the database are not reflecting in reports,
    even if i export the universe again.
    and i have refreshed the reports, that even not reflecting.
    i did Edit query and Run query  this action also not bringing the latest data to reports
    why this happens ?
    how to solve this issue ?
    Regards
    Dineshkumar

    You can search for KB articles on SAP Service Market Place .
    Here is first :
    Symptom
    You make changes a local Universe in Designer.
    When refreshing the report, in Desktop Intelligence, the results do not reflect Universe update.
    It used to be enough to simply refresh report's data, for Dataprovider to show object changes from the Semantic layer.
    Change of behaviour in SP3 codeline: the DeskI Query Panel does not automatically pick up the latest modifications made to the local Universe.
    Reproducing the Issue
    Using BusinessObjects Desktop Intelligence XIR2 SP3:
    Using your universe (eFashion), create and refresh a simple Desktop Intelligence report (.rep).
    Make a simple change to the universe (like renaming a field/ object name) and save these changes.
    Go back to the open DeskI report and try to refresh the data provider using: 'Data/Refresh Data'.
    This will not show the latest changes.
    However, if you follow the same workflow using XIR2 SP2, the universe update will be immediately visible (in the report) simply after refresh.
    Cause
    This is not a product regression, but intentional change in application's code delivered with FixPack3.1.
    Fix Request ADAPT00818520 changed the application's behaviour: << When a restricted user is logged on to view a Desktop Intelligence document, prompt windows may be slow to open. >>
    Resolution
    In Desktop Intelligence menu, go to:  Tools > Universes
    Click 'Refresh'
    Select and 'Import' your universe
    Next, go to toolbar menu:  Data >  Edit Data Provider
    In Query Panel, click 'Run' to regenerate the Query and interrogate the updated universe.
    Only after following these actions will the .unv ammendments be visible in the report.
    Here is second :
    Symptom
    Changes to object made for the Universe is not affected when refreshed from InfoView if we check 'Allow selection of multiple Contexts' in Universe Designer
    Desktop Intelligence (Deski) Report still prompts for selection of contexts even if 'Allow selection of contexts' is unchecked for Universe
    Row level Restriction is not applied correctly in InfoView(View Mode) when 'Allow selection of multiple Contexts' checked in the Universe Designer
    Environment
    BusinessObjects Enterprise XI 3.1 Service Pack 2 Fix Pack 2.6
    Reproducing the Issue
    Changes to object made in the Universe is not affected in InfoView(View mode) when 'Allow selection of multiple Contexts' is checked in Universe
    1. Log in to Designer
    i) Import Island Resort Marketing
    ii) Go to Universe Parameter >> SQL
    ii)Uncheck Allow Selection of Multiple Context
    2. Create a new Desktop Intelligence(Deski) Report based on Island Resort Marketing
    i) Drag the object Country in the Result's Pane
    ii) Save and Export the report to the repository.
    3. In Designer Change the Object Country under Resort from Resort_Country.country to
    i) Resort_Country.country+'ddd'
    Note: Uncheck Allow Selection of Multiple Context
    ii) Save and Export the Universe
    4. Log in to InfoView
    i) View the report
    ii) Refresh the report
    iii) Changes to the object taken place i.e Country is concatenated with ddd
    5. In the Universe Designer, change the Object Country under Resort from Resort_Country.country to
    i) Resort_Country.country+'eee'
    Note: Check Allow Selection of Multiple Context
    ii) Save and Export the Universe
    6. Log out from InfoView and login again
    i) View the report
    ii) Refresh the report
    iii) Changes not taken place. Shows only Country instead of Country concatenated with eee.
    Row level Restriction is not applied correctly in InfoView(view Mode) when 'Allow selection of multiple Contexts' checked for the Universe.
    Import efashion Universe 
    Drag the Outlet_Lookup table into the objects pane on the left hand side
    Create Row Level Restriction on the state field of Outlet_Lookup table as Outlet_Lookup.State=(u2018Texasu2019) 
    Apply the restriction to Administrator
    Save and Export the Universe. Note: Uncheck Allow Selection of Multiple Context in Universe Parameter>>SQL
    Log in to Desktop Intelligence (Deski) as administrator with Enterprise Authentication
    Create a new Deski report
    Drag the object state from the Outlet_Lookup table to the Results pane 
    Observed that the administrator is able to see only Texas which is expected behavior
    Save and export the report
    Log in to Infoview as Administrator
    View the report. Refresh the report
    Observed that the administrator is able to see only Texas which is expected behavior
    Log in to Infoview as any user say Test User
    View the report. Refresh the report
    Observed that Test User is able to see all the states which is expected behavior
    In the Universe Designer, Check Allow Selection of Multiple Context in Universe Parameter>>SQL for efashion Universe
    Save and export the Universe
    Log in to Infoview as Test user
    View the report
    Refresh the Report
    TestUser is  able to see only Texas which mean that the restriction is applied to Test User also
    Cause
    This is by Design as the  'Allow selection of multiple Contexts' forces selection of the context, which is not possible in Infoview, so that in Infoview it is assumed the Context is already selected and no SQL regeneration is required.
    Resolution
    Problem Description: Changes to object made in the Universe is not affected when refreshed from InfoView if we check 'Allow selection of multiple Contexts' in Universe Designer
    Explanation:
    If we modify an object and selects also the option 'Allow selection of multiple Contexts', it means that potentially there is more than one SQL that can be generated with the use of that object. Hence if a report is created in Deski, run and exported to enterprise, that means, one particular context (SQL) has been selected.
    If you then update one or more of the objects again, the SQL will have to be regenerated in Deski for the right context to be selected for that particular report.
    Therefore, if this option is used, for the objects to be updated, the SQL of the report will have to be regenerated in Deski, run and export it back to repository, then refresh the report in InfoView.
    For Deski reports viewed in InfoView, it is not possible to evaluate the context on refresh. The report will always use the context stored with the report and same for the SQL. Therefore the Deski report will need to be imported locally, refresh it and then export it back to repository for the changes to take place.
    Problem description: Desktop Intelligence (Deski) still prompts for selection of contexts even if 'Allow selection of contexts' is unchecked for Universe
    Explanation:
    The option 'Allow selection of Multiple Contexts' in Designer is not to disable the prompt. It will prompt you to select context if the object used is associated with context. The option is just to allow Deski to select multiple contexts at a time if in case the object used is associated with multiple contexts and accordingly generates the SQL.
    However if we uncheck the option even if there are multiple contexts associated with the object used, it will allow selection of only one context at a time.
    Problem Description: Issue with Row level Restriction when refreshed from InfoView with 'Allow selection of multiple Contexts' checked for the Universe.
    Explanation:
    We first have to regenerate the SQL in Deski, then export it to repository and refresh from InfoView for the changes to take place correctly. The explanation above applies.

  • Need distinct rows in BO XiR3 Webi report

    I have a report which is similar to below example. Report has multiple other columns like Issue owner, created date, target date etc which are different (means data doesnt repeat in any row and all are dimensions)
    1. User wants one single row for each ID. How to achieve this in BO Webi XiR3?
    ID
    Issue
    Severity
    1
    1.1
    High
    1
    1.2
    High
    2
    2.1
    High
    2
    2.2
    Medium
    2
    2.3
    Low
    3
    3.1
    High
    3
    3.2
    Medium
    3
    3.3
    Medium
    2. Above table is a detail tab. There is also summary tab which is as below. Requirement is that Count for High, Medium and Low in Summar tab should match with the count in detail tab and also should match with the row count in detail tab. This means only when ID column is unique, it will match with row count
    Original Target Dt
    Current Target Date
    Primary Owner
    High
    Medium
    Low
    Total
    1-Jan
    15-Jan
    A
    4
    3
    7
    14
    30-Jan
    14-Feb
    B
    6
    2
    0
    8
    24-Feb
    17-Mar
    C
    5
    6
    7
    18
    Total:
    15
    11
    14
    40
    Please help me to achieve the above target in BO report

    1)
    Please Check Universe Parameter .
    It Should Be Distinct .
    If It is Distinct Then In Web Trim all objects using formula.
    If ID is your granular level it should bring unique row for it ,
    For Unique row your  [ID] should be granular level .But in your image [Issue] is granular level .
    So you can do one thing apply Group on ID & Show Sum of Your KPIs in footer
    with specific color code for group total row.
    2)
    in Summary part
    Create Crosstab
    [Sevirity]
    Total
    [Original Target Dt]
    [Current Target]
    [Primary Date]
    { Count([ID / Issue] ) }
    Sum(use  Count)

  • Webi report throwing error when executed

    HI Experts,
    While executing a Webi Report we are gettign following error when executing with more than one characteristics -
    A Database error occured. The database eror text is : The MDX Query select { [Measures].[4225B1TBMEMOYKZGDKLVINMAW] } ON COLUMNS FROM [ZMEPSC01/ZMEPSC01_QRY_0001]
    failed to execute with the error Unknown error.(WIS 10901).
    We tried changing the Universe -> Parameter -> Control -> Limit size of result set to -> unchecked it.
    But still the error remains. Can u put some light over it.
    Thanks.

    Hello ,
    Just Check with the BI the people they might change the the column name or some thing else in the bex Query that s way It is showing error.
    Refresh the universe and generate the report then check it.
    Thanks
    Santhosh V

  • Oracle not using its own explain plan

    When I run a simple select query on an indexed column on a large (30 million records) table oracle creates a plan using the indexed column and at a cost of 4. However, what it actually does is do a table scan (I can see this in the 'Long Operations' tab in OEM).
    The funny thing is that I have the same query in a ADO application and when the query is run from there, the same plan is created but no table scan is done - and the query returns in less than a second. However, with the table scan it is over a minute.
    When run through SQL plus Oracle creates a plan including the table scan at a cost of 19030.
    In another (dot net) application I used the: "Alter session set optimizer_index_caching=100" and "Alter session set optimizer_index_cost_adj=10" to try to force the optimizer to use the index. It creates the expected plan, but still does the table scan.
    The query is in the form of:
    "Select * from tab where indexedcol = something"
    Im using Oracle 9i 9.2.0.1.0
    Any ideas as I'm completely at a loss?

    Hello
    It sounds to me like this has something to do with bind variable peeking which was introduced in 9i. If the predicate is
    indexedcolumn = :bind_variablethe first time the query is parsed by oracle, it will "peek" at the value in the bind variable and see what it is and will generate an execution plan based on this. That same plan will be used for matching SQL.
    If you use a litteral, it will generate the plan based on that, and will generate a separate plan for each litteral you use (depending on the value of the cursor_sharing initialisation parameter).
    This can cause there to be a difference between the execution plan seen when issuing EXPLAIN PLAN FOR, and the actual exectuion plan used when the query is run.
    Have a look at the following example:
    tylerd@DEV2> CREATE TABLE dt_test_bvpeek(id number, col1 number)
      2  /
    Table created.
    Elapsed: 00:00:00.14
    tylerd@DEV2> INSERT
      2  INTO
      3      dt_test_bvpeek
      4  SELECT
      5      rownum,
      6      CASE
      7          WHEN MOD(rownum, 5) IN (0,1,2,3) THEN
      8              1
      9          ELSE
    10              MOD(rownum, 5)
    11          END
    12      END
    13  FROM
    14      dual
    15  CONNECT BY
    16      LEVEL <= 100000
    17  /
    100000 rows created.
    Elapsed: 00:00:00.81
    tylerd@DEV2> select count(*), col1 from dt_test_bvpeek group by col1
      2  /
      COUNT(*)       COL1
         80000          1
         20000          4
    2 rows selected.
    Elapsed: 00:00:00.09
    tylerd@DEV2> CREATE INDEX dt_test_bvpeek_i1 ON dt_test_bvpeek(col1)
      2  /
    Index created.
    Elapsed: 00:00:00.40
    tylerd@DEV2> EXEC dbms_stats.gather_table_stats( ownname=>USER,-
    tabname=>'DT_TEST_BVPEEK',-
    method_opt=>'FOR ALL INDEXED COLUMNS SIZE 254',-
    cascade=>TRUE -
    );PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.73
    tylerd@DEV2> EXPLAIN PLAN FOR
      2  SELECT
      3      *
      4  FROM
      5      dt_test_bvpeek
      6  WHERE
      7      col1 = 1
      8  /
    Explained.
    Elapsed: 00:00:00.01
    tylerd@DEV2> SELECT * FROM TABLE(DBMS_XPLAN.display)
      2  /
    PLAN_TABLE_OUTPUT
    Plan hash value: 2611346395
    | Id  | Operation         | Name           | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT  |                | 78728 |   538K|    82  (52)| 00:00:01 |
    |*  1 |  TABLE ACCESS FULL| DT_TEST_BVPEEK | 78728 |   538K|    82  (52)| 00:00:01 |
    Predicate Information (identified by operation id):
       1 - filter("COL1"=1)
    13 rows selected.
    Elapsed: 00:00:00.06The execution plan for col1=1 was chosen because oracle was able to see that based on the statistics, col1=1 would result in most of the rows from the table being returned.
    tylerd@DEV2> EXPLAIN PLAN FOR
      2  SELECT
      3      *
      4  FROM
      5      dt_test_bvpeek
      6  WHERE
      7      col1 = 4
      8  /
    Explained.
    Elapsed: 00:00:00.00
    tylerd@DEV2> SELECT * FROM TABLE(DBMS_XPLAN.display)
      2  /
    PLAN_TABLE_OUTPUT
    Plan hash value: 3223879139
    | Id  | Operation                   | Name              | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT            |                   | 21027 |   143K|    74  (21)| 00:00:01 |
    |   1 |  TABLE ACCESS BY INDEX ROWID| DT_TEST_BVPEEK    | 21027 |   143K|    74  (21)| 00:00:01 |
    |*  2 |   INDEX RANGE SCAN          | DT_TEST_BVPEEK_I1 | 21077 |       |    29  (28)| 00:00:01 |
    Predicate Information (identified by operation id):
       2 - access("COL1"=4)
    14 rows selected.
    Elapsed: 00:00:00.04This time, the optimiser was able to see that col1=4 would result in far fewer rows so it chose to use an index. Look what happens however when we use a bind variable with EXPLAIN PLAN FOR - especially the number of rows the optimiser estimates to be returned from the table
    tylerd@DEV2> var an_col1 NUMBER
    tylerd@DEV2> exec :an_col1:=1;
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.00
    tylerd@DEV2>
    tylerd@DEV2> EXPLAIN PLAN FOR
      2  SELECT
      3      *
      4  FROM
      5      dt_test_bvpeek
      6  WHERE
      7      col1 = :an_col1
      8  /
    Explained.
    Elapsed: 00:00:00.01
    tylerd@DEV2> SELECT * FROM TABLE(DBMS_XPLAN.display)
      2  /
    PLAN_TABLE_OUTPUT
    Plan hash value: 2611346395
    | Id  | Operation         | Name           | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT  |                | 49882 |   340K|   100  (60)| 00:00:01 |
    |*  1 |  TABLE ACCESS FULL| DT_TEST_BVPEEK | 49882 |   340K|   100  (60)| 00:00:01 |
    Predicate Information (identified by operation id):
       1 - filter("COL1"=TO_NUMBER(:AN_COL1))
    13 rows selected.
    Elapsed: 00:00:00.04
    tylerd@DEV2>
    tylerd@DEV2> exec :an_col1:=4;
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.01
    tylerd@DEV2>
    tylerd@DEV2> EXPLAIN PLAN FOR
      2  SELECT
      3      *
      4  FROM
      5      dt_test_bvpeek
      6  WHERE
      7      col1 = :an_col1
      8  /
    Explained.
    Elapsed: 00:00:00.01
    tylerd@DEV2> SELECT * FROM TABLE(DBMS_XPLAN.display)
      2  /
    PLAN_TABLE_OUTPUT
    Plan hash value: 2611346395
    | Id  | Operation         | Name           | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT  |                | 49882 |   340K|   100  (60)| 00:00:01 |
    |*  1 |  TABLE ACCESS FULL| DT_TEST_BVPEEK | 49882 |   340K|   100  (60)| 00:00:01 |
    Predicate Information (identified by operation id):
       1 - filter("COL1"=TO_NUMBER(:AN_COL1))
    13 rows selected.
    Elapsed: 00:00:00.07For both values of the bind variable, the optimiser has no idea what the value will be so it has to make a calculation based on a formula which results in it estimating that the query will return roughly half of the rows in the table, and so it chooses a full scan.
    Now when we actually run the query, the optimiser can take advantage of bind variable peeking and have a look at the value the first time round and base the execution plan on that:
    tylerd@DEV2> exec :an_col1:=1;
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.00
    tylerd@DEV2> SELECT
      2      *
      3  FROM
      4      dt_test_bvpeek
      5  WHERE
      6      col1 = :an_col1
      7  /
    80000 rows selected.
    Elapsed: 00:00:10.98
    tylerd@DEV2> SELECT prev_sql_id FROM v$session WHERE audsid=SYS_CONTEXT('USERENV','SESSIONID')
      2  /
    PREV_SQL_ID
    9t52uyyq67211
    1 row selected.
    Elapsed: 00:00:00.00
    tylerd@DEV2> SELECT
      2      operation,
      3      options,
      4      object_name
      5  FROM
      6      v$sql_plan
      7  WHERE
      8      sql_id = '9t52uyyq67211'
      9  /
    OPERATION                      OPTIONS                        OBJECT_NAME
    SELECT STATEMENT
    TABLE ACCESS                   FULL                           DT_TEST_BVPEEK
    2 rows selected.
    Elapsed: 00:00:00.03It saw that the bind variable value was 1 and that this would return most of the rows in the table so it chose a full scan.
    tylerd@DEV2> exec :an_col1:=4
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.00
    tylerd@DEV2> SELECT
      2      *
      3  FROM
      4      dt_test_bvpeek
      5  WHERE
      6      col1 = :an_col1
      7  /
    20000 rows selected.
    Elapsed: 00:00:03.50
    tylerd@DEV2> SELECT prev_sql_id FROM v$session WHERE audsid=SYS_CONTEXT('USERENV','SESSIONID')
      2  /
    PREV_SQL_ID
    9t52uyyq67211
    1 row selected.
    Elapsed: 00:00:00.00
    tylerd@DEV2> SELECT
      2      operation,
      3      options,
      4      object_name
      5  FROM
      6      v$sql_plan
      7  WHERE
      8      sql_id = '9t52uyyq67211'
      9  /
    OPERATION                      OPTIONS                        OBJECT_NAME
    SELECT STATEMENT
    TABLE ACCESS                   FULL                           DT_TEST_BVPEEK
    2 rows selected.
    Elapsed: 00:00:00.01Even though the value of the bind variable changed, the optimiser saw that it already had a cached version of the sql statement along with an execution plan, so it used that rather than regenerating the plan. We can check the reverse of this by causing the statement to be invalidated and re-parsed - there's lots of ways, but I'm just going to rename the table:
    Elapsed: 00:00:00.03
    tylerd@DEV2> alter table dt_test_bvpeek rename to dt_test_bvpeek1
      2  /
    Table altered.
    Elapsed: 00:00:00.01
    tylerd@DEV2>
    20000 rows selected.
    Elapsed: 00:00:04.81
    tylerd@DEV2> SELECT prev_sql_id FROM v$session WHERE audsid=SYS_CONTEXT('USERENV','SESSIONID')
      2  /
    PREV_SQL_ID
    6ztnn4fyt6y5h
    1 row selected.
    Elapsed: 00:00:00.00
    tylerd@DEV2> SELECT
      2      operation,
      3      options,
      4      object_name
      5  FROM
      6      v$sql_plan
      7  WHERE
      8      sql_id = '6ztnn4fyt6y5h'
      9  /
    OPERATION                      OPTIONS                        OBJECT_NAME
    SELECT STATEMENT
    TABLE ACCESS                   BY INDEX ROWID                 DT_TEST_BVPEEK1
    INDEX                          RANGE SCAN                     DT_TEST_BVPEEK_I1
    3 rows selected.
    80000 rows selected.
    Elapsed: 00:00:10.61
    tylerd@DEV2> SELECT prev_sql_id FROM v$session WHERE audsid=SYS_CONTEXT('USERENV','SESSIONID')
      2  /
    PREV_SQL_ID
    6ztnn4fyt6y5h
    1 row selected.
    Elapsed: 00:00:00.01
    tylerd@DEV2> SELECT
      2      operation,
      3      options,
      4      object_name
      5  FROM
      6      v$sql_plan
      7  WHERE
      8      sql_id = '6ztnn4fyt6y5h'
      9  /
    OPERATION                      OPTIONS                        OBJECT_NAME
    SELECT STATEMENT
    TABLE ACCESS                   BY INDEX ROWID                 DT_TEST_BVPEEK1
    INDEX                          RANGE SCAN                     DT_TEST_BVPEEK_I1
    3 rows selected.This time round, the optimiser peeked at the bind variable the first time the statement was exectued and found it to be 4, so it based the execution plan on that and chose an index range scan. When the statement was executed again, it used the plan it had already executed.
    HTH
    David

  • Webi 4.0 Passing parameters - how the heck ! does it work or not ?

    dear all
    i am knew to all this, quite capable of reading manuals, and an ex ABAPer in SAP.
    but when it comes to trying to pass a single parameter to a Webi report, based upon the new open document v4.0 syntax, it has finally got me.
    it seems i am not alone either.
    this works, and opens the webi with the full contents
    http://localhost:8080/BOE/OpenDocument/opendoc/openDocument.jsp?iDocID=AXofXym2kBRLuR4NwFiMPwo&sIDType=CUID&sType=wid
    i have tried both, a "new parameter" and a universe parameter, based upon my dimension "State", with no such luck on the underlying webi query filter.
    i thought i would only have to add "&lsSState=VIC" (no including the quotes), for it to filter my records for the state Victoria (no points for guessing where i am). But no. I still get all the same old records.
    then i tried *District=VIC", still the same old records without applying the query filter.
    so what am i doing wrong ! please ! help !
    thanks

    finally, here's the deal
    the opendocument 4.0 documentation is wrong. the parameter values are separated by at semicolon, and not a comma. also, do not put square brackets around them.
    this works
    u2022     lsMpmDistrict=NSW
    u2022     lsMDistrict=NSW
    u2022     lsMpmDistrict=NSW;SA
    u2022     lsMDistrict=NSW;SA
    this does not work
    u2022     lsMDistrict=[NSW],[VIC]
    u2022     lsMDistrict=[NSW];[VIC]
    if only the documentation explained it properly, i would have saved hours of time.

  • Inserting data into a partition.

    Hi,
    I am inserting 10 million rows into a partition and its consuming lot of time (>24 hrs).
    I am using simple insert statement.
    Is there any better way to insert data into a partition.
    Thanks for your help in advance
    Thanks
    Manju

    Hello, this has nothing to do with the fact that the target table is partitioned.
    One thing you could try first-off, is a Direct Path Insert, i.e.,
    INSERT /*+ APPEND */ INTO part1
    SELECT...That will speed it up, but remember to do a COMMIT directly after INSERTing.
    Are you sure that the SELECT isn't taking a long time in itself?
    What is the value of your cursor_sharing database parameter?

  • How to set max rows in flowed textfield?

    Is there a way to limit the rows allowed to input on a flowed textarea? I now we can limit the length of max chars, but that would not help me.

    Hi Rishit,
    Thanks for your answer!
    Had a long holiday, so didn't give a feedback in time. Sorry for that!
    There is a tab 'Controls' in Universe Parameter, where there is a setting used to limit the size of result set.
    Then what's the priority between this setting and the similar setting in WebI query properties?
    However, acutally my question is how to set the limitation by user security profile in CMC.
    Do you have any idea about it?
    Qing
    Edited by: Qing Zhou on Jun 21, 2010 11:12 AM

  • Query as a web service Sorting issue

    Hi All,
    We have designed an existing BI query as a web service but it seems to be ignoring the Sort order of different characteristics used (as defined in Bex Query Designer).
    Using the Context menu in QAAS and defining/managing the Sort is not working.
    Has anyone experienced such an issue and how to handle this?
    Thanks and Regards,
    Bansi

    Hi All,
    You can try this solution. It has something to do with the universe parameter, END_SQL.
    I implemented this as a work around and it solved our problem about the sorting issue with QAAWS.
    Here are the steps:
    1: Open the universe
    2. Ope File,  then Universe Parameter
    3. Click the parameter tab
    4. Scroll down until you see the 'END_SQL' entry. This entry is blank by default.
    5. Select END_SQL
    6. On the VALUE box, type: ORDER BY 1
    7. This will enable the REPLACE button. Click REPLACE
    8. Save the universe
    9 Test a query using 2 columns and view the SQL.
    You should see now the ORDER BY 1 inferred in the SQL statement.
    Voila!!!!
    Of course you can always add ORDER By 1,2,3 later if there's a need.
    Enjoy.....
    Ferdinand

  • WaitTime for Browse messages

    Can WaitTime be specified for browsing queue messages just like receive messages.

    found END_SQL universe parameter which allowed it to work.
    I did not have the syntax correct when I tried it the first time.
    After replacing the default "blank" value in END_SQL.... I was able to accomplish this.
    Problem solved.

  • Using Ranking on MS SQL Server 2005

    Hello,
    We are on BOXI3.1 base version and have a universe on top of MS SQL Server 2005.
    My question is regarding use of rank functions. BO guides state that
    You can perform a database ranking only if your database supports
    it. If this is not the case, the Add a database ranking button is disabled on
    the Query Panel toolbar. Databases that support ranking are Oracle, DB2,
    Terradata and Redbrick.
    So SQL Server is not in the list. However the add database ranking button is enabled on
    my report panel. If i add a ranking the query runs for a long time and times-out.
    Is there any universe parameter i need to enable to use ranking? Has any-one mangaged to
    use ranking functionality with SQL Server 2005.
    Thanks in advance.

    Hi Bashir Awan,
    When we create this Object (using your example) at Universe level is the ranking hardcoded ?
    My questions is, say i have Product object (with values A, B, C, D, E), and sales aggregated (10, 20, 30, 40, 50, 60, 70, 80, 90, 100)
    Say the table is as follows
    Product;        sales
        A;               10
        A;                70*
        B;                 50
        B;                 20*
        C;                 30
        C;                 60*
        D;                 40
        D;                 90
        E;                 80
        E;                100
    Note: * represents Oversees sales outside US
    Case 1: Now when we rank whole data to select top 3 we should get (E, D, C in Desc order)
    Case 2: Now if I apply prompt on Country of sales as US will I get (E, B, D) or is it still (E, D, C as earlier).
    Case 3: Similarly if I apply prompt on Product (no prompt on Country) in the filter pane and select (A, D, E) will my results show (E, D, A) or (E, D) as the value of A may be restricted due to ranking formula based on sales at Universe level.
    I am sorry I may be asking a very basic question. Thanks
    Sudhir.

  • How to set Max Rows Retrieved by user security profile in CMC?

    Hi
    As we know, it is possible to set Max Rows Retrieved with query property (in the area 'Limits').
    However, it is mentioned in official documents that this setting can be overwritten by the BOE administrator in user security profile. Could any one tell me how this is done in CMC?
    Thanks in advance!
    Qing

    Hi Rishit,
    Thanks for your answer!
    Had a long holiday, so didn't give a feedback in time. Sorry for that!
    There is a tab 'Controls' in Universe Parameter, where there is a setting used to limit the size of result set.
    Then what's the priority between this setting and the similar setting in WebI query properties?
    However, acutally my question is how to set the limitation by user security profile in CMC.
    Do you have any idea about it?
    Qing
    Edited by: Qing Zhou on Jun 21, 2010 11:12 AM

  • Query as Web service issue.

    Hi,
    I have created a BAPI for sales order creation in one of the R/3 system. On top of that i created xeclsius report and used "Web service connection", and mapped the input and output fileds. when I click preview it working properly, but when next time open the xlf file it is not fetching the data, again we have to import and do the same process then only it is fetching the data.
    I have tried by Exsporting to SWF file and through opendoc url also, but the problem is same.
    Can any one help me on this?
    Best Regards
    Raju.k

    Hi All,
    You can try this solution. It has something to do with the universe parameter, END_SQL.
    I implemented this as a work around and it solved our problem about the sorting issue with QAAWS.
    Here are the steps:
    1: Open the universe
    2. Ope File,  then Universe Parameter
    3. Click the parameter tab
    4. Scroll down until you see the 'END_SQL' entry. This entry is blank by default.
    5. Select END_SQL
    6. On the VALUE box, type: ORDER BY 1
    7. This will enable the REPLACE button. Click REPLACE
    8. Save the universe
    9 Test a query using 2 columns and view the SQL.
    You should see now the ORDER BY 1 inferred in the SQL statement.
    Voila!!!!
    Of course you can always add ORDER By 1,2,3 later if there's a need.
    Enjoy.....
    Ferdinand

Maybe you are looking for