Search Results amw_load_ap_data




Overview
Explore in AI Chat

Overview

AMW_LOAD_AP_DATA is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, catalogued under the ETRM (E-Business Suite Technical Reference Manual) with an API classification of OTHER. It forms part of the Audit Management Workbench (AMW) module, which provides the infrastructure for maintaining audit procedures, audit owners, and security privileges within the EBS environment. The package functions as a data-loading and setup utility: it migrates audit procedure definitions into the AMW interface tables and resolves the function and responsibility metadata required to secure and expose those audit procedures through the application's menu and security model.

The dependency list confirms that the package is a consumer rather than a provider of services — it is not referenced by any other database object. It depends on AMW_AP_INTERFACE, the AMW audit procedure base, translation, and view objects (AMW_AUDIT_PROCEDURES_B, _TL, _VL, _PVT), AMW_EMPLOYEES_CURRENT_V, and the AMW security and utility packages (AMW_SECURITY_PUB, AMW_UTILITY_PVT). On the technology-stack side it relies heavily on FND foundation APIs and views, including FND_API, FND_FILE, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, FND_FORM_FUNCTIONS, FND_COMPILED_MENU_FUNCTIONS, FND_RESPONSIBILITY, FND_RESP_FUNCTIONS, FND_USER, and FND_DATA_SECURITY.

Key Procedures and Functions

Four documented program units are exposed by the package:

  • CREATE_AUDIT_PROCEDURES — The primary driver routine. It loads audit procedure records from the AMW interface staging table into the permanent AMW audit procedure tables, establishing the base and translated definitions used by the Audit Management Workbench.
  • UPDATE_INTERFACE_WITH_ERROR — A controlled error-handling routine that writes validation or processing failures back to the AMW_AP_INTERFACE staging record, allowing rejected rows to be identified, corrected, and re-submitted rather than silently discarded.
  • ADD_OWNER_PRIVILEGE — Grants ownership-level data security privileges in support of AMW security. It aligns with the package's use of FND_DATA_SECURITY and FND_USER to ensure that designated audit owners can access the procedures they are responsible for.
  • CHECK_FUNCTION — A validation utility that verifies the existence and correctness of function definitions in FND_FORM_FUNCTIONS and FND_COMPILED_MENU_FUNCTIONS, typically before the package registers or updates menu-function associations.

Tables Accessed

The package reads and writes several categories of data. AMW_AP_INTERFACE acts as the inbound staging area for audit procedure loads, with error rows updated in place. AMW_AUDIT_PROCEDURES_B stores the base (untranslated) audit procedure definitions, while AMW_AUDIT_PROCEDURES_TL holds the language-specific translated name and description rows; the _VL view presents both. FND_COMPILED_MENU_FUNCTIONS, FND_FORM_FUNCTIONS, FND_RESPONSIBILITY, and FND_RESP_FUNCTIONS are consulted or updated to establish the function and responsibility mappings that expose audit procedures to the correct users and menus. FND_USER is referenced for owner and privilege resolution in conjunction with the ADD_OWNER_PRIVILEGE routine.

Usage Notes

AMW_LOAD_AP_DATA is an internal setup and administration package. It is not a public API and is not invoked by any other database object; instead it is executed through AMW setup forms, concurrent programs, or one-off SQL*Plus / custom wrapper scripts during implementation and data-migration activities. Typical invocations include loading audit procedures from external or legacy sources via AMW_AP_INTERFACE, bootstrapping audit owners and their privileges, and validating function metadata before menu entries are compiled. Because the package calls FND_FILE, output is generally directed to the concurrent manager log and output files. The presence of FND_MSG_PUB and FND_API indicates the standard EBS error-stack convention: callers should check the message stack after execution rather than relying solely on return codes, and any rows written to AMW_AP_INTERFACE with errors should be corrected and reprocessed.