Search Results amw_load_ctrl_data




Overview
Explore in AI Chat

Overview

AMW_LOAD_CTRL_DATA is an Oracle Application Object Library package owned by the APPS schema that supports the loading and validation of control-related data within the Oracle E-Business Suite governance, risk, and compliance framework (the AMW module set, commonly associated with Application Management and internal controls functionality). Its principal business role is to move control definition data — controls, objectives, assertions, components, and purposes — from the interface staging table AMW_CTRL_INTERFACE into the corresponding base and translation tables, and to maintain the security and menu metadata that accompanies those records. The package is classified as OTHER in the ETRM registry, meaning it is not a published public API, and status is VALID. It has limited external coupling: it references only the SYS STANDARD package and is referenced by no other packaged objects, which indicates it is an internal utility rather than a shared library. A related identifier, AMW_LOAD_CTRL_DATA, also appears as the package's own name in the dependency listing, confirming self-containment.

Key Procedures and Functions

  • CREATE_CONTROLS — Creates control records from loaded interface data, writing into the base and translation control tables.
  • UPDATE_INTERFACE_WITH_ERROR — Flags or annotates rows in the interface staging table when validation or load processing fails, enabling error reporting to the caller.
  • CONTROL_OBJECTIVES — Handles the association between controls and the objectives they address.
  • CONTROL_ASSERTIONS — Manages the assertions linked to controls, maintaining the control-to-assertion relationships.
  • CONTROL_COMPONENTS — Processes control component definitions that are part of the assessment structure.
  • CONTROL_PURPOSES — Processes the purposes associated with controls.
  • ADD_OWNER_PRIVILEGE — Grants the necessary function or data privileges to an owner, touching the FND security tables.
  • CHECK_FUNCTION — Validates that a given function exists in the FND function catalog before referencing it.

The procedures collectively implement a load-and-validate pipeline: staging data is validated, base records are created, and the surrounding security metadata is provisioned. No parameter lists are documented, so signatures should not be assumed.

Tables Accessed

The package reads from and writes to the AMW control model. Base tables include AMW_CONTROLS_B, with translations in AMW_CONTROLS_TL and AMW_CONTROLS_TL_S1. Related definition tables are AMW_CONTROL_ASSERTIONS, AMW_CONTROL_OBJECTIVES, AMW_CONTROL_PURPOSES, and their respective _S security/MLS shadow tables (AMW_CONTROL_ASSERTIONS_S, AMW_CONTROL_OBJECTIVES_S, AMW_CONTROL_PURPOSES_S). Assessment structure data is held in AMW_ASSESSMENT_COMPONENTS and AMW_ASSESSMENT_COMPONENTS_S. Inbound data is read from AMW_CTRL_INTERFACE. For privilege and menu provisioning, the package consults FND_FORM_FUNCTIONS, FND_COMPILED_MENU_FUNCTIONS, and FND_RESPONSIBILITY. All are accessed through APPS synonyms.

Usage Notes

Because AMW_LOAD_CTRL_DATA is not a published API and is referenced by no other packages, it is normally invoked by the standard AMW control-loading concurrent program or by a form that drives the interface-to-base load. The typical sequence is: rows are populated in AMW_CTRL_INTERFACE by an external extraction or import process; the loading program calls CREATE_CONTROLS, which in turn calls the CONTROL_OBJECTIVES, CONTROL_ASSERTIONS, CONTROL_COMPONENTS, and CONTROL_PURPOSES routines; failures are recorded through UPDATE_INTERFACE_WITH_ERROR. ADD_OWNER_PRIVILEGE and CHECK_FUNCTION support the security side of the operation by validating and granting function access. Custom code should treat the package as internal and unsupported, calling it only if it must reproduce the standard load behavior, and should always stage data through AMW_CTRL_INTERFACE rather than writing directly to the AMW base tables. Behavior is consistent across EBS 12.1.1 and 12.2.2, where the AMW schema objects are unchanged in structure.