Results for “ele_entry_reason”

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

Overview

APPS.PAYBV_ELEMENT_ENTRY is a business view (BV) in the Oracle E-Business Suite Payroll (PAY) module. It is a decode-oriented presentation layer defined over the element entries entity and is designed primarily to expose human-readable values in place of the internal lookup codes stored in the base tables. The naming convention reflects this: "PAYBV" denotes a Payroll business view, and "ELEMENT_ENTRY" identifies the underlying transactional entity, namely element entries created against an assignment.

The view is typically consumed by Oracle Forms (the "Pay Element Entries" form referenced in the view text via the descriptive flexfield token _DF:PAY:PAY_ELEMENT_ENTRIES:ele), by Oracle Discoverer / BI Publisher reports, and by integration or extraction routines that need element entry data expressed in user-facing terms. Rather than forcing every consumer to join to lookup tables and decode values, the view centralizes the translation logic through calls to the HR_BIS package, which is the standard Oracle mechanism for business-view decodes.

Underlying Base Objects

The documented referenced objects for this view are:

• PAY_ELEMENT_ENTRIES_F (synonym) — the base table (aliased ele in the view text) that stores element entry records. All column references in the SELECT list are qualified with ele., confirming that the view is a single-table wrapper over this synonym.
• HR_BIS (package) — invoked repeatedly as hr_bis.bis_decode_lookup('LOOKUP_TYPE', column). This package performs the lookup-code-to-meaning translation for each decoded attribute and is the core reason the view exists.

The view does not perform joins to lookup tables directly; instead it delegates decoding to HR_BIS, each call passing a lookup type such as CREATOR_TYPE, ENTRY_TYPE, ELE_ENTRY_REASON, YES_NO, and ACTION_TYPE. This design keeps the view definition compact while returning display-ready values.

Key Columns

The view exposes the following categories of columns:

• Effective dating: EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, providing the date-tracked validity of each entry.
• Decoded lookup values: CREATOR_TYPE, ENTRY_TYPE, REASON (decoded from ELE_ENTRY_REASON), BALANCE_ADJ_COST_FLAG (decoded from YES_NO), and UPDATING_ACTION_TYPE (decoded from ACTION_TYPE). These return meaning text rather than stored codes.
• Preserved codes: CREATOR_TYPE_CODE, ENTRY_TYPE_CODE, REASON_CODE, and BALANCE_ADJ_COST_FLAG_CODE (truncated in the source excerpt). These allow consumers to retain the raw lookup values for filtering or downstream processing.
• Entry detail: SUBPRIORITY, DATE_EARNED, and SOURCE_TRIGGER_ENTRY.
• Source context: SOURCE_PERIOD, SOURCE_RUN_TYPE, SOURCE_START_DATE, and SOURCE_END_DATE, indicating the payroll run or period that generated the entry.
• Descriptive flexfield and information columns: ATTRIBUTE_CATEGORY with ATTRIBUTE1–ATTRIBUTE20, and ENTRY_INFORMATION_CATEGORY with ENTRY_INFORMATION1–ENTRY_INFORMATION30.
• Concurrency control: OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

Because the view decodes lookup values, it is well suited to reporting and reconciliation of element entries without manual lookup joins. A typical query retrieving entries with reasons rendered as descriptions is:

SELECT effective_start_date,
       effective_end_date,
       entry_type,
       reason,
       date_earned,
       source_period
FROM   apps.paybv_element_entry
WHERE  TRUNC(effective_start_date) >= :p_start_date
AND    TRUNC(effective_end_date)   <= :p_end_date;

For audit or integration work where the raw codes are required, the *_CODE columns can be selected alongside the decoded equivalents, for example comparing REASON with REASON_CODE to validate lookup configuration. The view also supports extraction of source-run context (SOURCE_RUN_TYPE, SOURCE_PERIOD) for payroll run analysis and of flexfield/information columns for organization-specific reporting. In practice, the majority of direct consumption occurs through the Pay Element Entries form, with ad hoc SQL and BI Publisher templates using the view as a convenient, display-ready data source over PAY_ELEMENT_ENTRIES_F.