Search Results audit_description

Overview

APPS.QA_SEQ_AUDIT_HISTORY_V is a reporting and integration view in Oracle E-Business Suite that consolidates sequencing audit trail data written by the Quality Management (QA) module. It presents a denormalized, human-readable projection of the base audit table QA_SEQ_AUDIT_HISTORY, enriching raw identifiers with descriptive attributes drawn from plans, characteristics, users, lookup codes, and inventory parameters. The view is defined in the APPS schema and is exposed as a synonym for use by reports, concurrent programs, OBIEE extracts, and custom SQL.

The view carries particular importance because it resolves the AUDIT_DESCRIPTION column requested in many user searches. Rather than requiring the caller to join QA_LOOKUPS manually, the view already resolves the audit_type code against lookup_type 'QA_SEQ_AUDIT_TYPE' and returns both the lookup MEANING and DESCRIPTION text, allowing report authors to display a readable audit narrative alongside the raw audit code.

Underlying Base Objects

The view is defined over six objects. QA_SEQ_AUDIT_HISTORY (synonym) is the driving table and contains the raw audit records written whenever sequence values are generated or altered. QA_PLANS and QA_CHARS provide the quality plan and characteristic context. FND_USER supplies the application user identity. QA_LOOKUPS, itself a view, resolves the audit_type code to descriptive text under lookup_type 'QA_SEQ_AUDIT_TYPE'. MTL_PARAMETERS supplies the inventory organization code that anchors the plan's organization_id.

Joins are mandatory inner joins on plan_id, organization_id, char_id, user_id, and audit_type/lookup_code, so any orphaned audit row lacking a valid user, characteristic, plan, or lookup entry is excluded from the result set. This is significant when reconciling counts against the base table. The synonym-to-synonym hops also mean the view is grant-dependent: the calling schema must have SELECT rights on the underlying objects, not merely on the view itself.

Key Columns

• PLAN_ID / PLAN_NAME / PLAN_DESCRIPTION – identity and descriptive text of the quality plan under audit.
• ORGANIZATION_ID / ORGANIZATION_CODE – inventory organization anchoring the plan, resolved via MTL_PARAMETERS.
• COLLECTION_ID / OCCURRENCE – the collection and occurrence context in which the sequence audit occurred.
• CHAR_ID / CHAR_NAME – the quality characteristic whose sequence value was audited.
• SEQUENCE_VALUE – the actual sequence number generated or adjusted.
• TXN_HEADER_ID – transaction header link, useful for drill-through to the originating transaction.
• USER_ID / USER_NAME – the FND user responsible for the audited action.
• SOURCE_CODE / SOURCE_ID – originating process or module reference.
• AUDIT_TYPE / AUDIT_MEANING / AUDIT_DESCRIPTION – the audit action code plus its lookup meaning and long description, the descriptive column most often sought.
• AUDIT_DATE, CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard audit stamp columns for traceability.

Common Use Cases and Queries

The view supports sequence audit reporting, SOX/Sarbanes-Oxley evidence gathering, and reconciliation of generated sequence numbers against transaction headers. A basic query returning the readable audit description for a plan is:

SELECT plan_name, char_name, sequence_value,
       audit_meaning, audit_description, audit_date, user_name
FROM   apps.qa_seq_audit_history_v
WHERE  plan_id = :p_plan_id
ORDER  BY audit_date;

To count audits by description for a period:

SELECT audit_description, COUNT(*)
FROM   apps.qa_seq_audit_history_v
WHERE  audit_date BETWEEN :p_from AND :p_to
GROUP  BY audit_description;

Because the joins are inner, organizations with incomplete plan or user setup may see excluded rows; where completeness is required, query QA_SEQ_AUDIT_HISTORY directly with outer joins to QA_LOOKUPS and FND_USER.