Results for “chk_scd_handicap”

5 results




Overview
Explore in AI Chat

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

Overview

GHR_CPDF_CHECK2 is a PL/SQL package body owned by APPS within the Oracle E-Business Suite 12.1.1 / 12.2.2 environment. It belongs to the Oracle Human Resources (HRMS) family of "GHR" packages and is classified under the ETRM API classification of OTHER. The package encapsulates a set of instructional and eligibility validation routines used by the Oracle HRMS Person and Assignment data-entry flows. Its core purpose is to enforce legislative and business-rule edits on data elements such as education level, academic discipline, year of degree attainment, award amounts, benefit amounts, date of birth, and handicap information. Each routine applies conditional logic against the supplied parameters and, where a rule is violated, signals a failure to the calling layer. Failures are raised via the standard HR_UTILITY message stack, which sets a message identifier against an application and then invokes RAISE_ERROR — a pattern that surfaces the validation failure back through the Oracle Forms or API caller without aborting the entire transaction abnormally.

Key Procedures and Functions

  • CHK_INSTRUCTIONAL_PGM — Validates instructional program data. The excerpt shows it rejects combinations where education level exceeds 12 without an academic discipline, where an academic discipline is supplied without a year of degree attained (outside specified education-level exceptions), and where a degree year is earlier than the employee's seventeenth birthday. Several edits are date-scoped, with the 005.07.1 rule end-dated at 31-July-2002.
  • CHK_AWARD_AMOUNT — Applies validation rules to award amount values captured against a person or assignment.
  • CHK_BENEFIT_AMOUNT — Applies validation rules to benefit amount values.
  • CHK_CUR_APPT_AUTH — Validates the authorisation status associated with the current appointment.
  • CHK_DATE_OF_BIRTH — Validates the recorded date of birth against applicable rule conditions.
  • CHK_DUTY_STATION — Validates duty station information attached to the assignment.
  • CHK_EDUCATION_LEVEL — Validates education level codes, including the numeric comparisons that underpin the instructional program edits.
  • CHK_EFFECTIVE_DATE — Validates effective dates, including the date-bounded applicability of the instructional program edits.
  • CHK_HANDICAP — Validates handicap information recorded for the person.
  • CHK_INDIV_AWARD — Validates individual award data.
  • CHK_SCD_HANDICAP — Validates handicap data in the context of the Service Computation Date.

Tables Accessed

The documented ETRM metadata for this object does not enumerate any tables accessed through APPS synonyms. This is consistent with the package's design as a pure rule-checking layer: the routines operate on the scalar parameters passed to them (education level, discipline, degree year, effective date, tenure group code, pay plan, date of birth) rather than performing direct SQL against application tables. Persistence of the underlying values is the responsibility of the calling forms or APIs, which then invoke these checks before committing. Where the package does interact with other schema objects, it does so through the HR_UTILITY messaging utility rather than through direct DML.

Usage Notes

GHR_CPDF_CHECK2 is referenced by one other documented package, indicating it is invoked programmatically rather than exposed directly. Typical invocation occurs from the Oracle HRMS person and assignment maintenance forms, and from the corresponding PL/SQL APIs, immediately before a record is saved so that invalid combinations are rejected with a meaningful message. Because the checks are date-aware — the 005.07.1 edit, for example, applies only to effective dates on or before 31-July-2002 — the effective date supplied by the caller governs which rules are enforced, allowing the same package to serve both historical and current records. The internal comments track successive versions (005.02.3, 780.04.3, 780.05.1 and others), with at least one edit renamed and one end-dated, which reflects the package's role as a maintained repository of legislative rules. Custom code should not bypass these routines; any new data-entry path for the affected person attributes should call the appropriate check procedure and honour the HR_UTILITY message set by the routine.