Search Results amw_execution_scope_pk

Overview

AMW_EXECUTION_SCOPE is a transactional table in the AMW (Internal Controls Manager) product schema of Oracle E-Business Suite, holding the execution scope defined for audit projects and process certification activities. In EBS releases 12.1.1 and 12.2.2, this table acts as the central record of which organizational entities, levels, and processes are included within a given certification or audit execution. It therefore governs what an auditor, process owner, or certifier is expected to review and sign off on during a certification cycle.

Under a heuristic Data Vault classification derived from its foreign key structure, AMW_EXECUTION_SCOPE presents a satellite-leaning profile. This is a modeling suggestion only: the table carries descriptive and contextual attributes about a scope, while its relationships to certification and organization entities suggest it could also be represented as a link in a fully normalized Data Vault design. Practically, ETRM documents this as a standard EBS table owned by AMW with 38 physical columns.

Key Information Stored

The table is anchored by the surrogate primary key EXECUTION_SCOPE_ID (constraint AMW_EXECUTION_SCOPE_PK). A unique index, AMW_EXECUTION_SCOPE_U1, also exists on EXECUTION_SCOPE_ID, confirming it as the principal business-key candidate for row identification.

The most significant columns include:

• ENTITY_TYPE and ENTITY_ID — identify the organizational entity in scope. ENTITY_ID carries a foreign key to AMW_CERTIFICATION_B.
• LEVEL_ID — references MSD_LEVELS, indicating the hierarchy or process level associated with the scope.
• TOP_PROCESS_ID, PARENT_PROCESS_ID, and PROCESS_ID — define the process hierarchy included in the execution scope.
• SCOPE_CHANGED_STATUS and SCOPE_MODIFIED_DATE — track whether the scope has been altered and when, supporting change audit.
• ORGANIZATION_ID and PROCESS_ORG_REV_ID — bind the scope to a specific organization and its process revision.
• SUBSIDIARY_VS, SUBSIDIARY_CODE, LOB_VS, and LOB_CODE — capture subsidiary and line-of-business value-set and code context.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, enforcing data security partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — provide the standard EBS flexfield DFF columns for client-specific extension.
• OBJECT_VERSION_NUMBER — supports optimistic locking and concurrent update control.
• The standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) record audit history.

Common Use Cases and Queries

Typical usage centers on evaluating what is in scope for a certification cycle. Analysts often join AMW_EXECUTION_SCOPE to AMW_CERTIFICATION_B on ENTITY_ID to correlate scope entries with certification definitions:

• Scope listing for a certification: SELECT s.EXECUTION_SCOPE_ID, s.ENTITY_ID, s.PROCESS_ID, s.SCOPE_CHANGED_STATUS FROM AMW_EXECUTION_SCOPE s WHERE s.ENTITY_ID = :cert_id;
• Detecting scope changes: Filter on SCOPE_CHANGED_STATUS and SCOPE_MODIFIED_DATE to identify scopes amended after initial setup.
• Process hierarchy reporting: Self-join on PARENT_PROCESS_ID and PROCESS_ID to reconstruct the scoped process tree.
• Security-scoped extracts: Restrict by SECURITY_GROUP_ID for organization-specific reporting.

Related Objects

The significant related objects, grounded in documented foreign keys, are:

• AMW_CERTIFICATION_B — referenced via AMW_EXECUTION_SCOPE.ENTITY_ID; provides the certification header definition.
• MSD_LEVELS — referenced via LEVEL_ID; supplies level definitions used in the scope hierarchy.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces row-level security partitioning.
• AMW_EXECUTION_SCOPE_PK — the primary key constraint enforcing EXECUTION_SCOPE_ID uniqueness.
• AMW_EXECUTION_SCOPE_U1 — unique index reinforcing the primary identifier.