BW:Read Master Data:如何规避Slowly Changing Dimension

正在装虚拟机,准备搞个Solution ManagerBW升升级,先尝试下。

   

凑这个功夫写点儿东西。

   

前段时间关注过TRtransfer rule)里面的read master data。

   

BW:Read Master Data:如何规避Slowly Changing Dimension

   

   

我们把一般的Rule Type 改成Read Master Data,会弹出个错误。

   

InfoObjects must be assigned to the DataSource fields

Message no. RSTRAN120

Diagnosis

Some source fields do not have an InfoObject assigned to them. However, you are using a rule type for which InfoObjects are mandatory sources, or you are using a unit conversion type or currency translation type.

Procedure

In the Source Fields area, fill the InfoObject Assignment field for each field that is being used as a source for this rule.

   

也就是说必须配合Data Source使用。

   

BW:Read Master Data:如何规避Slowly Changing Dimension

   

找一个带DataSource的,试试。

BW:Read Master Data:如何规避Slowly Changing Dimension

   

BW:Read Master Data:如何规避Slowly Changing Dimension

   

这是为啥呢,先说说这个Read Master Data啥意思吧

   

Read Master Data: The InfoObject is updated by reading a master data table of a characteristic, where the source contains a key and a value, and the corresponding InfoObject as an attribute.

   

来测试一下,先把0SOLD_TO0INDUSTRY放进维度里。激活

BW:Read Master Data:如何规避Slowly Changing Dimension

   

BW:Read Master Data:如何规避Slowly Changing Dimension

   

这下清楚了,这个0INDUSTRY属性,可以走导航,在取数据的时候通过主数据的S表,读取P表中的数据。也可以在上载的时候,就去读P表,至于读谁的P表呢,就需要选一下了,我这里选0SOLD_TO,检查一下,SOLD_TO就被自动带过来,放在Field下面。之后呢,0INDUSTRY属性就被写死在这条数据里,即使以后发生变化,这里也不会随之变动了。

   

总结:

   

一般来说,我们如果把IO的属性放在维度里,就会变成Slowly Changing Dimension,就是说这个属性会随时变化,也就是今天是今天。

如果要存留今天是昨天的数据,就需要使用Read Master Data。不得不感慨,想得真周到啊

之前我还以为这种情况要去增强呢~~~不过为啥不直接用导航呢,maybe..maybe...

你可能感兴趣的:(master)