Results for “delete_outcome”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.HR_COMPETENCE_OUTCOME_API package body provides the supported programmatic interface for maintaining competence outcome records within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Competence outcomes represent the measurable results or proficiency expectations associated with a competence element, allowing an enterprise to define what a person must demonstrate to be judged competent against a given competence. The package encapsulates the business rules, validation logic, and multi-row insert/update behavior required to keep the underlying competence model internally consistent, so that consumers do not write directly to the base tables. It is classified as a public API in the ETRM repository, meaning it is intended for supported external invocation by forms, concurrent processes, and custom extensions rather than as an internal-only utility. The package is referenced by two other packages in the ETRM inventory, confirming its role as a dependency within the broader competence management API layer.

Key Procedures and Functions

The documented interface exposes three procedures:

• CREATE_OUTCOME — Creates a new competence outcome record. This is the procedure most commonly sought by developers, reflected in the search term "create_outcome". It accepts a validation-only mode, an effective date, a language code defaulting to the session language, the parent competence identifier, an outcome number, a name, an effective date range, assessment criteria, and the standard descriptive flexfield and extra information attribute columns. The procedure performs the mandatory validations and writes the outcome across the base, translation, and cross-reference tables.
• UPDATE_OUTCOME — Modifies the attributes of an existing competence outcome, including date-tracked and translated values, while preserving referential integrity with the competence element definition.
• DELETE_OUTCOME — Removes a competence outcome record and its dependent translation and association rows, subject to the API's validation rules.

All three procedures follow the standard Oracle HRMS API pattern, supporting a validation mode in which the operation is validated but rolled back, allowing callers to pre-check data before committing.

Tables Accessed

• PER_COMPETENCE_OUTCOMES — The base table holding the outcome definition, effective dates, assessment criteria, and descriptive flexfield segments.
• PER_COMPETENCE_OUTCOMES_TL — The translation table storing the language-specific outcome name and description.
• PER_COMPETENCE_ELEMENTS — The parent competence element to which the outcome belongs; read to validate the foreign key relationship.
• PER_COMP_ELEMENT_OUTCOMES — The association table linking competence elements to their outcomes, maintained in step with the outcome definition.

Usage Notes

The package is typically invoked from the Competence Management forms, from concurrent programs that load or migrate competence data, and from custom PL/SQL code performing bulk setup or integration. Callers must supply a valid effective date and competence identifier, and should pass p_validate as true during a dry run to confirm that all business rules pass before committing. Since the API writes to translated and association tables in addition to the base table, direct DML against PER_COMPETENCE_OUTCOMES should be avoided. Customizations should invoke the package through the APPS schema and respect the session language and date-tracking conventions established by the HRMS API framework.