Search Results amw_risk_ctrl_count_pvt

Overview

AMW_RISK_CTRL_COUNT_PVT is a private (PVT) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Enterprise Trade Management / Advanced Pricing (AMW) module family, whose packages are conventionally prefixed with "AMW_" and organized into a public specification package and a corresponding private package body. In the ETRM architecture, the "PVT" suffix denotes a private implementation package that contains the core business logic invoked by its public wrapper; private packages are not intended to be called directly by external code.

The package's documented purpose centers on risk control counting within the trade management and pricing domain. Risk controls are the rules that constrain pricing, discounting, and quoting behavior for a given process or organization, and the "count" semantics indicate that this package maintains quantitative tracking of risk control records. The source header confirms this is a relatively stable component, carrying the RCS revision string "$Header: amwvrccb.pls 115.9 2003/12/03" — indicating the package has been largely unchanged since the 11i era and is carried forward essentially intact into EBS 12.1.1 and 12.2.2. This is typical of many AMW private packages, which were stabilized early and then inherited by later releases without functional modification.

Key Procedures and Functions

The ETRM metadata documents a single procedure in this package:

• INSERT_RISK_CONTROL_COUNT — The only documented procedure. Its evident purpose is to create a new risk control count record, that is, to persist a counting entry associated with a risk control within the trade management model. This procedure is the package's principal write operation and would be invoked by the public wrapper package (AMW_RISK_CTRL_COUNT_PUB) after validation and business-rule checks have been performed.

Although the source excerpt shows only the beginning of INSERT_RISK_CONTROL_COUNT's parameter list, the surrounding comments reference additional declarations and a separate procedure, Process_Process_Hierarchy, along with parameters such as p_process_id, p_organization_id, p_mode, p_apo_type, and the standard FND_API parameters (p_commit, p_validation_level, p_init_msg_list, x_return_status, x_msg_count, x_msg_data). These elements are documented in the package's internal comments but the metadata confirms only INSERT_RISK_CONTROL_COUNT as a defined procedure. The standardized FND_API parameter set, where present, indicates the package adheres to the Oracle Application Object Library (AOA) API conventions for error handling, message stacking, and transactional commit control.

Tables Accessed

The documented ETRM metadata lists no base tables referenced via APPS synonyms for this package. This absence is notable and can be attributed to one of two circumstances: either the package performs its insert operations through a view or a public package rather than directly against a base table, or the dependency metadata was not captured for this particular PL/SQL unit. In practice, a procedure named INSERT_RISK_CONTROL_COUNT would be expected to write to a table storing risk-control count data, most plausibly a table bearing a name similar to AMW_RISK_CTRL_COUNTS or an underlying ETRM risk control table. Because no tables are documented, integrators should treat the persistence target as implementation-dependent and verify it against the actual database before building any dependent logic.

Usage Notes

As a PVT-class package, AMW_RISK_CTRL_COUNT_PVT is not a supported integration point. The ETRM metadata records that zero other packages reference this package, and its single documented procedure is not exposed as a standalone public API. The conventional invocation path is indirect: ETRM application forms, concurrent programs, or the public package AMW_RISK_CTRL_COUNT_PUB call into this private body. The package initializes package-level globals for g_pkg_name, g_file_name, g_user_id, and g_login_id at load time, using FND_GLOBAL to capture the session user and concurrent login identifiers — a standard pattern for capturing audit context.

When the search term "check_apo_row" is used, it is worth noting that no such routine is documented in this package's metadata; it is neither a listed procedure nor a referenced object. Users investigating "check_apo_row" should inspect other AMW packages, particularly those handling APO (Advanced Planning and Optimization) row validation. For AMW_RISK_CTRL_COUNT_PVT specifically, custom code should avoid direct invocation. Any required extension should be built against the public wrapper or through supported ETRM APIs, preserving the isolation that the PVT naming convention is designed to enforce across both 12.1.1 and 12.2.2.