AE DB Revision Report

Revision reports can be created in each AE system to have detailed information about modified, imported, transported or deleted objects, objects that were modified at, task starts and abnormal ends, and accesses of any kind logged internally. The OBJECT_AUDIT key of the specific UC_CLIENT_SETTINGS variable serves to activate the logging procedure. To structure this data chronologically in a revision report, you can use the AE DB Revision Report (ucybdbrr) utility. For more information, see OBJECT_AUDIT.

This page includes the following:

Important!

Create Revision Reports

Start the AE DB Revision Report utility from the command line and define the parameters you require, such as the period, or the areas that should to be monitored. Use the following syntax where the order of the parameters does not matter:

Example:

All start time and runtime modifications of client 3 which take place between 1 April 2017, 20:00 (08:00 pm) and 2 April 2017, 06:30 am are output to the file C:\revision\report01.txt.

UCYBDBRR -B -C0003 -FSTART,RUN_MOD -OC:\revision\report01.txt -D120170401200000 -D220170402063000

The parameters -B and -C are required, the rest is optional with default values being used for the non-specified parameters. For a list of all values including their descriptions, see Start Parameters - Utilities.

The utility AE DB Revision Report returns the following codes and messages, depending on the situation that has occurred:

Monitored Areas

The following areas are logged and you can store the relevant data in revision reports. Manual modifications as well as modifications made via script elements are logged except for the specific situations described in the section object modifications: