Frequently Asked Questions About Logging with Audit Trail
Use
-
Question:
How can I create a link between a long text (text object, text ID) and the transactions in which it is used when configuring the deletion facility for long texts (transaction S_AUT04)?
Answer:
You will find a description of how to proceed to configure the long text logs for deletion in the document Configure Deletion of Long Text Logs. This enables you to draw conclusions about the transactions that generated the long text logs.
-
Question:
In evaluations of table and long text logs using transaction S_AUT10 and the deletion of long texts, system performance is very poor. What are possible reasons for this?
Answer:
The correct indexing of database tables is a key prerequisite for good performance. SAP Note 531923 explains which indices are advantageous in the above cases.
-
Question:
In evaluations carried out with transaction S_AUT10, it can happen that the Changed By field is populated correctly, but the full name is not shown. What are possible reasons for this?
Answer:
The document Display Evaluation Results describes what you must do in order that the full name is always displayed.
-
Question:
How is long text logging activated in Audit Trail?
Answer:
The prerequisites for the logging of long texts are set out in the document Logging of Long Texts.
-
Question:
When I evaluate change documents using transaction S_AUT10, individual field values or entire change documents are missing. What is the reason for this?
Answer:
SAP Note 582342 contains a list of points that you should check in this connection.
-
Question:
What are the effects of the different logging settings that can be made in transaction S_AUT01 on the clients in a system?
Answer:
All information on this topic is available in the document Client-Dependent Logging.
-
Question:
After the creation of data records in a transaction that is connected up with the change document creation facility and has been configured for the logging of data records, no logs are visible in transaction S_AUT10. What are possible reasons for this?
Answer:
No change documents are stored when data is created. The original data records are visible via the associated change or display transaction. For this reason, you need not record the creation of a data record redundantly in the form of a log. Only if the original values are changed is it necessary to store logs relating to GMP-relevant data.
-
Question:
Change document objects are implemented in an application. The change document object does not contain all relevant tables. I cannot configure all the desired data for logging. What can I do?
Answer:
The document Creation of Change Documents includes information on this topic.
-
Question:
Inactive data elements or tables are displayed on the Variances System <=> Own Settings screen of transaction S_AUT10. I cannot change the inactive objects. Only changes to active objects are allowed. What can I do?
Answer:
The document Remove Inactive Versions of Data Elements and Tables explains how to remove the inactive versions and thus make it possible to make changes again.
-
Question:
I have activated individual data elements for change document creation in transaction S_AUT01. After evaluation with transaction S_AUT10, I do not get any logs. What are possible reasons for this?
Answer:
The document Creation of Change Documents sets out the prerequisites for the correct functioning of the change document creation facility.
-
Question:
I am carrying out an evaluation using transaction S_AUT10. In the display of the table logs and the display of the change documents, I see only a technical representation of the data that is difficult to interpret. Can I change this technical representation into a display format that is easier to read?
Answer:
Yes, this is possible. To do so, you must use the Business Add-In BADI_S_AUT_CONV.
The Business Add-In BADI_S_AUT_CONV enables you to convert values from an internal to a more readable external display format. The Business Add-In is invoked in transaction S_AUT10. It is executed in the case of both the overview display and the detail view of the table logs. More information is available in the system documentation for the BAdI.
-
Question:
In the evaluation with transaction S_AUT10, a different transaction code than the one I expect is shown in the Transaction field. What are possible reasons for this?
Answer:
In this case, a jump to another transaction takes place within the transaction you are using. The change is saved under this other transaction code.
-
Question:
In the evaluation with transaction S_AUT10, the change appears under a different field name than the one expected. Why is this?
Answer:
The field name determined via F1 -> Technical Information is the name of the dynpro field. This is not always the same as that of the field in the database.
-
Question:
Changed data records are not shown in transaction S_AUT10 with the change log of the change type U ( Changed), but with two change logs, each with the change type D ( Deleted) and I ( Inserted). Why is this?
Answer:
If, as a result of a change, it is necessary to change a key field of a table, the corresponding data record must be deleted and a new entry inserted. This is a consequence of the basic architecture of relational database systems.
-
Question:
I delete long text logs using the report S_AUT_DEL or transaction S_AUT05. In the log, a date that is later than the start date I entered appears in the Deleted From (Date) field. Why is this?
Answer:
In transaction S_AUT04, you entered a deletion date for the relevant text that is later than the start date you specified on the selection screen for the deletion report S_ AUT_DEL.