Datasync Error In Business Objects
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 sap business objects #datasync PM Currently Being Moderated Hello!Could you please help with such a problem:I web intelligence #datasync have 2 Bex data sources:Query 1Query 2Hierarchies:- Date1- Accounts1Dimensions:- Year1- Month1- Account1Measure:- ActualHierarchies:- Date2- Accounts2Dimensions:- Year2- Month2- Account2Measure:- PlanI
Business Objects Merge Dimensions Datasync
want to merge both queries in one report.Step 1. I merge the dimensions: year1 to year2, acc1 to acc2, month1 to month2. So I've got 3 merged dims: Year, Month, AccountStep 2.
Datasync Error In Webi
I generate the tableX Axis: Date1 (Hierarchy from Q1), Month (Merged dim)Y Axis: Accounts1 (Hierarchy from Q1), Account (Merged dim)Body: 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 #context error in webi error #DATASYNC error in all the parts of the table(Picture attached)Thank you! datasync.JPG 32.3 K 20906Views Tagsnone (add) Tags: error, report, bex, bw, hierarchy, web_intelligence, webi Re: Datasync error in 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
BusinessObjects Web IntelligenceWhere is this place located?All Places SAP BusinessObjects Web Intelligence 4 Replies Latest reply: Jun 10, 2014 11:04 AM by Bala Manoj Kumar Gade Tweet #DATASYNC error while merging two different quires anil . Jun 6, 2014 11:50 PM Currently Being Moderated Hi All, I am on SAP BO
Errors In Webi Reports
4.1 SP2 Patch2 , I am trying to build a webi report on top of 2 merging dimensions in business objects different bex quires . I Merged on company code-Key from both the quires. Made query 1 as the primary query (a,b,c) and created the extend merged dimension values details objects (x,y,z) for dimensions from query 2.The brought in the merged Company code to report and fields directly from Primary query (a,b,c) , when I bring the fields from query 2 (x,y,z) . I am getting #DATASYNC error . https://scn.sap.com/thread/3250192 1.How to over come the # DATASYNC Error and what should be passed in for associated Dimension while creating the details for (x,y,z) . I am not able to find the Merged Dimensions (Company code- Keys).2.If I check the "Avoid duplicate rows aggregation" , I am getting the values . Is it the best practice to show the duplicate row aggregation (or) we need to always uncheck the option . Which is the best practice ? 3. After checking http://scn.sap.com/thread/3567163 the Avoid Duplicate row aggregation, I always ends up with the "Unable to get the first page of current report. Check the validity of report"Kindly find the errors below. Please suggest me the best practice to follow , while working on multiple bex quires . Suggestions Highly appreciated.ThanksAnil 3027Views Re: #DATASYNC error while merging two different quires Bala Manoj Kumar Gade Jun 8, 2014 3:43 PM (in response to anil .) Currently Being Moderated You have defined merged dimension on 'company code-Key' which is common in both the Bex-queries.You are able to bring the merged dimension and other objects from Query_ One to report block without any issue but when adding objects from Query_Two you are getting the error #DATASYNC.In this case objects from Query_One are got sync with the merged dimension object without any issue because they got added first to it.Similarly when you add merged dimension and objects from Query_Two you find no issue, because objects from Query_Two go sync first.Once objects from a query(Query_One/Query_Two) got added to a merged dimension, when we try adding objects from other query we get #DATASYNC error. This is because data in the other query is not able to sync with the initial result set, this is a know behavior.There are two workarounds:1) Merging all common dimension/characteristic objects: Only merged dimensions data will sync with the initial query, un-merged dimensions/characteristic objects will still give #DATASYNC error.2) Create detail objects/attribute
#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 build all http://ghuglu.com/?p=254 three in a block, you will get a #DATASYNC error because the Car Make and http://www.dagira.com/2009/09/03/using-forcemerge-to-fix-unbalanced-data-providers/ Year objects are not related. You will also encounter a #CONTEXT error for Sales Amount (because it's a measure). This 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 a warning rather than an business objects 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 Parameters under Multiple Paths. Check if the datasync error in 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: Tips and Tricks Post navigation ← BO Lead ETL TESTER → Leave a Reply
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