Results for “per_rating_levels_pk”

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

Overview

The APPS.HR_SUIT_MATCH_UTIL_SS package is a utility PL/SQL package within the Oracle E-Business Suite Human Resources (HR) and Self-Service Human Resources (SSHR) module. Its name derives from "Suitability Matching Utility – Self Service," and it provides the core support logic used to evaluate the fit between a person (employee or applicant) and a work opportunity such as a vacancy, job, or position. This is the "suitability match" feature that compares a candidate's competencies, ratings, and profile attributes against the requirements defined for a vacancy or position.

The package is declared with AUTHID CURRENT_USER, meaning that it executes with the privileges of the calling schema, and the header carries a version marker indicating it was delivered as a standard Oracle EBS object (hrsmgutil.pkh, 2008). It is classified as an OTHER API in the ETRM 12.2.2 repository metadata, which indicates it is not a public, supported business API in the same sense as the HRMS date-track or person APIs, but rather an internal utility used by the SSHR suitability-matching pages and logic.

Key Procedures and Functions

The package exposes three POPULATE_* procedures and one INSERT_* procedure that populate temporary working tables for competence details, person details, and work-opportunity details. These procedures accept a single parameter — a temp table of type SSHR_SM_COMP_DETAILS_TAB_TYP — and are used to stage comparison data before matching is performed.

• POPULATE_COMP_TEMP_TABLE — Stages competence-related data for the suitability comparison.
• POPULATE_PER_TEMP_TABLE — Stages person-related data for the suitability comparison.
• POPULATE_WORKOPP_TEMP_TABLE — Stages work-opportunity-related data for the suitability comparison.
• INSERT_WORKOPP_TEMP_TABLE — Inserts work-opportunity rows into the temporary staging structures.

Two function families provide the queryable match results:

• GET_ESS_DESIRED_MATCH — Returns the desired match value for a person in the context of an ESS (Employee Self-Service) request. It is overloaded, offering a simple person/request form and a richer form accepting enterprise, organization, job, position, vacancy, and person-template context. Both carry a PRAGMA RESTRICT_REFERENCES(...,WNDS,RNDS) purity declaration.
• IS_ESS_DES_MEETS — Determines whether the person meets the desired criteria, similarly overloaded with simple and rich parameter forms and carrying the same purity pragma.

Four additional getter functions retrieve supporting attributes: GET_BG_NAME (business group name), GET_APPLICATION_DATE (the person's application date), GET_EMP_START_DATE (start date from a period of service), and GET_CWK_START_DATE (the person's continuous work/calculated start date).

Tables Accessed

The package reads from and writes to core HR and suitability tables accessed via APPS synonyms:

• PER_SUITMATCH_COMP, PER_SUITMATCH_PERSON, PER_SUITMATCH_WORKOPPS — the principal suitability-match tables populated by the POPULATE_* and INSERT_* procedures.
• PER_COMPETENCE_ELEMENTS and PER_RATING_LEVELS — supply the competency and rating definitions used to evaluate matches.
• PER_ALL_PEOPLE_F, PER_APPLICATIONS, PER_PERIODS_OF_SERVICE, PER_PERIODS_OF_PLACEMENT — provide person, application, and service history data.
• PER_ALL_VACANCIES — vacancy definitions used in work-opportunity matching.
• HR_ALL_ORGANIZATION_UNITS_TL and HR_ALL_POSITIONS_F — organization and position definitions.
• PLITBLM — a PL/SQL index-by table helper, typically used for bulk data staging.

Usage Notes

This package is invoked internally by the SSHR suitability-matching feature set, most commonly from Employee Self-Service and manager self-service pages where a user compares their profile against an open vacancy or competency requirement. The get_ess_* functions are designed for ESS contexts and return match results and eligibility flags used directly in page rendering.

Because the ETRM metadata records that the package is referenced by zero other packages, it functions as a leaf-level utility rather than a shared dependency. Customizations should be cautious: as an internal OTHER classification object rather than a supported public API, its signature is not guaranteed stable across patch levels. Direct calls should generally be limited to diagnostic or reporting code, and any dependence on the POPULATE_* temp-table procedures should account for the SSHR_SM_COMP_DETAILS_TAB_TYP collection type being populated in advance.