Boxi #datasync Error
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 datasync in business objects you please help with such a problem:I have 2 Bex data sources:Query 1Query 2Hierarchies:- business objects merge dimensions datasync Date1- Accounts1Dimensions:- Year1- Month1- Account1Measure:- ActualHierarchies:- Date2- Accounts2Dimensions:- Year2- Month2- Account2Measure:- PlanI want to merge both queries in one report.Step merging dimensions in business objects 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. I generate the tableX Axis: Date1 (Hierarchy from Q1), Month
Errors In Webi Reports
(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 error #DATASYNC error in all the parts of the table(Picture attached)Thank you! datasync.JPG 32.3 K #error in webi 20917Views 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 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 an
+ Analytics Conference: Oct 18, Mastering SAP BI, Melbourne: Oct 23. Merge Dimensions - #DATASYNC Goto page 1, 2, 3Next Search this topic...|Search WebIntelligence XI...|Search Box Select a search Explain extend merged dimension values These Choices... --------------------Recent Topics (All Forums) Unanswered Posts Register or Login to Post
#multivalue Error In Webi
Forum Index -> Building Reports -> WebIntelligence XI Author Message DataGeekForum MemberJoined: 23 Jun 2004Posts: 17 Posted: Fri Jan
Business Objects Join Two Queries
19, 2007 12:42 pmPost subject: Merge Dimensions - #DATASYNC I have two very simple queries from the same universe in a WEBI report: Query 1 = ID, Number Query 2 = ID, Date If https://scn.sap.com/thread/3250192 I understand correctly, I should be able to create a table with ID, Number and Date after merging the ID dimensions. However, when I try to create a block with those objects, #DATASYNC is displayed in every column. I've tried using each of the ID dimensions (the merged and from both queries) to the same end. I've logged a case with BO, but thought I'd see if anyone else http://www.forumtopics.com/busobj/viewtopic.php?t=77386&sid=83539a6e7c1b342d6172e7f69f1679c9 has run into the same thing. Thanks, Mike Back to top MichaelWelterForum AficionadoJoined: 08 Aug 2002*6Posts: 14870Location: Rancho Cucamonga, CA, USA, Earth, Milky Way Posted: Fri Jan 19, 2007 1:13 pmPost subject: Re: Merge Dimensions - #DATASYNC My guess is that, either Date or Number is a dimension. You can only have one dimension from each query in a single block. ID is that dimension. Try creating a variable for Date, but make it a detail, and another for Number, and make it a detail, and see if you can add them to the block._________________Michael Welter, BOCP-BOE, Webi Image link BusinessObjects Practice Manager Claraview (Division of Teradata) (909)899-3002 ______________________ Follow me on TwitterLatest Blog Posts• 2016-02-02 Universe Design Best Practices• 2015-11-05 Review of Information Design Tool 4.1• 2015-04-29 Impact of a Database Migration Back to top konquistadorPrincipal MemberJoined: 03 Jan 2006Posts: 274Location: Hartford, CT Posted: Tue Mar 06, 2007 1:39 pmPost subject: Re: Merge Dimensions - #DATASYNC Hi Guys, Did you ever solve this....? Michael, i tried your solution but still the #datasync error when i try to put objects from different Data Providers(same universe) in one block?00 Any other ideas? Thanks, Kon Back to top anair_boPrincipal MemberJoined: 05 Dec 2006Posts: 255Location:
webi report, so that we can use them in same block. Mandatory condition to merge objects is to have same data type. For eg. See below tables , coming from two different queries in webi report. Query 1 Query 2 Now if you http://gsaxena-bobj.blogspot.com/2012/06/merge-dimensions-in-webi.html try to use all these objects in same block , you will get data sync error.(As webi will not be able to find any relation between these queries) I will now merge empid and cust id. Merge Id is showing https://michaelwelter.wordpress.com/2011/04/18/tips-for-merging-dimensions/ all rows coming from emp id and cust id and their corresponding revenue and salary column values. This is now showing results as Full outer join. But if I involve any one non-merged dimension in this block, the results will business objects start showing dimension values pertaining to that query only. So basically it is working as Left or Right Outer join when we try to use any dimension in the block which is not merged. But we will not be able to use both emp name and cust name in same block as these are not merged. We will get data sync error if we try to use them in same block. Similarly if you don't use merge id column and use in business objects emp id or cust id along with revenue and salary, that will work as Left or Right outer join and not as Full outer join. So this explains when merge dimension works as Full outer join and when it works as left or Right outer join. There is also one option which makes the functionality of left or right outer join to work as full outer join. i.e. Extended merge dimension. (note:- but this works only when unmerged dimension is not selected in the block) See for below example. When I used cust id revenue and salary, the block look like this: So its showing data as left outer join . Now I will check the option"Extended Merge Dimension" from document properties. Now it will work as full outer join as shown in screenshot: So this option makes the query to give full outer join result set even if you have selected specific and not merged object in the block. Note: this option wont work if you use non-merged dimension in the block. For eg. If you use cust name in the above block it wont work as full outer join. Posted by GS at 17:43 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: business objects, extended merge dimension, merge dimension, web intelligence 17 comments: Garima Saxena8 August 2012 at 21:32Good job...;)ReplyDeleteAnonymous9 August 2012 at 11:50Ok.. can you pls let us know How do u link different data p
Default Formatting In WebIntelligence → Tips for MergingDimensions April 18, 2011 81 Comments I've noticed lately that there seems to be a lot of confusion about merging dimensions in Web Intelligence. I've spent a fair amount of time on BOB answering questions about this topic. So, perhaps it's time to put together a comprehensive document covering this topic. After all, merging dimensions is one of the most powerful features of Web Intelligence. Tip 1: Adding “Incompatible” dimensions to the block Have you ever noticed that, sometimes when you try to add a dimension to a block that includes merged dimensions, you sometimes get an "Incompatible object" error? Let me explain why this happens, and then we'll look at ideas on how to fix it. Dimension objects and Detail objects have a fundamental difference: Dimension objects usually represent a different level of granularity. For example, State and City might be two dimension objects in your universe. City is a lower level of granularity than State. So, when you add City to an existing block that already includes State, the measure objects will be aggregated at a lower level of granularity. Detail objects, on the other hand, typically do not represent a lower level of granularity when used with their related dimension. For example, if I have Sales Revenue broken down by Customer in a block, and then add the Eye Color detail object, Sales Revenue will not be aggregated at a lower level. It will stay at the level of Customer. This is how detail objects work. So, if I have two queries merged on State, and try to display another dimension, that is not merged, such as State Capitol, Web Intelligence doesn't know how to aggregate the measures at the lower level of State Capitol, since that dimension doesn't exist as a merged dimension. Of course, you and I both know that each State only has one State Capitol, so it's not really a lower level of granularity. But Web Intelligence doesn't know that. So we have to tell it. The way we tell is as follows: Create a detail variable. In this case, maybe we call it Capitol. Make it a detail of the State merged dimension. The formula for this variable is: =[State Capitol] We can then add the variable to the block, as Web Intelligence sees it as a detail of State, rather than a different level of granularity. Note that the detail variable must be a detail of a merged dimension. Otherwise, you still won't be able to add it to