Search Results create_fnd_attachment

Overview

The APPS.AMW_LOAD_AUDIT_PROCEDURE_DATA package is a PL/SQL database object within the Oracle E-Business Suite (EBS) Audit Management module, part of the broader Governance, Risk, and Compliance (GRC) product family. In both release 12.1.1 and 12.2.2 the package retains a VALID status under the APPS schema, confirming it remains an active component of the delivered application code. Its primary business function is to load and staging-process audit procedure data — the structured questions, checklists, and opinion elements that auditors execute against an organisation's controls and business objects. The package bridges interface (staging) tables with the core Audit Management transactional model, applying the application's standard API conventions to validate, transform, and persist audit procedure content. Because it depends on FND_API and STANDARD, it conforms to the Oracle Application Object Library error-handling and return-status conventions (x_return_status, x_msg_count, x_msg_data) used throughout EBS public and private APIs.

Key Procedures and Functions

The ETRM metadata documents three procedures within the package body. Parameter lists are not published and are therefore not reproduced here; each entry describes purpose only.

• UPDATE_APR — Updates Audit Procedure related records, writing validated procedure content from the loading structures into the persistent Audit Management tables. It represents the primary write path for procedure data into the transactional schema.
• UPDATE_INTERFACE_WITH_ERROR — Marks or updates rows in the staging interface with error information when validation or loading fails. This supports the standard EBS interface-reprocessing pattern, allowing failed records to be identified, corrected, and resubmitted rather than silently discarded.
• CREATE_FND_ATTACHMENT — Creates an Oracle Application Object Library (FND) attachment, associating a document or file with the audit procedure record. This enables supporting evidence, working papers, or reference material to be linked to procedure data during the load process.

Tables Accessed

The package reads and writes a focused set of AMW tables through APPS synonyms:

• AMW_AUDIT_PROCEDURE_INTERFACE and AMW_AUDIT_PROCEDURE_INT_S — the inbound staging tables holding procedure data prior to validation and loading, and their distribution/sequence companion.
• AMW_AP_ASSOCIATIONS, AMW_AP_EXECUTIONS, AMW_AP_EXECUTIONS_S — link audit procedures to audit objects and store procedure execution results.
• AMW_CONTROLS_B and AMW_CONTROLS_TL — the base and translated control definition tables, providing context for procedures applied against controls.
• AMW_OPINION_COMPONTS_B, AMW_OPINION_DETAILS, AMW_OPINIONS, AMW_OPINIONS_S1, AMW_OPINIONS_S2, AMW_OPINIONS_LOG, AMW_OPINIONS_LOG_S, and AMW_OBJECT_OPINION_TYPES — the opinion model that captures audit conclusions and their component detail, together with the audit trail (log) tables that record changes.

Collectively these accesses show the package loading procedure definitions, resolving their associations and control references, and seeding the opinion structures and audit logs that record the outcome.

Usage Notes

This package is classified as OTHER (neither a fully public API nor a simple private routine) and is referenced by no other packages, indicating it is invoked directly rather than called as a library from other PL/SQL. Typical invocation paths are inbound data-loading concurrent programs, or form-driven actions in the Audit Management responsibilities that submit staged procedure data for processing. Because it depends on FND_API, callers should expect standard API return statuses and message-stack handling, and should inspect the interface table error columns populated by UPDATE_INTERFACE_WITH_ERROR when a load fails. Customisations should avoid modifying the delivered package; extension is preferably achieved by writing to the interface tables and re-invoking the standard loader.