Search Results amw_audit_scope_organizations

Overview

AMW_AUDIT_SCOPE_ORGANIZATIONS is a transactional table belonging to the Oracle Internal Controls Manager (AMW) product, a module that has since been designated obsolete within the Oracle E-Business Suite. The table stores aggregated counts and evaluation metrics for individual organizations that fall within the scope of a specific audit engagement. Each row represents one in-scope organization tied to an audit project, capturing how many sub-organizations, processes, risks, and controls were evaluated, along with the resulting findings and issues. In EBS 12.1.1 the table is owned by the AMW schema and contains 28 documented columns; the metadata notes that the object is "not implemented in this database," indicating availability depends on whether Internal Controls Manager was licensed and installed. Heuristically, the mined foreign-key structure classifies this object as a standalone table. Under a Data Vault modeling suggestion, this would typically be treated as a satellite attached to the AMW_AUDIT_PROJECTS hub (or, in a richer model, a link between the audit project and the organization dimension) because it records descriptive, measurable context about a combination of keys rather than serving as an independent business entity.

Key Information Stored

The table's grain is one organization per audit engagement. The most significant columns include:

• AUDIT_PROJECT_ID – Foreign key to AMW_AUDIT_PROJECTS; identifies the engagement to which the scope organization belongs.
• ORGANIZATION_ID – The in-scope organization being measured (typically referencing HR/INV organization structures).
• SUBSIDIARY_VS, SUBSIDIARY_CODE, LOB_VS, LOB_CODE – Descriptive attributes identifying the subsidiary and line-of-business context for the organization.
• EVALUATION_OPINION_ID – Reference to the evaluation opinion assigned to this organization's scope result.
• SUB_ORGS_EVALUATED, INEFFECTIVE_SUB_ORGS, TOTAL_SUB_ORGS – Roll-up counts of sub-organizations evaluated, found ineffective, and in total.
• PROCESSES_EVALUATED, INEFFECTIVE_PROCESSES, TOTAL_PROCESSES – Corresponding process-level metrics.
• RISKS_EVALUATED, UNMITIGATED_RISKS, TOTAL_RISKS – Risk coverage and exposure counts.
• CONTROLS_EVALUATED, INEFFECTIVE_CONTROLS, TOTAL_CONTROLS – Control testing outcomes.
• OPEN_FINDINGS, OPEN_ISSUES – Outstanding deficiency and issue counts.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group data isolation.
• OBJECT_VERSION_NUMBER – Optimistic locking column used by the OAF framework.

The documented schema does not expose a dedicated single-column surrogate primary key beyond the composite role of AUDIT_PROJECT_ID and ORGANIZATION_ID; the audit/audit-line combination functions as the effective business key. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit trail metadata.

Common Use Cases and Queries

Because this table drives Internal Controls Manager scope reporting, typical usage centers on engagement dashboards, coverage analysis, and deficiency roll-ups. Common scenarios include identifying organizations with the highest ineffective-control counts, comparing evaluated versus total scope, and summarizing open findings by subsidiary or line of business.

Sample query — scope summary for an engagement:

• SELECT o.ORGANIZATION_ID, o.TOTAL_CONTROLS, o.INEFFECTIVE_CONTROLS, o.OPEN_FINDINGS FROM AMW.AUDIT_SCOPE_ORGANIZATIONS o WHERE o.AUDIT_PROJECT_ID = :project_id;
• SELECT o.SUBSIDIARY_CODE, SUM(o.OPEN_ISSUES) FROM AMW.AUDIT_SCOPE_ORGANIZATIONS o GROUP BY o.SUBSIDIARY_CODE;
• SELECT o.ORGANIZATION_ID FROM AMW.AUDIT_SCOPE_ORGANIZATIONS o WHERE o.INEFFECTIVE_CONTROLS > 0 ORDER BY o.INEFFECTIVE_CONTROLS DESC;

These patterns support audit committee reporting, SOX compliance tracking, and remediation prioritization. Because AMW is obsolete, most organizations migrating to newer GRC platforms extract this data historically.

Related Objects

The following objects are most significant to this table:

• AMW_AUDIT_PROJECTS – Parent engagement table; joined via AUDIT_PROJECT_ID.
• FND_SECURITY_GROUPS – Security isolation reference via SECURITY_GROUP_ID.
• FND_ORGANIZATIONS / HR_ALL_ORGANIZATION_UNITS – Organization definition source for ORGANIZATION_ID.
• AMW_AUDIT_SCOPE_PROCESSES / AMW_AUDIT_SCOPE_RISKS – Detail-level scope tables feeding the aggregate counts.
• AMW_EVALUATIONS / AMW_EVALUATION_OPINIONS – Opinion assignment referenced by EVALUATION_OPINION_ID.
• AMW_AUDIT_FINDINGS – Underlying source for OPEN_FINDINGS and OPEN_ISSUES counts.

These relationships confirm the table's role as a consolidated reporting layer within the Internal Controls Manager data model.