Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

Historical database tables

  • Last UpdatedOct 28, 2024
  • 3 minute read

The following table provides a list of independent historical database tables that you can select from the Database Maintenance Properties window for archive or purge.

  • When archiving, other dependent tables (not listed here) will be archived with the selected independent tables.

  • When purging, only the independent table will be purged, not its dependent tables, unless otherwise noted in the table below.

    Internal Database Table Name

    Description

    audit_trail

    Provides a generic audit trail of who inserted, edited, or deleted important data, and when. Used to facilitate 21 CFR Part 11 compliance.

    cert_audit_log

    Records certification auditing sign-offs. This table allows for sign-offs to the operation or step level.

    data_entry_log

    Allows for the driving of and compliance to data collection schedules to be monitored. Database or other triggers insert rows into this table with default data when a trigger is detected. The values can then be updated and the entries_made field compared to the entries_reqd to detect non-compliance.

    data_log

    Stores logged data values.

    db_deleted_log

    Stores a record for any MES database table records that have been deleted. Each stored record includes the table name and, in XML format, the primary key for the record that was deleted.

    dx_log

    Supply Chain Connector log table. Captures all results and exceptions whenever any schedule is triggered to enable audit trails, error reporting, etc.

    error_log

    Populates system errors and events as they occur. The system can be configured to log or ignore errors of different severities which are defined as follows:

    0 = Critical errors. Significant, might crash system.

    1 = Serious errors. Affects operation and data.

    2 = Partial errors. Some data will be wrong.

    3 = Trivial errors. Small adverse effect on some data.

    4 = Events. No affect on data or operation. Affects information only.

    item_cons

    Item consumption table. Collects component item usage and waste quantities for each BOM item by job, shift, lot, and so on. This table captures component and parent item lot numbers, which provide the genealogy breakdown by lot.

    item_transfer

    Stores inventory transfers, except for production and consumption transactions.

    This table is also used to store received raw material and finished good shipments, if required.

    labor_usage

    Logs the labor time for each labor category and employee ID for each of the standard domains.

    lot

    Allows lots and their characteristics to be defined.

    Purging this table will also purge the following dependent tables:

    • assigned_lot

    • inv_lot_attr

    • item_inv

    • lot_attr

    • rework_count

    • sublot

    • sublot_attr

    po

    Stores details for each purchase order.

    Purging this table will also purge the following dependent tables:

    • po_line

    • receipt

    • receipt_lot

    so

    Stores details for each sales order.

    Purging this table will also purge the following dependent tables:

    • shipment

    • shipment_lot

    • so_line

    • so_wo_link

    sample

    Stores quality sample records and contextual information about the sample.

    Purging this table will also purge the following dependent tables:

    • result, result_attr

    • sample_attr

    • sample_char_link

    • sample_char_rule_link

    storage_ent_transfer

    Storage entity transfer table. Captures changes in the location or status of storage entities, as well as changes in their spare field values.

    util_history

    Captures utilization data and a chronological sequence of events for each entity that can capture utilization data. This data includes entity utilization states, utilization reasons, number of occurrences, and the timestamps when an entity's utilization state or reason changes (that is, when a new event occurs).

    Purging this table will also purge the following dependent table:

    • corr_action_log

    wo

    Contains header data for released work orders, which includes data such as which parent item is required, what quantity and by when. This data is common to all jobs (operations) within the work order. It thus defines what work orders are scheduled to run at the facility at various times. It also records data for work orders that are currently running or have been completed or suspended.

    Purging this table will also purge the following dependent tables:

    • assigned_lot

    • cert_job_link

    • cert_job_step_links

    • data_log_grp_job_link

    • data_log_grp_job_step_link

    • item_prod

    • job

    • job_alloc_rule

    • job_attr

    • job_bom

    • job_bom_step

    • job_bom_subst

    • job_event

    • job_history

    • job_hour_history

    • job_prod_rule

    • job_route

    • job_spec

    • job_step

    • job_step_choice

    • job_step_data

    • job_step_file

    • job_step_grp

    • lot_attr_default

    • res_job_link

    • rework_count

    • so_wo_link

    • wo_attr

    • wo_file

TitleResults for “How to create a CRG?”Also Available in