---
title: "Advanced database logging"
slug: "advanced-database-logging"
description: "Track changes to sensitive data with advanced database logging in Life Sciences Supply Chain Management to support confidentiality and integrity."
updated: 2026-06-25T10:24:09Z
published: 2026-06-25T10:24:09Z
canonical: "docs.staedean.com/advanced-database-logging"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Advanced database logging

Computer systems are enforced to:

- Maintain the confidentiality, integrity, and availability (CIA) of data.
- Create an auditable record of changes to specific tables that contain sensitive information.
- Monitor the use of electronic signatures.

To accomplish these requirements, tables containing sensitive data need to be listed in the **Database log setup** form (**System administration > Setup > Database log > Database log setup**).

### Database log for items, batches, and sub batches

Life Sciences Supply Chain Management allows users to easily identify which items, batches, or sub-batches have been subject to changes that are tracked in the database log. The **Database log** field is available in the following forms:

- **Released product details** form, **General** FastTab (**Product information management > Products > Released products**).
- **Batches** form, **Properties** FastTab (**Inventory management > Inquiries and reports > Tracking dimensions > Batches**).
- **Sub batches** form, **Properties** FastTab (**Inventory management > Inquiries and reports > Tracking dimensions > Sub batches**).

If a record has been modified and the modification is tracked in the database log, the **Database log** parameter is automatically set to **Yes** and the **Database log** button is enabled, which will open the **Database log** inquiry filtered by information related to the selected record.

### Database log inquiry and report

Life Sciences Supply Chain Management optimizes the usage of the **Database log** inquiry (**System administration > Inquiries > Database > Database log**) through the following enhancements:

- The **User name** field always displays the user’s full name responsible for the record modification instead of the system user ID.
- Users can easily filter the **Database log** report by a specific field or table by selecting the desired **Table name** or **Field name** value in the report print dialog.

> [!NOTE]
> Note
> 
> - Only tables that have been added in the **Database log setup** form (**System administration > Setup > Database log > Database log setup**) are available for selection in the **Table name** field.
> - If a value is not entered in the **Table name** field, the **Field name** field is not editable.
> - Use the standard filtering function to select multiple tables. However, you need to retrieve the table ID, and it is not possible to filter by a specific field. It is not possible to use the **Table name** field and select a criterion for the **Reference table ID** field through standard filtering simultaneously.
- Users can print additional electronic signature details in the **Database log** report, by enabling the following parameters in the print dialog:
  - **Print filters:** prints the applied filters (either through the **Table name**, **Field name**, or standard filters) on top of the report itself.
  - **Print reason code:** prints the **Reason code** that was selected by the user when electronically signing a change.
  - **Print comment:** prints the **Comment** that was entered by the user when electronically signing a change.