Search Results psb_hr_populate_data_pvt




Overview
Explore in AI Chat

Overview

PSB_HR_POPULATE_DATA_PVT is a private (PVT) PL/SQL package in the APPS schema that belongs to the Oracle Human Resources position budgeting and worksheet extraction subsystem. It supports the incremental extract process that gathers Human Resources position, assignment, grade, and costing data into staging structures used for budget worksheet generation. The package header carries the version marker $Header: PSBVHRPS.pls 120.6 2005/10/27, indicating a stable, long-lived code line maintained through the 12.1.1 and 12.2.2 releases.

A defining characteristic of this package is its use of package-level global variables to carry session state across the extract run. Variables such as g_psb_budget_group_id, g_psb_worksheet_id, g_psb_current_form, g_psb_data_extract_id, g_psb_business_group_id, g_psb_application_id, g_psb_org_id, and the revision date range globals are declared at package scope. Additional globals such as g_extract_method and g_pop_assignment were introduced under bug fixes 4153562 and 4213882, with g_extract_method set by the populate_position_assignments API. These globals are read and written through the accessor pair SET_GLOBAL and GET_GLOBAL, which is the reason a search for "get_global" resolves to this object.

Key Procedures and Functions

  • SET_GLOBAL — Assigns a value to a named package global, identified by the variable name and supplied value.
  • GET_GLOBAL — Returns the current value of a named package global as a VARCHAR2. This is the accessor most commonly referenced by callers and the object of the "get_global" search.
  • INSERT_POSITION_TXN_INFO — Inserts a position transaction record, capturing action date, position and organization identifiers, entry step and grade rules, supervisor and successor positions, amendment details, and related descriptive attributes.
  • UPDATE_POSITION_TXN_INFO — Modifies an existing position transaction record during the extract cycle.
  • INSERT_POSITION_INFO — Inserts core position definition data into the staging tables.
  • UPDATE_POSITION_INFO — Updates previously staged position data.
  • POPULATE_POSITION_INFORMATION — Drives population of position-level information for the extract.
  • POPULATE_EMPLOYEE_INFORMATION — Collects employee assignment data associated with the positions in scope.
  • POPULATE_ELEMENT_INFORMATION — Gathers payroll element information relevant to costing.
  • POPULATE_COSTING_INFORMATION — Populates costing detail used in budget worksheet calculations.
  • POPULATE_ATTRIBUTE_VALUES — Extracts descriptive flexfield attribute values for the staged records.
  • POPULATE_POS_ASSIGNMENTS — Populates position assignment rows and sets the g_extract_method global that governs extract behavior.
  • APPLY_DEFAULTS — Applies default values to staged records where source data is incomplete.
  • GET_DEBUG — Returns the debug flag controlling diagnostic output during the extract.

Tables Accessed

Through APPS synonyms, the package reads and writes several HRMS and FND tables. PSB_POSITIONS and PSB_EMPLOYEES_I are the primary staging targets. HR_ALL_ORGANIZATION_UNITS and HR_ALL_POSITIONS_F supply organization and position definitions. PER_ALL_ASSIGNMENTS_F, PER_GRADES, PER_JOBS, PER_PAY_BASES, PER_PARENT_SPINES, PER_SHARED_TYPES, and PER_SPINAL_POINTS provide assignment, grade, job, and spinal point reference data. PAY_RATES supplies pay rate values for costing. FND_DESCR_FLEX_COLUMN_USAGES and FND_ID_FLEXS drive descriptive flexfield attribute extraction, while FND_SESSIONS supports session context.

Usage Notes

PSB_HR_POPULATE_DATA_PVT is a private package and is not intended for direct customer invocation; its procedures are called by the position budgeting extract logic and by seven other packages in the PSB subsystem. The SET_GLOBAL and GET_GLOBAL pair exists to avoid passing a large parameter list between cooperating procedures during a single extract run, and callers should assume the globals are session-scoped and must be set before dependent procedures execute. In Oracle EBS 12.1.1 and 12.2.2 the package remains unchanged in behavior, though the 12.2 online patching architecture means its state is confined to a single runtime session. Custom code should not call these APIs directly, as internal signatures and globals may change without public notice.