Search Results process_risk_control_ap_id

Overview

AMW.AMW_PROCESS_RISK_CTRL_AP is a transactional table in the Oracle E-Business Suite Audit Management Workbench (AMW) schema. It serves as the association entity that links individual audit procedures to higher-level process risk controls, forming the operational backbone for risk-based audit planning and execution. Each row records the relationship between an audit procedure and the process risk control it addresses, enabling auditors to trace testing activities back to specific control objectives.

The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, reflecting its role as an actively written transactional store. It carries standard Oracle EBS Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATED_DATE), a SECURITY_GROUP_ID for hosted or multi-tenant deployments, and an OBJECT_VERSION_NUMBER used for optimistic locking during concurrent updates. Fifteen descriptive flexfield (DFF) columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15) provide extensibility for customer-specific attributes without schema modification.

Based on the mined foreign key structure, this table is heuristically classified as standalone within a Data Vault modeling context. This classification suggests the table operates primarily as an independent association record rather than a strict hub, link, or satellite, though its foreign keys to AMW_PROCESS_RISK_CONTROLS and FND_SECURITY_GROUPS do imply integration points. Modeling teams may consider treating it as a link between audit procedures and process risk controls when designing downstream analytical models.

Key Information Stored

The table contains 26 documented columns. The most operationally significant columns include:

• PROCESS_RISK_CONTROL_AP_ID — Surrogate primary key, defined by unique index AMW_PROCESS_RISK_CONTROL_AP_U1. This is the column users most commonly search for when tracing audit procedure linkages.
• PROCESS_RISK_CONTROL_ID — Foreign key referencing AMW.AMW_PROCESS_RISK_CONTROLS. This is the business-critical link tying each audit procedure to a parent risk control.
• AUDIT_PROCEDURE_ID — Identifier for the associated audit procedure, enabling correlation with audit testing steps.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, used in hosted or multi-org environments to isolate data by security group.
• OBJECT_VERSION_NUMBER — Locking column supporting concurrent update integrity; incremented on each modification.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATED_DATE, and LAST_UPDATE_LOGIN provide a full audit trail of row creation and modification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield structure defining and storing extensible, user-defined attributes up to 150 characters each.

It should be noted that while AMW_PROCESS_RISK_CTRL_AP_ID is the unique surrogate key, the natural business identity of a row is effectively the combination of PROCESS_RISK_CONTROL_ID and AUDIT_PROCEDURE_ID, which together define the specific procedure-to-control association.

Common Use Cases and Queries

Typical usage revolves around risk-based audit reporting and procedure traceability. Common query patterns include:

• Retrieving all audit procedures linked to a given process risk control using a join on PROCESS_RISK_CONTROL_ID.
• Identifying orphaned or unlinked audit procedures by left-joining to AMW_PROCESS_RISK_CONTROLS and filtering for nulls.
• Auditing the modification history of procedure-control links via the Who columns for SOX or internal audit compliance reporting.
• Extracting DFF segments (ATTRIBUTE1–ATTRIBUTE15) for custom reporting where the organization has configured flexfield values for segregation of duties or testing frequency.

A representative query to list procedures for a specific risk control:

SELECT p.process_risk_control_ap_id, p.audit_procedure_id, p.attribute1
FROM amw.amw_process_risk_ctrl_ap p
WHERE p.process_risk_control_id = :control_id
AND p.security_group_id = :sec_group;

Because Oracle designates this object as Internal Use Only, direct SQL access should be restricted to read-only reporting; all data changes must be performed through standard Oracle Applications programs to preserve referential and locking integrity.

Related Objects

The most significant related objects, based on documented foreign key and dependency metadata, are:

• AMW.AMW_PROCESS_RISK_CONTROLS — Parent table referenced via PROCESS_RISK_CONTROL_ID; defines the process risk control being audited.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs hosted-environment data partitioning.
• AMW_PROCESS_RISK_CTRL_AP_U1 — Unique index on PROCESS_RISK_CONTROL_AP_ID; the primary access path for lookups by surrogate key.
• Audit procedure definition objects within the AMW schema — Referenced implicitly via AUDIT_PROCEDURE_ID; provide the procedure master data joined for audit workpaper reporting.

Because the table is classified as standalone with limited outward foreign keys, its dependency footprint is relatively narrow, and most integration occurs through joins to AMW_PROCESS_RISK_CONTROLS for audit planning and reporting.