Report query changes

Hi,
when i open a report and do some changes to the query,it always happens that the columns are renamed with 1 concatinated to them.
eg. select empnum,ename from emp;
the columns will be
empnum
ename
now suppose i changed the query to
select emp_num,ename name from emp;
the column changes to
empnum1
name
now think about the formula columns which are using empnum ,now i have to change each and every formula column which is irritating,,,,,why does this happens? is it a report builder bug?

If it is not a bug I would consider it a poor design. I have run into this more than a couple of times myself. Reports renames your columns when it thinks you have two with the same name. I don't know why your problem started originally. Did by chance you save your query by accident one time having two columns with the same name? That was usually how my problem started. If just altering the query after it was made didn't work (which it never did for me either), then try completely deleting the query and all its groups. Then remake the query and groups making sure you have no two columns with the same name (DO NOT use cut and paste to achieve this). It's always worked for me in the past. Hopefully, your problem won't be any more difficult than this. Good luck.

Similar Messages

How to change report query dynamically in Oracle APEX?

Hi,
I want to dynamically change the where condition in APEX report query. Can anyone help me solve my this problem?
(Just want to change the query which we change in Oracle Reports using lexical parameter to change &Where, &Order by etc. dynamically!!)
Thanks, Praful

Hi
I've been using flexible queries in APEX for a few years now, and your question just added a whole new dimension to the flexible and powerful nature or writing reports in APEX.
While APEX Interactive reporting has almost completely removed the need the equivalent of Lexicals in Oracle Reports, I thought it might be fun to try and use lexicals in an APEX report.
Before we start I should summarise the powerful capability of APEX reporting to have oprtional parameters (lots and lots of them if this is needed).
For each parameter, you simply add a page item which will hold the value of the parameter.
The item/parameter can be populated by typing in the value, defining an LOV, using a date-picker etc.
To make the parameter optional simply use an OR in the where clause.
So for a apge item P200_PARAM1.....include
WHERE (:P200_PARAM1 IS NULL
OR COLUMN1 = :P200_PARAM1)
This way you can either leave the page item null or type in / select a value from a LOV.
There is a small quirk in APEX LOV's which sometimes returns a value of '%' or '%null%' - depending on the version - when no value is selected.
See Patrick Wolf's solution for this at Re: Null value handling in LOVs
I include this Application Process in all my APEX applications ;)
Now let's look at using the equivalent of Oracle Reports Lexicals......
First-off - this is based on the APEX SQL report - NOT Interactive Report.
It relies on the fact that you can let the query be parsed only at runtime.
1. Define an SQL report entering the 'core' of your query.
With a query like SELECT ENAME, JOB FROM EMP
Select 'Generic Columns' option in the 'Column Headings' section
Finish the report creation
2. Define a page item - say P200_LEXICAL - type text on the page
3. Edit the report and update the SQL query to include your lexical page item
SELECT ENAME, JOB FROM EMP &P200_LEXICAL. (REMEMBER THE '.' AT THE END)
Ensure that the option "Use Generic Column Names (parse query at runtime only)" is selected at the bottom of the query
4. Add a button to the page -using 'Create a button displayed among this region's items' the will submit the page.
5. Run the page - you will see all the employee names and job desdriptions
6. Enter a where clause into the 'Lexical' textbox - say "WHERE ENAME LIKE 'K%'" and click the 'Go' button
Voila! your where clause is magically applied.
Try any variant you like adding an ORDER BY clause etc...... this is FUN!
7. Clear the value of the LEXICAL and click go.
Edit the report and move the &P200_LEXICAL. into the selected columns (or add another one)
SELECT ENAME, JOB &P200_LEXICAL. FROM EMP
8. Run the page
Enter ",SAL" in the textbox and "Go"
We can add as many columns as we like (subject to the "Maximum number of generic report columns:" set below the SQL query in the report edit section)
Now because we have all the flexibility in APEX of setting page items using SQL or PLSQL you can set the value of the lexical programatically, or just pre-set a few values in an LOV - the options are limitless.
While I've never had the need to use lexicals - you can see that APEX provides the most Flexible Lexicals in town.
Eat your heart out "Oracle Reports"!!!
Have fun
Mike

Change date format in reporting (query)

I need to change date format from dd.mm.yyyy to dd/mm/yyyy in reporting (query)

Hi Suresh,
Go to transaction su01d in that enter your user.
Now go to defaults and change the date format.
Ya but this format will be user specific, so if you want everyone to see that format you have to change it for all.
Regards
Mansi

Fail to parse SQL query after report attributes changes on sample app

This errors occurs in the sample application istalled in Workspace PMW on the http://htmldb.oracle.com web site. Goto home page, edit Page 1, Select "Top Orders" in Region, select report attributes, change max count from 5 to 5 in "Layout and Pagination", apply changes, run page and parse SQL error occurs. Select "debug" and the following is shown regarding the query.
0.10: query could not be parsed:
SELECT a.ORDER_ID, a.ORDER_TIMESTAMP, a.CUSTOMER_ID,
b.cust_last_name || ', ' || b.cust_first_name cust_name, NVL(a.ORDER_TOTAL, 0)
FROM demo_orders a, DEMO_CUSTOMERS b
WHERE a.customer_id = b.customer_id
ORDER BY NVL(a.ORDER_TOTAL, 0) DESC order by 5 desc,5 desc
failed to parse SQL query:
ORA-00933: SQL command not properly ended
I can't see that I'm doing anything wrong but maybe someone can shed some light on this!
Thanks

this is sort of an oversight on our part. what's going on is that the sample app installs with that order by clause in the query. at the same time, the report attributes page for that region has a default sort sequence value of "1 desc" (even though column heading sorting isn't enabled). when you go to that page and try to apply any change, htmldb tries to set things up correctly for you...and you end up with that double order by. the best way to avoid the issue is to remove the order by clause from the query on the Region Definition page.
hope this helps,
raj

Can I change column headings dynamically based on report query conditions ?

Hi All,
Is there a possibility in OBIEE to change the headings of the column dynamically depending on the conditions that i keep on the report query ?
Assume that i am showing an emp table data of one department at a time.
The column heading of employee name should be like <DEPT>_EMP, Where <DEPT> is the department on which i was reporting..
Example:
Report query : Select * from emp where dept = 'PHYSICS'
The column heading of employee name should be PHYSICS_EMP.
Thanks in advance.

Hello,
did you try to create a column with the data of dept and put it in a column level of a pivot table?
In the example that you gave, the column head would show 'PHYSICS' because it's the data filtered at your query. Them, you just edit this column and concatenate the '_EMP' string.

Performance issues when creating a Report / Query in Discoverer

Hi forum,
Hope you are can help, it involves a performance issues when creating a Report / Query.
I have a Discoverer Report that currently takes less than 5 seconds to run. After I add a condition to bring back Batch Status that = Posted we cancelled the query after reaching 20 minutes as this is way too long. If I remove the condition the query time goes back to less than 5 seconds.
Please see attached the SQL Inspector Plan:
Before Condition
SELECT STATEMENT
SORT GROUP BY
VIEW SYS
SORT GROUP BY
NESTED LOOPS OUTER
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
TABLE ACCESS BY INDEX ROWID GL.GL_CODE_COMBINATIONS
AND-EQUAL
INDEX RANGE SCAN GL.GL_CODE_COMBINATIONS_N2
INDEX RANGE SCAN GL.GL_CODE_COMBINATIONS_N1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUES
INDEX RANGE SCAN APPLSYS.FND_FLEX_VALUES_N1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUE_SETS
INDEX UNIQUE SCAN APPLSYS.FND_FLEX_VALUE_SETS_U1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUES_TL
INDEX UNIQUE SCAN APPLSYS.FND_FLEX_VALUES_TL_U1
INDEX RANGE SCAN APPLSYS.FND_FLEX_VALUE_NORM_HIER_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_LINES
INDEX RANGE SCAN GL.GL_JE_LINES_N1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
TABLE ACCESS BY INDEX ROWID GL.GL_JE_HEADERS
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_DAILY_CONVERSION_TYPES_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_SOURCES_TL
INDEX UNIQUE SCAN GL.GL_JE_SOURCES_TL_U1
INDEX UNIQUE SCAN GL.GL_JE_CATEGORIES_TL_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
INDEX UNIQUE SCAN GL.GL_BUDGET_VERSIONS_U1
INDEX UNIQUE SCAN GL.GL_ENCUMBRANCE_TYPES_U1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
TABLE ACCESS BY INDEX ROWID GL.GL_JE_BATCHES
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
TABLE ACCESS BY INDEX ROWID GL.GL_PERIODS
INDEX RANGE SCAN GL.GL_PERIODS_U1
After Condition
SELECT STATEMENT
SORT GROUP BY
VIEW SYS
SORT GROUP BY
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS
NESTED LOOPS
NESTED LOOPS OUTER
NESTED LOOPS
TABLE ACCESS FULL GL.GL_JE_BATCHES
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_HEADERS
INDEX RANGE SCAN GL.GL_JE_HEADERS_N1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
INDEX UNIQUE SCAN GL.GL_ENCUMBRANCE_TYPES_U1
INDEX UNIQUE SCAN GL.GL_DAILY_CONVERSION_TYPES_U1
INDEX UNIQUE SCAN GL.GL_BUDGET_VERSIONS_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_SOURCES_TL
INDEX UNIQUE SCAN GL.GL_JE_SOURCES_TL_U1
INDEX UNIQUE SCAN GL.GL_JE_CATEGORIES_TL_U1
INDEX UNIQUE SCAN GL.GL_JE_BATCHES_U1
TABLE ACCESS BY INDEX ROWID GL.GL_JE_LINES
INDEX RANGE SCAN GL.GL_JE_LINES_U1
INDEX UNIQUE SCAN GL.GL_SETS_OF_BOOKS_U2
TABLE ACCESS BY INDEX ROWID GL.GL_CODE_COMBINATIONS
INDEX UNIQUE SCAN GL.GL_CODE_COMBINATIONS_U1
TABLE ACCESS BY INDEX ROWID GL.GL_PERIODS
INDEX RANGE SCAN GL.GL_PERIODS_U1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUES
INDEX RANGE SCAN APPLSYS.FND_FLEX_VALUES_N1
INDEX RANGE SCAN APPLSYS.FND_FLEX_VALUE_NORM_HIER_U1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUES_TL
INDEX UNIQUE SCAN APPLSYS.FND_FLEX_VALUES_TL_U1
TABLE ACCESS BY INDEX ROWID APPLSYS.FND_FLEX_VALUE_SETS
INDEX UNIQUE SCAN APPLSYS.FND_FLEX_VALUE_SETS_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
INDEX UNIQUE SCAN GL.GL_JE_HEADERS_U1
Is there anything i can do in Discoverer Desktop / Administration to avoid this problem.
Many thanks,
Lance

Hi Rod,
I've tried the condition (Batch Status||'' = 'Posted') as you suggested, but the qeury time is still over 20 mins. To test i changed it to (Batch Status||'' = 'Unposted') and the query was returned within seconds again.
Ive been doing some more digging and have found the database view that is linked to the Journal Batches folder. See below.
I think the problem is with the column using DECODE. When querying the column in TOAD the value of P is returned. But in discoverer the condition is done on the value Posted. Im not too sure how DECODE works, but think this could be the causing some sort of issue with Full Table Scans. How do we get around this?
Lance
DECODE( JOURNAL_BATCH1.STATUS,
'+', 'Unable to validate or create CTA',
'+*', 'Was unable to validate or create CTA',
'-','Invalid or inactive rounding differences account in journal entry',
'-*', 'Modified invalid or inactive rounding differences account in journal entry',
'<', 'Showing sequence assignment failure',
'<*', 'Was showing sequence assignment failure',
'>', 'Showing cutoff rule violation',
'>*', 'Was showing cutoff rule violation',
'A', 'Journal batch failed funds reservation',
'A*', 'Journal batch previously failed funds reservation',
'AU', 'Showing batch with unopened period',
'B', 'Showing batch control total violation',
'B*', 'Was showing batch control total violation',
'BF', 'Showing batch with frozen or inactive budget',
'BU', 'Showing batch with unopened budget year',
'C', 'Showing unopened reporting period',
'C*', 'Was showing unopened reporting period',
'D', 'Selected for posting to an unopened period',
'D*', 'Was selected for posting to an unopened period',
'E', 'Showing no journal entries for this batch',
'E*', 'Was showing no journal entries for this batch',
'EU', 'Showing batch with unopened encumbrance year',
'F', 'Showing unopened reporting encumbrance year',
'F*', 'Was showing unopened reporting encumbrance year',
'G', 'Showing journal entry with invalid or inactive suspense account',
'G*', 'Was showing journal entry with invalid or inactive suspense account',
'H', 'Showing encumbrance journal entry with invalid or inactive reserve account',
'H*', 'Was showing encumbrance journal entry with invalid or inactive reserve account',
'I', 'In the process of being posted',
'J', 'Showing journal control total violation',
'J*', 'Was showing journal control total violation',
'K', 'Showing unbalanced intercompany journal entry',
'K*', 'Was showing unbalanced intercompany journal entry',
'L', 'Showing unbalanced journal entry by account category',
'L*', 'Was showing unbalanced journal entry by account category',
'M', 'Showing multiple problems preventing posting of batch',
'M*', 'Was showing multiple problems preventing posting of batch',
'N', 'Journal produced error during intercompany balance processing',
'N*', 'Journal produced error during intercompany balance processing',
'O', 'Unable to convert amounts into reporting currency',
'O*', 'Was unable to convert amounts into reporting currency',
'P', 'Posted',
'Q', 'Showing untaxed journal entry',
'Q*', 'Was showing untaxed journal entry',
'R', 'Showing unbalanced encumbrance entry without reserve account',
'R*', 'Was showing unbalanced encumbrance entry without reserve account',
'S', 'Already selected for posting',
'T', 'Showing invalid period and conversion information for this batch',
'T*', 'Was showing invalid period and conversion information for this batch',
'U', 'Unposted',
'V', 'Journal batch is unapproved',
'V*', 'Journal batch was unapproved',
'W', 'Showing an encumbrance journal entry with no encumbrance type',
'W*', 'Was showing an encumbrance journal entry with no encumbrance type',
'X', 'Showing an unbalanced journal entry but suspense not allowed',
'X*', 'Was showing an unbalanced journal entry but suspense not allowed',
'Z', 'Showing invalid journal entry lines or no journal entry lines',
'Z*', 'Was showing invalid journal entry lines or no journal entry lines', NULL ),

Report on changes to sales orders

Hi Experts,
I am looking for a way to report on changes to sales orders, specifically the row shipping date and quantity.
I can see that the data is apparently in tables ADOC and ADO1 but am having trouble getting useful results. What I need is a report that, for sales orders only and for a date range, shows all changes to row quantities or row shipping dates. The type of output that would be useful is:
Change date - document # - row# - Item code - old shipping date - new shipping date - old qty - new qty
filtered on change date for sales orders only. This seems beyond my preferred option of XL-Reporter and I'm getting lost in the history tables in creating a query.
Best Regards
Matthew

Hi,
Without doing the query for you, history tables are linked as the "normal" table but with the addition of the LogInstance column. Then the UpdateDate column (from base table ie. ADOC) will tell you when it was changed.
Your query isn't an easy one... SInce you have to link an instance (ie. LogInstance = 1, which will be the original created object) to all the modified ones.
Regards,
Eric

Forming a report query dynamically with the value of an item

Hi Gurus,
We wanted to create a report based on the value of an item in the page.
For example
There is a text box named p1_table depending on the value of this item the query of the report should change
1) when p1_table = emp then report query should be select * from emp
2) when p1_table = dept then report query should be select * from dept
I tried doing this using
select * from :p1_table and select * from v('p1_table') , it is not working.
Kindly help me in achieving the requirement.
Thanks & Regards,
Vikas Krishna

Hi Vikas,
You have to do this as a report based on a function that returns the query as a string. You build up the string dynamically in the function.
Regards
Andre

What is the best practice for running a long report/query against an active database?

We are using SQL Server 2012 EE but currently do not have the option to run queries on a R/O mirror though that is my long term goal. I am concerned I may still run into the below issue in that scenario as well since the mirror would also be updating data I
am querying.
I have a view that joins across several tables from two databases and is used by an invoicing program on existing data. Three of these tables are also actively updated by ongoing transactions. Running a report that used this view did not use to be a problem
but now our database is getting larger and we have run into some timeout problems for the live transactions coming in.
First the report query was timing out so I set command timeout to 0 and reran the query which pegged all 4 CPUs 100% for 90 minutes and so I finally killed it. Strangely there were no problems with active transactions during that time so I'm wondering if the
query was really running doing anything useful or somehow spinning and waiting. I reviewed the view and found a field I was joining on that was not indexed so created an index on that field, reran the report, which then finished in three minutes and all the
CPUs were busy but not at all pegged out. Same data queried both times. I figured problem solved. Of course later, my boss ran a similar invoice report, with the same amount of data, and our live transactions started timing out 100% while his query was running.
I did not get a chance to see the CPU usage during that time.
I looked at the execution plan of the underlying view and added the suggested index but that did not help. When I run the just the view at SQL Server it does not seem to cause any problems and finished in a couple seconds. Perhaps something else going on in
the reporting tool using the view.
My main question is - Given I have to use the live and active database, what is the proper way to run a long R/O query/report so that active transactions can still continue to update
tables that I am querying? sp_who2 did show transactions being blocked so I guess a long query accessing the tables blocks live transactions accessing those same tables, but certainly I'm not the only one doing this. I
am considering adding "with (nolock)" but am hoping there is a better standard practice as that clause can return dirty data and I understand why. Thx, Dave
Thanks, Dave
Dave

Hello
You can change the DB isolation level to Read uncommitted
http://technet.microsoft.com/en-us/library/ms378149(v=sql.110).aspx
or use WITH (NOLOCK)
I do use NOLOCK option for the dirty reads to avoid locks on the tables
Javier Villegas |
@javier_vill | http://sql-javier-villegas.blogspot.com/
Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you

Report Layout Changed After Upgrade from 4.6C to ECC6

Dear Gurus,
I do functional test of every process in ECC6 after upgrade from 4.6C. I found all report layout changed without variant (it's happen to all Query/SQ01 reports ). So I've to assign manually the fields for the reports, and create a default variant then.
Why it happen ? Is there configuration or setting missed or this is standard while we do upgrade ?
Thx in advance.
Tri Wicaksono

We do re arrange for all ALV report ...

Report Query - XML data source empty

Hello!
I built a report query, using the wizard, under Shared Components and when I test the query using bind variables I get the correct data, but as I click Apply Changes and get to the screen where it gives me the option to Download the data source for the report layout, the file is empty. I've repeated the steps multiple times, each time getting correct data when testing the query, yet nothing in my xml file.
Any ideas on why this is happening?
Thank you.

Hello! Thank you for responding!
I actually am having problems on the "Report Queries" section under "Shared Components"...my query doesn't return any data when I try to download/open the xml file. Once I'm able to get this fixed, I'll be able to open my report on the page that has the branch.

Use of writeChanges() / conformResultsInUnitOfWork in report query

I have a usecase where i am saving data in different tables in same transaction
I want to use ReportQuery so as to use functions likeaddAverage.
ReportQuery query = new ReportQuery(res);
query.setReferenceClass(Subject.class);
query.addAverage("average-score", res.get("score"));
But since data is still not commited, I wanted to use conformResultsInUnitOfWork.
1.But I assume conformResultsInUnitOfWork can't be used with ReportQuery.
Am I correct?
2. According to toplink docs, we can use writeChanges() method on uow.
But after you call the unit of work writeChanges method , we can'r egister objects or execute object-level queries.
But after executing report query, I need to register obj /read objects to perform other use case operation.
So how can we use Report query to perform query on uncommited changes & still be able to other UOW operations or read object queries
Thanks for your help.

Hi Jayesh,
Please have a look at the below attachment.
[http://help.sap.com/saphelp_470/helpdata/en/5b/d22e3843c611d182b30000e829fbfe/content.htm]
Warm regards,
Murukan Arunachalam

Get XSD from Report Query

APEX 4.0.2
Oracle 11.2.0.1.0
Hello,
We are trying to retrieve the XML Schema for a Report Query.
The following code example is working, but the 'xsd' parameter for p_document_format is not documented.
Is 'xsd' a supported parameter value for APEX_UTIL.GET_PRINT_DOCUMENT?
v_blob := APEX_UTIL.GET_PRINT_DOCUMENT (
    p_application_id      => NV('APP_ID'),
    p_report_query_name   => 'test',
    p_report_layout_name => null,
    p_report_layout_type => null,
    p_document_format     => 'xsd',
    p_print_server => null);Thank you in advance!

Hi Eric,
We have four different versions of apex_util.get_print_document, so depending on what you want to do, you can create PDFs and other document types based on your own XML data, your own style-sheets, or referencing pre-defined report-queries, with pre-defined layouts, or custom layouts. We support the output formats I've previously listed for all four versions. However the internal implementation of those APIs is different for the APIs that reference report queries and those that reference custom XML data. When referencing report queries, APEX first loads and executes those queries and generates the XML data, and then passes the XML on the the print rendering engine. The parsing and execution of those queries happens to use the same internal functions that are also used on the report query edit page, where you have buttons that allow for downloading XML and XML Schema representations of your report query. Those XML and XSD documents are intended to be used with the BI Publisher Word Plug-In or third-party XSL design tools to design report layouts. Now given that the same internal functions are used, you can actually generate XML Schema (XSD) documents using the apex_util.get_print_document API, but only with those versions that let you reference a pre-defined report query. This isn't officially supported, so I can guarantee that this behavior won't change in the future, though I don't see why we would change that. The main reason for supporting XML in those APIs is really to test the print functionality without requiring a print rendering engine. But looks like there are some other use cases for those output formats as well.
Hope the helps,
Regards,
Marc

How to get bex query changes reflected in webi.

Hi expert,
I am using sap bex query in WEBI by BICS connection, but I have done some change in bex query, how can I get those changed reflected in webi.
Many Thanks,

Hi Zhang,
Please review following link which would help you to understand the impacts of changes in the BEx Query to associated universes and webi reports.
http://wiki.scn.sap.com/wiki/display/BOBJ/Impact+of+a+BEx+query+change+to+universes+and+WebI+documents
Regards,
Veer

Report query with multiple selects

On some of my Report Queries (that have multiple selects) it sometimes changes the rowset when I edit the specific SQL.
For example, I have 2 selects in my Report Query andnd when I download the XML my first select’s data goes into <ROWSET1> and my second select’s data goes into <ROWSET2>. I then make my template and everything is good.
But, sometimes when I edit the SQL in the report it changes the ROWSET number of the data so now my first select’s data in ROWSET2. This blows up the report. Is this a bug? Why is it switching the rowsets back and forth?

I'm referring to the Report queries under shared components.
My first query is like this:
select A.emp_id
from tab1 AC4, tab2 AC3, tab3 AC2, tab4 AC1, tab5 A
where A.year = :page_year
and C.FK_SCHOOL IN (SELECT c001
FROM apex_collections AC1
WHERE AC1.collection_name = 'SIS_REPORTS_SCHOOLS')
and nvl(C.ACTIVE,'NONE') IN (SELECT decode(c001,'NONE',nvl(C.ACTIVE,'NONE'),C001)
FROM apex_collections AC2
WHERE AC2.collection_name = 'SIS_REPORTS_ACTIVES')
and nvl(C5.CALENDAR_NO,'NONE') IN (SELECT decode(c001,'NONE',nvl(C5.CALENDAR_NO,'NONE'),C001)
FROM apex_collections AC3
WHERE AC3.collection_name = 'SIS_REPORTS_SCHOOL_CALENDAR_NOS')
and nvl(C10.CLUSTER_CODE,'NONE') IN (SELECT decode(c001,'NONE',nvl(C10.CLUSTER_CODE,'NONE'),C001)
FROM apex_collections AC4
WHERE AC4.collection_name = 'SIS_REPORTS_CLUSTER_CODES')
My second query needs to select the detail info from other tables, but I only want to do it for the (master) records that were returned in the first query.

Report query changes

Similar Messages

Maybe you are looking for