Search Results psp_organization_accounts




Overview
Explore in AI Chat

Overview

The PSP_ORGANIZATION_ACCOUNTS table is a core data structure within the Oracle E-Business Suite (EBS) Labor Distribution module (PSP). Its primary function is to store default and suspense accounting flexfield (AFF) combinations for organizations. This configuration is critical for the automated processing of labor costs. The table enables the system to determine the correct general ledger accounts for distributing payroll expenses, either by providing a default destination or a suspense holding account when a valid distribution cannot be automatically determined. Its integrity is maintained through a robust set of primary and foreign key relationships, ensuring data consistency across the financial, human resources, and projects modules.

Key Information Stored

The table's design captures the necessary dimensions to uniquely define an accounting rule for an organization. The primary key is ORGANIZATION_ACCOUNT_ID, a system-generated unique identifier. A unique key constraint (PSP_ORGANIZATION_ACCOUNTS_U1) enforces business logic on the combination of ORGANIZATION_ID, ACCOUNT_TYPE_CODE, and START_DATE_ACTIVE. The ACCOUNT_TYPE_CODE distinguishes between 'DEFAULT' and 'SUSPENSE' account types. The core accounting reference is the GL_CODE_COMBINATION_ID, which points to the specific AFF. For project-related distributions, the table can store PROJECT_ID, TASK_ID, AWARD_ID, EXPENDITURE_ORGANIZATION_ID, and EXPENDITURE_TYPE to define a more precise accounting rule. The SET_OF_BOOKS_ID links the rule to a specific ledger, and START_DATE_ACTIVE (and typically an END_DATE_ACTIVE, implied by naming convention) manages the rule's effective period.

Common Use Cases and Queries

A primary use case is troubleshooting labor distribution errors. When a batch fails because it cannot find a valid account, consultants often query this table to verify that a valid default or suspense account is defined for the employee's organization and the relevant set of books. Common SQL patterns include identifying active rules for a specific organization or validating the existence of a suspense account. For reporting, the table is frequently joined to HR_ALL_ORGANIZATION_UNITS for organization names and to GL_CODE_COMBINATIONS for the full account segment values.

  • Sample Query: Retrieve active suspense account details for an organization:
    SELECT hou.name org_name, gcc.concatenated_segments suspense_account
    FROM psp_organization_accounts poa,
         hr_all_organization_units hou,
         gl_code_combinations_kfv gcc
    WHERE poa.organization_id = hou.organization_id
    AND poa.gl_code_combination_id = gcc.code_combination_id
    AND poa.account_type_code = 'SUSPENSE'
    AND poa.organization_id = :p_org_id
    AND SYSDATE BETWEEN poa.start_date_active AND NVL(poa.end_date_active, SYSDATE);

Related Objects

PSP_ORGANIZATION_ACCOUNTS is a central hub with extensive relationships. It references master data tables to validate its keys: HR_ALL_ORGANIZATION_UNITS (ORGANIZATION_ID), GL_CODE_COMBINATIONS (GL_CODE_COMBINATION_ID), PA_PROJECTS_ALL (PROJECT_ID), PA_EXPENDITURE_TYPES (EXPENDITURE_TYPE), PA_TASKS (TASK_ID), and GL_SETS_OF_BOOKS (SET_OF_BOOKS_ID). Crucially, its ORGANIZATION_ACCOUNT_ID is referenced as a foreign key (SUSPENSE_ORG_ACCOUNT_ID) by several transactional and history tables in the PSP module, including PSP_ADJUSTMENT_LINES, PSP_ADJUSTMENT_LINES_HISTORY, PSP_PRE_GEN_DIST_LINES, and PSP_PRE_GEN_DIST_LINES_HISTORY. This demonstrates its direct role in the labor distribution posting process.