Business Objects Data Sync Error
Contents |
SAP 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 sap business objects #datasync Hi All, I am on SAP BO 4.1 SP2 Patch2 , I am trying
Web Intelligence #datasync Error
to build a webi report on top of 2 different bex quires . I Merged on company code-Key from both the quires. web intelligence #datasync Made query 1 as the primary query (a,b,c) and created the 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
Business Objects Merge Dimensions Datasync
I bring the fields from query 2 (x,y,z) . I am getting #DATASYNC error . 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 datasync error in webi duplicate row aggregation (or) we need to always uncheck the option . Which is the best practice ? 3. After checking 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 3007Views 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 ab
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 These Choices... --------------------Recent
#context Error In Webi
Topics (All Forums) Unanswered Posts Register or Login to Post Forum Index -> Building
Merging Dimensions In Business Objects
Reports -> WebIntelligence XI Author Message DataGeekForum MemberJoined: 23 Jun 2004Posts: 17 Posted: Fri Jan 19, 2007 12:42 pmPost subject: errors in webi reports 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 I understand correctly, I should be able http://scn.sap.com/thread/3567163 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 has run into the same thing. Thanks, Mike Back http://www.forumtopics.com/busobj/viewtopic.php?t=77386&sid=83539a6e7c1b342d6172e7f69f1679c9 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: 253Location: Philly, PA Posted: Fri Mar 14, 2008 3:59 pmPost subject: Re: Merge Dimensions - #DATASYNC Facing the same issue.Any r
#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 http://ghuglu.com/?p=254 Year from another and try to 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 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 business objects the report. Synchronized queries aren't all 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 web intelligence #datasync 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 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 Jo