Search Results amw_ap_executions_s

Overview

AMW_LOAD_AUDIT_PROCEDURE_DATA is a PL/SQL package body owned by the APPS schema that supports the Oracle E-Business Suite Audit Management module (AMW), part of the Enterprise Risk and Compliance Management (ETRM) family of applications. Its principal business role is to load, validate, and persist audit procedure definitions and related audit execution data into the ETRM transactional schema. In practice, the package acts as a staging-to-production loader: it consumes records held in the audit procedure interface tables (AMW_AUDIT_PROCEDURE_INTERFACE, AMW_AUDIT_PROCEDURE_INT_S), applies business validation against audit procedures, controls, projects, tasks, and units, and then writes the validated results into the base Audit Management tables. It additionally maintains the audit opinion structures that capture auditor conclusions, findings, and supporting details, and it can attach supporting documents to the corresponding FND document framework entities.

The object is documented as VALID in ETRM 12.1.1 and remains valid in the 12.2.x application editions. It is an "OTHER"-classified API rather than a public, fully versioned open interface, and it is not referenced by any other database object, indicating it is invoked directly by concurrent programs or form-driven logic rather than by dependent PL/SQL callers.

Key Procedures and Functions

The package body exposes three documented procedures:

• UPDATE_APR — Updates the audit procedure record. This is the core persistence routine that moves validated interface data into the base audit procedure and auditable entity structures, reflecting changes to audit procedures, associated controls, and any related execution records.
• UPDATE_INTERFACE_WITH_ERROR — Writes error information back onto the interface rows. When validation or loading fails, this procedure stamps the offending interface record with the appropriate error status/message so that users or administrators can review and correct the rejected data through the interface.
• CREATE_FND_ATTACHMENT — Creates an attachment in the Oracle Application Object Library document framework. It registers a document (using the FND_DOCUMENTS / FND_ATTACHED_DOCUMENTS objects) and links it to the relevant ETRM entity so that supporting evidence or documentation accompanies the audit procedure record.

No parameter signatures are published in the ETRM metadata; the descriptions above reflect the operational purpose of each routine.

Tables Accessed

The package touches a broad set of AMW base and interface tables plus Oracle Application Framework objects. Interface and load tables include AMW_AUDIT_PROCEDURE_INTERFACE and its synonym AMW_AUDIT_PROCEDURE_INT_S (the object the user searched for), which hold inbound procedure records and their error status. Audit execution data is read from and written to AMW_AP_EXECUTIONS, AMW_AP_EXECUTIONS_S, and AMW_AP_ASSOCIATIONS, while audit procedure, step, project, task, and unit definitions are resolved from AMW_AUDIT_PROCEDURES_VL, AMW_AP_STEPS_VL, AMW_AUDIT_PROJECTS_V, AMW_AUDIT_TASKS_V, and AMW_AUDIT_UNITS_V. Controls are validated against AMW_CONTROLS_B and AMW_CONTROLS_TL.

Audit opinion data is maintained across AMW_OPINIONS, AMW_OPINIONS_S1, AMW_OPINIONS_S2, AMW_OPINIONS_LOG, AMW_OPINIONS_LOG_S, AMW_OPINION_TYPES_B, AMW_OBJECT_OPINION_TYPES, AMW_OPINION_COMPONTS_B, AMW_OPINION_DETAILS, AMW_OPINION_DETAILS_S1, and the log detail tables. Attachment metadata is stored in FND_ATTACHED_DOCUMENTS, FND_ATTACHED_DOCUMENTS_S, FND_DOCUMENTS_TL, FND_DOCUMENTS_SHORT_TEXT, FND_OBJECTS, and FND_USER. Utility and messaging helpers include AMW_UTILITY_PVT, FND_API, FND_GLOBAL, FND_MSG_PUB, and FND_FILE.

Usage Notes

AMW_LOAD_AUDIT_PROCEDURE_DATA is typically invoked from an ETRM concurrent program or a supporting form that performs the audit procedure load. It is designed to run under the APPS schema with a valid FND_GLOBAL session context, since it relies on FND_GLOBAL for user and responsibility identification. Because it is not called by other database objects, it should be treated as an entry-point program rather than a reusable library. The presence of FND_FILE and FND_MSG_PUB indicates it writes log/output and raises messages through the standard EBS messaging framework. When troubleshooting failed loads, the primary diagnostic path is to inspect error rows flagged by UPDATE_INTERFACE_WITH_ERROR, correct the source data in the interface table, and re-run the loader. Customizations should avoid modifying this package directly; instead, extensions should be built against separate custom logic to preserve upgrade safety across 12.1.1 and 12.2.2.