本文介绍了一份报告中的Business Objects WEBI 3 Universe的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

自昨天以来,这一直困扰着我,我无法解决,希望您能提供帮助:

this is bugging me since yesterday and I cannot work it out, hope you can help:

我在Business Objects中有一个报告(我使用WEBI界面),具有从3个不同的Universe中提取的数据:Universe 1和2已针对每个客户编号出售了数量信息,Universe 3查询只是客户编号及其相关区域的列表。所有3个Universe具有相同的客户编号,因此我在该字段上进行了合并。
我能够完成的第一个任务是:我创建了一个表,用于检查Universe 1中特定客户的已售出数量,然后为该客户显示此数量,如果没有,则显示此数量。来自Universe 2的客户。

I have a report in Business Objects (I use WEBI interface) which has data being pulled from 3 different universes: universes 1 and 2 have sold qty information per customer number, universe 3 query is just a list of customer numbers and their relevant region. All 3 universes have same customer numbers therefore i merged on that field.The first task which i have been able to achieve is: i created a table that checks if there is sold qty for a particular customer in universe 1 then this qty is shown for this customer, if not, show qty for this customer from universe 2.

我正在苦苦挣扎的是:我需要将第三个Universe中的客户区域字段添加到同一报表中,以查找客户编号并返回客户区域字段,但是问题是-第三个Universe中缺少一些客户编号,在添加该字段时,我从表中完全失去了该客户的已售出数量条目。但是,我仍然希望在该区域的空值报告中看到它们。

What i am struggling with is: i need to add the customer region field from the third universe into the same report looking up the customer number and returning the customer region field, however the problem is - there ARE some customer numbers that are missing from the third universe and on adding that field i lose this sold qty entries for this customer from the table completely. However i would like to still see them in a report with "Null" values for the region.

我在互联网上的不同来源中搜索了类似的解决方案,但是我找不到类似的东西(在同一份报告中有3个Universe),因为所提供的所有解决方案仅覆盖2个Universe,如果需要,我可以复制自己。

I have searched for a similar solution in different sources across internet, however i couldn't find anything similar(having 3 universes in same report) as all solutions offered cover only 2 universes, which i could have replicated myself if needed.

这是可以实现的吗?

推荐答案

合并维度是所涉及的数据提供者之间的联接。它在块中是充当外部联接(大致而言)还是内部联接,取决于要组合的对象的类型。

Merging dimensions functions as a "join" between the data providers involved. Whether it acts as an "outer join" (roughly speaking) or an "inner join" within a block depends on the types of objects you are combining.

假设您有两个数据提供程序DP1和DP2。它们可以来自不同的宇宙,也可以来自相同的宇宙。重要的是它们之间可以合并一个共同的维度。

Imagine you have two data providers, DP1 and DP2. They can be from different universes or from the same; what matters is that there is a common dimension which can be merged between them.

DP1选择维度客户编号以及其他对象。 DP2选择维度客户编号,维度客户区域和度量已售数量。维度客户编号是两个数据提供者中的通用维度,将被合并,但是DP2并不包含DP1中存在的所有值(为简化示例,假设DP1确实包含了所有

DP1 selects dimension "Customer Number", along with other objects. DP2 selects dimension "Customer Number", dimension "Customer Region", and measure "Quantity Sold". Dimension "Customer Number" is the common dimension in the two data providers and will be merged, but DP2 does not contain all of the values which are present in DP1 (in the interest of simplifying the example, let's say DP1 does contain all of the values in DP2).

在同一块中包含合并的维度客户编号和售出数量将返回两个数据提供商中的所有客户编号, DP2中缺少值的售出数量的空白值。这等效于外部联接,它是左联接,右联接还是完全外部联接取决于其他选项,在这里对其进行了详细说明:

Including the merged dimension "Customer Number" and "Quantity Sold" in the same block will return all of the customer numbers in both data providers, with blank values for "Quantity Sold" for missing values in DP2. This is the equivalent of an outer join, and whether it is a left, right, or full outer join depends on other options, which are well described here:

包括合并的维度客户编号和客户同一块中的区域将客户编号限制为仅在DP2中找到的客户编号。这等效于内部联接,并且可能存在其他限制,例如不兼容的对象。如果可以适应Universe,则在示例中可能需要一个局部对象。一些更有用的解释在这里:

Including the merged dimension "Customer Number" and "Customer Region" in the same block will restrict customer numbers to only those found in DP2. This is the equivalent of an inner join, and can present other limitations like incompatible objects. You may need a detail object in your example, if you can adapt the universe; some more useful explanations are here:

因此,我认为这个问题与在同一文档中具有三个Universe无关,而是与您从每个对象中选择的对象类型有关。

Therefore I think this problem is not related to having three universes in the same document, but rather the types of objects you are selecting from each.

这篇关于一份报告中的Business Objects WEBI 3 Universe的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-23 04:32