Results for “amw_risks”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.AMW_LOAD_RCM_ORG_DATA package body is a data-loading and integration utility within the Oracle E-Business Suite Risk Management (ETRM / Oracle Advanced Controls) module. Its primary business function is to consume staged records from a risk and control interface table—referred to in the header comments as amw_risk-ctrl_interface—and to load them into the normalized Risk Management repository. In effect, it acts as the RCM (Risk and Control Matrix) import engine, transforming flat interface rows into fully associated risk, control, association, objective, and assertion records.

The package performs both inserts and updates. It inserts into the base and translation tables AMW_RISKS_B/AMW_RISKS_TL and AMW_CONTROLS_B/AMW_CONTROLS_TL, and it creates the relationship records in AMW_CONTROL_ASSOCIATIONS, AMW_RISK_ASSOCIATIONS, AMW_CONTROL_OBJECTIVES, and AMW_CONTROL_ASSERTIONS. After processing, it updates the interface table with error messages and, subject to a profile option, deletes rows that were successfully inserted. The header confirms the package was authored under ETRM and carries a version identifier dated 2006.

Key Procedures and Functions

The documented package exposes seventeen procedures and functions. At a high level they fall into a small number of functional groups:

• CREATE_RISKS_AND_CONTROLS — the principal driver that processes interface rows and creates the risk and control master records.
• UPDATE_INTERFACE_WITH_ERROR — writes validation or processing error messages back to the interface table for failed rows.
• RISK_TYPES — validates or resolves the risk type classification used during risk creation.
• CONTROL_OBJECTIVES and CONTROL_ASSERTIONS — populate the objective and assertion relationships associated with a control.
• CONTROL_COMPONENTS — handles assessment component linkage for a control.
• CREATE_PROCESS_OBJECTIVES — establishes process-level objective records.
• CREATE_AMW_CTRL_ASSOC, PROCESS_AP_CTRL_ASSOC_RCM, and PROCESS_AP_CTRL_ASSOC_ORG — build control associations, distinguishing RCM-scope from organization-scope processing.
• CREATE_AMW_AP_ASSOC, CREATE_AMW_OBJ_ASSOC, and CREATE_AMW_RISK_ASSOC — create the Action Plan, Objective, and Risk association records respectively.
• ADD_OWNER_PRIVILEGE — grants the appropriate owner-level data access privilege to the loaded records.
• CHECK_FUNCTION — performs a functional authorization/check step.
• CREATE_ENTITY_RISK and CREATE_ENTITY_CONTROL — create risk and control records tied to a specific organizational entity.

Private helper functions visible in the excerpt include Has_Import_Privilege, which verifies the invoking user holds the AMW_DATA_IMPORT privilege, and related validation routines that populate the v_*_msg and status variables used during exception handling.

Tables Accessed

Through APPS synonyms the package reads and writes the following documented tables:

• AMW_CONTROLS_B and AMW_CONTROLS_TL (and AMW_CONTROLS_TL_S1) — base and translation storage for control definitions.
• AMW_CONTROL_ASSOCIATIONS (+ _S) — links controls to the objects they address.
• AMW_CONTROL_ASSERTIONS (+ _S) — maps controls to financial assertions.
• AMW_CONTROL_OBJECTIVES (+ _S) — maps controls to objectives.
• AMW_AP_ASSOCIATIONS (+ _S) — action plan associations created for imported risks/controls.
• AMW_OBJECTIVE_ASSOCIATIONS (+ _S) — objective-level relationship records.
• AMW_ASSESSMENT_COMPONENTS (+ _S) — assessment component linkage used by CONTROL_COMPONENTS.

The package additionally updates the interface table and, per the header, inserts the AMW_RISKS_B/AMW_RISKS_TL and AMW_RISK_ASSOCIATIONS records, though those are documented at the procedure level rather than listed among the synonyms above.

Usage Notes

This package is a server-side loader rather than an end-user-facing API. It is typically invoked from a concurrent program or from custom integration code that first populates the risk/control interface table. Because it relies on FND_GLOBAL.USER_ID and FND_GLOBAL.CONC_LOGIN_ID for audit context, it is designed to run within an authenticated EBS session or a concurrent request. The package enforces the AMW_DATA_IMPORT privilege before performing any work, so the invoking user or the concurrent program's requestor must hold that function. After a successful pass it optionally purges successful interface rows according to a profile option, supporting repeatable bulk imports. In Oracle EBS 12.1.1 and 12.2.2 the package is classified as OTHER and is not referenced by any other documented package, so it should be treated as a top-level load utility called directly by import processes rather than as a shared dependency of the RCM runtime.