Results for “opinion_type_code”

35 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AMW_OPINION_TYPES_B table is the base table for Opinion Types within the Oracle E-Business Suite module AMW — Internal Controls Manager. This module is documented as obsolete in the ETRM reference set, which means the object may not be deployed in every environment and carries limited functional relevance in current 12.1.1 and 12.2.2 implementations. The table stores the core definition of opinion types, which are classification values used when recording audit or control opinions against business objects. Its role is that of a foundational lookup or reference entity: it holds the surrogate identity and denormalized attributes for each opinion type, while translated and descriptive text is held separately.

From a Data Vault modeling perspective, the mined relationship structure classifies this table as hub-leaning. It contains a single-column surrogate primary key (OPINION_TYPE_ID), a natural business key candidate (OPINION_TYPE_CODE), and no foreign keys pointing outward except to the security group, which is a common EBS partitioning construct rather than a true parent relationship. This pattern is characteristic of a hub with attached descriptive attributes. This classification is a modeling heuristic only and should not be treated as a definitive architectural statement.

Key Information Stored

The documented physical schema under ETRM 12.1.1 contains nine columns. The most significant are:

  • OPINION_TYPE_ID — the surrogate primary key defined by constraint AMW_OPINION_TYPES_B_PK and reinforced by the unique index AMW_OPINION_TYPES_B_U1. This is the identifier propagated to dependent tables.
  • OPINION_TYPE_CODE — the business-key candidate. In standard EBS design, this code is the user-meaningful, stable identifier used in integration and lookup logic, distinct from the internal surrogate.
  • SECURITY_GROUP_ID — the row-level security partition reference, joined to FND_SECURITY_GROUPS. It enables multi-organization or data-scoped filtering.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit who/when columns maintained automatically for concurrency and audit traceability.
  • OBJECT_VERSION_NUMBER — the optimistic locking counter used by the EBS framework to detect concurrent updates.

The metadata does not document additional attribute columns beyond these nine, so descriptive text such as the opinion type name is presumed to reside in the companion translation table rather than in the base table.

Common Use Cases and Queries

Because AMW is obsolete, the primary practical use cases involve historical reconciliation, migration auditing, and reporting against legacy Internal Controls Manager data that may still persist in a migrated database. A typical pattern resolves the base row to its translated description:

SELECT b.opinion_type_id,
       b.opinion_type_code,
       t.description
FROM   amw_opinion_types_b  b,
       amw_opinion_types_tl t
WHERE  b.opinion_type_id = t.opinion_type_id
AND    b.security_group_id = :p_security_group_id
AND    t.language = USERENV('LANG');

Another common query counts how opinion types are applied to business objects through AMW_OBJECT_OPINION_TYPES, which is useful for impact analysis before purging or archiving the AMW schema. Metadata queries against FND_TABLES and FND_COLUMNS are also used to confirm whether the object is implemented in a given environment, since the documentation notes it is "not implemented in this database" for the reference instance.

Related Objects

  • AMW_OPINION_TYPES_TL — the translation table joined on OPINION_TYPE_ID; holds language-specific descriptive text.
  • AMW_OBJECT_OPINION_TYPES — the assignment table linking opinion types to objects via OPINION_TYPE_ID; the principal dependent child.
  • FND_SECURITY_GROUPS — parent of SECURITY_GROUP_ID; enforces row-level security partitioning.
  • FND_TABLES / FND_COLUMNS — data dictionary views used to verify physical implementation.
  • AMW_OPINION_TYPES_B_PK / AMW_OPINION_TYPES_B_U1 — the primary key constraint and unique index that enforce identity and the business key.

Given the obsolete status of the AMW module, dependencies outside the AMW schema are unlikely, but any custom reports or extracts referencing Opinion Types should be inventoried before decommissioning.