Results for “psp_payroll_interface_u2”

12 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PSP.PSP_PAYROLL_INTERFACE is a Labor Distribution interface table in the PSP (Public Sector/Projects) schema of Oracle E-Business Suite, defined in both 12.1.1 and 12.2.2. It stores non-Oracle payroll sublines awaiting import into Labor Distribution, enabling third-party payroll systems to feed employee and pay information into the same summarization and General Ledger posting engine used by native Oracle Payroll. The table is registered in FND Design Data as PSP.PSP_PAYROLL_INTERFACE and holds status VALID.

Data resides in the APPS_TS_INTERFACE tablespace with PCTFREE 10. The documented physical schema at 12.2.2 comprises 47 columns. The primary key is defined as PSP_PAYROLL_INTERFACE_PK on (BATCH_NAME, PAYROLL_INTERFACE_ID). From a heuristic Data Vault modeling perspective, this object classifies as a link: it resolves the intersection of employee, assignment, payroll, and payroll period, attaching interface-level pay facts rather than functioning as a standalone hub.

Key Information Stored

The surrogate key is PAYROLL_INTERFACE_ID, a system-generated NUMBER(10) primary key. Two unique indexes act as business-key candidates: PSP_PAYROLL_INTERFACE_U1 on (BATCH_NAME, PAYROLL_INTERFACE_ID) and PSP_PAYROLL_INTERFACE_U2 on (PAYROLL_INTERFACE_ID). The search term "psp_payroll_interface_u2" therefore maps directly to the single-column unique index that supports efficient lookup by interface record identifier.

Common Use Cases and Queries

Typical scenarios include validating a third-party payroll batch before import, reviewing error rows from a failed Labor Distribution run, and reporting payroll amounts by employee, assignment, or effective date. A batch validation query follows:

  • SELECT b.batch_name, b.payroll_interface_id, b.person_id, b.assignment_id, b.pay_amount, b.effective_date FROM psp_payroll_interface b WHERE b.batch_name = :batch AND b.status_code = 'ERROR';
  • SELECT b.payroll_source_code, SUM(b.pay_amount) FROM psp_payroll_interface b WHERE b.set_of_books_id = :sob AND b.effective_date BETWEEN :start AND :end GROUP BY b.payroll_source_code;
  • SELECT b.assignment_id, SUM(b.pay_amount) FROM psp_payroll_interface b WHERE b.status_code = 'PROCESSED' GROUP BY b.assignment_id ORDER BY 2 DESC;

Because EFFECTIVE_DATE governs GL and Projects summarization, most reporting joins filter on it to align with posting periods.

Related Objects

These relationships confirm the table's role as the integration link between external payroll subline detail and Oracle Labor Distribution postings.