Datasync Error Bo
Contents |
BusinessObjects Web IntelligenceWhere is this place located?All Places SAP BusinessObjects Web Intelligence 8 Replies Latest reply: May 26, 2015 6:30 PM by Dee J. Tweet Datasync error in Webi Alexey Veselov Oct 11, 2012 1:31 PM Currently Being Moderated Hello!Could you please help with such datasync error in webi a problem:I have 2 Bex data sources:Query 1Query 2Hierarchies:- Date1- Accounts1Dimensions:- Year1- Month1- Account1Measure:- ActualHierarchies:-
Datasync In Business Objects
Date2- Accounts2Dimensions:- Year2- Month2- Account2Measure:- PlanI want to merge both queries in one report.Step 1. I merge the dimensions: year1 to year2, business objects merge dimensions datasync acc1 to acc2, month1 to month2. So I've got 3 merged dims: Year, Month, AccountStep 2. I generate the tableX Axis: Date1 (Hierarchy from Q1), Month (Merged dim)Y Axis: Accounts1 (Hierarchy from Q1), Account (Merged dim)Body:
#context Error In Webi
Actual, PlanAnd everything is OK.Step 3. I replace Accounts1 (Hierarchy from Q1) by Accounts2 (Hierarchy from Q2)So, I've got the following table:X Axis: Date1 (Hierarchy from Q1), Month (Merged dim)Y Axis: Accounts2 (Hierarchy from Q1), Account (Merged dim)Body: Actual, PlanThen there is an error #DATASYNC error in all the parts of the table(Picture attached)Thank you! datasync.JPG 32.3 K 20900Views Tagsnone (add) Tags: error, report, bex, bw, hierarchy, web_intelligence, webi Re: Datasync error in merging dimensions in business objects Webi Simone Caneparo Nov 8, 2012 3:47 PM (in response to Alexey Veselov) Currently Being Moderated you get the #DATASYNC message because the engine is unable to synchronize the two dataproviders. it is not sufficient to declare the merged dimensions and hierarchies are more complex than it seems so you are using a non supported workflow. Alert Moderator Like (0) Re: Datasync error in Webi Mark Singley Nov 8, 2012 10:04 PM (in response to Alexey Veselov) Currently Being Moderated You'll get a datasync error if you try to use an object from each query. The common way around this is to create a detail object, which is very simply =Accounts2, which is a detail of the merged dimension. I'm not 100% this will work on a hierarchy- but that's how you get around the datasync error and take objects from both queries that are merged together. Give that a try. Alert Moderator Like (1) Re: Datasync error in Webi Simone Caneparo Nov 12, 2012 10:13 PM (in response to Mark Singley) Currently Being Moderated this could be dangerous if there is no logical relationship between detail and dimension, at some point you could get incorrect results on a hierarchy the risks are much higher... Alert Moderator Like (0) Re: Datasync error in Webi Leela Padmanabhuni Nov
Business Objects Suggest New Category What is #DATASYNC error how to remove it? Question Posted / sunnyodc
Extend Merged Dimension Values
2 Answers 31001 Views IBM, TCS, I also Faced E-Mail Answers Answers were
#error In Webi
Sorted based on User's Feedback Answer / sunnyodc This error come when you fetch more than 1 #multivalue error in webi dimensions from 2 joined queries. if you are merging 2 queries , you can pull all objects of 1st query , but only one dimension object from 2nd query. you can use https://scn.sap.com/thread/3250192 merged object from 2nd query but not the other ones, if you want to show remaining objects of 2nd query make a measure variable of each dimension. that means put them in new variable and define that variable as measure. now bring them on report. select table go to property click the option > show rows with empty measure values. Is This Answer http://www.allinterview.com/showanswers/138226/what-is-datasync-error-how-to-remove-it.html Correct ? 39 Yes 12 No Answer / amit rathi #DATASYNC :#DATASYNC occurs when you place a dimension from a different dataprovider in a block containing dimensions from another data provider, and the two data providers are not synchronized through a merged dimension. #DATASYNC appears in all dimensions in the block and #CONTEXT in the measures. Example: Dimensions from different data providers in a block If a report based on the Island Resorts Marketing universe contains data providers with the objects (Year, Revenue) and (Quarter), a block containing Year, Quarter and Revenue displays #DATASYNC in the Year and Quarter columns because the two data providers are not synchronized through a merged dimension Is This Answer Correct ? 20 Yes 2 No Post New Answer Categories Teradata (205)Business Objects (780)Cognos (888)Informatica (1801)Crystal Enterprise Suite (29)Actuate (36)Ab Initio (209)Data Stage (636)SAS (599)Micro Strategy (41)ETL (208)OBIEE (45)Data Warehouse General (219) More Business Objects Interview Questions how to optimize the query perfomance in b.o? 1 Answers TCS, How to solve the following errors coming in report development? 1.Syntax 2.multi value 3. #Error 4.computation and 5.Objects are not compatible 2 Answ
#DATASYNC errors occur when you are working with multiple providers and you try to use unrelated objects from different queries. If you have Car Make and Sales Amount from one query and Year from another and try to http://ghuglu.com/?p=254 build all three in a block, you will get a #DATASYNC error because the Car Make and Year objects are not related. You will also encounter a #CONTEXT error for Sales Amount (because it's a measure). This http://www.dagira.com/2009/09/03/using-forcemerge-to-fix-unbalanced-data-providers/ happens when you have a dimension imbalance between the two contexts. Whether you avoid it or confront it depends on what you need to do in the report. Synchronized queries aren't all that bad. Think of it as error in a warning rather than an error. It just means that you have an incompatible object in the query. So what BO does is run the query for each synchronization and then automatically merges the result before displaying the data. if you are using contexts in the universe and that join should exist in that context. This type of join is usually caused by the parameter you set in the universe. Check the SQL tab in error in webi Parameters under Multiple Paths. Check if the multiple queries for each measure are checked. Trying disabling this and see if it makes a difference. To make query Synchronization work with a table: In the table: 1. Only display dimensions (one or more…) that are synchronized through all queries participating in the table; 2. Display any measures coming from any query; 3. But you can use any non-synchronized objects from any query to build a measure that will be displayed in the table… It just has to be Summarizable… Anything that is not a number cannot be defined as a measure thus has to be synchronized. The basic concept of synchronization is if you want to merge the two dimensions they should have of same datatype.it is not mandatory to be have same name. If 2 dimensions with different names but same data type we can comfortably merge them. in following case the reason for getting #DATASYNC is Query 1 = ID, Number Query 2 = ID, Date hare first one is number data type, date is other data type. So you'll get error. Try with dimensions with same data type. In order for you to get a Join instead of Synchronization, you need to have all the same dimensions available to both contexts. If synchronization changes the sort of values Crate a new column using the merge dimension itself and do the sort on that. Category:
Variables!, Web IntelligenceDave Rathbun @ 7:30 am I have discussed the MultiCube() function a number of times in my series of Variables presentations. In certain situations it allows you to fix measure objects when you have two (or more) unbalanced data providers in a full-client document. ForceMerge() is the equivalent for Web Intelligence. So how do they work, exactly? What do I mean by unbalanced data providers? How is it fixed with these functions? Are there any special conditions to be aware of? Merged Data Provider Review I recently published a blog post that described unbalanced data providers. If you want the full description, I have included a link at the end of this post. If you want the executive summary, here it is: When you have two (or more) data providers in the same document and want to merge the data, you have to link them using dimension objects. If you don't have the same number of dimensions from each data provider, then they are unbalanced. That can cause issues. It took me twelve hundred words (and six pictures) to provide a detailed explanation in my earlier post. In the sample report I used for that post I had one common dimension (Year) and one unique dimension from each side (Resort and Region). I showed how I could use Year with either measure since it was a shared (and linked) dimension. I also showed how (and explained why) trying to use the "extra" dimensions like Region or Resort caused problems. I don't intend to repeat everything here; please use the link at the end of this post to read the prior post if you are unclear on anything so far. What About MultiCube()? One of the comments I got on that post suggested that MultiCube() could be used to fix the issue. My response was accurate as far as I was concerned, but later when I read it again I realized it could also be quite confusing. Here's what I said: …the MultiCube() function will help if data providers are unbalanced “upwards” but not “downwards” … After reviewing my response, I realized that it was quite likely that I was the only person that understood what I meant by that statement. While at times I do enjoy talking with myself that's not why I have this blog. So I am going to try to explain that a bit further. The problem with trying to use MultiCube() or the Web Intelligence equivalent ForceMerge() to solve this specific case is that the data doesn't support the solution. There is no hierarchy or relationship between Region and Resort. (Yes, they are both related via links to the fact