Search Results material_value

Overview

AMW.AMW_RISK_ASSOCIATIONS is a transaction data table within the Oracle E-Business Suite Financials product family, owned by the AMW schema (the application module historically associated with Oracle Enterprise Governance, Risk and Compliance / Application Management Workspace). The table records which business objects are linked to a specific risk, where the risk is identified by RISK_ID and the nature of the linked object is declared in OBJECT_TYPE. The two documented association types are PROCESS and PROCESS_ORG, meaning the table defines the relationship between a risk register entry and the process (or process-organization combination) that the risk affects.

From a Data Vault modeling perspective, the mined metadata classifies this object as standalone, with a primary key of AMW_RISK_ASSOCIATIONS_PK (RISK_ASSOCIATION_ID). The absence of a defined parent-child hub relationship in the FK data, combined with the presence of effective dating columns (EFFECTIVE_DATE_FROM, EFFECTIVE_DATE_TO), suggests this table behaves more like a link-plus-satellite construct: a link associating risks to processes, carrying an effectively dated satellite of risk scoring attributes. This is offered as a modeling suggestion; the physical ETRM implementation simply treats it as a standalone association table.

Key Information Stored

The table contains 42 documented physical columns. The most significant are summarized below.

• RISK_ASSOCIATION_ID — the surrogate primary key and sole unique index candidate (AMW_RISK_ASSOCIATIONS_U1), generated as the unique identifier for each association row.
• RISK_ID — the foreign key pointing to the risk being associated; indexed by AMW_RISK_ASSOCIATIONS_N1 together with OBJECT_TYPE.
• OBJECT_TYPE — the discriminator that governs how the associated-object identifier column (PK1) is interpreted; valid values include PROCESS and PROCESS_ORG.
• PK1 — holds the associated object identifier: the process_id when OBJECT_TYPE = 'PROCESS', or the process_org_id when OBJECT_TYPE = 'PROCESS_ORG'. Columns PK2 through PK5 are documented as "Not currently used."
• RISK_LIKELIHOOD_CODE and RISK_IMPACT_CODE — codes capturing the assessed likelihood and impact of the risk for this specific association.
• MATERIAL and MATERIAL_VALUE — flags and amounts indicating whether the association is financially material and, if so, its value.
• EFFECTIVE_DATE_FROM and EFFECTIVE_DATE_TO — effective dating that supports date-tracked or audit-timeline reporting of the association.
• ASSOCIATION_CREATION_DATE, APPROVAL_DATE, DELETION_DATE, and DELETION_APPROVAL_DATE — lifecycle timestamps supporting approval and soft-deletion workflows.
• RISK_REV_ID — foreign key to AMW.AMW_RISKS_B, linking the association to the risk revision under which it was created.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enabling multi-organization / security-group data segregation.
• OBJECT_VERSION_NUMBER — optimistic locking column used to detect concurrent updates.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments reserved for customer extensions.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — audit metadata present on all EBS transactional tables.

Common Use Cases and Queries

The primary reporting scenario is determining which risks are associated with which processes. The unique and non-unique indexes (U1 on RISK_ASSOCIATION_ID; N1 on RISK_ID and OBJECT_TYPE; N2 and N3 on OBJECT_TYPE) are designed to support both directions of that lookup efficiently.

To retrieve all process associations for a given risk:

SELECT ra.risk_association_id,
       ra.object_type,
       ra.pk1            AS process_or_process_org_id,
       ra.risk_likelihood_code,
       ra.risk_impact_code,
       ra.effective_date_from,
       ra.effective_date_to
FROM   amw.amw_risk_associations ra
WHERE  ra.risk_id = :p_risk_id
AND    ra.object_type = 'PROCESS'
AND    ra.deletion_date IS NULL;

Common queries include listing all risks linked to a particular process by filtering PK1 with a fixed OBJECT_TYPE, and reporting high-exposure combinations by filtering on RISK_LIKELIHOOD_CODE and RISK_IMPACT_CODE. Materiality reporting filters on MATERIAL = 'Y' and aggregates MATERIAL_VALUE. Trend analysis uses the effective dates and the association/approval timestamps. Note that PROCESS_ORG rows carry organization-scoped identifiers in PK1, so joins to process master data must account for OBJECT_TYPE to avoid mismatched interpretations of the key column.

Because flexfield segments extend the table, any DFF-enabled reporting should include ATTRIBUTE_CATEGORY in the join predicate.

Related Objects

The documented foreign keys establish the following relationships, which are the most relevant joins for this table:

• AMW.AMW_RISKS_B — referenced via AMW_RISK_ASSOCIATIONS.RISK_REV_ID; the primary parent for risk revision data and the anchor for any risk-descriptive attributes.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs data access segregation.
• AMW.AMW_RISKS_TL and the AMW_RISKS_B base/revision pair — conventional companions for joining human-readable risk names in the operating language.
• Process and process-organization tables — joined through PK1 depending on OBJECT_TYPE (PROCESS → process_id; PROCESS_ORG → process_org_id).
• FND_APPLICATION / FND_DESCR_FLEX_* configuration tables — define the descriptive flexfield structure declared in ATTRIBUTE_CATEGORY.

Consumers should treat the table as the authoritative association link between the risk register and the process hierarchy, and preserve the OBJECT_TYPE discriminator in every query and view built over it.