Search Results ineffective_controls




Overview
Explore in AI Chat

Overview

AMW.AMW_AUDIT_SCOPE_PROCESSES is an Oracle E-Business Suite table within the Application Management Workbench (AMW) schema, which underpins the Audit Management functionality delivered with the GRC (Governance, Risk, and Compliance) module in EBS 12.1.1 and 12.2.2. The table stores summary metrics for each audit process that has been scoped into an engagement, capturing rolling counts of risks, controls, findings, and issues evaluated during the audit lifecycle. It functions as a denormalized aggregation snapshot: rather than deriving these totals dynamically from transactional detail tables, the application persists them here to accelerate dashboards, engagement summaries, and workflow decisions.

Based on the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a satellite. It carries descriptive, measurable attributes (counts and evaluation identifiers) tied to a defined business key composed of audit project, organization, process, and process-organization revision. It does not act as a standalone hub or a pure link, because its payload is the quantitative state of an audit scope rather than a relationship between two entities. The presence of standard WHO columns and OBJECT_VERSION_NUMBER confirms it is a transactable, concurrency-controlled application table.

Key Information Stored

All 20 documented columns are physical, but the following carry the substantive business meaning:

The composite surrogate candidate for uniqueness is the combination of AUDIT_PROJECT_ID, ORGANIZATION_ID, PROCESS_ID, and PROCESS_ORG_REV_ID; the AMW tablespace APPS_TS_TX_DATA placement confirms it is transactional data, not setup.

Common Use Cases and Queries

The primary use case is audit engagement reporting: listing processes with outstanding open findings, tracking remediation progress, and building engagement scorecards. A typical query retrieves open findings per engagement:

  • SELECT p.AUDIT_PROJECT_ID, p.PROCESS_ID, p.OPEN_FINDINGS, p.OPEN_ISSUES FROM AMW.AMW_AUDIT_SCOPE_PROCESSES p WHERE p.OPEN_FINDINGS > 0 ORDER BY p.OPEN_FINDINGS DESC;
  • Risk-versus-control coverage: join TOTAL_RISKS against RISKS_EVALUATED, and TOTAL_CONTROLS against CONTROLS_EVALUATED, to identify processes lagging in testing.
  • Engagement rollup: aggregate OPEN_FINDINGS and UNMITIGATED_RISKS by AUDIT_PROJECT_ID for management dashboards.
  • Trending: use LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER to detect recent status changes in extract processes.
  • Multi-org filtering: constrain by ORGANIZATION_ID for divisional reporting, since SECURITY_GROUP_ID supports hosted/multi-tenant deployments.

Related Objects

The documented foreign keys and dependency metadata tie this table to the following significant objects:

  • AMW.AMW_AUDIT_PROJECTS — Parent engagement table; joined on AUDIT_PROJECT_ID (documented FK).
  • FND_SECURITY_GROUPS — Joined on SECURITY_GROUP_ID (documented FK) for hosted-environment security partitioning.
  • AMW process and risk/control definition tables — Related via PROCESS_ID and PROCESS_ORG_REV_ID to the process master and its revisions.
  • AMW findings and issues tables — Source detail records for the OPEN_FINDINGS and OPEN_ISSUES aggregates.
  • AMW_AUDIT_SCOPE_* sibling tables — Parallel scope tables (risks, controls, organizations) that share the AUDIT_PROJECT_ID and PROCESS_ORG_REV_ID keys.
  • Evaluation opinion tables — Referenced through EVALUATION_OPINION_ID for opinion classification.

No database object is documented as depending on AMW_AUDIT_SCOPE_PROCESSES, indicating it is a leaf fact-style table referenced primarily by reports and concurrent programs rather than by downstream constraints.