Bo Context Error
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 Forums) Unanswered Posts Register
Business Objects Context Error
or Login to Post Forum Index -> Building Reports -> WebIntelligence XI Author Message business objects context selection smacForum MemberJoined: 04 Dec 2003Posts: 22Location: Santa Clara Posted: Wed Apr 11, 2007 4:19 pmPost subject: #Context Error in BO XI Webi
Business Objects Context Operators
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 Sales Revenue DP 2 State Store Name Quanity Sold common errors in webi reports 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: 1154 Posted: Fri Jul 23, 2010 2:12 amPost subject: Re: #Context Error in BO #multivalue error in webi 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, Prashant "You cannot believe in God until you believe in yourself" - Swami Vivekanand Back to top Mark PForum DevoteeJoined: 03 Feb 2003Posts: 10295Location: Manchester, UK Posted: Fri Ju
data provider in a block containing dimensions from another data provider and 2 data providers are not synchronized through a merge dimension.#Incompatible
#datasync Business Objects
and #Context: Occurs if you try to include objects from 2 Queries/contexts #overflow error in bo which does not have any relationship or tables which are not linked then #Context appears in case of measures
#error In Webi Report
and #Incompatible appears in case of dimensions because it has a non-existent calculation context.#Incompatible in case of single data provider: may be having multiple sql queries in one data provider http://www.forumtopics.com/busobj/viewtopic.php?t=82605&sid=18a57698e9d5adebea2ef634d6d5f3cb 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 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 http://bobjanalytics.weebly.com/blog/-errors 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 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
@ 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 http://www.dagira.com/2010/01/04/calculation-context-part-i-overview/ for a while have started nodding their heads in agreement, only to stop and https://michaelwelter.wordpress.com/2011/07/31/removing-the-confusion-from-calculation-contexts/ say, "Hey, wait a second, is Dave talking about universe contexts or report calculation 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 business objects turn my attention to the report technique of calculation contexts. Note that this concept is used in Desktop Intelligence and Web Intelligence but not 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 business objects context 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 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 t
Line to aChart → Removing the Confusion from CalculationContexts July 31, 2011 83 Comments If you've read enough of my blog posts, you're probably aware that I've been using BusinessObjects for a long time, and, during the early years, I was pretty clueless. One of the topics that had me completely stumped was Calculation Contexts. I attended the classes, and learned a lot, but could not grasp the concept of Calculation Contexts. So, I studied the training manuals, but it just wasn't sinking in. So, I studied the user guides, but it still wasn't making sense. So, I decided that I just wasn't smart enough to understand this concept, and did my best to live without it. It wasn't until 2002, while attending the BusinessObjects User Conference that I finally got it. I was attending a session by my good friend Dave Rathbun. One of his topics was Calculation Contexts. Dave explained them in a slightly different way than the books. Suddenly the light bulb went on, and it hasn't dimmed since. In 2004, I started teaching BusinessObjects classes, and I always taught Calculation Contexts the way I learned it, and it seemed to make more sense than what was in the books. So, my first piece of advice is, if you really want to understand Calculation Contexts, don't read the books.🙂 What is Calculation Context? The bottom line is that all calculations in Web Intelligence, by default, happen in the context of where they appear on a report. The same formula, in different places, can give different results. Often, the default context is exactly what we want. But sometimes it isn't, and it's then that we need to understand how to manipulate the contexts. Default Calculation Context Let's start with a simple example, using the infamous eFashion universe. Create and run the following query: Next, section the report on Store name. Add a Sum to the Sales revenue column. Notice that, even though the formula for the Sum is the same in every section, it yields different results in each section: =Sum([Sales revenue]) This is because the calculation takes place in the context of where it appears on the report. In this case, the formula is within a section, so it outputs a different value for each section. Next, drag the cell with the sum, out of the block, and drop it next to the section header cell. Notice that the results are the same as when the sum was in the