Search Results unique_case_number




Overview
Explore in AI Chat

Overview

APPS.PER_PERSON_ANALYSES_PKG is a PL/SQL package in Oracle E-Business Suite that supports the Person Analyses (Extra Information Types) framework within Oracle Human Resources / Oracle Payroll. Its role is to validate and populate rows in the PER_PERSON_ANALYSES entity, which stores the analysis (extra information) records attached to a person assignment outside of standard person attributes. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the definer, and it is owned by the APPS schema. In the ETRM 12.2.2 repository it carries an API classification of OTHER, indicating that it is not published as a formal public API but is used internally by Oracle's own forms and processing logic. The package exposes five documented program units and has no known dependents among other packages, which is consistent with a utility-style component invoked directly by forms or triggered processing rather than by way of a layered API stack.

Key Procedures and Functions

The package declares three procedures and two functions, all documented in the package specification:

  • CHECK_FOR_DUPLICATES — Validates whether an analysis record already exists for the given combination of person, business group, and analysis criteria before a new row is created. Parameters include context identifiers for the business group, ID flex number, analysis criteria, an end-of-time date, a from/to date range, person, and a ROWID for the row being checked.
  • GET_UNIQUE_ID — A function that returns a generated unique numeric identifier, typically used to obtain a surrogate key when inserting a new analysis row (for example, populating PER_PERSON_ANALYSES.ANALYSIS_id style surrogate values).
  • SINGLE_INFO_TYPE — Counts or restricts information-type entries for a person and customized restriction configuration. The count parameter is declared IN OUT NOCOPY, allowing the procedure to increment the caller's variable directly.
  • UNIQUE_CASE_NUMBER — Receives a business group ID, legislation code, ID flex number, and segment1 value. Its purpose is to determine or validate a unique case number for the analysis record, a requirement often linked to legislative or statutory reporting where case references must not collide within a business group. This is the procedure referenced by the user's search term, and it directly accepts the p_segment1 value that typically carries the case number.
  • POPULATE_INFO_EXISTS — A function returning VARCHAR2 that reports whether extra information already exists for a given combination of ID flex number, person, and business group.

Tables Accessed

Although the specification does not expose SQL, the documented ETRM table references show the package operates across the following objects (through APPS synonyms):

  • PER_PERSON_ANALYSES — the primary entity, holding the analysis/extra information rows per person. The package validates and populates this table.
  • PER_PERSON_ANALYSES_S — the sequence or shadow/translation object associated with the entity, used for unique identifier generation.
  • PER_ANALYSIS_CRITERIA — defines which analyses are valid for a given business group and configuration, driving duplicate and existence checks.
  • PAY_LEGISLATION_RULES — supplies legislation-specific rules that govern how case numbers and validations must behave per legislation code.
  • PAY_RESTRICTION_VALUES — provides the restriction values against which SINGLE_INFO_TYPE and customized restrictions are counted.

Usage Notes

Because this package has no package-level dependents and is not marked as a public API, it is intended for internal consumption. It is most commonly invoked from the Person Extra Information Type maintenance forms in Oracle HRMS (the Person Analyses / Extra Information window) during insert and update validation, and from Oracle's payroll/legislative processing where case numbers must be validated against legislation rules. Custom code may call it, but doing so should be treated as unsupported, since the specification is not guaranteed across patches. When invoked, callers should supply a valid business group and ID flex number consistent with the flexfield definition for Person Analyses, and a segment1 value representing the case number when UNIQUE_CASE_NUMBER is used. The AUTHID CURRENT_USER clause means grants must be in place for the calling schema to reach the referenced tables.