Search Results distribution_date




Overview
Explore in AI Chat

Overview

APPS.PSP_ADJUSTMENT_COMBO_V is a consolidated reporting view in the Oracle E-Business Suite Payroll (PSP) schema. Its purpose is to present a unified, de-duplicated projection of payroll distribution and adjustment activity across three distinct historical sources: distribution lines history, pre-generated distribution lines history, and adjustment lines history. Rather than requiring a report or integration to query each of these history tables separately, the view applies a UNION across the three sources and exposes a consistent set of columns for each row, together with a discriminating literal column named SOURCE that identifies the originating table.

Because the row sets are drawn from historical tables, the view is oriented toward audit, reconciliation, and post-run analysis rather than transactional processing. The distribution_date column is central to this purpose: it is the attribute most commonly used by downstream consumers to slice distribution activity by accounting or payroll period, and it is exposed uniformly regardless of which underlying history table contributed the row.

Underlying Base Objects

The view is defined over five documented base objects, all referenced through APPS synonyms:

The first UNION branch joins PSP_DISTRIBUTION_LINES_HISTORY to PSP_PAYROLL_SUB_LINES and PSP_PAYROLL_LINES on payroll_sub_line_id and payroll_line_id respectively. Its projected assignment_id and element_type_id are taken from the payroll lines table, while distribution_date, business_group_id, and set_of_books_id come from the distribution lines history table. The second branch reads directly from PSP_PRE_GEN_DIST_LINES_HISTORY, and the third reads directly from PSP_ADJUSTMENT_LINES_HISTORY. Both of these branches supply all five data columns from their own table without joins.

Key Columns

  • assignment_id — Identifies the employee assignment associated with the distribution or adjustment record.
  • element_type_id — Identifies the payroll element type to which the distribution amount relates.
  • distribution_date — The date on which the distribution was applied; the primary period-selection attribute for reporting.
  • business_group_id — The business group (legislative context) owning the record.
  • set_of_books_id — The accounting set of books to which the distribution is directed.
  • source — A literal discriminator with the values 'distribution_lines_history', 'pre_gen_dist_lines_history', or 'adjustment_lines_history', indicating the origin row set.

Note that the view is a projection only; no cost allocation amounts, account codes, or run identifiers are exposed, so it is best suited to existence checking, date-based activity analysis, and source attribution.

Common Use Cases and Queries

Typical uses include reconciling distribution history against adjustment and pre-generated history for a given period, confirming whether a distribution exists for an assignment and element, and establishing which history table holds a record. The distribution_date column is the most frequent filter predicate.

  • Activity by period for a business group and set of books.
  • Source attribution for a specific assignment and element type.
  • Existential checks prior to re-running distribution or adjustment processes.

Representative query:

SELECT source,
       assignment_id,
       element_type_id,
       distribution_date,
       business_group_id,
       set_of_books_id
  FROM apps.psp_adjustment_combo_v
 WHERE distribution_date BETWEEN :p_start_date AND :p_end_date
   AND business_group_id = :p_business_group_id
 ORDER BY distribution_date, assignment_id;

To isolate one source, add a predicate such as WHERE source = 'adjustment_lines_history'. All access should respect the view's read-only, historical nature and appropriate business group security.