Search Results new_pk1

Overview

AMW_EXCEPTIONS_VL is a public Oracle E-Business Suite view owned by the APPS schema, registered under the FND Design Data node AMW.AMW_EXCEPTIONS_VL. It is a translation (VL) view that combines the base and translation tables of the exceptions entity — namely the _B (base) and _TL (translation) tables of the AMW exceptions schema. Its documented purpose is broad: it is a public view that may be useful for custom reporting or other data requirements, and it is a standard candidate for ad hoc inquiry, extract, and integration use.

The view provides a consolidated, user-facing representation of exception records generated by the Oracle Enterprise Data Quality / Data Management (TCA/AMW) exception framework. Exception rows capture the "before" and "after" state of an entity affected by a data-changing transaction, together with a justification, so that data stewards and auditors can review what was deleted, added, or replaced. The VL suffix indicates that the view joins the translation-independent columns of the _B table with the translated name/description columns from the _TL table, filtering on the current language at query time.

Underlying Base Objects

Per the ETRM documentation, the view is a combination of the exceptions _B and _TL tables. The documented referenced base objects list is "none documented," so the precise underlying object names (for example, AMW_EXCEPTIONS_B and AMW_EXCEPTIONS_TL) are inferred from the AMW exceptions data model rather than explicitly enumerated in the metadata. The _B table stores the transaction-level attributes and the primary-key transition columns, while the _TL table stores language-dependent descriptive text keyed by EXCEPTION_ID and LANGUAGE. The VL view resolves the language join and exposes a single logical row per exception for the session language. The AMW_EXCEPTIONS_B/_TL tables were introduced with the EBS data quality and duplicate-resolution framework, which is why the view appears in AMW rather than in a core HRMS or financials schema.

Key Columns

• EXCEPTION_ID — Unique exception identifier; the primary joining key across the base and translation rows.
• OBJECT_TYPE (VARCHAR2, 30) — The type of entity that experienced the exception (for example, a party, location, or contact), allowing consumers to identify what was changed.
• OLD_PK1 through OLD_PK6 (VARCHAR2, 100 each) — Up to six primary-key components describing the entity that was deleted or replaced. NEW_PK1 through NEW_PK6 hold the corresponding keys of the entity added or replaced with; NEW_PK1 is the first key segment of the resultant record and is the column most frequently used to trace a replacement back to its new entity.
• TRANSACTION_TYPE (VARCHAR2, 30) — The nature of the transaction that produced the exception.
• TRANSACTION_DATE, END_DATE — When the transaction occurred, and the end of exception effectivity.
• JUSTIFICATION (VARCHAR2, 4000) — Free-text reason recorded by the user or process performing the change; central to audit and compliance review.
• SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER, and the WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — Standard EBS concurrency, audit, and multitenancy attributes.

Common Use Cases and Queries

The principal application is auditing a specific change: identifying which record replaced a deleted one, or tracing who removed a record and why. A sample query filtering on NEW_PK1 — the column most commonly searched for in this context — follows:

SELECT exception_id, object_type, old_pk1, new_pk1,
       transaction_type, transaction_date, justification
  FROM apps.amw_exceptions_vl
 WHERE new_pk1 = :p_new_pk
   AND transaction_date >= :p_from_date;

Other typical uses include reporting all exceptions within a date range, reconciling what was deleted against what was added using OBJECT_TYPE, and producing an audit extract of JUSTIFICATION text for a given SECURITY_GROUP_ID. Because the localization view already joins the _TL table, it returns translated descriptive text without requiring the caller to join translation tables manually, making it well suited to ad hoc reporting in Discoverer, BI Publisher, or external data-migration reconciliation scripts.