Defining Data Views for Audit Areas
In the ILM Retention Warehouse System of SAP NetWeaver ILM
, you can define views for queries of the data of multiple master data tables. You can use these views when defining audit packages and audit package templates.
It is only possible to link tables to a data view if the key fields of a table can be derived from the key fields of another table. The definition of data views enables you to link tables for which the system cannot define a uniform key. This is the case if multiple master data tables have the same data element as the last key field and the fields before the data element are based on different tables. By building a data view to the affected tables, you can ensure that the system includes all and not just the first of the tables during an analysis.
Procedure
1. Calling a Function
In the ILM Retention Warehouse Cockpit
for administrators, choose 
Services for Settings
Customizing for Retention Warehouse
Audit Area
Define Data Views
.
In the system, you can also use transaction ILMVIEWM
to call the function.
Creating Data Views
Choose
Create
.Enter the name and the description of a data view.
Define the segments, tables, and fields of the data view that you want to include in the audit area.
Use join conditions to link the different tables in the data view.
Choose
Check View
to check the data view.Save by specifying a Customizing request.
NoteIf you define your own data views, you have to enter the keys for them in Customizing. In addition, it is usually necessary to map the text tables for the given master data tables using the data views. To make the required adjustments, in
ILM Retention Warehouse Cockpit
for administrators, choose Services for Settings
Customizing for Retention Warehouse
Configure Creation of Audit Package in BW
Table Adjustments
.End of the note.
Editing Data Views
Select the data view and choose
Continue
.Enter the name and the description of a data view.
Make your changes.
Choose
Check View
to check the data view.Save by specifying a Customizing request.
Deleting Data Views
Make sure that the data view is not included in audit packages or audit package templates.
Choose the
Display
icon.Confirm the prompt.
Confirm the deletion by specifying a Customizing request.
Example
Using view building, you can link master data tables with one another, if the key fields of one table can be derived from the key fields of the others. The G/L account is an example for this.
Table SKA1
describes the G/L account dependent on the chart of accounts
; table SKB1
describes the G/L account dependent on the company code
. Starting from table SKB1
a view is created, in which, using the company code and with table T001
, the chart of accounts can be determined, and thereby the related entry in table SKA1
can be found. Depending on the company code, the resulting view can therefore contain all of the data from table SKB1
and the data of the G/L account from table SKA1
. The key is now made up of the company code and the G/L account; the chart of accounts is no longer contained in the partial key. The view is adopted in the audit area, as well as the original tables. Although they are no longer needed, they have to be in the set of the archive files to be processed. The audit package template, however, contains only the data view, and only the data view is considered in the analysis.