Show TOC

Background documentationAnalyzing Audit Packages

 

The analysis of audit packages is a function of the Retention Warehouse, which the system executes while extracting audit packages to SAP NetWeaver BW.

Features

The Retention Warehouse processes the following table types:

  • Master data definition tables and master data text tables

  • Transaction data tables

  • Fixed value tables

  • Relation definitions

Analysis of master data definition tables and master data text tables

The Retention Warehouse analyzes the definition tables together with the corresponding text tables. This information is then used to define “complex InfoObjects”. Complex InfoObjects are InfoObjects that contain attributes, texts and compounds. If a table has multiple key fields, the last key field that is not a date field or language key defines the InfoObject to be generated. The InfoObject contains the name that corresponds to the field from the definition table.

Example Example

The table CSKS contains the data element KOSTL as its last relevant key field.

End of the example.

For the other key fields, insofar as they are not date fields or language keys, the system determines simple or complex InfoObjects and compounds them with the originally created InfoObject. If the table key contains a date field, the system registers a time-dependent InfoObject for it. The system assumes that this is the end date. In this case, the system interprets the first date field outside of the key as the corresponding start date.

For all fields that are not key fields, the system determines simple InfoObjects and adds them as attributes to the InfoObject that was created first. If the InfoObject already exists, it may also be a complex InfoObject.

The length of the InfoObjects (incl. the length of compound InfoObjects) is derived from the definition table. If the length exceeds 60 characters, the system truncates the length of the InfoObject to 60 characters. In that case, the system issues a message.

The text tables contain the texts defined for the assigned objects. If no text table exists for a definition table, the system creates InfoObjects without texts. Otherwise an InfoObject receives the texts defined in the text table. If the key of a text table contains a language key, the system defines the texts of the InfoObject as language-dependent. If the key of a text table also contains a date field, the system defines the texts of the InfoObject as time-dependent. The InfoObject adopts the length of the short, medium and long names of the objects from the table. The system registers all InfoObjects that it has determined from the definition tables as characteristics, even if they are numerical objects.

Analyzing Transaction Data Tables

The Retention Warehouse processes transaction data tables in the following three steps:

  • Determination of simple InfoObjects

    Simple InfoObjects are InfoObjects that have no definition table of their own. They have no texts, attributes or compounds. They draw their contents from transaction data, but do not have master data of their own. When it analyses a table, the system checks whether a data element has already had an InfoObject assigned to it and registers a simple InfoObject as appropriate.

  • Determination of key figures

    The system registers all numeric fields as key figures. If the values have units, the system also registers the standard InfoObjects for units or currencies (0currency, 0unit).

  • Determination of InfoProviders

    When an audit package is extracted, the user decides whether the system should use InfoCubes or DataStore objects for the transaction data. Depending on this setting, the system determines whether the selected InfoProvider can be created. The following restrictions apply:

    • InfoCubes must contain at least one key figure.

    • DataStore objects may not contain more than 16 key fields.

    If the user-defined type of InfoProvider cannot be used for a transaction data table, the system automatically registers the InfoProvider than can be used and issues a corresponding message. If the transaction data table contains more than 16 keys and no key figure, the system cannot create an InfoProvider.

    With transaction data tables, the system distinguishes the following table types:

    • For tables that contain no periodic values, such as table BSEG, the system registers a key figure for each numerical value.

    • For tables that do contain periodic values, such as table GLT0, the system registers only one key figure for the periodic values, but for the InfoProvider it additionally registers the InfoObjects for fiscal year, fiscal year variant and fiscal year period.

Analyzing Fixed Value Tables

The system processes only the domain fixed values for simple InfoObjects. In the case of complex InfoObjects, the system ignores domain fixed values. If domain fixed values are defined for a simple InfoObject, the system adds them. This makes the simple InfoObject into a complex InfoObject.

Analyzing Relation Definitions

The system maps the relations between tables in SAP NetWeaver BW as an InfoSet. The relation definitions also contain the assignments between the fields of the different tables. They are mapped by the system in the registered InfoProviders and the corresponding fields. With this information, the system registers the InfoSet. The relation definitions can also contain constants. These cannot be transferred to the InfoSet by the system, and the system issues a message to that effect.

To set up a single point of access for reporting, the system registers an InfoSet for each registered InfoCube or DataStore object that contains only that InfoCube or that DataStore object.