Attribute view is data model through which you can present the master data attribute, text and hierarchies for consumption by Analytical and Calculation views.

We will be covering creating Attribute Views with the basic options in HANA 1.0 SP05 , the look and feel in other versions might vary slightly, especially in older versions.

Prerequisite:

1.      1. Sufficient Authorizations to create data models (Please contact your administrator if you are facing authorization issue)

2.      2. The Base tables on top of which you are creating the Attribute view should be present in the HANA server (e.g. If you are trying to create attribute view for material master data then MARA table should be present in the system)

3.      3.  Delivery Unit and Packages must already have been created.

Navigation:

You have to be in Modeler Perspective, which can be accessed by the Windows Menu as shown in below screenshot.

/wp-content/uploads/2013/10/1_307012.jpg

The Modeler perspective has multiple views

/wp-content/uploads/2013/10/1_307012.jpg

You can access all views using Menu path Windows -> Show View

Steps to Create Attribute View:

1.       In the navigator view inside the Content folder, right click on the Package inside which you want to create your Attribute view, from the context menu select New -> Attribute View

/wp-content/uploads/2013/10/1_307012.jpg

/wp-content/uploads/2013/10/1_307012.jpg

2.       In the next screen that pops out enter the name and description of your attribute view.

The package name will be prefilled with the name of the Package in which you are creating the attribute view.

In view type, select Attribute view.

The copy from option allows you to copy an existing attribute view (similar to template for info objects in SAP BI). We are going to create a new attribute view so will skip this option.

In the subtype we have the following options:

1.     Standard – We will be using this option for our exercise. There are other types of attribute view that you can create apart from Standard Attribute view, which are discussed below.

2.     Time – HANA provides some standard tables which you can fill with time data for Gregorian calendar or Fiscal calendar. If you want to create time based attribute view on top of these standard tables, you can choose this option. (The tables used for time attribute creation with calendar type Gregorian are, M_TIME_DIMENSION, M_TIME_DIMENSION_ YEAR, M_TIME_DIMENSION_ MONTH, M_TIME_DIMENSION_WEEK and for calendar type Fiscal is M_FISCAL_CALENDAR)

3.     Derived – You can create derived attribute view on top of any existing attribute view. This is used in cases where for business reasons a new description is required for existing attribute views, only description is editable in a derived attribute view, rest all the properties are inherited from the base attribute views  e.g. you can create Sold_to_party derived attribute view on top of customer attribute view (Similar to reference Info Objects in SAP BI)

/wp-content/uploads/2013/10/1_307012.jpg

Click on Finish.

3.       In the subsequent screen from the context menu of the Data Foundation select Add Objects. (Note that there will be four parts of the screen i.e. Scenario, Details, Output and Properties)

/wp-content/uploads/2013/10/1_307012.jpg

A new window titled “FIND” pops up, enter the name of the table on top of which you want to create the attribute view. (e.g. MARA). Select the required table from the search hits and press on OK.

/wp-content/uploads/2013/10/1_307012.jpg

4.       Now the selected table i.e. MARA should be visible in details.

/wp-content/uploads/2013/10/1_307012.jpg

We do not want all the fields in the base table to be present in the attribute view, only a selected subset of the fields are required to be available in the attribute view as per the reporting requirement.

                Right click on the fields that are required for reporting and select add to output.

/wp-content/uploads/2013/10/1_307012.jpg

You can also apply filter so that only a subset of the data is presented through the attribute view. e.g. if the reporting requirement is such that only “Article type” = “WERT” is to be available in the attribute view then we can apply filter on Article type in this step.

/wp-content/uploads/2013/10/1_307012.jpg

Note – You can also Join multiple tables in data foundations as per your reporting requirement. There are multiple types of joins available such as left outer, inner, text and referential.

5.       After all the required Attributes are added to the output then they will be visible in the output under columns folder.

/wp-content/uploads/2013/10/1_307012.jpg

6.       Calculated Columns – You can create calculated attributes using this option. A simple use case will be that there are columns called “CITY” and “PIN_CODE” and you want to create a calculated column “ADDRESS” concatenating the values of “CITY” and “PIN_CODE”. So if “CITY” = ‘DELHI’ and “PIN_CODE” = ‘110001’ than “ADDRESS” =  ‘DELHI110001’.

In the output area, right click on Calculated Columns and from the context menu select NEW

/wp-content/uploads/2013/10/1_307012.jpg

In the Formula editor that pops out, enter a name and description for this new Calculated column, enter the data type details, in the expression editor enter the calculation that is to be done (you can do calculation upon columns as well as other calculated columns, various types of operators and functions are available for calculation). Make sure you do only calculations relevant to an attribute. Press OK once you are done

/wp-content/uploads/2013/10/1_307012.jpg

This new calculated column will be present under the “Calculated Columns” folder in the output.

7.       Click on the Semantics node in Scenario

/wp-content/uploads/2013/10/1_307012.jpg

In the column select the Key Attribute. In our case it will be MATNR. Click on Type in the row corresponding to the required key attribute and select key attribute.

/wp-content/uploads/2013/10/1_307012.jpg

You can also change the Description of any field. Let us say that the description of the MATNR field should be “Article Number” than we can enter the same under the Label Column as shown below.

/wp-content/uploads/2013/10/1_307012.jpg

In the Label Column you can associate any column with the column which provides the text for it. e.g let us say we have a column BUKRS which provide the company code and other column BUTXT which provides the text for these company codes, then in the Label column for BUKRS, from the drop down we can choose BUTXT

Any fields can be hidden by checking the check box in its row under the column “Hidden”.

/wp-content/uploads/2013/10/1_307012.jpg

8.       Select the Default Client. If it is Dynamic then only the data pertaining to the client associated with the USER consuming this View ( while creating a user in HANA a client is associated with it) will be presented by this Attribute view, if it is cross client than all data of all Clients will be presented by the Attribute view.

Press Save and Validate. This triggers a Validation job. Once Validation is finished, press on Save and Activate. This triggers an Activation Job. Once Activation Job is finished this Attribute View is ready for consumption by Analytical and Calculation View.

/wp-content/uploads/2013/10/1_307012.jpg

The Attribute view is now available for consumption by reports, analytic views and calculation view. Happy Reporting!

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply