Master Data Attribute of

[Former Member]

Hi,

What is the parameter to use this option-<b>Master Data Attribute of</b>

When do we go about deciding to populate the data with this option at the Update rules.

And also when do we use the option --<b>Initial value</b>at update rules.

can u explain me with real time project perspective..

Message was edited by:

Indira SR

[Former Member]

HI iNDRA

Lets take an example, 0Material. In this case, you have amny attributes like division, brand, product , and some dates like Material creation date etc.

When youa re loading data, you may not have these fields in the source. In that case, you need not load again from another source. If 0Material is part of the source data, you can just go to update rule and assign "master data attribute". You can load all.

Hope ur clear now

Thanks=POINTS in SDN

SANJEEV KUMAR HAMSALA

[Former Member]

It is uset to populate a cube characteristic with an attribut of another char.

Example:

in cube you have 0costecenter and 0respperson (attribute of costenter).

To fill 0respperson you use this function.

Hope it's clear.

Regards

[Former Member]

This is directly from the help from the update rules window in BW:

<b>Method for Characteristic Derivation</b>

You use the calculation method to control if and how a key field is updated in the data target.

<b>Source field:</b> The key field is filled directly from the selected field in the InfoSource.

<b>Constant:</b> The key field is not filled by the InfoSource. Instead it is filled directly by the specified value.

<b>Formula:</b> The key field is filled by a formula.

<b>Master data attribute for:</b> The key field is filled by reading the master data from another field in the InfoSource. If the attribute is time-dependent, you must also determine when you want the read to take place; the current date (sy-date), at the start or end of a period ( determined by a time-characteristic in the InfoSource) or on a constant date that you specify directly. The sy-date is used by default.

<b>Routine:</b> The key field is filled by an ABAP routine written by you.

<b>Blank:</b> The key field is not filled. It remains empty.

<b>Blank</b> (or initial value) means that the field is not filled.

As Paolo said before, <b>Master Data Attribute for</b> will pull in the value of the attribute from the master data of another attribute (as long as that attribute is available in the datasource). One note, however, this is different than it being a Navigational Attribute. The value of this attribute will belong to the transaction (ie. it will never change).

Eg. If you are collecting a sales transaction and you want to post it with the salesperson number that belongs to the customer number.

Let's assume you have ZSLSPERSON as an attribute of 0CUSTOMER. If you have ZSLSPERSON as an attribute of the cube, you can fill this value in the update rules using Master data attribute of 0CUSTOMER. However, if later, the value ZSLSPERSON changes for the customer, the value of ZSLSPERSON in the cube will not change.

<u>Date</u>......<u>0CUSTOMER</u>.....<u>ZSLSPERSON</u>.....<u>ZSLSPERSON(Attr of 0CUSTOMER)</u>

12/1.......100010...............100.....................100

12/15.....100010...............100.....................200

Hope this helps.

[Former Member]

Just as an addition...you need to have the main infoobject in the communication structure for you to be able to load its attribute using this option. For example, Territory ID (0CRM_TRID) is an attribute of Territory (0CRM_TR). My transaction data extractor does not provide me the values for Territory ID but it gives me the values of Territory. Since I need the Territory ID values in the cube, I would use the option of loading Territory ID using the Territory (0CRM_TR) values which are coming along thru my extractor. During loading, for each Territory, the process will lookup on the master data and fills the values of Territory ID accordingly into my cube. Hope this helps.