Search Results le_organization_id

Overview

PSB_HR_EXTRACT_DATA_PVT is a private PL/SQL package body in the APPS schema that supports the Oracle EBS HRMS extract framework, specifically the data extraction logic used to assemble employee, position, salary, and costing information for external reporting and interface purposes. The package is classified as PVT (private) in the ETRM repository, indicating it is not intended to be called directly by external applications or end users; instead, it is consumed internally by the extract processing engine. Its primary responsibility is to gather attributes from HRMS tables, resolve segment values for costing and general ledger mapping, manage reentrant processing state, and persist extract rows into staging tables such as PSB_COST_DISTRIBUTIONS_I. The package header/body carries a version marker (120.34, dated 2006/02/24), which reflects the lineage of the PSB HR extract module across the EBS 12.1.1 and 12.2.2 application tiers. The user search term le_organization_id relates to the organizational identifier used to scope extract data to a legal entity or business group context.

Key Procedures and Functions

The package exposes 16 documented procedures and functions:

• INIT — Private initialization routine that establishes the effective session date and seeds FND_SESSIONS, ensuring downstream extract logic operates against a consistent date context.
• GET_POSITION_INFORMATION — Retrieves position-level data from PER_ALL_POSITIONS for inclusion in the extract.
• GET_EMPLOYEE_INFORMATION — Collects core person and assignment attributes from PER_ALL_PEOPLE_F and related HR tables.
• GET_SALARY_INFORMATION — Extracts salary and rate data from PAY_RATES for the employees in scope.
• GET_COSTING_INFORMATION — Resolves costing allocations and GL flex mappings, drawing on PAY_COST_ALLOCATION_KEYFLEX and PAY_PAYROLL_GL_FLEX_MAPS.
• GET_ATTRIBUTES — Gathers configured attribute definitions and values for the extract.
• GET_EMPLOYEE_ATTRIBUTES — Retrieves employee-specific attribute values.
• GET_LD_SCHEDULE — Returns the learning/development or legislative schedule associated with the extract.
• UPDATE_REENTRY — Updates reentrant processing state for the extract run.
• CHECK_REENTRY — Validates whether a reentrant run condition exists.
• REENTRANT_PROCESS — Drives the reentrant extract logic across multiple passes.
• FINAL_PROCESS — Performs final commit and cleanup for the extract.
• VALIDATE_ATTRIBUTE_MAPPING — Confirms that configured attribute mappings are complete and valid.
• GET_DEBUG — Returns the package's debug flag for troubleshooting.
• GET_SEGMENT_VAL — Resolves a specific GL or payroll segment value from the flex column usage metadata.
• IS_LD_ENABLED — Determines whether the learning/development feature set is enabled for the business group.

Tables Accessed

The package reads and writes through APPS synonyms against several core tables:

• PER_ALL_POSITIONS / HR_ALL_POSITIONS_F — position definitions and history.
• PER_ALL_PEOPLE_F / PER_ALL_ASSIGNMENTS_F — person and assignment records.
• PAY_ALL_PAYROLLS_F — payroll definitions.
• PAY_RATES — salary and rate values.
• PAY_COST_ALLOCATIONS_F / PAY_COST_ALLOCATION_KEYFLEX — costing allocations and their flex key values.
• PAY_PAYROLL_GL_FLEX_MAPS — mapping between payroll and GL flex structures.
• FND_ID_FLEXS / FND_ID_FLEX_STRUCTURES / FND_DESCR_FLEX_COLUMN_USAGES — key flexfield definition metadata, used to resolve segment values and validate the costing/GL structure.
• FND_SESSIONS — session-to-effective-date association, written by INIT.
• HR_ALL_ORGANIZATION_UNITS — organization unit definitions; the user's search term le_organization_id typically filters or joins here to scope extract rows by legal entity or business group.
• PSB_COST_DISTRIBUTIONS_I — the extract staging/interface table into which cost distribution rows are inserted.

Usage Notes

PSB_HR_EXTRACT_DATA_PVT is invoked indirectly by the PSB HR extract concurrent programs and supporting forms, and is referenced by four other packages in the PSB module. Because it is classified as a private package body, custom code should not call its procedures directly; developers extending the extract must instead use the public API layer that wraps it. In both EBS 12.1.1 (Forms-based) and 12.2.2 (OA Framework / OAF) environments, the package's behavior is identical at the database tier, since it operates entirely within the APPS schema and depends on the presence of the PSB module objects. When troubleshooting extract results — particularly when filtering by LE_ORGANIZATION_ID or a specific legal entity — DBAs typically enable the package debug flag via GET_DEBUG and inspect rows inserted into PSB_COST_DISTRIBUTIONS_I to trace the resolved costing and GL segment values.