Error while Activating the cube after changing the structure of the cube which has a DAP established (NLS).

[Former Member]

Applies to:

SAP BW NW 7.0. For more information, visit the Business Intelligence homepage.

Summary

Error (RSDA156 ) while Activating the cube after removing a field from infoprovider  which has a DAP established (NLS).

This guide gives a step-by-step detail of when this error occurs and how to resolve it.

Author: Megha Katore , Ashwini A Gosavi

Created on: 11^th Dec, 2013

Introduction:

In cases where there is a large amount of data in SAP BI, we cannot hold all the data in the BW system has it would occupy unnecessary space, as this data can be archieved in some other place and can be accessed by the BW system as and when required. The process to do the same is Data Archival Process, which enables us to archive data on remote or logical file.

Error:

We had an infocube which had 10 fields we had to remove 2 fields from the cube. The cube had a NLS based DAP established. After removing the field and activating the infocube we were facing an error stating “Infoobject ABC cannot be removed from infoprovider ZXYZ .This is because it has been used as a selection characteristic or semantic group characteristics in dap or in near line storage for the infoprovider”.

Solution:

While analyzing the same scenario we came across a few findings and the way this error can be resolved.

Consider the following scenarios and the steps followed to resolve the errors:

Scenario 1: (ADK Based DAP)

  We have an Infocube ZCUBE_TST, having 5 objects (ZT1, ZT2, ZT3, ZT4 and ZT5).

And it has an ADK base DAP established. All the fields present  in the Infocube ZCUBE_TST are reflected in the DAP :

The below screenshot shows the selection profile which has all the characteristics objects available for partioning .

The below screenshot shows the Semantic group which has all the characteristics and Key figure objects available for Sorting .

Now, we have to remove the field ZT2 from the infocube.(The below screenshot shows the Infocube after removing the field from the infocube.)

After removing the field and while activating the Infocube you will get a pop-up as shown below:

In this scenario when it is an ADK based DAP we do not face any error while activating the Infocube after removing the field from the Infocube as it automatically updates the DAP after activation of DAP and all the underline objects that are inactive like transformation and DTP.

The below screenshot shows the DAP after activation and the updated structure of the same. Now you can see that the field ZT2 is now being removed from the Infocube as well as the DAP.

Scenario 2: (NLS Based  DAP)

In this scenario we are using the same Infocube ZCUBE_TST, but we will make use of a NLS based DAP.

In the below screenshot you can see a NLS based DAP. All the fields present  in the Infocube ZCUBE_TST are reflected in the DAP :

The below screenshot shows the selection profile which has all the characteristics objects available for partioning .

The below screenshot shows the Semantic group which has all the characteristics and Key figure objects available for Sorting .

Now, we have to remove the field ZT2 from the infocube.(The below screenshot shows the Infocube after removing the field from the infocube.)

After removing the field and while activating the Infocube you will get a pop-up as shown below:

Earlier for an ADK based DAP , while activating the Infocube we did not receive any error while activalting the cube. But for an NLS based DAP , while activating the cube after removing the field we recived the following error as shown below:

So you can see we are unable to activate the Infocube after removing the field from the Infocbe which has a NLS based DAP.

As earlier in the ADK based DAP we were able to see that when we remove the field from the cube the same gets automatically updated in the DAP after activation. As we are unable to activate the Infocube the changes are not reflected in the DAP as shown below.

(Note: The field ZT2 is still present in the DAP)

As the fields are present in selection profile and semantic group the structure is different, due to change in the structure it is showing and ambiguity as the structure of Infocube and DAP are different it is now allowing us to activate the cube. So we thought of manually removing the fields from selection profile and semantic group. But as you can see these fields are in disabled mode even if you switch to change mode.You can only make changes in the settings of the DAP and not the structure. The Structure gets updated automatically.

Now, the solution that we implemented to resolve the issue is as follows:

Step 1: Delete the DAP .(Right Click the Infocube à  goto Data Archival Process à goto delete ).

Step 2: After deleting the DAP. Now again try to activate the cube. You will again see the standard pop-up that appears after you remove any fields from the cube as shown below.

Now, you can see the field ZT2 has been removed from the Infocube and the Infocube is now in active state.

Step 3:  Now activate the underline transformation for the same.

Step 4: Now re-create the DAP , once the Infocube is active(Right Click and goto Create Data Archival Process).

Now you can see the DAP will contains the same structure as the Infocube as shown below.

Note: This error occurs only when you remove any field from the Infocube after creation of DAP. While adding a new field to the Infocube the structure gets reflected automatically in the DAP.

Caution: When you delete the DAP, the archived data also gets deleted. So to avoid losing the data,we should reload all the archived data back into the info-provider before the DAP deletion process is started.