Search Results get_line_conclusion_code




Overview
Explore in AI Chat

Overview

AMW_EVALUATIONS_PKG is a public PL/SQL package in the APPS schema that encapsulates the persistence and retrieval logic for evaluation records within Oracle Enterprise Asset Management (eAM), part of the Enterprise Asset Management (EAM) module in Oracle EBS 12.1.1 and 12.2.2. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute with the privileges of the calling user rather than the package owner, and it relies on APPS synonyms for all underlying tables. Its primary purpose is to support quality or assessment evaluations performed against assets, work orders, and related maintenance objects: creating evaluation header and detail rows, resolving effectiveness and conclusion values, and enforcing ownership and executor security checks.

The package is small, with ten documented procedures and functions, and is not referenced by any other packaged API, indicating it is intended for direct invocation from the eAM application forms, concurrent programs, or customer extensions rather than as an internal dependency of other PL/SQL units.

Key Procedures and Functions

The single documented procedure, INSERT_ROW, is the main data-creation entry point. It accepts the evaluation set identifier, the evaluated object name and context, the evaluation type and date, a five-part composite primary key (PK1_VALUE through PK5_VALUE), entered-by and executed-by identifiers, comments, the effectiveness attributes (description, operation, and overall), a process mode, an evaluation identifier, and standard FND_API messaging parameters. Per the header comment dated 12.31.2003 (bug 3326347), the date evaluated parameter was changed from VARCHAR2 to DATE, a compatibility consideration for any legacy custom code.

The remaining documented objects are query functions with well-defined single responsibilities:

  • GET_OP_EFFECTIVENESS and GET_OP_EFFECTIVENESS_CODE — return the operational effectiveness of an evaluation, the coded variant returning the lookup code value rather than the display meaning. This pair is the object of the user's search term.
  • GET_DES_EFFECTIVENESS and GET_DES_EFFECTIVENESS_CODE — return the description effectiveness and its coded equivalent.
  • GET_LINE_CONCLUSION and GET_LINE_CONCLUSION_CODE — return an evaluation line's conclusion text and its coded value.
  • ISEVALOWNEROREXECUTOR — returns a flag indicating whether a given user is the owner or the executor of an evaluation; typically used to enable or suppress update actions in the UI.
  • ISEVALEXECUTOROFASSESSMENT — returns a flag indicating whether a user is the executor of an assessment, taking an evaluation context argument because the assessment may belong to a different evaluation context than the evaluation record.
  • ADD_LANGUAGE — the standard multilingual seed data routine used to populate translated rows for the _TL table.

Tables Accessed

The package operates against AMW_EVALUATIONS_B (the base evaluation header), AMW_EVALUATIONS_DETAILS (line-level evaluation detail rows), AMW_EVALUATIONS_TL (translatable columns such as comments or names), AMW_EVALUATION_ID_S (the sequence supplying evaluation identifiers), and FND_LANGUAGES. INSERT_ROW writes the header, details, and translation rows and draws the next identifier from the sequence; the effectiveness, conclusion, and security functions read from AMW_EVALUATIONS_B and AMW_EVALUATIONS_DETAILS; ADD_LANGUAGE joins against FND_LANGUAGES to install translations.

Usage Notes

AMW_EVALUATIONS_PKG is invoked from the eAM evaluation and assessment forms, from concurrent programs that generate or validate evaluations in bulk, and from custom code needing to create an evaluation or resolve its effectiveness and conclusion values for reporting. Callers using INSERT_ROW should honor the FND_API conventions: pass P_INIT_MSG_LIST and P_COMMIT according to transaction control needs, inspect X_RETURN_STATUS before proceeding, and harvest X_MSG_COUNT/X_MSG_DATA for errors. Because the functions return effectiveness and conclusion values as VARCHAR2, use the _CODE variants when storing or comparing coded values and the non-suffixed variants when presenting user-facing text. No mandatory install-time validation error has been documented, but the DATE signature change for P_DATE_EVALUATED should be confirmed when migrating customizations across releases.