Search Results build_project_audit_task

Overview

AMW_SCOPE_PVT is a private PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that implements the scope-definition engine for Oracle Audit Management and Enterprise Risk Management (part of the Applications Technology / GRC family under the AMW module prefix). Its purpose is to build, maintain, and evaluate the "audit scope" — the set of organizations, subsidiaries, lines of business, and business processes that an audit project, control, or execution is permitted to cover. The package is classified as a private API (PVT), meaning it is an internal implementation layer not intended for direct customer invocation; public wrapper packages and concurrent programs call into it.

The scope model is hierarchical. Organizations roll up into parent-child hierarchies, business processes are organized into process hierarchies with top-level and parent process identifiers, and subsidiaries and lines of business provide an additional filtering dimension. AMW_SCOPE_PVT resolves these dimensions into denormalized association tables so that downstream audit execution, certification, and evaluation processes can query scope membership efficiently. It also enforces access control by determining which root organizations a user may access within a hierarchy.

Key Procedures and Functions

• ADD_SCOPE — Adds entities (subsidiaries, LOBs, organizations, processes) into an audit or execution scope, accepting the entity identifier and type along with subsidiary, LOB, and organization collections.
• REMOVE_FROM_SCOPE — The counterpart to ADD_SCOPE; removes previously added entities from the defined scope.
• REMOVE_ORGS_FROM_SCOPE — Specialized removal routine that strips organizations (and their dependent rows) from the scope.
• MANAGE_PROCESSES — Orchestrates insertion and maintenance of process-scope records for a given entity.
• INSERT_PROCESS — Inserts an individual process into the scope/association structures.
• POPULATE_SCOPE — Master routine that drives the full population of scope data for an entity.
• POPULATE_CUSTOM_HIERARCHY — Builds hierarchy rows when a custom (non-standard) organization hierarchy is used.
• POPULATE_PROCESS_HIERARCHY — Materializes the process hierarchy, including top process, parent process, process, and level identifiers.
• GENERATE_ORGANIZATION_LIST — Produces the list of organizations falling within scope.
• GENERATE_SUBSIDIARY_LIST — Produces the list of in-scope subsidiaries.
• GENERATE_LOB_LIST — Produces the list of in-scope lines of business.
• POPULATE_DENORMALIZED_TABLES — Flattens hierarchical scope data into denormalized tables for fast retrieval.
• POPULATE_PROJ_DENORM_TABLES — Project-specific variant of denormalization.
• POPULATE_ASSOCIATION_TABLES — Writes scope-to-entity association rows.
• BUILD_PROJECT_AUDIT_TASK — Creates audit task records tied to a project's scope.
• GET_ASSOC_TASK_ID — Retrieves the association/task identifier for a given context.
• FIND_CHILD_ORGS — Recursively determines child organizations beneath a parent.
• FIND_CHILD_OBJECTS — Generalization that locates child objects within the hierarchy.
• GET_ACCESSIBLE_ROOT_ORGS — Returns root organizations the current user may access.
• HAS_ORG_ACCESS_IN_HIER — Boolean-style check indicating whether an organization exists in the accessible hierarchy.

Tables Accessed

The package reads and writes AMW_AUDIT_SCOPE_ORGANIZATIONS and AMW_AUDIT_SCOPE_PROCESSES, which hold the authoritative scope membership for organizations and processes respectively. Association and control linkage is stored in AMW_AP_ASSOCIATIONS, AMW_AP_ASSOCIATIONS_S, AMW_CONTROL_ASSOCIATIONS, and AMW_CONTROL_ASSOCIATIONS_S. Task and procedure definitions come from AMW_AP_TASKS, AMW_AUDIT_PROCEDURES_B, and AMW_CONTROLS_B. Project context is held in AMW_AUDIT_PROJECTS, while execution-level scope uses AMW_EXECUTION_SCOPE and AMW_EXECUTION_SCOPE_S. Hierarchy definitions are read from AMW_ENTITY_HIERARCHIES and AMW_ENTITY_HIERARCHIES_S, and organization certification/evaluation summary data is drawn from AMW_ORG_CERT_EVAL_SUM. All are accessed through APPS synonyms.

Usage Notes

Because AMW_SCOPE_PVT is a private package, it is invoked indirectly. The Oracle Audit Management and ERM setup forms (organization, process, and scope definition screens) call the public AMW packages, which in turn delegate to these private routines. Concurrent programs that build or refresh audit scope and denormalized project tables invoke POPULATE_SCOPE and its related population procedures. The package is also referenced by three other PL/SQL packages, confirming its role as a shared internal service. Custom code should call the public API layer rather than AMW_SCOPE_PVT directly, since private signatures are subject to change across releases such as 12.1.1 and 12.2.2. The header indicates a stable lineage with the last substantive revision noted in 2008.