Search Results audit_type_description

Overview

APPS.QA_SEQ_AUDIT_HISTORY_V is a reporting view in the Oracle E-Business Suite Quality Management module. It exposes the audit history of sequence values generated by QA collection plans, joining the underlying audit history table to descriptive attributes for plans, elements, organizations, users, and audit types. The view is owned by the APPS schema, carries the FND Design Data reference QA.QA_SEQ_AUDIT_HISTORY_V, and is documented as a valid internal view in both Oracle EBS 12.1.1 and 12.2.2.

The documentation explicitly states that this object is for Oracle Internal Use Only and that Oracle does not support direct access to application data through it except from standard Oracle Applications programs. Customers and integrators should therefore treat QA_SEQ_AUDIT_HISTORY_V as a read-only reporting surface, not as an API or a supported integration point. Its role is primarily analytical: it lets standard Oracle programs and, at the customer's own risk, reporting tools reconstruct who generated a sequence value, when, for which plan, and under which audit context.

The view does not appear in the list of files shown in the metadata excerpt; the excerpt lists only the object structure. It is nonetheless documented with full column and dependency metadata, which is sufficient to describe its reporting behavior.

Underlying Base Objects

According to the documented view metadata for ETRM 12.2.2, QA_SEQ_AUDIT_HISTORY_V is defined over the following referenced objects:

• QA_SEQ_AUDIT_HISTORY (SYNONYM) — the primary fact object holding the sequence audit records.
• QA_PLANS (SYNONYM) — provides plan name and plan description.
• QA_CHARS (SYNONYM) — provides the element (characteristic) name.
• MTL_PARAMETERS (SYNONYM) — supplies the organization code and organization context.
• FND_USER (SYNONYM) — resolves the user ID to a user name.
• QA_LOOKUPS (VIEW) — supplies the audit type meaning and audit type description.

The dependency list in the 12.1.1 documentation shows the same set, expressed as QA_L and QA_LOOKUPS for the lookup access. In other words, the view is a join of the audit history fact with plan, element, organization, user, and lookup dimension data. Because all base objects are synonyms or views in APPS, the view is independent of the physical table owner and can be consumed from the APPS schema without fully qualifying the underlying tables.

Key Columns

• PLAN_ID, PLAN_NAME, PLAN_DESCRIPTION — identify the QA collection plan associated with the audit record.
• ORGANIZATION_ID, ORGANIZATION_CODE — the inventory/QA organization context.
• COLLECTION_ID, OCCURRENCE — the collection instance and its occurrence number.
• CHAR_ID, CHAR_NAME — the QA element (characteristic) whose sequence value was generated.
• SEQUENCE_VALUE — the generated sequence value, stored as VARCHAR2(50). This is the central payload of the audit record.
• TXN_HEADER_ID, SOURCE_CODE, SOURCE_ID — contextual links to the originating transaction or source.
• USER_ID, USER_NAME — the user who performed the action.
• AUDIT_TYPE, AUDIT_TYPE_MEANING, AUDIT_TYPE_DESCRIPTION — the audit action code and its decoded meaning. AUDIT_TYPE_DESCRIPTION is VARCHAR2(240) and is derived from QA_LOOKUPS; this is the column most commonly searched by report authors.
• AUDIT_DATE — the timestamp of the audit event.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include sequence-value traceability, audit reporting for regulated environments, and investigating which user generated a given value for a plan element.

To list recent sequence audits for a plan:

• SELECT plan_name, char_name, sequence_value, audit_type_description, audit_date
• FROM apps.qa_seq_audit_history_v
• WHERE plan_id = :p_plan_id
• ORDER BY audit_date DESC;

To trace a specific generated value:

• SELECT sequence_value, char_name, user_name, source_code, audit_type_meaning
• FROM apps.qa_seq_audit_history_v
• WHERE sequence_value = :p_value;

To summarize activity by audit type and user:

• SELECT audit_type_description, user_name, COUNT(*)
• FROM apps.qa_seq_audit_history_v
• WHERE audit_date >= :p_start_date
• GROUP BY audit_type_description, user_name;

Because the object is marked Oracle Internal Use Only, such queries should be reserved for diagnostics and custom reporting, and should not be embedded in supported production integrations.