Results for “paybv_run_result”

15 results




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

Overview

PAYBV_RUN_RESULT is a read-only BI Publisher (BIS) view owned by the APPS schema within the Oracle Payroll (PAY) product. Its purpose is to expose payroll run result records in a report-friendly format by translating the internal coded values stored in the base transaction table into their human-readable lookup meanings. The view is part of the PAYBV ("Payroll Business Intelligence View") family, which is designed to support Oracle Business Intelligence Publisher report definitions, ad hoc extracts, and downstream integrations that require descriptive payroll data rather than raw codes.

Because the view is defined with the "WITH READ ONLY" clause, it is strictly a query object; no DML can be issued against it. This reinforces its role as a presentation and reporting layer rather than a transactional interface. For users searching on the term "entry_type," the relevant point is that PAYBV_RUN_RESULT exposes both the descriptive ENTRY_TYPE value and the underlying ENTRY_TYPE_CODE, allowing reports to display meaningful labels while still supporting joins or filters on the stored code.

Underlying Base Objects

The view is defined over two documented objects: the PAY_RUN_RESULTS synonym, which resolves to the base payroll run result table, and the HR_BIS package. The SELECT statement takes the columns from the PAY_RUN_RESULTS table (aliased PRR) and passes three of them — ENTRY_TYPE, SOURCE_TYPE, and STATUS — through the HR_BIS.BIS_DECODE_LOOKUP function. This function converts each stored lookup code into its corresponding display value using the lookup types ENTRY_TYPE, RUN_RESULT_SOURCE_TYPE, and RUN_RESULT_STATUS respectively. As documented in the ETRM metadata, the referenced base objects are HR_BIS (PACKAGE) and PAY_RUN_RESULTS (SYNONYM). The relationship is therefore one of decoding and projection: the view adds lookup resolution and column aliasing on top of the raw run result rows without altering the underlying data set.

Key Columns

The view exposes thirteen columns. The most significant, given the search context, are:

  • ENTRY_TYPE — The decoded, descriptive entry type derived via BIS_DECODE_LOOKUP('ENTRY_TYPE', ...). This is the display-friendly value.
  • ENTRY_TYPE_CODE — The raw stored code from PAY_RUN_RESULTS.ENTRY_TYPE, retained for filtering and joins.
  • SOURCE_TYPE / SOURCE_TYPE_CODE — The decoded and coded run result source type (decoded via the RUN_RESULT_SOURCE_TYPE lookup).
  • STATUS / STATUS_CODE — The decoded and coded run result status (decoded via the RUN_RESULT_STATUS lookup).
  • JURISDICTION_CODE — The legislative jurisdiction under which the result was produced.
  • START_DATE / END_DATE — The effective date range of the run result, useful for time-based analysis and reporting periods.
  • RUN_RESULT_ID, ELEMENT_TYPE_ID, ASSIGNMENT_ACTION_ID, SOURCE_ID — Surrogate keys linking the result to its owning run, element type, assignment action, and source record, supporting joins to related payroll entities.

Common Use Cases and Queries

Typical scenarios include payroll run auditing, element entry analysis, and feeding run result data into BI Publisher reports or external systems. Because the view carries both decoded and coded columns, reports can group by the descriptive ENTRY_TYPE while still joining on codes. A basic query filtering on entry type would be:

SELECT RUN_RESULT_ID, ENTRY_TYPE, ENTRY_TYPE_CODE, SOURCE_TYPE, STATUS, START_DATE, END_DATE FROM APPS.PAYBV_RUN_RESULT WHERE ENTRY_TYPE_CODE = :entry_type;

To summarize volumes by entry type and status across a period:

SELECT ENTRY_TYPE, STATUS, COUNT(*) FROM APPS.PAYBV_RUN_RESULT WHERE START_DATE >= :from_date AND END_DATE <= :to_date GROUP BY ENTRY_TYPE, STATUS;

Because the view is read-only, it is safe for concurrent reporting use and is well suited to integration extracts where consistent, decoded payroll run result data is required.