Search Results psp_element_types




Overview
Explore in AI Chat

Overview

The PSP_ELEMENT_TYPES table is a core data repository within the Oracle E-Business Suite (EBS) Labor Distribution module (PSP). Its primary function is to store a synchronized copy of element type definitions imported from the Oracle HRMS (Human Resources Management System) module. This table acts as the master reference for compensation and benefit elements—such as regular salary, bonuses, or allowances—that are subject to labor distribution. By maintaining this centralized store, the Labor Distribution module can accurately allocate labor costs associated with specific earning types to the correct general ledger accounts, forming a critical integration point between HR payroll data and financial accounting.

Key Information Stored

The table's structure is designed to support the versioning of element type definitions over time, as indicated by its composite primary key. While the full column list is not detailed in the provided metadata, the key columns inferred from the primary and foreign key relationships are fundamental. The ELEMENT_TYPE_ID column uniquely identifies the specific earning element (e.g., "Regular Pay," "Overtime"). The START_DATE_ACTIVE column enables effective-dated tracking, allowing for historical changes to an element's definition. Other columns typically present in this table, based on standard EBS design, would include the element's name, reporting name, classification, and relevant HRMS source information, facilitating accurate mapping and reporting within the labor distribution processes.

Common Use Cases and Queries

This table is primarily accessed for setup, validation, and reporting tasks. A common operational use case is verifying which HR elements are available for labor distribution setup. Administrators often query this table to populate lists of values when defining distribution sets or group element lists. For reporting purposes, it is frequently joined to labor distribution transaction tables to provide descriptive context for distributed amounts. A typical validation query would check for active elements missing corresponding account mappings:

  • SELECT pet.element_type_id, pet.element_name FROM psp_element_types pet WHERE NOT EXISTS (SELECT 1 FROM psp_element_type_accounts peta WHERE peta.element_type_id = pet.element_type_id) AND SYSDATE BETWEEN pet.start_date_active AND NVL(pet.end_date_active, SYSDATE);

Another standard pattern is retrieving all element types effective for a given payroll period, which is essential for cost allocation runs.

Related Objects

PSP_ELEMENT_TYPES serves as a parent table in two key relationships within the Labor Distribution schema, as documented in the provided metadata. These relationships enforce data integrity for critical configuration objects:

  • PSP_ELEMENT_TYPE_ACCOUNTS: This child table stores the default accounting flexfield (GL accounts) assignments for each element type. It references PSP_ELEMENT_TYPES via the foreign key on columns ELEMENT_TYPE_ID and START_DATE_ACTIVE. This link ensures that account mappings are defined only for valid, version-controlled element types.
  • PSP_GROUP_ELEMENT_LIST: This child table defines the membership of element types within distribution groups. It references PSP_ELEMENT_TYPES via the foreign key on column ELEMENT_TYPE_ID. This relationship allows administrators to group related elements (e.g., all taxable earnings) for easier assignment to distribution sets.

The table's data originates from the HRMS module, typically via a dedicated concurrent request or program, making underlying HR objects like PAY_ELEMENT_TYPES_F its ultimate source.