Search Results get_special_info_type_id

Overview

APPS.PER_SIT_PKG is an Oracle E-Business Suite PL/SQL package that encapsulates the server-side logic governing Special Information Types (SIT) within Oracle Human Resources. A Special Information Type defines a business-group-specific flexfield structure that captures additional personal data about employees, applicants, and other person records beyond the standard HR fields. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking user rather than the package owner.

The package enforces the integrity rules that surround the SIT definition lifecycle: uniqueness of a Special Information Type within a business group, validation before deletion, detection of active usage, and the persistence of SIT header rows in the underlying tables. It operates against the Descriptive Flexfield infrastructure that stores the segment definitions referenced by PER_SPECIAL_INFO_TYPES.ID_FLEX_NUM.

Key Procedures and Functions

The documented API comprises eleven procedures and functions:

• check_unique_sit — Ensures that the Special Information Type is unique within the Business Group. This is the routine most commonly associated with the search term "check_unique_sit" and is the validation gate invoked before a new SIT definition is committed.
• sit_flex_used — A Boolean function that determines whether the flex structure has been used in Personal Analyses. It provides a reuse test for a given business group and flexfield number.
• sit_del_validation — Performs delete validation, confirming that a Special Information Type may safely be removed for the specified business group and flex structure.
• sit_in_use — Determines whether a Special Information Type is currently referenced by dependent records.
• populate_fields — Populates the name and flex-enabled flag fields for a given flexfield number, returning values through IN OUT NOCOPY parameters.
• get_special_info_type_id — Retrieves the next unique identifier for a Special Information Type, typically sourced from the sequence and used before insert.
• ins_sit — Inserts a record into PER_SPECIAL_INFO_TYPES, accepting the business group, flexfield number, comments, enabled flag, standard WHO audit columns, and descriptive flexfield attribute columns.
• upd_sit — Updates an existing Special Information Type record.
• del_sit — Deletes a Special Information Type record.
• lck — Locks the target SIT row to serialize concurrent modifications.
• reset_usages — Clears or reinitializes usage tracking associated with a Special Information Type.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• PER_SPECIAL_INFO_TYPES and PER_SPECIAL_INFO_TYPES_S — the base and translation tables that hold SIT header definitions; these are the primary insert, update, and delete targets.
• PER_SPECIAL_INFO_TYPE_USAGES — records where a Special Information Type has been attached, used by the usage and delete-validation logic.
• PER_PERSON_ANALYSES and PER_ANALYSIS_CRITERIA — Personal Analysis definitions that may reference the flex structure, underpinning sit_flex_used.
• PER_JOB_REQUIREMENTS — job requirement definitions that may also reference the SIT flex structure.
• PAY_LEGISLATION_RULES — legislation rule data consulted during validation.
• DUAL — used for single-row computations and sequence retrieval.

Usage Notes

PER_SIT_PKG is an internal, form-driven API rather than a publicly published interface. It is invoked by the Oracle HRMS Special Information Types setup form (and related person/analysis forms) when a user defines, modifies, or removes a Special Information Type. Because the package is not referenced by any other documented package, callers are expected to be Forms or bespoke code operating within the APPS schema.

Custom integrations should not call these routines directly without accounting for the surrounding form logic: the procedures enforce row locking, uniqueness, and usage checks that assume an active form session. Any custom invocation of check_unique_sit or ins_sit must supply a valid business group and a flexfield number that has already been defined in the Descriptive Flexfield segments, otherwise the validation will fail or the SIT will be unusable.