Results for “delete_audit_task_in_icm”

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

Overview

AMW_AUDIT_ENGAGEMENT_PVT is an Oracle Application Object Library (APPS) schema package belonging to the Oracle Enterprise Governance, Risk, and Compliance (EGRC) / Audit Management (AMW) product family. The "PVT" suffix designates this as a private implementation package: it encapsulates the low-level business logic that supports the public Audit Engagement APIs consumed by the Audit Management workbench and by external service layers. In Oracle EBS 12.1.1 and 12.2.2, this package functions as the procedural engine for creating, updating, and propagating audit engagements, audit tasks, and execution scopes between the Audit Management module and Oracle Projects (PA). It mediates the synchronization of engagement structures into project workplans, providing the mechanisms that keep audit task hierarchies, procedure scopes, and control associations consistent across the AMW data model.

The package is classified under ETRM with a PVT API classification and is validated (VALID status) in the APPS schema.

Key Procedures and Functions

The documented package body exposes twelve procedures and functions covering engagement and task lifecycle operations:

• COPY_SCOPE_FROM_ENGAGEMENT — Copies execution scope records from a source engagement to a target, establishing the baseline scope of procedures and controls under audit.
• CREATE_ENGAGEMENT_FOR_PA — Creates an engagement record intended for subsequent synchronization with Oracle Projects.
• CREATE_ENGAGEMENT_IN_PA — Creates the corresponding engagement representation within Oracle Projects.
• UPDATE_ENGAGEMENT_IN_PA — Propagates changes on an existing engagement to the Oracle Projects side.
• CREATE_AUDIT_TASK_IN_PA, UPDATE_AUDIT_TASK_IN_PA, and DELETE_AUDIT_TASK_IN_PA — Manage the lifecycle of individual audit tasks as they are mirrored into Oracle Projects workplans.
• DELETE_AUDIT_TASK_IN_ICM — Removes an audit task from the Integrated Compliance Management (ICM) context.
• IS_WORKPLAN_VERSION_SHARED — A boolean-style function that determines whether a workplan version is shared, typically used to guard update operations.
• CP_TASKS and CP_TASKS_ALL — Task-processing routines invoked in the concurrent program / bulk-processing context for one task or all tasks in scope.
• COPY_SCOPE_INEFF_CONTROLS — Copies scope entries associated with ineffective controls, supporting deficiency remediation workflows.

Tables Accessed

All tables are referenced through APPS synonyms. The package reads and writes base and translation tables in the AMW schema:

• AMW_AUDIT_PROJECTS and AMW_AUDIT_PROJECTS_S — Engagement (audit project) header and its sequence/attribute extensions.
• AMW_AUDIT_TASKS_B, AMW_AUDIT_TASKS_S, and AMW_AUDIT_TASKS_TL — Audit task base, extension, and translatable name/description records.
• AMW_AP_ASSOCIATIONS and AMW_AP_ASSOCIATIONS_S — The linkage records mapping audit entities to Oracle Projects artifacts; central to the PA synchronization procedures.
• AMW_EXECUTION_SCOPE and AMW_EXECUTION_SCOPE_S — Execution scope definitions used by the scope-copy routines.
• AMW_AUDIT_PROCEDURES_B and AMW_AUDIT_PROCEDURES_TL — Procedure definitions and translations constituting the audit methodology.
• AMW_CONTROL_ASSOCIATIONS — Links between procedures and controls, used by COPY_SCOPE_INEFF_CONTROLS.
• AMW_ENTITY_HIERARCHIES and AMW_ENTITY_HIERARCHIES_S — Organizational entity hierarchy definitions that scope engagements.
• AMW_PROCEDURES_S — Sequence/extension records for procedure entities.

Usage Notes

AMW_AUDIT_ENGAGEMENT_PVT is not intended for direct invocation by end users or custom code; it is a private package behind the Audit Management public API surface. It is typically invoked from the Audit Engagement and Audit Task forms, from the workplan synchronization concurrent programs that push engagement and task changes into Oracle Projects, and from intermediate public packages that wrap these procedures. Subscription against the package shows only self-reference and standard PL/SQL dependencies (SYS.STANDARD), and the ETRM metadata reports zero dependent packages, confirming its position as a leaf-level implementation unit. Because it manipulates engagement, task, scope, and association tables transactionally, any custom extension should call the supported public API rather than this PVT package, and the procedures should be invoked within a single logical transaction to preserve AMW-to-PA integrity.