Search Results amw_object_assessments_pvt

Overview

AMW_OBJECT_ASSESSMENTS_PVT is a private (PVT) PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Asset Management (Enterprise Asset Management / eAM) module family identified by the AMW prefix. Its business purpose is to encapsulate the low-level data manipulation logic for object assessments—the records that link an assessment definition to a specific object type within the ETRM (Enterprise Transaction and Reference Model) framework. In EBS 12.1.1 and 12.2.2 the package acts as the private implementation layer behind the assessment data model, providing the create, update, remove and existence-check operations used by higher-level public APIs, concurrent programs, or Oracle Forms that manage assessment assignments against objects.

As a PVT package, it is not intended to be called directly by customer code; instead it exposes a stable internal interface (including FND_API-compliant signatures such as the standard p_api_version_number, p_init_msg_list, p_commit and x_return_status/x_msg_count/x_msg_data parameters seen in CREATE_OBJECT_ASSESSMENT) so that other APPS packages can invoke its operations consistently. The header comment shows a source version of 120.0 dated 2005, reflecting a comparatively old but stable code line carried forward into the 12.x releases.

Key Procedures and Functions

• check_object_assess_exists — A function that determines whether an assessment already exists for a given assessment identifier and object type combination. It queries the base table and returns a simple Y/N flag, treating NO_DATA_FOUND as 'N' and TOO_MANY_ROWS as 'Y'. This is the standard guard routine used before insert or update operations.
• create_object_assessment — A procedure that inserts a new object assessment record. It follows the Oracle EBS PL/SQL API standard: an API compatibility check via FND_API.Compatible_API_Call, conditional message-list initialization through FND_MSG_PUB.initialize, and use of a SAVEPOINT for transactional control. It accepts the object type, assessment ID, certification ID, organization ID and process ID as inputs.
• update_object_assessment — A procedure that modifies an existing object assessment. This is the routine most relevant to the user search term "update_object"; it is the documented entry point for changing assessment attributes on an existing record. As with the create API, it adheres to the FND_API interface conventions.
• remove_object_assessment — A procedure that deletes or logically removes an object assessment for a specified assessment/object type. It completes the CRUD lifecycle of the assessment entity.

Tables Accessed

• AMW_OBJECT_ASSESSMENTS — The primary transactional table holding assessment-to-object relationships. The existence-check function reads it, and the create/update/remove procedures write to it.
• AMW_OBJECT_ASSESSMENTS_S — The corresponding sequence (or shadow) object referenced by the package, used to generate primary key values when new assessment rows are inserted.
• DUAL — Referenced for lightweight PL/SQL expressions and validation logic. All tables are accessed through APPS synonyms.

Usage Notes

The package is typically invoked by the public API layer or by Oracle Forms that maintain assessment data, and by concurrent programs performing bulk assessment maintenance. Because it is classified PVT, customizations should avoid calling it directly and instead use the corresponding public API; direct calls risk bypassing validation and message-handling conventions. The metadata records zero dependent packages, indicating it is a leaf-level utility in the dependency chain. When troubleshooting an "update_object" or similar assessment error, verify the assessment_id and object_type combination exists first via check_object_assess_exists before invoking update_object_assessment, and confirm the SAVEPOINT/commit behavior matches the calling program's transaction scope.