Search Results insert_risk_control_count




Overview
Explore in AI Chat

Overview

The APPS.AMW_RISK_CTRL_COUNT_PVT package is a private (PVT) PL/SQL API belonging to the Oracle E-Business Suite Enterprise Risk Management (formerly Treasury/ETRM) module. Its documented purpose is to create and register the association between a risk and a control within a given process and process organization — that is, to maintain the risk–control linkage records that underpin the risk assessment, control assessment, and risk register functionality. The _PVT suffix indicates that this is an internal implementation package rather than a public, customer-callable API; it is designed to be invoked by other ETRM packages or by the ETRM forms layer, which pass validated data down through it. The package header carries the version marker amwvrccs.pls 115.7, dated December 2003, confirming it is an early-generation (11i-era) ETRM component carried forward into 12.1.1 and 12.2.2 with the AUTHID CURRENT_USER clause.

Key Procedures and Functions

One documented program unit is exposed:

  • INSERT_RISK_CONTROL_COUNT — Inserts a risk–control count (association) record. The caller supplies the process, risk, control, and process organization identifiers, together with an association mode (defaulting to 'ASSOCIATE') and an object indicator (defaulting to 'RISK'). The procedure follows the standard Oracle EBS API contract: p_init_msg_list controls message-list initialization, p_commit controls whether the transaction is committed internally, p_validation_level governs the degree of validation applied, and p_api_version_number provides version compatibility checking. It returns the standard trio of x_return_status, x_msg_count, and x_msg_data so callers can inspect success, warning, or error outcome and retrieve any error messages. Parameters are declared with NOCOPY on the OUT arguments for performance.

Tables Accessed

The ETRM metadata records no directly referenced tables via APPS synonyms for this package. In practice, a risk–control association insertion of this nature operates against the ETRM risk-control mapping tables (the risk/control association entities owned by the AMW_ schema objects) and may consult process and organization setup tables to validate the incoming identifiers. Because the metadata lists no explicit table references and no dependent packages are recorded, the precise physical object names cannot be confirmed from the supplied documentation and should be verified against the live data dictionary for the specific instance.

Usage Notes

As a private API, AMW_RISK_CTRL_COUNT_PVT is not intended for direct invocation by customers. It is typically called by higher-level ETRM public APIs or the ETRM HTML/Forms user interface when a user creates or modifies a risk–control relationship. The association mode parameter allows the same procedure to serve both associate and, potentially, dissociate operations, while the object parameter distinguishes whether the operation is anchored to a risk or another entity such as a control or process. Because the header was supplied in full, developers integrating custom ETRM extensions should mirror the standard EBS exception-handling pattern: call the procedure, branch on x_return_status, and drain the message stack using FND_MSG_PUB when x_msg_count is greater than zero. The ETRM metadata states the package is referenced by zero other packages, which suggests its callers are the application's UI layer or form-level logic rather than other PL/SQL APIs.