Search Results amw_control_assertions_s

Overview

AMW_CONTROLS_PAGE_PKG is an Oracle E-Business Suite package body residing in the APPS schema that supports the Oracle Internal Controls Manager (formerly part of the Enterprise Technical Reference Model / ETRM governance toolset). Its primary business role is to manage the presentation and validation logic behind the Controls workbench pages used during the definition and assessment of internal controls, objectives, assertions, and the associations that tie them together. Within the 12.1.1 and 12.2.2 releases, the package serves as a server-side engine that determines whether control records are complete and valid before they are written to the underlying AMW tables, and it orchestrates the creation, modification, and deletion of control relationships.

The package is classified as an API of type OTHER. It carries no invalid status and is reported as VALID in the object repository, and it is not referenced by any other database object, indicating that its public entry points are consumed directly by application forms and workflow rather than by dependent PL/SQL callers. It does, however, depend upon AMW_UTILITY_PVT and numerous FND public utilities, so its runtime behavior is tied to the standard EBS forms and message infrastructure.

Key Procedures and Functions

The package exposes twenty-four documented procedures and functions. They fall into several functional groups and, taken together, provide the validation and data-maintenance operations that back the Controls user interface.

• Presence and validation checks: OBJECTIVE_PRESENT, NEW_OBJECTIVE_PRESENT, PREVENTIVE_CONTROL_PRESENT, ASSERTION_PRESENT, NEW_ASSERTION_PRESENT, COMPONENT_PRESENT, and NEW_COMPONENT_PRESENT verify whether the required objective, control, assertion, or assessment component exists for the current transaction context. The "NEW_" variants are used during record creation to confirm the incoming value before insertion.
• Association maintenance: ASSOCIATION_EXISTS tests whether a relationship already exists, while DELETE_CONTROL_ASSOCIATION and DELETE_OBJ_ASSERT_COMP remove existing control-to-objective and objective-to-assertion-to-component links. PROCESS_OBJECTIVE, PROCESS_ASSERTION, and PROCESS_COMPONENT insert or update these parent and child records.
• Lookup and attribute retrieval: GET_LOOKUP_VALUE and GET_UOM_TL return descriptive and translated values, and GET_OBJ retrieves an objective record. GET_CONTROL_SOURCE identifies the origin of a control definition.
• Control decision support: IS_CONTROL_EFFECTIVE evaluates whether a control satisfies effectiveness criteria, and GET_POLICY returns policy information associated with a control.
• Workflow and configuration: IS_WKFLW_APPR_DISBLD indicates whether workflow approval has been disabled for the current context.

Tables Accessed

The package reads and writes the core Internal Controls Manager base and translation tables through APPS synonyms. The control definition tables AMW_CONTROLS_B and AMW_CONTROLS_ALL_VL hold the master control records, while AMW_CONTROL_ASSERTIONS and AMW_CONTROL_ASSERTIONS_S store assertions and their translation rows. Objectives are stored in AMW_CONTROL_OBJECTIVES and AMW_CONTROL_OBJECTIVES_S, and purposes in AMW_CONTROL_PURPOSES and AMW_CONTROL_PURPOSES_S. Assessment components are held in AMW_ASSESSMENT_COMPONENTS and AMW_ASSESSMENT_COMPONENTS_S. The junction tables AMW_CONTROL_ASSOCIATIONS and AMW_OBJECTIVE_ASSOCIATIONS record the many-to-many links the package maintains. AMW_OPINIONS supplies audit opinion data, and AMW_PROCESS supports process-related context.

Reference and cross-application data are also accessed, including AMW_CONSTRAINTS_VL, AMW_CONTROLS_ALL_VL, AMW_LOOKUPS, FND_LOOKUPS, FND_APPLICATION_VL, FND_FORM_FUNCTIONS_VL, FND_CONCURRENT_PROGRAMS_VL, FND_PROFILE_OPTIONS_VL, FND_PRODUCT_INSTALLATIONS, and the BIS measures and XML publisher indicators BIS_APPLICATION_MEASURES, BIS_INDICATORS, and BIS_INDICATORS_TL. Workflow activities are checked through WF_ACTIVITIES_VL. The FND_API, FND_GLOBAL, FND_MSG_PUB, and FND_PROFILE packages provide the standard API, session, message, and profile services.

Usage Notes

AMW_CONTROLS_PAGE_PKG is primarily invoked from the Internal Controls Manager forms that implement the Controls, Objectives, Assertions, and Components pages. The presence-check functions are typically called during WHEN-VALIDATE-ITEM and pre-save processing to enforce completeness before records are committed, while PROCESS_OBJECTIVE, PROCESS_ASSERTION, and PROCESS_COMPONENT handle the save logic. DELETE_CONTROL_ASSOCIATION and DELETE_OBJ_ASSERT_COMP support delete and detach operations from the same forms.

Because the package is not referenced by any other database object, custom development should call its public procedures directly rather than relying on an intermediate wrapper. Profile and lookup dependencies mean that behavior can be modified through standard EBS profile options and lookup values, and workflow-related checks will reflect the approval configuration at runtime. Consistent with its documented role, the package should be treated as a supporting API for the AMW controls pages rather than as a general-purpose integration interface.