Types of Attributes

Attributes are InfoObjects that exist already, and that are assigned logically to the new characteristic

Navigational Attributes

A Navigational Attibute is any attribute of a Characteristic which is treated in very similar way as we treat as Characteristic while Query Designer. Means one can perform drilldowns, filters etc on the same while Query designing.

Imp Note:

• While Creating the Info Object -- Attributes Tab Page -- Nav Attri butes to be switched on .
• While Designign the Cube we need to Check mark for the Nav. Attributes to make use of them.

Features / Advantages

• Nav. Attr. acts like a Char while Reporting. All navigation functions in the OLAP processor are also possible
• Filters, Drilldowns, Variables are possible while Reporting.
• It always hold the Present Truth Data .
• Historic Data is not possible through Nav. Attributes.
• As the data is fetching from Master Data Tables and Not from Info Cube.

Disadvantages:

• Leads to less Query Performance.
• In the enhanced star schema of an InfoCube, navigation attributes lie one join further out than characteristics. This means that a query with a navigation attribute has to run an additional join
• If a navigation attribute is used in an aggregate, the aggregate has to be adjusted using a change run as soon as new values are loaded for the navigation attribute. http://help.sap.com/saphelp_nw04s/helpdata/EN/80/1a63e7e07211d2acb80000e829fbfe/frameset.htm

Transitive Attributes

A Navigational attribute of a Navigational Attributes is called Transitive Attribute. Tricky right Let me explain

• If a Nav Attr Has the further more Nav. Attributes ( as its Attributes ) in it those are called Transitive Attributes .
• For Example Consider there exists a characteristic ‘Material’ .It has ‘Plant’ as its navigational attribute. ‘Plant’ further has a navigational attribute ‘Material group’. Thus ‘Material group’ is the transitive attribute. A drilldown is needed on both ‘Plant’ and ‘Material group’.
• And again we need to have both Material & Plant in your Info Cube to Drill down. (To fetch the data through Nav. Attrs. we need Master Data tables hence, we need to check mark/select both of them in the Cube ) http://help.sap.com/saphelp_nw04s/helpdata/EN/6f/c7553bb1c0b562e10000000a11402f/frameset.htm

  If Cube contains both ‘Material’ and ‘Plant’

Dimension table having both ‘Material’ and ‘Plant’ will have Dim ID, Sid of Material, and Sid of Plant. Since both the Sids exists reference of each navigational attribute is made correctly.

• If Cube contains only 'Material’

Dimension table having only ‘Material’ will have Dim ID, Sid of Material. Since Sid for first level navigational attribute (Plant) does not exists, reference to navigational attribute is not made correctly.

Exclusive Attributes / Attributes Only/ Display Attribute

If you set the Attribute Only Indicator(General Tab page for Chars / Addl Properties tabpage for Key Figs) for Characteristic while creating, it can only be used as Display Attribute for another Characteristic and not as a Nav. Attr.

Features:

• And it cannot be included in Info Cubes
• It can be used in DSO, Infoset and Char as InfoProviders. In this Info Provider , the char is not visible during read access (at run time)
• This means, it is not available in the query. If the Info Provider is being used as source of Transformation or DTP the characteristic is not visible.
• It is just for Display at Query and cannot be used for Drill downs while reporting.

Exclusive attributes:

If you choose exclusively attribute, then the created key figure can only be used as an attribute for another characteristic, but cannot be used as a dedicated key figure in the InfoCube.

• While Creating A Key Figure -- The Tabpage:Additional Properties -- Check Box for Attributies Only

http://help.sap.com/saphelp_nw04s/helpdata/en/a0/eddc370be9d977e10000009b38f8cf/frameset.htm

SAP BW Notes - Part 1

1.       Infoobject Maintenance

·         ‘Attribute only’ flag in RSD1

If you mark the characteristic as an exclusive attribute, it can only be used as a display attribute for another characteristic, but not as a navigational attribute. In addition, the characteristic cannot be transferred into InfoCubes. But it can have master data.

·         Global Transfer routine

If this indicator is set, a transfer routine is defined for the InfoObject. This routine is integrated into all transfer rules where the InfoObject is contained in the communication structure. With data transfers, the logic contained in the individual transfer rules (from transfer structure to communication structure) runs first. The transfer routine is then carried out on the value of the corresponding field in the communication structure for every InfoObject that has a transfer routine and is contained in the communication structure.

In the transfer routine, you can define DataSource-independent code that you only have to maintain once, but is valid for all transfer rules.

·         Filter selection values

Selection of Filter Values for Query Definition

This field describes how the selection of filter values and the restriction of characteristics functions when you define queries.

The values from the master data table are normally displayed when you restrict characteristics. For characteristics without a master data table, the values from the SID table are displayed instead. In a number of cases, however, it could be better to display only the values that are in the InfoProvider. The setting "InfoProvider Values Only" is permitted for this reason.

Selection of Filter Values for Query Execution

This field describes how the selection of filter values functions when a query is executed.

Normally the values from the data selected by the query are defined when you select filter values as you execute the query. Only the values for which data was selected for the current navigation status are displayed.

In a number of cases it can make sense to permit additional values as well. The settings "InfoProvider Values Only" and "Master Data Table Values" are allowed for this reason. If you make this selection, the message "No Data Found" may appear after selecting filter values.

·         Master Data Tables Created in the DDIC

As seen above the following tables are created

P Table – This table is created for the time independent attributes. The important fields of this table are as shown below

The key is comprised of the characteristic value, compounding characteristics (if any), OBJVERS (which can be A – active or M- modified), CHANGED (which can be D – deleted or I – to be inserted)

Q Table – For time independent attributes. Similar to the P table, but with an addition of Date To in the key.

X Table – This table is for the time independent navigational attributes. The important fields are as shown below

The key is comprised of the SID of the characteristic value, Compounding characteristics (if any) and then the SIDs of the navigational attributes.

Y Table – This is for the time dependent navigational attributes. The structure is similar to the X table above, with the addition of the Date to field in the key.

·         Hierarchy Tables

H Table

This table contains the structure of the hierarchy. The fields of the table are as shown

K Table - SID table for hierarchies

Hierarchy nodes (like characteristic values) are not stored with actual values, but with master data IDs (SIDs) in aggregates. The conversion of hierarchy nodes into SIDs is stored in this table. Contrary to characteristic values, hierarchy nodes get negative SIDs.

I Table - SID Structure of the hierarchy

With the aid of SIDs from characteristic values and hierarchy nodes, the hierarchy structure is stored in this table. In principle, this table saved the same information as the hierarchy table.

Since only SIDs and no characteristic values, or hierarchy nodes can be stored in aggregates and InfoCubes, the analysis of the data using this table is more effective and is quicker.

J Table - Hierarchy interval table (of a characteristic)

In this table information is stored on hierarchy nodes that are intervals.