#context Business Objects Error
Contents |
+ Analytics Conference: Oct 18, Mastering SAP BI, Melbourne: Oct 23. HTML Query Panel Search this topic...|Search WebIntelligence XI...|Search Box Select a search Explain These calculation context in business objects Choices... --------------------Recent Topics (All Forums) Unanswered Posts Register or Login to Post context in business objects universe Forum Index -> Building Reports -> WebIntelligence XI Author Message rit372002Principal MemberJoined: 01 Nov 2006Posts: 284 Posted: Mon
Alias And Context In Business Objects With Example
Feb 04, 2008 8:55 pmPost subject: HTML Query Panel Hi, Due to Performance problem, we have to use HTML-Query Panel instead of Java but HTML version seems to lack rich Java qualities.
Business Objects Error Err_wis_30270
If I have 5 queries, then does any one know how to run the individual queries in HTML-Query Panel? Thanks, rk Back to top MayhewMForum AssociateJoined: 22 Oct 2003Posts: 742Location: North America Posted: Tue Feb 05, 2008 12:57 amPost subject: Re: HTML Query Panel Your queries shouldn't run any differently between viewer types. Usually the lack of speed is due to the refresh business objects error inf rate of the viewer you are using. Generally, I would think your java panel would be more robust and should run faster. I think there's more to your issue and other questions need to be answered. Such as how many users are running on-demand reports at the same time. Maybe additional Webi Services (Report and Job Servers) need to be added to handle the requests. More investigation is needed. Have a great day!_________________God's Blessing to You! Michael E. Mayhew, Sr. Business Intelligence Architect, BECP Oracle Certified Specialist (Exadata/Datawarehousing) BOEXI 4.0, 3.1, 3.0, BOEXIR2, BOEXIR1, 6.x, 5.x, 4.x, Crystal Reprots XI, 2008, Xcelsius 2008 Migration and Architecture Specialist Oracle 10, 11g, 12c ODI, OBIEE 10 and 11g Business Intelligence North America Back to top rit372002Principal MemberJoined: 01 Nov 2006Posts: 284 Posted: Tue Feb 05, 2008 3:33 amPost subject: Re: HTML Query Panel Thanks for your reply MayhewM. Well, Java panel is not robust...I have tried different options...like having unlimited cache in the java panel, exclude the .jar file from scanning in the antivirus... You made a good point of on demand reports...which services are used for on demad webi repor
data provider in a block containing dimensions from another data provider and 2 data providers are not synchronized through a merge dimension.#Incompatible and #Context: Occurs if you try to include objects from 2 Queries/contexts which does not
Common Errors In Webi Reports
have any relationship or tables which are not linked then #Context appears in case of #multivalue error in webi measures and #Incompatible appears in case of dimensions because it has a non-existent calculation context.#Incompatible in case of single data provider: may #overflow error in bo be having multiple sql queries in one data provider that is if you include objects from different contexts. How do you resolve #Incompatible? By creating a detailed variable for the incompatible dimension and associating it with the http://www.forumtopics.com/busobj/viewtopic.php?t=101966&view=next&sid=b9e3ccfd74f93109c649945419feab1b merged dimension, and using this variable in the report.#Computation: Occurs when a slicing dimension specified in the Relative Value () function is no longer available in the calculation context. I.e. object might be deleted or renamed. #Div/0: Occurs when a formula tried to divide a number by zero.#Multivalue: Occurs when you place a formula that returns more than one value in a cell that outputs. Or if a single cell is trying to display multiple http://bobjanalytics.weebly.com/blog/-errors values. Or occurs when you don’t set sql aggregate functions for a measure object in universe designer.Ex: [Revenue] ForEach ([Country]) returns #Multivalue because country might have multiple countries like India; US.one cell cannot display revenue for 2 countries.If report is broken into section on country the formula is correct.#Overflow: Occurs when a calculation returns a value that is too large for Web I to handle.#Partial Result: Occurs when we set Query controls in universe designer.#ToRefresh: Occurs if the measure object has projected function “Database delegated”.#Syntax: Occurs when a formula references an object that no longer exists in the report. 2 Comments En uygun banka kredisi bulma link 06/01/2015 22:12 How do you resolve #Incompatible? By creating a detailed variable for the incompatible dimension and associating it with the merged dimension, and using this variable in the report. Reply Yıldırım Turan link 28/02/2015 22:19 How do you resolve #Incompatible? By creating a detailed variable for the incompatible dimension and associating it with the merged dimension, and using this variable in the report. Reply Leave a Reply. Author Ganesh Appanahas 3+ years of experience as an SAP BO Consultant. Archives December 2013 Categories All Sql Aggregate Functions Vs. Report Projection Functions Types Of Connections Universe Designer Webi What Is Business Objects RSS Feed Create a free website Powered by Create your own free w
a context? A context is a group of path that defines a specific path for a query. Any objects created on a table column which belong to specific contexts is naturally compatible with all other objects from same contexts. When http://www.bidw.org/business-objects/universe-design/understanding-context-and-its-use-in-business-objects-universe/ objects from two or more contexts are used, separate SQL is generated and results http://www.dagira.com/2008/03/10/what-is-a-context-anyway/ are then merged in a micro cube. This makes sure that no incorrect result is generated due to loop or any other join path issue. How to Create Context. There are multiple ways to create context. Automatically using Detect Context Automatically using Loop Detection Tool. Manually For automatic detection of context, cardinalities must be set correctly. How to detect business objects context automatically Click on Detect context icon from the toolbar. Designer will show up the name and joins for the candidate context Review the highlighted joins in respective context if you are ok with it click on add button. once done click OK How to detect context using Loop Detection Tool Click on tools Click on Automated detection-> detect loops Detection tool will show the loops in universe and it will propose either business objects error alias on context to resolve the loop. Click on forward button till it says “The loop is not covered by any context” Click on candidate context button to detect context. It will show the possible context. Follow the process of “Creating context automatically” to create context and resolve loop. Creating context manually. To create context manually Click on Insert->Context A create context box will appear. Enter the name of context and joins in context. Click OK Make sure each join except shortcut join is included in at least one context. Testing Contexts When context exist in universe. Designer can generate three types of queries. Ambiguous query Inferred query Incompatible Objects query. Whenever you create a context you should check context against these three queries two test correctness of context. Ambiguous query If you have multiple contexts in universe, try creating a report which includes objects common to both the context. This situation does not give enough information on which context to use while generating the query and inturn it prompts all available contexts to user to choose from. Once user selects the context, query is generated accordingly. Make sure Allow selection of multiple context option is selected from SQL tab of universe parameters as user might select multiple context in case of ambiguous query. Incompatible Objects query.
Rathbun @ 10:09 am A few days ago I finally got started on what will become a series of posts about fan and chasm traps. The post was "Do I Have a Fan Trap?" and it included a definition of a fan trap in a universe and showed a basic solution. However, it also mentioned that the basic solution would not work in most cases, and that contexts would be required for a more complete solution. If you are new to the Universe Designer, or even if you just have not worked with contexts that much, the first step is understanding exactly what a context does for you. That is what I hope to do with this post. Just the Facts One of the comments that you will see quite frequently on BOB is that you need one context for each fact table. That assumes that you have fact tables. It turns out that the statement is, in fact (heh, pun intended ), true, but why is that? What is it about a fact table that requires a context? Universe Structure A universe is a combination of two things: the structure (map) of the tables and the required joins, and the classes and objects that are presented to the user as the interface to the data. For the most part contexts are associated with the first part (structure) although they do have a user interface component as well. In the last post on this subject I included this quote: As a designer you cannot control which objects a user selects to use on a query. You are not building a specific query, you are building a framework for any query. What this means is that as a designer you include all of the potential joins in your universe structure without knowing in advance which query path a user is going to require for any given report. In most cases that isn't a problem. But in some cases it might be, and that's where contexts become valuable. Context Definition A context is nothing more th