Search Results psb_salary_i




Overview
Explore in AI Chat

Overview

PSB_SALARY_I is a staging (interface) table within the Public Sector Budgeting (PSB) product family of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to hold salary rate information as it is loaded from external or upstream sources before validation and transfer into the base PSB salary and rate tables. In the ETRM metadata, PSB is flagged as obsolete, and the object is explicitly recorded as "Not implemented in this database," meaning it is retained for reference, upgrade lineage, or legacy catalog completeness rather than active runtime use in current installations.

The table belongs to the PSB schema and carries twenty-two documented columns in the 12.1.1 ETRM extract. It is keyed for batch processing through a data extract identifier, so it participates in the same extract lifecycle as other PSB interface tables. From a heuristic Data Vault modeling perspective, the mined FK structure classifies PSB_SALARY_I as standalone, with a single outbound reference to PSB_DATA_EXTRACTS. This suggests treating it as a satellite-like staging object anchored on the data extract hub, rather than a pure hub or link.

Key Information Stored

Each row describes one salary rate line scoped to a specific extract and business group. The most significant columns are:

No single-column surrogate primary key is documented. Instead, the unique index PSB_SALARY_1_U1 identifies the business key as the composite (RATE_OR_PAYSCALE_ID, GRADE_ID, GRADE_STEP, SEQUENCE_NUMBER, DATA_EXTRACT_ID).

Common Use Cases and Queries

The primary use case is extract-driven salary rate loading. A typical reconciliation query counts staged rows per extract and validates that the business key is unique:

  • SELECT data_extract_id, COUNT(*) FROM psb_salary_i GROUP BY data_extract_id;
  • Detect duplicates against the unique key: SELECT rate_or_payscale_id, grade_id, grade_step, sequence_number, data_extract_id, COUNT(*) FROM psb_salary_i GROUP BY 1,2,3,4,5 HAVING COUNT(*) > 1;
  • Validate payroll element mappings: SELECT element_type_id, element_value, pay_basis FROM psb_salary_i WHERE element_type_id IS NULL;
  • Check effective-date integrity: SELECT * FROM psb_salary_i WHERE effective_end_date < effective_start_date;
  • Join staged rows to their extract header: SELECT s.*, d.* FROM psb_salary_i s, psb_data_extracts d WHERE s.data_extract_id = d.data_extract_id;

Because the object is marked obsolete and not implemented, these patterns apply mainly to legacy data migration validation, historical upgrades, or archive analysis rather than current production budgeting cycles.

Related Objects

Given the mined relationship data, the most relevant dependent and associated objects are:

  • PSB_DATA_EXTRACTS — parent of the DATA_EXTRACT_ID foreign key; governs the extract lifecycle.
  • PSB_SALARY_1_U1 — the unique index enforcing the composite business key.
  • Base PSB salary/rate tables (grade rate, pay scale, and element definition tables) that consume validated interface rows during the load step.
  • HRMS grade and grade step definitions referenced by GRADE_ID and GRADE_STEP.
  • Payroll element type definitions referenced by ELEMENT_TYPE_ID.
  • Other PSB interface tables sharing the same DATA_EXTRACT_ID anchor and staging pattern.