Different ways to run Attribute Change Run(ACR) in SAP BI

Sometimes due to some issue or user requirement we will do master data loading apart from daily loading. After master data loading is done, the first doubt we get is do I need to run ACR or Activating master data is enough.

What is ACR? : We need to run ACR when you have aggregates which are using your characteristics. ACR will update newly added/changed master data to aggregates and activates the master data in characteristic.

What is Activate master data? : Activate master data activates the newly or changed master data(which is in M version), but it will not update the same to aggregates.

So ACR is required if you have aggregates which are suing these characteristics.

Generally in Projects this ACR will be done as part of Process chain after master data loading is done.

How can we run ACR for one characteristic or multiple individually. This can be done in 2 ways.

First:

1) Goto RSA1

2) In menu bar, click on Tools --> Apply Hierarchy/Attribute Change.

3) In the next screen, click on "Info Objects" list. You will get the list of characteristics for which ACR is required. By default all the characteristics will be selected, unselect the characteristics for which you don't want to run ACR.

Note: If you don't get your info object here, then ACR is not required for this characteristic.

4) Now click on execute, you can monitor the job in SM37.

Second:

1) Go to SE38, give the program RSDDS_AGGREGATES_MAINTAIN and click on execute.

2) In the next screen enter the characteristics for which you want to run ACR and execute.This will be done as fore ground.

Note: If you want to run this as back ground job, then in menu bar --> program --> execute in back ground.

Hope it helps...

How to do Repeat Delta in SAP BI

We have table ROOSPRMSC which stores the successful last delta request time stamp for each data source(if it is delta enabled).

When ever the delta IP got successful, the time stamp will get update in the table (it doesn't bother about whether request is there in target or not). If the over all status of IP comes to green, then time stamp will get updated to system table.

So when ever you have any failed delta request or if you want to load the previous delta request again, follow the below steps.

1) Open the failed request or request you want to run again by going into manage tab of target and click on monitor of request, then change the over all status to red.(you can do the same like, open the delta IP in RSA1 --> on top click on monitor --> in left side you will get all requests)

here system will prompt you message saying that" you have to perform repeat delta".click on "Repeat Delta"

2) Now goto target and make the request red and delete it.

Now run your delta IP, it will pick earlier and present delta records.

Note: If you are already deleted the request from target, then open the request in RSRQ and make the request to Red. This is enough to get the last delta records.

Hope it helps...

Use of Aggregates,Compression, Roll Up and Partitioning in SAP BI

Aggregates:

Aggregates are used to improve query performance. Say you have cube with 30 characteristics and everytime you run query on this cube, it is hitting 10 characteristics frequenty.

So to improve the query performace create Aggregate on those characteristics. Instead of seraching for data in Cube, query will hit the Aggregate first.

Compression:

As we all know, we have two tables in info cube for transaction data(F-table and E-Table). F-table will store facts data and E-table will store compressed data. COmpression also used to improve the query performance and loading performance.

Query Performance:

Compression is nothing but removing request number an aggregating key figure values based characteristics data. We can get same sales documnet in different request(lets assume we got same sales document 5 times into cube in different request). When we compress it will become one record based on sales document number, so when we execute query system has to pick only one record instead of 5 records. this will improves query performance.

Loading Performance:

It is recommended to delete and re-create the index when we load the data into cube. Deleting index will delete the index for data in Ftable and re-creates. If you have huge uncomressed data in cube(F-table is high), delete and create index steps will take log time to complete.

Roll Up:

This is nothing but updating the lastest transaction data to aggregates which is loaded to Info Cube (if you have any aggregates on cube).

Partitioning:

This is also used to improve the query performance and we can do partitioning in two ways

i) Logical partitioning

ii) Physical partitioning(database level partitioning)

refer below links for clear information about partitioning.

http://forums.sdn.sap.com/thread.jspa?threadID=154800

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/607a8ad7-3a2d-2e10-9697-907f7277c483?QuickLink=index&overridelayout=true

Hope it helps...

How to de-schedule or reschedule jobs/process chains in SAP in single shot using programs

When we are working in Support projects we often face upgrades or system outages. When there is an outage/upgrade we need to de-schedule all the loads in BW system and reschedule them once system comes from outage/maintenance.

Then the first thing which comes in our mind is how can i stop all the chains running in my system in one shot. If we have huge number of process chains, it is going to be hassle process to perform.

The below blog will give you how we can do this using programs.

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

Hope it helps...

Setup Tables filling without Locking Users in SAP BI

While filling setup tables, the first step we think about is locking the users.Why we think about locking users is we might miss the records posted by the users when we are filling setup tables. The next doubt we get is " Can't we fill without locking users..?".
Yes, we can fill the setup tables without locking users if data source supports that feature.

We can fill the setup tables and load the data to BI in 2 ways.

1) Init with data transfer option:

In this method we need to do the below steps.
i) Lock the users in R3 system
ii) Delete the data in setup tables for specific application component
iii) Fill the setup tables.
iv) Run the Info Package with option "Init with data transfer"
v) Unlock the users in R3 system.

This is very time consuming process, because we need to lock the users until the data reaches to BI system.This affects client business.

2) Init without data transfer and full repair:

In this method we need to do the below steps.

i) Lock the users in R3 system
ii) Delete the data in setup tables for specific application component
iii) Fill the setup tables.
iv) Run the Info package with option "init without data transfer".This sets the delta queue and timestamp for delta in R3 system.
v) Unlock the users in R3 system
vi) Load the data to BI system using Full repair Info Package.

In this method, after data is loaded to setup tables we can unlock the users in R3 system. This is better than the first option.

We have one more option in Info Package called "Early Delta Initialization"

Early Delta Initialization:

In this one we do the initialization before filling setup tables. So that users can post the records when we are performing setup tables filling. we will get the posted records in next delta run.

In this method we need to do the below steps.

i) Run the Info Package with option " early delta initialization". This will enable the delta queue and setup the timestamp for delta in system
ii) Delete the data in setup tables for specific application component
iii) Fill the setup tables.
iv) Load the setup tables data to BI using full repair IP.

How to check whether Data source supports for Early Delta Initialization?

We can check this in table ROOSOURCE.
i) Go to SE16 --> table name and enter
ii) In the next screen give the data source name and execute.
iii) If field ZDD_ABLE in the result has value X, then data supports for early delta initialization.
iv) If it has space, then it doesn't support.

Hope it will be useful.

Refer the below links for more details.

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

http://forums.sdn.sap.com/thread.jspa?threadID=2120981

You can also go through BW 350 -- Data Acquisition book.

DSO Activation Errors in SAP BI

Most of the cases we will face below errors in DSO Activation.

1) Activation of M records from Data Store object terminated.
    i) SQL Error while reading table in database.

    ii) No batch process available. Process terminated

2) Request not exist in DSO and DSO is inconsistent. You will get request number.

Now we will see the solutions for the above issue.

1) i) : a) Right click on your DSO in RSA1 and click on manage.Please check if you have any red request in request tab of DSO.

In request tab below, you will find option "Request Display: Date of Update From" change this date to one or two months back and click on refresh. you will get the old request now, now check if you have any red request.

b) If you find any red request, click on monitor tab and make the technical status to red. Now come back and make the request status red in request tab of DSO.Delete the request from request tab.

c) Activate the DSO now, it will get successful.

1) ii) : You will get this error, if you don't have enough background processes in your server.

a) check number of background processes maintained by going into tcode RSODSO_SETTINGS.

Please follow the below steps to rectify this error.

a) go to manage tab of DSO. now go to request tab and select the request and click on activate.

b) In the next screen select the request you want to activate.

c) Now click on parallel activation

  

d) In the next screen, you will get the no of parallel processes maintained for DSO activation. Make this to 1 and save it.(By default we will have 3)

 

e) Now click on activate, this time your DSO will get activate successfully.

for more details you can refer below thread as well.

http://forums.sdn.sap.com/thread.jspa?threadID=1285217

2) : You will get this error if someone is wrongly deleted the request from manage of DSO. wrongly means properly making the request red and deleting from manage tab. If request is deleted from manage tab but still present in back end tables then you will get this error.

The request loaded to the DSO will be stored in the following back end tables.

RSICCONT, RSMONICDP, RSODSACTUPDTYPE and RSODSACTREQ.

If we have any discrepancy between these four tables, we will get the above error.

Apart from this error we will get the request number in error log. We need to delete that request number from these four tables if it exist.

please check the note 868391 for details.

Hope this will be useful...

Process Chain errors in SAP BI

The below blog covers the following process chain errors which we get when we are working in support project.

1) Job BI_PROCESS_LOADING could not be scheduled. Termination with return code 8
2) Process Chain stops at intermediate point and does not execute further
3) You ran a process chain mostly it is in green, one is in yellow error
4) Object .................... of type ‘Info package' is not available in version ‘D'
5) Activation of DSO through Process Chain gets failed

check the below blog for details.

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

Program to convert full load to repair full request

As we all know If we want to load any selective to the target which is already loading using daily delta, Then we need to go for repair full request loading.

Lets's assume you forgot to check the repair full flag and loaded the data successfully to the target. Now definitely your next day delta will fail with the message " selection dosn't meet with intialization". This is caused because we should not run full load when the target has successful intialization.

In such senarios the below program is useful to change the already loaded request from full to repair full request.

1) Execute the program RSSM_SET_REPAIR_FULL_FLAG using SE38

2) give the Info cube name, data source name and soure system

3) Execute it

 

Triggering the Failed Process Chain Step's Status Manually to Green

In many situations while monitoring Process Chains, we find that the status of the chain is red indicating errors while data loading. We check and find that in the Process Chain, one of the steps has failed and the status is appearing in red colour. But in actual everything has loaded, in order, still the chain is not moving forward because of the error.


The blow document shows the process to make the failed step in process chain to green and proceed the chain further.


Procedure to make failed PC to green.

Data load failure due to invalid Characters in SAP BW

One of the most common reasons for data load failure in SAP BW is invalid characters present in the data records. The system doesn't permit certain characters to be loaded into BW.


The below blog will explain you how to solve this issue.


Invalid characteristics error

How to delete master data

Follow the below steps to delete the master data.


1) RSA1 --> find your Info object --> right click --> maintain master data

2) Select rows you want to delete and click 'Delete' icon. Then SAVE.

3) If system prompt you message "some master data cannot be deleted" ... continue with this message.

4) Then goto tcode SLG1 --> enter Object: RSDMD and Subobject: MD_DEL and User: your userID and press F8.

5) In the next screen Expand node and double click 'Problem class additional information'

6) This will give you which ever objects using SIDs of this master data.

7) You should delete this SID according to that list.

8) Then U should delete particular data from DSO/Cubes.

Once data deleted from cube, then 

9) Use Tcode RSRV -> Tests in Transaction RSRV -> All Elementary Tests -> Transaction Data -> Entries Not Used in the dimension of an InfoCube (Double Click)

10) From the right side window, expand “Entries Not Used in the Dimension of an InfoCube” Node & Enter InfoCube (like 0SD_C01), click “Transfer”

11) Now, click “Execute” (Toolbar)… and the results displayed in the right side window..

12) Now, click “Correct error” (Toolbar)


That's it... :)

Manually Restoring Lost Delta Data from ECC

This article will give the information about how to restore the lost delta loads from ECC to BI system. in this article we will get two scenarios.
Manually Restoring Lost Delta Data from ECC

Common production support issues

The below are the most common issues you face if you are working in SAP BI support project

1) Transactional RFC Error(trfc) – Non Updated IDOCs in the Source System

2) Time Stamp Error.

3) Error occurred due to Short Dump.

4) Job Cancellations in R/3 Source System.

5) Incorrect data in

6) ODS Activation

7) Caller 70 is

8) Attribute Change Run Failed – ALEREMOTE was locked

9) SAP R/3 Extraction Job Failed.

10) File not found (System Command for file check failed)

11) Table space issue

12) How is it possible to restart a process chain at a failed step/request?

Check the below document which explains every error and how to solve it.

Common Production Failures Encountered at BW Production Support

No SID value found for OUNIT

Generally we will get this type of errors when we are loading transaction data.If we get this error for characteristics, then we can load the master for that object and repeat the load then it will get successful.


But if we get this error for unit or currency info objects, then follow the below procedures.


1) goto RSA1 ---> right click on source system from which you are loading transaction data.
2) select transfer global settings.
3) in the next screen, select currencies and unit of measures.
4) now execute this.


after the above is done, you can repeat your load.


check the below document for detail steps.
How to Update the Currencies and Unit of Measurements from ECC Source System to BI System by Automatically and Manually