#context Error In Business Objects Report
Contents |
SAP BusinessObjects Web IntelligenceWhere is this place located?All Places SAP BusinessObjects Web Intelligence 3 Replies Latest reply: Aug 25, business objects context selection 2010 11:00 AM by Srivatsa Kondapalli Tweet #CONTEXT error and
Business Objects Context Operators
#INCOMPATIBLE error Muntasir Jilani Aug 25, 2010 9:42 AM Currently Being Moderated Hi, I datasync error in business objects am getting #CONTEXT error and #INCOMPATIBLE error in webi report values when refresh the report.Any suggestion?Thanks & Regards,M.A.Jilani 11483Views Re: #CONTEXT error and #INCOMPATIBLE #multivalue error in business objects error Amr Salem Aug 25, 2010 9:59 AM (in response to Muntasir Jilani) Currently Being Moderated this happens in cause of putting incompatible dimensions and measures from different contexts.try to check your universe or your query.and when you create the query try to select compatible dimensions and
Computation Error In Business Objects
measures which all come under the same contextgood luck Alert Moderator Like (0) Re: #CONTEXT error and #INCOMPATIBLE error Muntasir Jilani Aug 25, 2010 10:52 AM (in response to Amr Salem) Currently Being Moderated Thanks bro...i will see to it. Alert Moderator Like (0) Re: #CONTEXT error and #INCOMPATIBLE error Srivatsa Kondapalli Aug 25, 2010 11:00 AM (in response to Muntasir Jilani) Currently Being Moderated In addition to the above, this also happens when you try to bring in dimensions from different data providers and try to display them in one table.In such a case, you will have to create DETAIL variables for Dimensions coming in from one of the data providers Alert Moderator Like (0) Go to original post Tweet Actions Login to follow, like, comment, share and bookmark content. Login Register Follow SCNJive Software Version: 5.0.6.2 , revision: 201308121150.54f5b14.release_5_0_6_2
+ Analytics Conference: Oct 18, Mastering SAP BI, Melbourne: Oct 23. #Context Error in BO XI Webi Search this business objects report writing topic...|Search WebIntelligence XI...|Search Box Select a search Explain These Choices... --------------------Recent Topics business objects report performance tuning (All Forums) Unanswered Posts Register or Login to Post Forum Index -> Building Reports -> WebIntelligence
Business Objects Report Writing Training
XI Author Message smacForum MemberJoined: 04 Dec 2003Posts: 22Location: Santa Clara Posted: Wed Apr 11, 2007 4:19 pmPost subject: #Context Error in BO XI Webi Hi, Does https://scn.sap.com/thread/1768632 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 Merged Dimension is State Variable = Sum([Sales revenue] Where ([City] = "Austin") ) Report Display: State (DP1), Store Name, Variable The Variable displays http://www.forumtopics.com/busobj/viewtopic.php?t=82605&sid=18a57698e9d5adebea2ef634d6d5f3cb 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 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 Vive
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 http://www.bidw.org/business-objects/universe-design/understanding-context-and-its-use-in-business-objects-universe/ all other objects from same contexts. When objects from two or more contexts are https://michaelwelter.wordpress.com/2011/07/31/removing-the-confusion-from-calculation-contexts/ 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 business objects 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 error in business 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 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
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 block. This is because the formula is still in the context of the section, Store name, and therefore, outputs a different value for each Store name. Next, drag the ce