#context Error In Bo
Contents |
+ Analytics Conference: Oct 18, Mastering SAP BI, Melbourne: Oct 23. #Context Error in BO XI Webi Search this topic...|Search WebIntelligence XI...|Search Box Select a search Explain These Choices... --------------------Recent Topics (All business objects context error Forums) Unanswered Posts Register or Login to Post Forum Index -> Building Reports business objects context selection -> WebIntelligence XI Author Message smacForum MemberJoined: 04 Dec 2003Posts: 22Location: Santa Clara Posted: Wed Apr 11, 2007 4:19 pmPost business objects context operators subject: #Context Error in BO XI Webi Hi, Does anyone know the work around for a #Context error that occurs in Webi and not in Deski? I have two Data Providers: DP 1 City State business objects universe context Sales Revenue DP 2 State Store Name Quanity Sold Merged Dimension is State Variable = Sum([Sales revenue] Where ([City] = "Austin") ) Report Display: State (DP1), Store Name, Variable The Variable displays result in BO XI Deski but it gives #CONTEXT in BO XI Webi. Does anyone know how to fix this in Webi? Or is it a known bug? Thanks, Stewart Back to top BOCPForum EnthusiastJoined: 02 Jul 2007Posts:
Calculation Context In Business Objects
1154 Posted: Fri Jul 23, 2010 2:12 amPost subject: Re: #Context Error in BO XI Webi Hi Stewart, Don't go after State (DP1). Use Merged Dimension State Object not DP1 or DP2. Hope it works out. Thanks...!! Back to top Prashant PurohitForum EnthusiastJoined: 18 Feb 2009Posts: 1047Location: Pune Posted: Fri Jul 23, 2010 2:25 amPost subject: Re: #Context Error in BO XI Webi Even if you use merged state error will not go, the reason is your variable used one unmerged dimension (city) from DP1 and you also include (Store name) an unmerged dimension from DP2, create a new detail variable for store name, link it to merged state and then use it in your table._________________Thanks & Regards, Prashant "You cannot believe in God until you believe in yourself" - Swami Vivekanand Back to top srijacksonPrincipal MemberJoined: 29 Jul 2009Posts: 132 Posted: Fri Jul 23, 2010 6:33 amPost subject: Re: #Context Error in BO XI Webi am having simple question 1. Can we merge detail object with dimention object from different data provider Thanks, Sriraman Back to top Prashant PurohitForum EnthusiastJoined: 18 Feb 2009Posts: 1047Location: Pune Posted: Fri Jul 23, 2010 7:05 amPost subject: Re: #Context Error in BO XI Webi Simple answer is NO. _________________Thanks & Regards, Prashan
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
Common Errors In Webi Reports
include objects from 2 Queries/contexts which does not have any relationship or tables #multivalue error in webi which are not linked then #Context appears in case of measures and #Incompatible appears in case of dimensions because it #datasync business objects has a non-existent calculation context.#Incompatible in case of single data provider: may be having multiple sql queries in one data provider that is if you include objects from different contexts. How do you resolve http://www.forumtopics.com/busobj/viewtopic.php?t=82605&sid=18a57698e9d5adebea2ef634d6d5f3cb #Incompatible? By creating a detailed variable for the incompatible dimension and associating it with the 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 http://bobjanalytics.weebly.com/blog/-errors a formula that returns more than one value in a cell that outputs. Or if a single cell is trying to display multiple 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 Rep
@ 6:28 pm One of the hardest concepts to explain when introducing new folks to Business Objects is context. I now imagine blog readers who have been working with the tools for a while have started nodding their heads in agreement, only to http://www.dagira.com/2010/01/04/calculation-context-part-i-overview/ stop and say, "Hey, wait a second, is Dave talking about universe contexts or report calculation http://www.bidw.org/business-objects/universe-design/understanding-context-and-its-use-in-business-objects-universe/ contexts?" And the answer is, of course, yes. Both concepts can be quite complicated and take a while to fully understand. Since I have already written a number of blog posts about universe contexts I thought it was time to turn my attention to the report technique of calculation contexts. Note that this concept is used in Desktop Intelligence and Web Intelligence but not business objects in Crystal. This post is intended to be an overview only. I have plans for a detailed post on each of the various context operators where I will go into much more depth. For this post my goal is to introduce the concept and provide some basic definitions. Introducing Calculation Context The default calculation context is defined by the dimensions that participate in a report block. It is this feature that makes the dynamic nature of measures possible. When business objects context dimensions are removed from or added to a block the context changes and the measure amounts also change. This is controlled by the projection function set on each measure by the universe designer. However, a report writer sometimes wants a measure to be fixed at a particular value. Percentages are a really simple example. To calculate a contribution percentage I need to divide each individual value by the overall grand total. In order to do that, I need to know how to generate the grand total anywhere I want it. In order to do that, I need to understand how to use the various calculation context operators. Context Operators There is a simple (but powerful) set of context operators that I can choose from. I intend to briefly define each one in this blog post and then dive into more detail in future posts. As I mentioned when I started, the default context for a measure is based on the dimension values present in the block structure. I can alter which of those dimensions impact the calculation using one of the following three context operators. In is used to specify exactly which dimensions to include in a context. Other dimensions in the block are ignored. Adding / removing elements from the block does not impact this calculation unless a removed dimension was specified in the context. In that case a #MULTIVALUE error is displayed. ForEach is use
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 objects from two or more contexts are used, separate SQL is generated and results 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 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 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 c