Search Results get_des_effectiveness_code




Overview
Explore in AI Chat

Overview

AMW_EVALUATIONS_PKG is a stored PL/SQL package in the APPS schema that supports the Oracle E-Business Suite Environment, Health and Safety (EHS) / Enterprise Tracking and Reporting (ETRM) evaluation framework. Its primary business function is to persist and expose the results of risk and effectiveness evaluations performed against assessment objects. Evaluations capture how a given control, action, or mitigation affects a risk, together with effectiveness ratings across several dimensions — design effectiveness (DES), operational effectiveness (OP), and overall effectiveness (OV). The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling user rather than the definer, consistent with Oracle EBS API conventions.

The package header carries the source control identifier amwevals.pls 115.8, dated 27 January 2004, and references a fix for bug 3326347, in which the DATE_EVALUATED attribute was migrated from a VARCHAR2 to a proper DATE datatype. This confirms the package has been stable across the 12.1.1 and 12.2.2 releases, forming part of the long-lived evaluation infrastructure underlying ETRM assessments.

Key Procedures and Functions

  • INSERT_ROW — The package's sole write API. It inserts a new evaluation record, accepting the evaluation set, object name, evaluation context and type, date evaluated, up to five primary-key values identifying the evaluated entity, the entered-by and executed-by users, comments, the three effectiveness values (DES_EFF, OP_EFF, OV_EFF), program mode, and evaluation ID. It follows the standard EBS API contract with COMMIT, validation level, initialization, and return-status parameters, and defaults the evaluation set status code to 'P' (pending).
  • GET_OP_EFFECTIVENESS / GET_OP_EFFECTIVENESS_CODE — Return the operational effectiveness of an evaluation, either as display text or as its underlying lookup code, keyed by evaluation ID.
  • GET_DES_EFFECTIVENESS / GET_DES_EFFECTIVENESS_CODE — The functions matching the user's search term. They return the design effectiveness of a specified evaluation, in display form and code form respectively. Because the code variant returns the stored lookup value, it is the appropriate choice for programmatic comparisons and integrations, while the non-code variant suits user-facing display.
  • GET_LINE_CONCLUSION / GET_LINE_CONCLUSION_CODE — Return the overall conclusion recorded for an evaluation line, again in display and code forms.
  • ISEVALOWNEROREXECUTOR — Determines whether a given user is the owner or executor of an evaluation, supporting authorization checks.
  • ISEVALEXECUTOROFASSESSMENT — Determines whether a user is the executor of the evaluation associated with a given assessment and context, extending the authorization model to the assessment level.
  • ADD_LANGUAGE — The standard multilingual seed routine used to populate translation (TL) rows for supported languages.

Tables Accessed

  • AMW_EVALUATIONS_B — The base table holding evaluation header attributes; written by INSERT_ROW and read by the getter functions.
  • AMW_EVALUATIONS_DETAILS — Stores evaluation detail and effectiveness values.
  • AMW_EVALUATIONS_TL — The translation table populated by ADD_LANGUAGE and read by display-oriented getters.
  • AMW_EVALUATION_ID_S — The sequence supplying unique evaluation identifiers.
  • FND_LANGUAGES — The language repository referenced by the ADD_LANGUAGE routine.

Usage Notes

The package is typically invoked from ETRM evaluation forms and concurrent programs, and from custom extensions that need to create evaluations or retrieve effectiveness values for reporting. Because it is not referenced by any other documented package, integration is generally direct: callers use INSERT_ROW to persist evaluation outcomes during assessment processing, and the GET_* functions to resolve effectiveness and conclusion codes for display or downstream logic. Custom code should respect the standard API parameters — checking X_RETURN_STATUS after INSERT_ROW and honoring the initialization and validation level flags — and should prefer the _CODE variants of the effectiveness functions whenever the returned value is used in comparisons rather than shown to users.