Audit

You can use this data audit to monitor changes to an InfoProvider's transaction data, for example when changes were made via input-ready queries, planning functions or Warehouse Management, and who made these changes. You can use the audit information to design queries that depict the change history in the form of delta values and thus also as absolute values.

Supported InfoProviders

You can use the data audit for the following InfoProviders:

  • DataStore object (advanced) with the modeling property All Characteristics are Key, Reporting on Union of Inbound and Active Table: In this type of InfoProvider, the data audit is a fixed component and is always active.

  • Real-time InfoCube (if SAP HANA-optimized): A BW dimension with audit characteristics is added to this InfoCube, which is activated for data audit.
  • Local provider in BW workspace (activated for planning): Audit characteristics are also added to this local provider.

Using Audit Characteristics in Providers

DataStore object (advanced) with the modeling property All Characteristics are Key, Reporting on Union of Inbound and Active Table

The prerequisite for this is that the Show Audit Characteristics in Query property is set in a CompositeProvider containing the DataStore object (advanced).

As the audit infrastructure is a fixed component in the DataStore object (advanced), no audit dimensions like in a real-time InfoCube have to be created. The audit information is updated via the request and can be included in queries via the navigation attributes.

The following InfoObjects are used:

  • Time stamp: 0REQTSN, has the same role as 0ATIMSTMP in the InfoCube

  • User: Navigation attribute 0REQTSN__0AUSER, has the same role as 0AUSER in the InfoCube

  • Data source: Navigation attribute 0REQTSN__ 0ASOURCE, has the same role as 0ASOURCE in the InfoCube

Real-Time InfoCubes

Mode Audit Characteristics
Planning mode Data audit active:
  • 0ATIMESTAMP = time stamp of the save event
  • 0AUSER = SY-UNAME
  • 0AMODE = PLAN
  • 0ASOURCE = name of query or planning function (if unique)
Data audit inactive:
  • 0ATIMESTAMP = UTC time stamp of the save event
  • 0AUSER is empty
  • 0AMODE = OFF
  • 0ASOURCE is empty
Loading mode Data audit active:
  • 0ATIMESTAMP = time stamp of the save event
  • 0AUSER = SY-UNAME
  • 0AMODE = WHM
  • 0ASOURCE empty
Data audit inactive:
  • 0ATIMESTAMP = fixed time stamp (time when mode switched from active to inactive)
  • 0AUSER is empty
  • 0AMODE = OFF
  • 0ASOURCE is empty
InfoCube data that was written before any audits were performed. All audit characteristics are empty.

Local Provider in BW Workspace

If data is written to a local provider using BW-integrated planning (in other words, using an input-ready query or planning function), the system fills the audit characteristics like in the planning mode of a real-time InfoCube.

However, there is no suitable loading mode for local providers. Here, the loading mode involves uploading a file to create a local provider.

Related Information