Results for “amw_entity_hierarchies_s”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMW_AUDIT_ENGAGEMENT_PVT is a private PL/SQL package body in the APPS schema that implements the core business logic for audit engagements within Oracle E-Business Suite's Enterprise Tax, Risk, and Compliance Management (ETRM) module, also marketed as Oracle Audit Vault and Internal Controls Manager (ICM). In the 12.1.1 and 12.2.2 releases, this package serves as the integration bridge between the audit engagement data model owned by the AMW (Audit Management Workbench) schema objects and the Oracle Projects foundation (PA) schemas. The package encapsulates the logic required to create and synchronize audit engagements, audit tasks, and engagement scope as Oracle Projects entities, ensuring that audit workplans are represented as projects and tasks with the correct associations to the underlying audit procedures and controls.

The "PVT" suffix signals that this is a private API: it is not intended as a public integration point, and its procedures are invoked internally by other AMW packages and by the Audit Engagement, Audit Task, and Scope forms. Its role is transactional and orchestration-oriented — it coordinates multi-table DML across audit projects, audit tasks, scope definitions, and Project Accounting (PA) interface tables within a single logical unit of work.

Key Procedures and Functions

• CREATE_ENGAGEMENT_FOR_PA and CREATE_ENGAGEMENT_IN_PA — Create the Oracle Projects representation of an audit engagement. The first variants prepare and stage engagement data; the second performs the actual project creation through the PA public APIs, establishing the linkage between the AMW_AUDIT_PROJECTS record and the corresponding PA_PROJECTS_ALL row.
• UPDATE_ENGAGEMENT_IN_PA — Propagates changes to an existing engagement, such as name, dates, or organizational attributes, to the underlying Project Accounting project.
• CREATE_AUDIT_TASK_IN_PA, UPDATE_AUDIT_TASK_IN_PA, and DELETE_AUDIT_TASK_IN_PA — Manage audit tasks as Oracle Projects tasks, keeping the AMW_AUDIT_TASKS_B/_TL records synchronized with PA_TASKS.
• DELETE_AUDIT_TASK_IN_ICM — Removes an audit task from the ICM data model itself, complementing the PA-side deletion.
• COPY_SCOPE_FROM_ENGAGEMENT and COPY_SCOPE_INEFF_CONTROLS — Replicate engagement scope definitions, including scope for ineffective controls, typically when rolling a scope forward to a new audit engagement or a new period.
• IS_WORKPLAN_VERSION_SHARED — A check function determining whether the current workplan version is shared, which governs whether certain destructive operations are permitted.
• CP_TASKS and CP_TASKS_ALL — Task-copying routines that duplicate task structures, supporting workplan templates and repetitive engagement setup.

Tables Accessed

The package reads and writes the AMW audit project tables (AMW_AUDIT_PROJECTS, AMW_AUDIT_PROJECTS_S) that hold engagement definitions. Audit procedures are sourced from AMW_AUDIT_PROCEDURES_B and _TL, procedures from AMW_PROCEDURES_S and AMW_PROCEDURE_REV_S, and tasks from AMW_AUDIT_TASKS_B, _TL, _S, and the AMW_AUDIT_TASKS_V view. Scope and control relationships reside in AMW_ENTITY_HIERARCHIES and AMW_ENTITY_HIERARCHIES_S, AMW_EXECUTION_SCOPE and _S, AMW_CONTROL_ASSOCIATIONS, and AMW_AP_ASSOCIATIONS and _S. On the Projects side the package interacts with PA_PROJECTS_ALL, PA_TASKS, PA_PROJECT_TYPES_ALL, and the PA public APIs (PA_PROJECT_PUB, PA_INTERFACE_UTILS_PUB, PA_PROJECT_STRUCTURE_UTILS, PA_WORKPLAN_ATTR_UTILS). Standard FND services (FND_API, FND_MSG_PUB, FND_GLOBAL, FND_ATTACHED_DOCUMENTS) support error handling, messaging, and attachments.

Usage Notes

AMW_AUDIT_ENGAGEMENT_PVT is not a supported public API and is not referenced by any other database object per the ETRM metadata. It is invoked internally — primarily by the Audit Engagement and Audit Task OAF/Forms pages and by sibling AMW packages such as AMW_SCOPE_PVT — when users create, update, or delete engagements and tasks that must be mirrored in Oracle Projects. Because engagement creation can fail at the PA interface stage, callers must handle FND_MSG_PUB error stacks. The documented count of 12 procedures/functions confirms that the package's surface is deliberately narrow and focused on PA synchronization and scope copying. The user search term "amw_entity_hierarchies_s" corresponds to the entity hierarchy shadow table consumed here for scope resolution, confirming that this package is the runtime consumer of that table when assembling engagement scope for Projects integration.