Search Results create_amw_obj_assoc

Overview

AMW_LOAD_RC_DATA is a PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Risk Management and Compliance (formerly Enterprise Transaction Risk Management, ETRM) module. Its principal business purpose is to load and materialize risk and control data from interface and staging tables into the operational AMW base tables. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, which is significant for how it is called from concurrent programs and forms.

The package header carries the revision marker amwrclds.pls 120.0.12000000.1, dated 2007, indicating it is a mature component of the AMW data model that has remained stable across the 12.1.1 and 12.2.2 releases. Its procedures serve two broad functions: bulk conversion of interface records into risks, controls, objectives, assertions, and their associations, and direct creation of individual AMW records with associated lookups and privileges.

Key Procedures and Functions

• CREATE_RISKS_AND_CONTROLS — The primary driver procedure. It accepts a batch identifier and user identifier along with the standard concurrent program OUT parameters, and processes a set of interface records into risk and control records.
• UPDATE_INTERFACE_WITH_ERROR — Writes an error message back to the originating interface row, identified by table name and interface ID, so failed loads can be diagnosed and corrected.
• RISK_TYPES, CONTROL_OBJECTIVES, CONTROL_ASSERTIONS, CONTROL_COMPONENTS — Lookup and reference-data population procedures. Each accepts a flag and lookup tag, and the risk types procedure additionally accepts a flag indicating whether it is the last call in a sequence.
• CREATE_PROCESS_OBJECTIVES — Creates a process objective record from a supplied name, description, and requestor, returning a status indicator to the caller.
• CREATE_AMW_CTRL_ASSOC — Establishes an association between a control, a process, and a risk.
• CREATE_AMW_AP_ASSOC — Associates a control with an audit procedure and records design and operational effectiveness, returning status, message count, and message data.
• CREATE_AMW_OBJ_ASSOC — Links a process objective to one or more primary keys for a given object type, supporting control-to-objective associations.
• CREATE_AMW_RISK_ASSOC — Creates a risk association keyed on the risk identifier.
• ADD_OWNER_PRIVILEGE — Grants ownership-level access to the relevant AMW entity.
• CHECK_FUNCTION — Validates function security for the calling context.

Tables Accessed

The package reads and writes the core AMW entity and association tables through APPS synonyms. Control data is maintained in AMW_CONTROLS_B, AMW_CONTROLS_TL, and AMW_CONTROLS_TL_S1, with assertions in AMW_CONTROL_ASSERTIONS and AMW_CONTROL_ASSERTIONS_S and objectives in AMW_CONTROL_OBJECTIVES and AMW_CONTROL_OBJECTIVES_S. Association records are stored in AMW_CONTROL_ASSOCIATIONS, AMW_AP_ASSOCIATIONS, and AMW_OBJECTIVE_ASSOCIATIONS together with their _S shadow columns. Assessment and component data reside in AMW_ASSESSMENT_COMPONENTS, AMW_ASSESSMENT_COMPONENTS_S, and the component lookup procedures populate the corresponding control component structures. The dual use of base and _S tables reflects the standard EBS audit-trail implementation, in which the shadow table stores the original values of updated rows.

Usage Notes

The ETRM metadata records no packages referencing AMW_LOAD_RC_DATA, which indicates it is not called programmatically by other PL/SQL units but rather is invoked as a top-level entry point. The presence of ERRBUF, RETCODE, and batch ID parameters in CREATE_RISKS_AND_CONTROLS follows the standard Oracle concurrent program signature, so this procedure is most plausibly registered as a concurrent program used to load risk and control batches. The lookup procedures are typically called from Oracle Forms during migration or setup, while the individual CREATE_AMW_*_ASSOC procedures may be invoked from forms or custom code when associations are established interactively. Because the package executes with invoker's rights, the calling user must already hold the necessary privileges on the AMW tables. Customizations extending the load logic should call the documented procedures only, as the internal implementation is not part of the supported interface, and error handling should always inspect the returned status and message data.