#datasync Error
Contents |
SAP 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 #datasync error in web intelligence Oct 11, 2012 1:31 PM Currently Being Moderated Hello!Could you please datasync error in business objects help with such a problem:I have 2 Bex data sources:Query 1Query 2Hierarchies:- Date1- Accounts1Dimensions:- Year1- Month1- Account1Measure:- ActualHierarchies:-
Web Intelligence #datasync
Date2- Accounts2Dimensions:- Year2- Month2- Account2Measure:- PlanI 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
Sap Business Objects #datasync
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: 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 #context error in webi (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 20810Views 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 datasy
Business Objects Suggest New Category What is #DATASYNC error how to remove it? Question Posted / sunnyodc 2 Answers 30611 Views IBM, TCS,
Errors In Webi Reports
I also Faced E-Mail Answers Answers were Sorted based on User's Feedback merging dimensions in business objects Answer / sunnyodc This error come when you fetch more than 1 dimensions from 2 joined queries. if you are extend merged dimension values merging 2 queries , you can pull all objects of 1st query , but only one dimension object from 2nd query. you can use merged object from 2nd query but not the other ones, https://scn.sap.com/thread/3250192 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 Correct ? 39 Yes 12 No Answer / amit rathi #DATASYNC :#DATASYNC occurs when you http://www.allinterview.com/showanswers/138226/what-is-datasync-error-how-to-remove-it.html 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 What are universe parameters? 6 Answers Difference between Decode and Case? 1 Answers TCS, Why do we need Three environments Like DEV, UAT, PROD. Need detailed answer please 1 Answers HCL, What is pragma? 1 Answers Once the project is submited to the Client. Client says that report is taking long time to run? Where u need to check? 2 Answers
#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 http://ghuglu.com/?p=254 and try to build all three in a block, you will get a #DATASYNC https://dwbicastle.com/2014/02/12/merge-dimension-data-synchronization-and-force-merge-in-bo-report/ 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 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 error in that bad. Think of it as 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 error in web set in the universe. Check the SQL tab in 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 t