Navigational and Display Attributes

Display attributes - You can display these attributes of the main info object in the query but cannot drill down beyond these attributes and apply some formula's.

We cannot restrict the display attribute nor can we create variables on them at query level.

Navigational attributes - You can display these attributes in the query as well as apply drill down beyond these attributes and apply formula's and do some calculation.

We can restrict the navigational attribute and also create variables on them at query level.

Lets consider we have objects Material, Material type and sales amount. We have the below data.

Material    Material Type  Sales amount

M1          ABC                   200
M2          ABC                   300
M3          XYZ                   500
M4          XYZ                   400
M5          TYS                   600
M6          XYZ                   100

Navigational Attribute:

Assume that Material type is as navigation attribute to master data Material. If we want to have an analysis about the sales based on Material Type. Since 'Material Type' is navigational attribute we have an independent drill down of 'Material Type' without the support of Material in report .

Material Type   Sales amount

ABC                   500
XYZ                  1000
TYS                   600

Here Material Type  is an attribute of Material, as we made this as navigational attribute, it can be standalone in report without Material.

Display Attribute:

We cannot go for individual drill down to 'Material Type' without Material, i.e. if we want 'Material Type' in our report then we have to drill down Material along with 'Material Type'. Report output will be as below.

Material  Material Type Sales amount

M1            ABC               200
M2            ABC               300
M3            XYZ               500
M4            XYZ               400
M5            TYS               600
M6            XYZ               100

Just observe the report in our first case is having only three records with aggregated value based on 'Material Type' but in the second we have 6 records.

-----------------------------------------------------------------------------------------------------------------------------------------

Event Based Process Chains

There may be a requirement where you may need to schedule a process chain after an event is being triggered.

In this Example I have a process chain A runs weekly, when completed should trigger an event which will result in execution of Process chain B.

Steps to be followed is as follows :

Step 1) Create an Event-->    Go to Transaction code SM62   --> Select  BckProcEvnts tab  --> Create an event.

In the snapshot  above  we can see I have created an Event 'ZTEST'.

Step 2) Create variant for Program ''BTC_EVENT_RAISE"

    Go to se38 --> Enter Program name 'BTC_EVENT_RAISE'---> Select Variant radio Button --> Click Display

Enter a name for Variant and click 'Create'.

 

In the following screen, enter the event name which you have created in SM62 (in Step 1). In my case I had created 'ZTEST' Event.

Click on Attributes , enter description for variant  and click on 'Save'

Step 3) Go to Process Chain A

At the end of your Process chain, insert process type 'ABAP Program'.

In the next Screen insert  the ABAP Program 'BTC_EVENT_RAISE'.

Enter the variant created in Step 2.

Your Process chain A will look like this

Schedule process chain A as per your requirement .Example I scheduled it weekly, (on Sunday, Morning 6 AM)

Step 4  ) Go to your RSPC and open Process chain B

Go to Start Variant --> Change selections --> After Event --> Enter the Event Name created in Step 1.

Check box 'Periodic job'

Now , every Sunday 6 am Process chain A  gets executed. As soon as the ABAP Program is completed  in the last step of Process chain A, event ZTEST is gets triggered and as a result of that Process chain B starts.

So you get the desired result as per event based scenario.

Difference Between SAP BW 3.5 and 7x

The difference can be described as follows :

1) The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only available for infocubes in  SAP BW 7x.

2) The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100.

3) Search functionality has improved. You can search any object you want to, which was not possible in SAP BW 3.5

4) The transformation replaces the transfer and update rules.

5) Introduction of Write-optmized DataStore  Object in which does not have any change log and the requests do need any activation. The goal of such DSO is mainly to request its data with the Bex tools in order to provide queries at the raw data level..

6) One level of Transformation. This replaces the Transfer Rules and Update Rules.

7) Load in the PSA is a must in SAP BW 7x, which was optional in SAP BW 3.5 and data could be directly loaded to data targets.

8) In Infosets now you can include Infocubes as well.

9) Renamed ODS as DataStore Object (DSO).

10) Datawarehousing workbench replaces the administrator workbench.

11) New data flow capabilities such as Data Transfer Process (DTP), Real time data Acquisition