Search Results check_date_effective




Overview
Explore in AI Chat

Overview

The APPS.PER_POSITIONS_PKG package is a server-side PL/SQL API within Oracle E-Business Suite Human Resources (Oracle HRMS) that manages the lifecycle of position records stored in the PER_ALL_POSITIONS entity. A position represents a defined role within an organization structure to which one or more employees may be assigned, and it is the anchor for headcount planning, vacancy tracking, budgeting, and reporting in Oracle HRMS. The package supplies the insert, update, delete, and lock primitives for position rows as well as the supporting business validation logic required to keep position data consistent with the surrounding HRMS model — job definitions, grade structures, location and organization assignments, position hierarchies, and budget elements. In an Oracle EBS 12.1.1 or 12.2.2 environment it is registered under the APPS schema and is classified as an OTHER API, meaning it is a supporting data-maintenance package rather than a fully public, versioned business API. Because the object dates from the 11i era (the header references pepos01t.pkh 120.0, 2005), it is written in the traditional unconstrained VARCHAR2 style and remains present, largely unchanged, across both 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes twelve documented program units:

  • EXISTS_IN_HIERARCHY — a function that determines whether a given position participates in a specified position structure version; this is the entry point most commonly referenced by callers checking hierarchy membership before performing structural operations.
  • INSERT_ROW — creates a new position row, assigning the position identifier and rowid, and populating business group, job, organization, location, successor and relief position references, effective dates, working-time attributes and the twenty descriptive flexfield attribute columns.
  • LOCK_ROW — acquires a row-level lock on a position so that concurrent maintenance cannot corrupt it.
  • UPDATE_ROW — applies changes to an existing position row.
  • DELETE_ROW — removes a position row.
  • PRE_DELETE_CHECKS — validation executed before deletion to confirm the position may safely be removed.
  • CHECK_ID_FLEX_STRUCT — validates the key flexfield structure associated with position data.
  • CHECK_DATE_EFFECTIVE — verifies effective-date validity for the position record.
  • CHECK_VALID_GRADES and MAINTAIN_VALID_GRADES — validate and maintain the set of grades permitted for a position.
  • GET_SHARED_POS_WARN_FLAG and SET_SHARED_POS_WARN_FLAG — read and write the flag controlling warning behaviour for shared positions.

Tables Accessed

The package operates primarily against PER_ALL_POSITIONS and its translated/secure shadow table PER_POSITIONS_S. Hierarchy operations reference PER_POS_STRUCTURE_ELEMENTS and PER_MM_POSITIONS. Grade validation touches PER_GRADES and PER_VALID_GRADES. Job-related validation reads PER_JOB_REQUIREMENTS and PER_JOB_EVALUATIONS. Budget and assignment cross-checks use PER_BUDGET_ELEMENTS and PER_ALL_ASSIGNMENTS_F. Flexfield structure validation reads FND_ID_FLEX_STRUCTURES and FND_COMPILED_ID_FLEX_STRUCTS. Benefits-integration references include PAY_ELEMENT_LINKS_F and BEN_COPY_ENTITY_RESULTS/_S.

Usage Notes

PER_POSITIONS_PKG is normally invoked indirectly through the Position form and related HRMS forms, and through concurrent programs that load, copy, or validate position data. Two other packages reference it, indicating that higher-level HRMS APIs delegate to it. Custom code should generally prefer the supported public HRMS APIs, but where direct use is required, callers must supply the full column list, use LOCK_ROW for concurrency control, and run PRE_DELETE_CHECKS before DELETE_ROW. All calls must be made with the APPS schema context and appropriate HRMS security profiles in force.