Search Results txn_header_id




Overview
Explore in AI Chat

Overview

QA_SEQ_AUDIT_HISTORY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered with the Quality (QA) module. It exposes the audit trail of sequence value consumption for quality collection plans. In Oracle Quality, collection plans may be associated with sequence-generating elements; each time a sequence value is consumed or assigned, a record is written to the QA_SEQ_AUDIT_HISTORY table. The view joins that audit table to plan definitions, character (collection element) definitions, user accounts, organization parameters, and lookup values to present a fully denormalized, human-readable audit record.

Because the view resolves identifiers into names and decoded lookup meanings, it is intended for inquiry, reporting, and integration rather than for transactional updates. Its status is VALID in both the 12.1.1 and 12.2.2 documentation sets, and it is referenced in the ETRM metadata as "sequence audit table." The presence of the AUDIT_TYPE column, decoded through the QA_SEQ_AUDIT_TYPE lookup, is central to how consumers interpret each row.

Underlying Base Objects

The view is defined over six documented objects, all referenced through APPS synonyms except QA_LOOKUPS, which is itself a view:

The joins are inner joins throughout: QASH.PLAN_ID = QP.PLAN_ID, QP.ORGANIZATION_ID = MP.ORGANIZATION_ID, QASH.CHAR_ID = QC.CHAR_ID, QASH.USER_ID = FU.USER_ID, and QASH.AUDIT_TYPE = QL.LOOKUP_CODE with QL.LOOKUP_TYPE = 'QA_SEQ_AUDIT_TYPE'. Consequently, an audit row is only visible when all referenced entities resolve and the AUDIT_TYPE has a matching QA_SEQ_AUDIT_TYPE lookup entry.

Key Columns

  • PLAN_ID, PLAN_NAME, PLAN_DESCRIPTION — the collection plan context for the audit event.
  • ORGANIZATION_ID, ORGANIZATION_CODE — the inventory organization owning the plan.
  • COLLECTION_ID, OCCURRENCE — the collection instance and its occurrence number.
  • CHAR_ID, CHAR_NAME — the collection element that consumed the sequence value.
  • SEQUENCE_VALUE — the actual sequence number assigned or consumed.
  • TXN_HEADER_ID — link to the transaction header associated with the event, where applicable.
  • USER_ID, USER_NAME — the user who triggered the audit entry.
  • SOURCE_CODE, SOURCE_ID — the originating process or entity that produced the event.
  • AUDIT_TYPE — code indicating the nature of the audit event; decoded as AUDIT_MEANING and AUDIT_DESCRIPTION (aliased in the view text as AUDIT_MEANING and AUDIT_DESCRIPTION, and exposed in the column list as AUDIT_TYPE_MEANING and AUDIT_TYPE_DESCRIPTION).
  • AUDIT_DATE — timestamp of the audit event.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes reconciling sequence gaps, tracing who consumed a given sequence value, and auditing sequence behavior by plan, organization, or user. Because AUDIT_TYPE is decoded, reports can group or filter by meaning rather than code.

All audit events for a plan within a date range:

  • SELECT plan_name, organization_code, char_name, sequence_value, audit_type, audit_meaning, user_name, audit_date FROM qa_seq_audit_history_v WHERE plan_id = :plan_id AND audit_date BETWEEN :start_date AND :end_date ORDER BY audit_date;

Events by audit type meaning:

  • SELECT sequence_value, char_name, user_name, audit_date FROM qa_seq_audit_history_v WHERE audit_meaning = :meaning ORDER BY audit_date DESC;

Reconciling a specific sequence value to its source transaction:

  • SELECT plan_name, occurrence, txn_header_id, source_code, source_id, user_name FROM qa_seq_audit_history_v WHERE sequence_value = :seq_val;