FR query ready export gives error

Hi
We are exporting a FR report in Query ready mode to Excel but its giving javascript error as Permission Denied.
Any idea.
Thanks

You could check this IE settings :
1. From the Tools menu, click Internet Options.
2. Click Advanced.
A. Scroll to "Disable script debugging". Check the option.
B. Scroll to "Display a notification about every script error". Un-check the option.
3. Click the Security tab.
4. Click Internet, and then click Custom Level.
5. In the Security Settings list, scroll to Miscellaneous.
6. Set "Access data sources across domains" to "Enable" or "Prompt".
Thanks...

Similar Messages

Content Query Web Part gives error when trying to edit

Hello there,
When I put the page in edit mode and try to edit the content query web part I get an unexpeced error. When searching the correlation ID from the error message I see this message a lot:
07/08/2014 11:51:03.72
w3wp.exe (0x5370)
0x49D8
Web Content Management
Publishing
7fz0
Medium
ConsoleUtilies.GetContextualControlMode had no currentPage so the current SPWebPartManager mode cannot be retrieved.
The error message says something about Publishing and I had an Publishing issue before the CQWB issue happened.
The thing is that the CQWB is dependent on the Publishing feature. The publishing feature when turned on (as site collection feature) creates Content types. One of these content types was removed because when I tried to create a new publishing site
I got an error about a missing content type.
I deactivated the site collection publishing feature (after deactivating it on all sites where it was activated) and then activated it again so it reacreates the content types. This was working, since now I can create Publishing sites again.
The problem is that I can not edit the CQWB anymore. But it is still showing the query in correct lay-out. Also when I add a new CQWB I have the same issue. I can add it, but not edit.
I also made a new test site collection and here everything works fine. I tried to copy the .webpart from the test to the problem-sitecollection, but the webpart is just not editable on my broken site collection.
Does anyone have any idea how to fix this? Im assuming it has something to do with the publishing issue I had....
Please help......

I disabled all publishing features on all subsites
Then I disabled the site collection publishing feature
Then I enabled the site collection publishing feature again
I enabled publishing feature on the subsites where I want to use the content query web part and also on the subsites where the query is coming from
So: Yes, the publishing feature is enabled

Running an ABAP Query with transaction gives error!

The queries are there (only in production systems), from PHX. When the queries are started from SQ00 they work.
*The question is, if this has to be done for every single query*?

Hi,
When we upgraded, we had only few queries to be generated. Not all the queries were required to be generated...
Hence would depend on case to case..Better regenerate the query. This is similar to activation. Hence will not be an issues for already generated queries.
Hope this helps
Regards
Shiva

FR error exporting to excel Query ready mode

We are getting an error while exporting to Query ready mode. Error says report is not a valid single file web page.
but its working for other user.
any clue.

check this might help :
Re: "not a valid single file Web Page"

Hyperion Workspace Financial Reporting Export to Excel Query-Ready Missing

Hyperion Workspace Financial Reporting Export to Excel "Query-Ready" option is Missing in the dropdown when you go to File>Export>Excel
Only the "Fully Formatted" option is available.
From what I recall this option for a "query-ready" export should be available from the HTML preview?
Is there something in configuration that needs to be enabled or something that needs to be checked on to get this option?
We are running 11.1.1.3
The Query-Ready option is available when exporting forms in Planning.
When opening Financial Reports in Smartview the option for "Query-Ready" is available.
For some reason this is not showing up in workspace, does it not exist in 11.1.1.3? Is this a bug?
TIA

Hi,
The option to export the financial report output in "Query-Ready" format is actually at the bottom right hand corner of the report page (look at the report footer) instead of File>Export>Excel.
Hope this helps
Genti

Export in Query Ready Mode get Essbase Error 1020047

Through Workspace when in a Financial Reporting Report, when we click on Export in Query Ready Mode, we get the following error in Excel and then Excel closes. 'Essbase Error (1020047): A column item [%] conflicts with a row item[%].'
Any ideas?
We are using 11.1.2
Thanks.

This is bug and fixed in 11.1.2.1.102 Smart View

How to hide/disable option "Export In Query Ready Mode" in HTML FR reports

Hi all,
is there a way to hide or disable the option "Export In Query Ready Mode" for HTML FR reports?
Thanks in advance!
Regards
André

Yes, it is a cool feature but I didnt ask for it :-) Besides it doesnt work completely without errors/warnings:
If i click on the link and then on open (save xls works fine) an error message occurs: "Could not open 'http://<servername>/hr/hrget/modules/com/hyperion/reporting/web/office/HROfficeReport.jsp/test.xls?gridname=grid1&iInstanceId=18885&format=excel.2002&viewAs=query&previewDone=true&promptDone=true'"
After click on OK another error message occurs:
"Microsoft Excel cannot access the file 'http://<servername>/hr/hrget/modules/com/hyperion/reporting/web/office/HROfficeReport.jsp/test.xls?gridname=grid1&iInstanceId=18885&format=excel.2002&viewAs=query&previewDone=true&promptDone=true'. There are several possible reasons:
The file name or path does not exist.
The file is being used by another program.
The workbook you are trying to save has the same name as a currently open workbook.
After click on OK the XLS export opens correctly but the messages are annoying. Perhaps anybody can help me ;-)
Thanks and kind regards
Andre

Export to query ready mode

In version 11.1.2 when exporting a report to query ready mode from workspace we are getting an HRdialogue error message. However when I turn off the POV preview in user preferences it works. Anyone else experiencing this?
Thanks,
Jeff

Hi,
Can anybody explain me the option of this *"Export in Query ready mode"*???
Is there any document through which I can understand???
Thanks
Sourabh
Edited by: CM on May 11, 2011 6:32 AM

Select query gives error in Code inspector and extended program check

Hi,
I have a query .
SELECT pernr
FROM pa9100
INTO TABLE t_nca_tab
WHERE endda EQ c_date AND
z_nca_required EQ c_yes.
This query gives me an error in Code inspector like :
Large table pa0001: No first field of table index in WHERE condition
I have one more query that gives error in extended program check
SELECT SINGLE stell ename
      INTO (g_stell, g_name)
      FROM pa0001
      WHERE pernr EQ wa_nca_tab-pernr AND
            endda EQ c_date.
The warning says:
*In "SELECT SINGLE ...", the WHERE condition for the key field "SEQNR" does not
test for equality. Therefore, the single record in question may not be unique.*
Its too urgent.
Please reply.
Regards,
Binay.

The first field is PERNR .. so if UR not giving pernr it will fetch
all the data from the said table and between the given dates ..
Check if this is your requirement ...
write the select as ...
where r_pernr is a range ...
SELECT pernr
FROM pa9100
INTO TABLE t_nca_tab
WHERE pernr in r_pernr <----
             endda EQ c_date AND
             z_nca_required EQ c_yes.
As UR using select single it's expecting to use all the key
fields in the where condition ...
U can ignore this warning message

Error In Query Level export with multiple conditions

When i am running the following Query for Export with i am getting the result.
C:\Documents and Settings\ITL>exp scott/tiger@orcl tables=(emp) QUERY='"WHERE deptno > 10 and sal !=2850"' LOG=log011.log FILE=exp.dmp
Export: Release 10.2.0.1.0 - Production on Wed Jan 30 10:01:27 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
About to export specified tables via Conventional Path ...
. . exporting table EMP 10 rows exported
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
Export terminated successfully with warnings.
But When I run with The following condition then it shows the following error...
C:\Documents and Settings\ITL>exp scott/tiger@orcl tables=(emp) QUERY='"WHERE deptno > 10 and job!='CLERK' "' LOG=log011.log FILE=Exp01.dmp
LRM-00111: no closing quote for value ' LOG=log01'
EXP-00019: failed to process parameters, type 'EXP HELP=Y' for help
EXP-00000: Export terminated unsuccessfully
C:\Documents and Settings\ITL>exp scott/tiger@orcl tables=(emp) QUERY="WHERE deptno > 10 and job!='CLERK'" LOG=log5.log FILE=exp01.dmp
LRM-00112: multiple values not allowed for parameter 'query'
EXP-00019: failed to process parameters, type 'EXP HELP=Y' for help
EXP-00000: Export terminated unsuccessfully
Please suggest a solution for it.

966523 wrote:
Padma.... wrote:
Hi,
The single quotes used for CLERK are causing the issue most probably.
C:\Documents and Settings\ITL>exp scott/tiger@orcl tables=(emp) QUERY='"WHERE deptno > 10 and job!='CLERK' "' LOG=log011.log FILE=Exp01.dmp
try replacing with this
C:\Documents and Settings\ITL>exp scott/tiger@orcl tables=(emp) QUERY='"WHERE deptno > 10 and job!=''CLERK'' "' LOG=log011.log FILE=Exp01.dmp
Two single quotes(not double quotes) in the place of one single quote for CLERK.
Thanks
Padma...Thanks A Lot...if/when you place all inside control file, then you do not have to worry about such complications

Export in Query Ready mode not working in 11.1.2.1

Hi,
I have created a report with 3 grids;
Grid 1 - populates employee information,
Grid 2 - populates employee salary
Grid 3 - calculation of Grid 1 and Grid 2.
In Report I am able to see the data, but when I am using the "Export in Query Mode" option the report is exporting into Excel where as Grid 3 has NO more formulas.
Please suggest by modifying the settings/options in Excel will resolve the issue or is it a bug?
Thanks in advance!
Regards,
VA

It is the behavior, Query ready mode will only pulls the members which are in Essbase (no FR calculated fields)
Regards
Celvin
http://www.orahyplabs.com

Export in Query ready mode - Office 2010 not working

Hello everyone,
I am facing the following problem with Hyperion Financial Reporting:
When I display a Financial Reporting report in Workspace and click on "Export in query ready mode", a new Excel session is launched with an empty sheet and nothing else happens. Eventually Internet explorer displays a message "The application hasn't started yet. Do you want to wait?" This cycle repeats forever unless I close the small IE window that popped up.
We are using Windows 7 and Office 2010. The Smart View version is 11.1.1.3.500 (Build 008) and Workspace is version 11.1.1.3.0.956.
Would be very grateful if anyone can help me solve this issue as this function is very useful.
Thanks,
Martin

Alright,
There is some development with this problem, but unfortunately another one arose.
To solve the issue I had to disable the option "Protected mode" for the Internet Zone of Internet Explorer. Although the App server is on the local intranet, to launch Excel the web page uses the protocol oraclesv:// which appears to IE as "Internet" address.
When I disabled protected mode, some of the reports started to open normally in query ready mode. Unfortunately for some other reports Excel crashes. I.e. I open the report in workspace and click "Export in Query ready mode". I see Excel open up and the cells are filled in with members, etc. but at some point Excel just crashes and restarts. This can be destructive if I am currently working in some file.
And now the interesting part: I tried to find the reason why some of the reports are ok and some crash excel. It turned out that this depends on the amount of data in the report. For smaller reports (i.e. less than 50 rows) there is no problem, but for larger reports -> excel crashes.
I hope this explanation is helpful for someone else, as it took me quite a while to find the problem.
Martin

Export in Query Ready mode not Working.for FR reports in HTML view

Hi,
When we run the FR reports in HTML view in Workspace,there is an option at the bottom to "Export in Query Ready mode",it's not exporting the report in Smart view excel .
But some of our users are able to export the report in SV.We are using EPM 11.1.1.3. I have checked the IE 7 settings with other users and it's same.
Does anybody has any idea what could be the cause?
Thanks in advance.
BC

It is the behavior, Query ready mode will only pulls the members which are in Essbase (no FR calculated fields)
Regards
Celvin
http://www.orahyplabs.com

Query in 10g DB gives error when size of element exceeds 4000 characters?

I used this query give in this thread Need help in reading a _fmb.XML and writing the item properties to a table
select x1.item_name
     , x1.item_type
     , x2.property
     -- to convert back entities such as
to their character values :
     , utl_i18n.unescape_reference(x2.property_value) as property_value
     -- parent information :
     , x1.parent_item_name
     , x1.parent_item_type
from xmltable(
       xmlnamespaces(default 'http://xmlns.oracle.com/Forms', 'http://xmlns.oracle.com/Forms' as "def")
     , 'for $i in /Module/descendant::*[@def:Name]
        return element item {
          attribute item_name {data($i/@def:Name)}
        , attribute item_type {local-name($i)}
        , attribute parent_item_name {data($i/parent::*/@def:Name)}
        , attribute parent_item_type {local-name($i/parent::*)}
        , $i
       passing xmltype(bfilename('TEST_DIR','length_test_fmb.xml'), nls_charset_id('AL32UTF8'))
       columns item_name         varchar2(50) path '@item_name'
             , item_type         varchar2(50) path '@item_type'
             , parent_item_name varchar2(50) path '@parent_item_name'
             , parent_item_type varchar2(50) path '@parent_item_type'
             , item              xmltype      path '.'
     ) x1
   , xmltable(
       xmlnamespaces(default 'http://xmlns.oracle.com/Forms', 'http://xmlns.oracle.com/Forms' as "def")
     , 'for $i in /item/*/attribute::def:*
        let $propname := local-name($i)
        where $propname != "Name"
        return element p {
          element name {$propname}
        , element value {data($i)}
       passing x1.item
       columns property       varchar2(50) path 'name'
             , property_value varchar2(4000) path 'value'
    ) x2
;This works perfectly, but I tried a form which has a program unit which exceeds 4000 characters, i.e. I converted a fmb to xml, I.E. PROPERTY VALUE. When you run the query then you get error "function returned value too large".
I tried changing the VARCHAR2 to CLOB but then you get another error.
We cannot migrated to 11g as yet, so how to handle this in 10g?
Any help would be greatly appreciated.
Edited by: Channa on Oct 25, 2011 6:40 AM

Hi Channa,
I should have mentioned it in the previous thread, a sound approach to the overall requirement would be to use object-relational storage for loading XML documents in the database.
You can read more here : http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14259/xdb03usg.htm#g1055369
However, that's not possible if we use the DUMP=ALL option to convert Forms files to XML because the generated files do not conform to the Forms XML schema.
So unless you decide to use DUMP=OVERRIDDEN, you're stuck with the current situation.
If I remember correctly, the ability to project large strings as CLOB with XMLTable was added in version 10.2.0.4.
You're not out of options though.
Here are two, one being "dirtier" than the other...
1) Divide the property value into multiple chunks of 4000 characters (or less if the db uses a multi-byte character set), then rebuild the string as CLOB in the SELECT clause :
select x1.item_name
     , x1.item_type
     , x2.property
     , to_clob(utl_i18n.unescape_reference(x2.property_value1)) ||
       to_clob(utl_i18n.unescape_reference(x2.property_value2)) as property_value
     , x1.parent_item_name
     , x1.parent_item_type
from xmltable(
       xmlnamespaces(default 'http://xmlns.oracle.com/Forms', 'http://xmlns.oracle.com/Forms' as "def")
     , 'for $i in /Module/descendant::*[@def:Name]
        return element item {
          attribute item_name {data($i/@def:Name)}
        , attribute item_type {local-name($i)}
        , attribute parent_item_name {data($i/parent::*/@def:Name)}
        , attribute parent_item_type {local-name($i/parent::*)}
        , $i
       passing xmltype(bfilename('TEST_DIR','module2.xml'), nls_charset_id('AL32UTF8'))
       columns item_name         varchar2(50) path '@item_name'
             , item_type         varchar2(50) path '@item_type'
             , parent_item_name varchar2(50) path '@parent_item_name'
             , parent_item_type varchar2(50) path '@parent_item_type'
             , item              xmltype      path '.'
     ) x1
   , xmltable(
       xmlnamespaces(default 'http://xmlns.oracle.com/Forms', 'http://xmlns.oracle.com/Forms' as "def")
     , 'for $i in /item/*/attribute::def:*
        let $propname := local-name($i)
        let $propval := data($i)
        where $propname != "Name"
        return element p {
          element name {$propname}
        , element value1 {substring($propval,1,4000)}
        , element value2 {substring($propval,4001,4000)}
       passing x1.item
       columns property        varchar2(50)   path 'name'
             , property_value1 varchar2(4000) path 'value1'
             , property_value2 varchar2(4000) path 'value2'
    ) x2
;2) Output the property value as a text() node (XMLType datatype) and serialize as CLOB in the SELECT :
select x1.item_name
     , x1.item_type
     , x2.property
     , dbms_xmlgen.convert(x2.property_value.getclobval(),1) as property_value
     , x1.parent_item_name
     , x1.parent_item_type
from xmltable(
       xmlnamespaces(default 'http://xmlns.oracle.com/Forms', 'http://xmlns.oracle.com/Forms' as "def")
     , 'for $i in /Module/descendant::*[@def:Name]
        return element item {
          attribute item_name {data($i/@def:Name)}
        , attribute item_type {local-name($i)}
        , attribute parent_item_name {data($i/parent::*/@def:Name)}
        , attribute parent_item_type {local-name($i/parent::*)}
        , $i
       passing xmltype(bfilename('TEST_DIR','module2.xml'), nls_charset_id('AL32UTF8'))
       columns item_name         varchar2(50) path '@item_name'
             , item_type         varchar2(50) path '@item_type'
             , parent_item_name varchar2(50) path '@parent_item_name'
             , parent_item_type varchar2(50) path '@parent_item_type'
             , item              xmltype      path '.'
     ) x1
   , xmltable(
       xmlnamespaces(default 'http://xmlns.oracle.com/Forms', 'http://xmlns.oracle.com/Forms' as "def")
     , 'for $i in /item/*/attribute::def:*
        let $propname := local-name($i)
        where $propname != "Name"
        return element p {
          element name {$propname}
        , element value {data($i)}
       passing x1.item
       columns property        varchar2(50)   path 'name'
             , property_value xmltype        path 'value/text()'
    ) x2
;Edited by: odie_63 on 25 oct. 2011 17:03
Edited by: odie_63 on 25 oct. 2011 17:04

How to hide/disable option "Export In Query Ready Mode" in HTML FR reports (workspace)version 11.1.1.3

Hi all,
is there a way to hide or disable the option "Export In Query Ready Mode" for HTML FR reports (workspace) version 11.1.1.3.
Thanks in advance!
Regards
Tej.

Hi Tej,
The feature, "to hide or disable the option "Export In Query Ready Mode" has been introduced in Financial Reporting 11.1.2.3.
    Logon to EPM Workspace.
    Open menu File > Preferences > Financial Reporting.
    The new option, called "Disabled" is available for Query Ready Mode. If selected will disable Query Ready mode completely.
Thanks,
Krish

FR query ready export gives error

Similar Messages

Maybe you are looking for