Note 1370848 - New Master Data Deletion - Information

Summary:

Symptom
 
The current Master Data deletion functionality has severe performance problems in your system/scenario. Moreover, there are cases when you run into memory overflow issues when using this feature.

To overcome these issues, a new version of the Master Data Deletion functionality is available.

Please note the support packages of the respective releases needed for using this feature (mentioned in the 'Solution' section of the note).

Other Terms

Master Data Deletion:
RSDMDD
RSMD_UC

Reason and Pre-requisites

A new version of the Master Data Deletion functionality in now available in the support packages mentioned below.

The details about how to activate and use this new version of the functionality are as follows -

• Switching it ON/OFF - The new version of the Master Data deletion can be switched ON/OFF by accessing the menu Settings -> Global Settings in the DataWarehousing Workbench. Under the settings menu, the check box named - 'Pack.Mas.Data.Del' can be used to turn the new Master Data Deletion ON/OFF. The new version is switched ON by the selecting the checkbox.

• Procedure for deleting Master Data

1. You are in the Modeling functional area in Data Warehousing Workbench. In the InfoObject tree, choose Delete Master Data from the context menu for your InfoObject.

2. When you delete master data, you can choose whether entries in the SID table of the characteristic are to be retained or deleted. If you delete the SID table entry for a particular characteristic value, the SID value assigned to the characteristic value is lost. If you reload attributes for this characteristic value later, a new SID value has to be created for the characteristic value. This has a negative effect on the runtime required for loading. In some cases, deleting entries from the SID table can also lead to serious data inconsistencies. This occurs if the list of used SID values geneated from the where-used list is not comprehensive.

• Delete, Retaining SIDs

For the reasons given above, you should choose this option as standard. If for example you want to make sure that individual attributes of the characteristic that are not needed any more are deleted before you load master data attributes or texts, the option of deleting master data but retaining the entries from the SID table is completely adequate.

• Delete with SIDs

Note that it is not usually necessary to delete entries from the SID table. Deleting entries from the SID table does make sense for example if the composition of the characteristic key fundamentally changes and you want to swap a larger record of values with a new  record that contains new key values. 

3. You can choose whether or not the texts will be deleted. 

4. You can select the search mode the program uses to build the where-used list. The search mode has a significant effect on the run , time for the where-used list. You can select from the following search modes.

• O - Only one usage per value:

If the where-used list has found a value, this value is not searched for anymore in the other InfoProviders. This search mode is the default setting. If you just want to delete all , values that are not used anymore ,it can be a good idea not to investigate any further and thus keep the runtime for the where-used list low.

• P - One usage per value per InfoProvider:

Each value is searches in each InfoProvider. Once a hit is found for one InfoProvider, the value is not searched anymore. This search mode is recommended if you are interested in the usage. You can find out which InfoProvider you need to delete from first, before you can delete them all.

• E - One usage is enough:

If a value has been found once, the search will stop. This setting is recommended if you only want to fully delete the attributes and texts.

• A - All usages of all values:

Every values is searched for once in each InfoProvider. Every usage is counted. This is a complete where-used list. This search mode has the longest runtime and is only recommended if you are interested in all usages. 

5. You can decide to have the deletion process run in thebackground. Having chosen this option, you can plan the start the delete job using the standard job planner. 

6. You can simulate the master data deletion. The where-usedlist is then run without master data being deleted. Note however that the list of usages might not be complete, as no locks are set during the simulation. 

7. Choose Start. The programs checks the entries in the masterdata table to see if they are used in other objects. If the master data is used, you can either only delete records that are not used or view the where-used list. 

8. When the deletion process has finished, you receive a message and can view the log (Object - RSDMD; Sub-object : MD_DEL). This shows the where-used list and the list of deleted  records.

• Selective Master Data Deletion

The InfoObject context menu entry in the Datawarehousing Workbench can be used when you want to try and delete all the (un-used) Master Data in any given Characteristic. However, if you would like to delete the Master Data of a Characteristic selectively, you may use one of the following options -

• Master Data Maintenance (Transaction - RSDMD)

Using this Transaction, you can select the data that you would like to delete using the selection screen. After this, you can choose individual records or all records from the list displayed and press the DELETE button followed by the SAVE. The system performs a where-used check on the selected records and deletes those records for which no usages were found.

• Report - RSDMDD_DELETE_BATCH

You can use this report to delete Master Data selectively from any InfoObject by using the FILTER button on the toolbar (otherwise a full deletion is performed). On choosing the FILTER button, you will encounter a pop-up, where selection conditions can be specified on the key fields of the InfoObject or even the attributes. All data satifying this selection criteria is taken up for a where-used check and subsequent deletion. In addition to all the previously known settings with Master Data Deletion, you can also choose to run this report in simulation mode using the parameter, P_SIMUL = 'X'. Further, you can parameterize the program to use the search mode you prefer using the parameter - P_SMODE (using one of the above-mentioned values of the search mode).

Solution

• SAP NetWeaver BI 7.00

Import Support Package 23 for SAP NetWeaver BI 7. 00(SAPKW70023) into your BI system. The Support Package will be available when note 1367799 with the short text "SAPBINews NW BI 7.0 ABAP SP23", describing this Support Package in more detail, is released for customers.

• SAP NetWeaver BI 7.01 (SAP NW BI7.0 EnhP 1)

Import Support Package 06 for SAP NetWeaver BI 7. 01 (SAPKW70106) into your BI system. The Support Package will be available when note 1369212 with the short text "SAPBINews NW7.01 BI ABAP SP06", describing this Support Package in more detail, is released for customers.

• SAP NetWeaver BI 7.02 (SAP NW BI7.0 EnhP 2)

Import Support Package 02 for SAP NetWeaver BI 7. 02 (SAPKW70202) into your BI system. The Support Package will be available when note 1367863 with the short text "SAPBINews NW7.02 BI ABAP SP02", describing this Support Package in more detail, is released for customers.

• SAP NetWeaver BI 7.11

Import Support Package 04 for SAP NetWeaver BI 7. 11 (SAPKW71104) into your BI system. The Support Package will be available when note 1367864 with the short text "SAPBINews NW7.11 BI SP04", describing this Support Package in more detail, is released for customers.
         
This note may already be available before the Support Package is released. However, the short text will still contain the words "preliminary version" in this case.