Attribute Change Run (ACR) SAP BI 7.0

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

Implementation of Attribute

Change Run (ACR) Concept for

Purchase Cube in SAP BI 7.0

Applies to:

SAP BI 7.0 Also works on SAP BW 3.5. For more information, visit the Business Intelligence Homepage.

Summary

This article is about Attribute Change Run (ACR), which adjusts aggregates for any change in characteristics value. It is useful for characteristics which are used in aggregates build over cubes. Attributes, hierarchies and aggregates need ACR, while text loads don‟t require. Attribute change run is specific to aggregates. If any aggregates built on master data info objects it‟s important to perform ACR.

Author: Arun Bala Ganesan

Company: Wipro Technologies Ltd.

Created on: 6 January 2010

Author Bio

The author currently works for Wipro Technologies (Bangalore, India) as an Associate SAP BI Developer. His expertise includes SAP BI 7.0 and ABAP.

http://www.sdn.sap.com/irj/scn/articles-bi-all

Implementation of Attribute Change Run (ACR) Concept for Purchase Cube in SAP BI 7.0


© 2010 SAP AG 2

Table of Contents

Introduction: ........................................................................................................................................................ 3

Scenario .............................................................................................................................................................. 3

Attribute Change Run ......................................................................................................................................... 3

Steps for ACR ................................................................................................................................................. 4

Process Chains ............................................................................................................................................. 33

Implementation Results .................................................................................................................................... 33

Related Contents .............................................................................................................................................. 34

Disclaimer and Liability Notice .......................................................................................................................... 35



© 2010 SAP AG 3

Introduction:

This article addresses the requirement of Attribute Change Run (also known as ACR) Concept for Purchase Cube in SAP BI 7.0. This article describes a scenario of implementing the ACR Concept on SAP Demo: Purchase Cube (0D_PU_C01) which is as follows.

Scenario

In SAP BI 7.0, we often require a sub set of data to be accessed from Info cube. So, in this case we need to create smaller sets of data from the larger info cube. For Example: For a FY2009 with „Material A‟ data is only required from a set of 10 materials

Since the info cube is small, the required disk I/0 volumes during the query execution will be smaller too, and the query users will have an improved query performance.

SAP implements this idea in Business Intelligence & calls the new Info cube an Aggregate. An Info cube can have many aggregates, and all these aggregates are very transparent to users. That is, End users can comfortably create aggregates on Info cubes, and the BI OLAP processor does all the selection of the appropriate aggregate. In case of non-availability of aggregates, OLAP decides need to retrieve data directly from Info cube.

Attribute Change Run

A change run refers to the activating master data changes to attributes and hierarchies, realigning aggregates containing navigational attributes or defined on hierarchy levels

The main problem when the master data is changed (i.e. after data is loaded into the Info cube) is that the change on the attribute is not reflected at the cube side. We need to perform a PSA to DTP. We‟ll try an approach to solve this issue using Aggregate maintenance.

Fig 1.1 describes the changes affected to the availability of master data once a new record has been added.



© 2010 SAP AG 4

Steps for ACR

First of all we need to use the transaction code RSA1, which is the SAP BI Administrative Workbench.

Now, create a test Info Area (say testX), and provide its description also as in Fig 1.2.

Fig 1.2 – Creation of an Info area for demo purposes

After creating the Info Area, create 2 main things,

1. Characteristic Info object catalog

2. Key Figure Info object catalog

Fig 1.3 – Creation of an Info area for demo purposes

Do not forget to activate any info objects. It can lead to varied results, as often the object exists in either A or M state. It‟s necessary for these objects to be first Edited Saved Activated.

Note: Please check status before activating any info object.



© 2010 SAP AG 5

Fig 1.4 – Now, we create a Characteristic Info object with the name “TESTX_C”

Note: Important fact is that, we need to decide the type of objects we create here. It must be either Char / Key Fig.

Fig 1.5 – Right click the corresponding Info provider & create an Info object catalog



© 2010 SAP AG 6

Next, we now create a Key Figure Info object catalog.

Fig 1.6 – Similar to Fig 1.5 we now create a Key figure Info Object Catalog.

We now create info objects inside the Info catalogs.

Note: Remember, Info objects are holders of information/data. These acts similar to buckets of data

Fig 1.7 – Now, right click on the Characteristic Info object Create Info object

This action will trigger the creation of the Info object within the Info provider similar to files in a „folder‟



© 2010 SAP AG 7

Fig 1.8 – Describes how to name the characteristic – Necessary to specify a name & a description

Fig 1.9 – This describes the “Attribute” field of the particular Info object.

Note: Remember, Key Info objects are basically used in reporting as figures / numerical.

Fig 1.10 – Here we‟ll create a Key figure info object, which holds transactional data.



© 2010 SAP AG 8

Attribute change run (ACR), adjusts aggregates for any change in characteristics value. It is useful for

characteristics which are used in aggregates build over cubes.

Fig 1.11 – Here we select the data type for a particular KFs Example: Quantity here is a data type which has a unit of measure, which has been specified as 0UNIT.

Fig 1.12 – The Characteristic IO „Materials‟ defaults: CHAR (5) now click on „Maintain Master data‟



© 2010 SAP AG 9

Note: Quantity here refers to the data type. We fix it with 0UNIT for simplicity of the scenario description.

Fig 1.13 – Further to this step, we will now create some records for the Material master.

Note: Always note to have a Max. No. of hits > # of objects in master data

Fig 1.14 – Record #1 Entry



© 2010 SAP AG 10




Similarly create master data as below, 2 sections of Material groups (0D_MATGRP) are as shown.



© 2010 SAP AG 11

Fig 1.18: Record #5 Data Entry

Fig 1.19: Record #6 Data Entry

Fig 1.20 – This describes the creation of Info Cube for the particular Info provider. Click on the Info provider

TESTX Right Click & choose the option “Create Info Cube”

Attributes, hierarchies and aggregates need ACR, while text loads don‟t require the process.

Note: Now, we need to create an Info cube for the same. So, the best way to resolve this is by using Copy cubes.



© 2010 SAP AG 12

Fig 1.21 – Here, we are copying a standard cube‟s structure (With phyiscal data store) to an sample test cube called “TESTXube” which is nothing but meta data or skeletal model of the cube.

As shown now we create copy cubes for the same.

Fig 1.22 – Selection of IOC.



© 2010 SAP AG 13

Fig 1.23 – Further after this step we need to choose the Dimensions, Navigational Attributes & Keyfigures for the newly created cube. We have to now make sure that the deimensions are perfectly modelled, as the reporting section (Viz. using BEx etc) will encounter lot of planning from modelling side.

Info Cubes

The Infocube database design has a central database table, known as „Fact Table‟ which is surrounded by associated dimension tables.

Info Objects can contain single field definitions such as transaction data or complex Customer Master Data that hold attributes, hierarchy and customer texts that are stored in their own tables.

These dimension tables contain references to pointer tables that point to master data tables which in turn contain Master data objects such as material and destinations stored in BI 7.0 as Info objects.



© 2010 SAP AG 14

Fig 1.24 – Currently checking the Info object Z38_MATID after activation.

Fig 1.25 – Here, once after activation, we create a new “Application component Area” in the Data Sources section. To perform this operation, right click on the top of the DS “Create new Appl. Comp. Area”



© 2010 SAP AG 15

Note: This Data Source is for Transactional Data.

Attribute change run is specific to aggregates. This is the CSV flat file which holds the values. It‟s to be noted there‟s no MATGRP referencing here. If any aggregates built on master data info objects it‟s important to perform ACR. This is really important as the CSV/Excel flat files are the raw input data for these specific aggregates, must hold the referencing very well.

Fig 1.26 – Now that we have created a new Application Component Area, we need to create a Data Source (say „ds_et‟). Just right click on the ACA & perform “Create Data Source”

Fig 1.27 – Now that the Data Soruce needs to be created, we‟ll now specify the Source names & Data type DS

Fig 1.28 – This is a CSV/Excel sheet output for the data which must be loaded into the PSA.



© 2010 SAP AG 16

Fig 1.29 – This details the „Extraction‟ tab of the Data source. Here, its necessary to note that we need to make correct settings for the CSV upload. The Data seperator for the CSV is „,‟ [Comma] and the Escape Sign is „ “ ‟ (double-hypen).

Fig 1.30 – This is the “Proposal” tab. In the previous Fig. 1.29 please note the “Header rows to be ignored” here is set to 1. Once these minor details are cared, which also important ones, the extraction will be pretty smooth.



© 2010 SAP AG 17

We need to perform a transformation. We key in the source & the target names of Data Source.

Fig 1.31 – Press “Copy” to move the field properties from the info objects

Fig 1.32 – After this, press “Activate”

Fig 1.33 – Notice that the CSV file has been properly referenced, and that as we click the “Read Preview data”, a sample data list is generated from flat file.

Fig 1.34 – Now, we now need to create a transformation for this Info provider.



© 2010 SAP AG 18

Possibility: If you are not able to see your characteristic in ACR as either it is not used in any aggregate or there is no master data change recorded for the characteristic.

Solution: Perform a right click on Characteristic name and activate master data and then check.

Fig 1.35 – Here, choose the Source (Data Source) & the target (Info Cube) Info provider

Fig 1.36 – Here, we need to choose the mappings between the source & target groups.

Fig 1.37 – Now, we‟ll start creating a DTP.

Right click Create DTP which intitates the „Data Transfer Process‟ Creation.



© 2010 SAP AG 19

Fig 1.39 – This describes the “Execute” tab. We need to initiate this at the end to mandate flow of data from PSA level to the Info provider(s) level, via the DTP.

Fig 1.38 – Here, we need to specify the source (Info Cube) & target (Data Source) for the transfer.



© 2010 SAP AG 20

Fig 1.40 – Now, at last we need to create an Info package. Just right click on the Data source & choose the option “Create Info Package”

Fig 1.41 – The Info package must be named with its „Description‟ & now, click on Save Activate.

Fig 1.42 – This shows activated IP. Info Package is an important & first thing to be initiated in data flow. We must always trigger IP only after complete model has been complete to avoid complications.



© 2010 SAP AG 21

Fig 1.43 – Now in the IP level, trigger the start of the data load immediately by choosing the respective option & press “Start”

Fig 1.44 – Describes the number of records in the PSA.

PSA is nothing but Persistent Staging Engine. Its similar to the middle level of the data staging process. This must also contain the error dumps (if any has occurred)

Pl. note data for X600 is not loaded. It‟s a reference flag variable.

Fig 1.45 – Here, we can note that we have left it as a flag variable.



© 2010 SAP AG 22

All the characteristics for which there is any master data change appear in the ACR screen.

If you do not have aggregates, just activating the master data is same as attribute change run.

Possibility:

How can we rectify when an attribute change run job fails in a process chain?

Solution:

If attribute change run fails in a process chain, it will most probably due to ALEREMOTE lock. Then you had to wait for some time and repeat the failed process

When it fails, just go to RSA1 Tools Apply Hierarchy/Attribute change.

Now if we click on info objects, it will have a list of info objects which are affected by last master data run and hierarchy list tells us the list of hierarchies which got changed

Now we can select all info objects & hierarchies and click on execute button.

The attribute change is scheduled with the given job name in background. We can monitor this job in background and can have a look at logs.

Fig 1.46 – Note the REQ is Green [Good]



© 2010 SAP AG 23

We now execute the cube for results.

Fig 1.47 – Choose the option “Fld Selection for Output” or press [Ctrl + F1]

Fig 1.48 – Now, we choose the particular options necessary for the review purposes.

Here we have chosen, Material ID & Qty.



© 2010 SAP AG 24

Now, we perform Aggregation; Right click the cube TESTXBE and then select „Maintain Aggregates‟

Now, click „Create by yourself‟ as we know the aggregate we need to create.

Now, on clicking the button, we can create the aggregates.

Fig 1.49 – This is the initial output before performing ACR (Attribute Change Run)

Fig 2.1 – This part will describe creation of the Aggregates.

Right click on Info provider to „Maintain Aggregrates‟



© 2010 SAP AG 25

Fig. 2.2 – Here, enter short description & long description, and then click to continue

Possibility:

Info object not found, what we must do.

Solution:

If we could not find the Info Object, it's because it doesn't have to be activated. Check if any modified data in the master data tables (SE16 on the tables, data with the version A)

Also if we want to do an attribute change run forcefully then we can create a variant and then execute attribute change run

In Attribute Change Run screen Now, Create a Variant Select your Info object and Save Later, Choose your created variant Execute.

This variant will be handy for you whenever you do a load and for some reason the info object is not available in list of ACR.

Fig 2.3 – The tech. name highlighted in yellow describes what the Aggregate is based upon



© 2010 SAP AG 26

Select the Info objects & click drag into the right frame TESTXUBE Below „Materials‟

After this, Save & Activate the Aggregate.

Fig 2.6 – This dialog prompts us to start the background job immediately -or- later. Click on

„Immediate‟ as there‟s no big data loads from the flat files.

Fig 2.4 – Activation proces in progress…

Fig 2.5 – Describes the dialog box to prompt the sub. Aggregates availiable at this Info provider level.

Here, we click „Start‟ to proceed the aggregation.



© 2010 SAP AG 27

Fig 2.7 – Further after this, we need to click on the “Aggregate Data” or alternatively Shift + F9

Fig 2.8 – Select the „Field Selection for Outputs‟ for the TESTXUBE cube

Fig 2.9 – Choose the options like…

“Don‟t use any conversion”, “Use mat. aggregates”, “Use DB Aggregation” etc.



© 2010 SAP AG 28

On executing, we get the following output.

To perform Attribute change run concept, we now practice by initiating a small change Master data.

We change the Material ID (MATID) for the change initiation.

Here, the change we have initiated is like Material ID: X400 object‟s Material Group is changed from Material Group: BREAD Material Group: BISCUIT

Fig 2.10 – We are aware of the fact that, here in the list X600 has no material group data.

Fig 2.11 – Change is now introduced at this stage.

PS. Mtl.group is BREAD

Fig 2.12 – Change reflected on clicking OK

PS. Mtl.group is BISCUIT



© 2010 SAP AG 29

Now, that we initiated the change, we can visibly find the value change for X400.

For further understanding, we are initiating another change for X500‟s data.

Here, the change we have initiated is like Material ID: X500 object‟s Material Group is changed from Material Group: BREAD Material Group: BISCUIT

So, overall we get such an output.

Now, go to the Info provider & apply the Attribute Change, which is the main step.

Fig 2.13 – Now, the output

is displayed using F8

Fig 2.14 – Again a change is introduced for more clarity

Fig 2.15 – Notice all except one displays output as mat.group = BREAD.



© 2010 SAP AG 30

Fig 2.16 – We now goto the cube level to apply the most important change – ACR.

Fig 2.17 – Now, we must select modes of performing ACR here.



© 2010 SAP AG 31

If info object needs attribute change run it will get automatically listed in the attribute change run list.

If it‟s not there in the list, it means your data is already active and doesn't need attribute change run.

Fig 2.18 – Notice that we must click to “Display/Change” the list(s).

Fig 2.19 – Now, choose the Info objects which are intended for the structure change.

Fig 2.20 – Now, Execute for initiating Attr. Change Run.

Fig 2.20 – Sucessful generation of the Job! (Job Name is a long string of numericals)



© 2010 SAP AG 32

There are different strategies to adapt aggregates in an ACR:

1. Rebuild the aggregate

2. Delta Mode

3. Rollup from previously adapted aggregate (Parent Child Aggregates)

Fig 2.21 – Now display data from the cube, by right clicking on the Info provider Display data

Fig 2.22 – Notice the Instant delivery of data from aggregates for any change in characteristics value



© 2010 SAP AG 33

Process Chains

Step by step analysis for the integration of attribute change runs in process chains

1. Start

2. Execute Info package ( Say if you are loading 2 Info Objects just have them all parallel )

3. You might want to load in sequence - Attributes Texts Hierarchies

4. And all connecting Info packages

5. Attribute Change Run ( Add all relevant Info Objects)

Fig 2.23 – This figure is a simple demonstration of further simplicity introduced by process chains for ACR.

The above are the steps which are to be followed for effective data transfer.

Implementation Results

Thus, the Implementation of Attribute Change Run (ACR) Concept for Purchase Cube SAP in BI 7.0 has

been successfully completed.

Start

Attributes: Infopackge1A Attributes: Infopackge2A

Text: Infopackge1B Text: Infopackge2B

ACR

( Add In object 1 & Info object 2 to this variant )

Text: Infopackge1C



© 2010 SAP AG 34

Related Contents

SAP: Adjusting Changes to Hierarchies and Attributes

System Response Upon Changes to Data: SAP Net Weaver BI Accelerator Index

SAP SCN Blogs - ACR Concept

Wipro Knet Websites - Attribute Change Run

For more information, visit the Business Intelligence homepage.

http://help.sap.com/saphelp_nw04/helpdata/en/80/1a67ece07211d2acb80000e829fbfe/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/9a/e1914206d7a970e10000000a155106/frameset.htm

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13726

http://km.wipro.com/sites/WT01CIOFOP/Wipro/DocKNet2009/Dec/Week3/SAP_BI_Attribute_Change_Run_Demo.pdf

https://www.sdn.sap.com/irj/sdn/nw-bi



© 2010 SAP AG 35

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

Date post:	29-Mar-2015
Category:	Documents
Upload:	tammy009
View:	1,579 times
Download:	3 times

Attribute Change Run (ACR) SAP BI 7.0

Documents