Search Results amw_control

Overview

AMW_LOAD_CTRL_DATA is an Oracle E-Business Suite (EBS) PL/SQL package body owned by the APPS schema and belonging to the Oracle Internal Controls Manager / Audit Management Workbench (AMW) product family. Its principal business function is to load and process control data received through the AMW Risk-Control interface. The package header comment states that the major functionality "Reads the amw_risk-ctrl_interface table" and then performs controlled inserts and updates against the AMW base and translation tables that store risks, controls, control associations, risk associations, control objectives, and control assertions.

The package is classified as an OTHER API in ETRM for both 12.1.1 and 12.2.2. It is not a public, supported integration API; it is an internal loader invoked by the AMW data import framework. The import driver is identified by the constant v_import_func VARCHAR2(480) := 'AMW_DATA_IMPORT', and the expanded length reflects the FND mandate (increased from 30 to 480 characters in the 2005 revision by npanandi) for fully qualified function identifiers.

Key Procedures and Functions

The documented package exposes eight procedures and functions:

• CREATE_CONTROLS — the primary loader procedure. It reads rows from the AMW Risk-Control interface and creates the corresponding controls in the base and translation tables, applying approval-status logic.
• UPDATE_INTERFACE_WITH_ERROR — writes error messages back to the interface record when validation or processing fails, enabling the concurrent request to report per-row diagnostics.
• CONTROL_OBJECTIVES — loads and associates control objectives for the controls being imported.
• CONTROL_ASSERTIONS — loads and associates control assertions with the imported controls.
• CONTROL_COMPONENTS — loads component relationships for assessment components tied to controls.
• CONTROL_PURPOSES — loads the purposes (business reasons) associated with controls.
• ADD_OWNER_PRIVILEGE — grants the necessary owner or privilege records so that the imported control is accessible to the requestor.
• CHECK_FUNCTION — a helper used by the Has_Import_Privilege function to verify that the calling user holds the AMW_DATA_IMPORT function under an assigned responsibility.

The package also declares Has_Import_Privilege, which joins FND_RESPONSIBILITY, FND_COMPILED_MENU_FUNCTIONS, and FND_FORM_FUNCTIONS to determine whether the current user is authorized to perform the import. User and login context are captured from FND_GLOBAL.USER_ID and FND_GLOBAL.CONC_LOG_ID, and local booleans (v_error_found) and message variables track error state.

Tables Accessed

The loader inserts into and queries the following documented objects via APPS synonyms:

• AMW_CTRL_INTERFACE — the staging/interface table read for incoming control records and updated with error messages.
• AMW_CONTROLS_B — base table for control definitions.
• AMW_CONTROLS_TL — translation table for control names and descriptions.
• AMW_CONTROL_ASSOCIATIONS, AMW_CONTROL_OBJECTIVES, AMW_CONTROL_ASSERTIONS, AMW_CONTROL_PURPOSES — association detail tables populated by the corresponding procedures.
• AMW_ASSESSMENT_COMPONENTS and its _S sequence-backed tables, together with the various _S synonyms, used to obtain primary-key values during inserts.
• FND_RESPONSIBILITY, FND_COMPILED_MENU_FUNCTIONS, FND_FORM_FUNCTIONS — used by the privilege check function to validate that the importing user has the AMW_DATA_IMPORT function compiled under an active responsibility.

Usage Notes

AMW_LOAD_CTRL_DATA is not intended for direct invocation by customer code. It is called by the AMW data import routine (AMW_DATA_IMPORT) which is exposed as a concurrent program in Oracle Internal Controls Manager. The typical lifecycle is: a user populates the AMW Risk-Control interface table (via spreadsheet or flat-file upload), submits the import concurrent request, and the request invokes CREATE_CONTROLS and its subordinate procedures. Errors are written back to AMW_CTRL_INTERFACE through UPDATE_INTERFACE_WITH_ERROR, and successful rows may be deleted from the interface based on a profile option setting.

Because the package is documented as OTHER and is referenced by zero other packages in ETRM, it should be treated as an internal implementation detail. Customizations should rely on the supported AMW import interfaces and concurrent program rather than calling these procedures directly. In 12.2.2 the same structure applies; the Online Patching (adop) editioning model does not change the logical behavior, but custom code should never be applied to the APPS edition of these objects.