Search Results amw_utility_pvt




Overview
Explore in AI Chat

Overview

AMW_UTILITY_PVT is the private utility package body for the Oracle E-Business Suite Audit Management (AMW) module, part of the Governance, Risk, and Compliance (GRC) product family. In EBS 12.1.1 and 12.2.2, the AMW schema family supports internal audit planning, audit project execution, risk and control assessment, and opinion tracking. AMW_UTILITY_PVT centralizes the low-level helper logic that the public AMW APIs depend on, which is why it is classified as a PVT (private) API package — it is not intended as a public integration surface, but rather as the shared internal toolbox for the module.

The package has a status of VALID in the APPS schema and is instantiated as a PACKAGE BODY. ETRM documentation records 51 documented procedures and functions, and the package is referenced by 42 other database objects. Notably, AMW_UTILITY_PVT is not referenced by any database object upward — it is a leaf consumer of AMW, FND, WF, ENG, and XDO infrastructure, not a provider to them.

Key Procedures and Functions

The 51 documented routines fall into four functional clusters.

Parameter lists are intentionally omitted here; the routines are described by purpose only.

Tables Accessed

The package reads and writes a broad set of AMW base and view objects through APPS synonyms. Key base tables include AMW_AUDIT_PROJECTS (audit project headers), AMW_CONTROL_ASSOCIATIONS (linkages between controls and other entities), AMW_EXCEPTIONS_B and AMW_EXCEPTIONS_TL (exception headers and translated text), AMW_EXCEPTIONS_REASONS (exception rationale), AMW_EXECUTION_SCOPE (scope definitions for audit execution), AMW_LATEST_HIERARCHIES (current hierarchy snapshots), AMW_OBJECTIVE_ASSOCIATIONS (objective linkages), AMW_OBJECT_OPINION_TYPES (opinion type mapping), AMW_OPINION_TYPES_B (opinion type definitions), AMW_PARAMETERS (module configuration), AMW_PROCESS (process headers), AMW_PROCESS_LOCKS (concurrency control on processes), AMW_PROCESS_NAMES_TL (translated process names), and AMW_PROCESS_ORGANIZATION (process-to-organization mapping).

It also joins a large set of AMW views — including AMW_AUDIT_UNITS_V, AMW_CONTROLS_ALL_VL, AMW_EMPLOYEES_CURRENT_V, AMW_OPINIONS_V, AMW_PROCESS_OBJECTIVES_VL, AMW_PROCESS_VL, AMW_RISKS_ALL_VL, and AMW_PROC_HIERARCHY_DENORM — reflecting its role as a cross-cutting utility layer. FND infrastructure objects (FND_MESSAGE, FND_MSG_PUB, FND_LOG, FND_PROFILE, FND_REQUEST, FND_CONCURRENT, FND_LOOKUP_VALUES, FND_FLEX_VALUES) supply messaging, concurrency, profile, and flexfield services. Workflow (WF_NOTIFICATION, WF_ACTIVITIES, WF_DIRECTORY), engineering change (ENG_ENGINEERING_CHANGES, ENG_CHANGE_SUBJECTS), and XDO_TEMPLATES_B are also referenced.

Usage Notes

AMW_UTILITY_PVT is invoked indirectly by the public AMW APIs and by the Audit Management OAF pages and concurrent programs that call those APIs. It is not exposed to end users and should not be called directly from custom code, because its signatures are not part of the supported public interface and may change between point releases. Customizations that require AMW validation, messaging, or lookup resolution should instead call the corresponding public AMW package procedures. The presence of FND_LOG and FND_MSG_PUB references means AMW_UTILITY_PVT participates in standard EBS logging and message-stack handling, so its DEBUG_MESSAGE and ERROR_MESSAGE routines will honor the current FND_LOG level and FND profile settings. Because the package is not referenced by any database object, it can be recompiled at any time without invalidating dependents, but changes to its body are still subject to Oracle's standard patching and licensing terms.