Results for “data_extract_id”

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

Overview

The view PSB_POSITION_PAY_DISTR_DATE_V belongs to the PSB — Public Sector Budgeting product family, which Oracle classifies as obsolete within the E-Business Suite 12.1.1 and 12.2.2 releases. It is a reporting and integration-oriented view that exposes position pay distribution records together with their effective date ranges and worksheet association. The view is defined as a distinct projection over the internal view PSB_POSITION_PAY_DISTRS_V, filtering out any rows where the CODE_COMBINATION_ID is null. Its primary role is to provide a stable, denormalized surface for external extracts, data conversions, and budget reconciliation reporting where consumers require position, worksheet, and effective date context without the full detail of the underlying distribution records.

The DATA_EXTRACT_ID column, which the user searched for, is a key integration column. It links each row to a specific extraction run or batch, allowing downstream processes to trace position pay distributions back to a single data extract event. This is consistent with ETRM-style reporting views that carry an extract identifier to support auditing and reload scenarios.

Underlying Base Objects

Per the ETRM metadata, no concrete base tables are documented for this view. The view text reveals that its sole documented source is the internal view PSB_POSITION_PAY_DISTRS_V, from which it selects a subset of columns. Because PSB_POSITION_PAY_DISTRS_V is not further decomposed in the supplied metadata, the deeper physical objects (for example position and pay distribution tables within the PSB schema) are not enumerated here. In practice, PSB_POSITION_PAY_DISTRS_V resolves position pay distribution rows joined to code combination data, and this view applies an additional null-filter on CODE_COMBINATION_ID to guarantee that only fully account-validated distributions are surfaced.

Note that the ETRM record states this object is not implemented in the reference database, so the view may not exist in every environment. It is described as obsolete, and DBAs should confirm its presence before relying on it in custom code.

Key Columns

• POSITION_ID — Identifier of the budget position to which the pay distribution belongs.
• DATA_EXTRACT_ID — Identifier of the data extract batch or run that produced or owns the row; central to traceability and extract reconciliation.
• EFFECTIVE_START_DATE — Start of the date range for which the distribution is valid.
• EFFECTIVE_END_DATE — End of the validity range for the distribution.
• WORKSHEET_ID — Identifier of the budget worksheet associated with the position distribution.

The DISTINCT keyword in the view text indicates that duplicate combinations of these five columns are collapsed, which is useful when the same position/extract/date combination appears across multiple distribution detail rows.

Common Use Cases and Queries

Typical scenarios include extracting position pay distributions by extract batch, reconciling effective date coverage for budget positions, and reporting which worksheets are tied to a given extract. A representative query filtering on the searched term is:

• SELECT position_id, data_extract_id, effective_start_date, effective_end_date, worksheet_id FROM psb_position_pay_distr_date_v WHERE data_extract_id = :extract_id;
• SELECT worksheet_id, COUNT(DISTINCT position_id) FROM psb_position_pay_distr_date_v WHERE effective_start_date BETWEEN :start AND :end GROUP BY worksheet_id;

Because the view excludes null code combinations, results align with financially validated distributions, making it suitable for integration feeds and audit extracts while keeping reliance on obsolete PSB constructs to a minimum.