Search Results amw_process_risk_ctrl_ap_pk

Overview

AMW_PROCESS_RISK_CTRL_AP is a table residing in the AMW schema, owned by the Oracle Internal Controls Manager (ICM) product module. Per the ETRM documentation metadata, this table is explicitly marked as Obsolete. Its designation as obsolete is significant: Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments may still contain this object due to upgrade or migration paths, but Oracle no longer supports its use for new development or active functional processing. The name suggests it once served as an application-intersection ("_AP" suffix) object, associating audit procedure definitions with process, risk, and control combinations within the ICM framework.

From a Data Vault modeling perspective, the metadata's heuristic classification assigns this object a standalone designation, meaning no foreign-key relationships were mined from its physical structure. In practical modeling terms, this implies the table does not behave as a classic hub, link, or satellite within a normalized integration layer; instead, it should be treated as an isolated legacy artifact. Any downstream data warehouse or reporting layer should avoid treating it as a reliable relational anchor.

Key Information Stored

The documented 12.1.1 physical schema lists 26 columns. The most operationally relevant are:

• PROCESS_RISK_CONTROL_AP_ID — The surrogate primary key, backed by the index AMW_PROCESS_RISK_CTRL_AP_PK and also exposed through the unique index AMW_PROCESS_RISK_CTRL_AP_U1. Because both the PK and the sole unique index reference the same column, no independent business-key candidate is documented.
• PROCESS_RISK_CONTROL_ID — A reference to the parent process/risk/control combination; likely the intended join key despite the standalone classification.
• AUDIT_PROCEDURE_ID — Identifies the audit procedure linked to the process-risk-control record.
• SECURITY_GROUP_ID — Supports Oracle's multi-organization-style data partitioning convention.
• OBJECT_VERSION_NUMBER — Enables optimistic locking for concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATED_DATE, LAST_UPDATE_LOGIN — Standard "Who" audit columns maintained by EBS concurrent and form processing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The flexible descriptive flexfield (DFF) segment columns common to older EBS transactional and intersection tables.

Common Use Cases and Queries

Because the table is obsolete, its primary practical use in 12.1.1 and 12.2.2 is legacy data inspection. DBAs and technical consultants commonly query it during upgrade assessments, orphan-object audits, or data-migration validation. A representative pattern:

SELECT prca.process_risk_control_ap_id, prca.process_risk_control_id, prca.audit_procedure_id, prca.creation_date FROM amw.amw_process_risk_ctrl_ap prca WHERE prca.security_group_id = :org_id;

Reporting scenarios typically involve reconciling historical control records before archiving, verifying whether any rows persist after ICM patch application, or confirming that the obsolete status matches a metadata repository. Since the object is not FK-linked, joins must be inferred from column semantics rather than enforced constraints, which means any integration query should be validated carefully against the target ICM tables before use.

Related Objects

Given the standalone classification, no enforced referential dependencies are documented. Logically, however, the following AMW family objects are candidates for correlation, using the columns named in this metadata:

• AMW_PROCESS_RISK_CONTROL_AP joins conceptually to process-risk-control master tables via PROCESS_RISK_CONTROL_ID.
• Audit procedure definitions, referenced through AUDIT_PROCEDURE_ID.
• AMW security-group-scoped ICM tables, aligned via SECURITY_GROUP_ID.
• Adjacent obsolete intersection tables in the AMW schema sharing the same naming pattern.

Consumers should verify each relationship against the live data dictionary, as the standalone classification indicates the mined evidence is insufficient to guarantee these join paths.