Results for “source_trigger_entry”

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

Overview

PAYBV_ELEMENT_ENTRY is a business view in the APPS schema belonging to the PAY (Payroll) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a reporting-oriented, decoded projection of element entry records, exposing the transactional detail of element entries alongside human-readable values resolved through the HR_BIS package. The view is validated and enabled, making it suitable for use in reports, extracts, and integration queries that require element entry information without the raw lookup codes stored on the underlying base table.

A distinctive characteristic of this view is its reliance on HR_BIS.BIS_DECODE_LOOKUP, the Business Intelligence System decode utility. Several columns—CREATOR_TYPE, ENTRY_TYPE, REASON, BALANCE_ADJ_COST_FLAG, and UPDATING_ACTION_TYPE—are passed through this function so that values stored as lookup codes in the base table are returned as their translatable display meanings. This makes the view particularly valuable where business users or downstream systems require descriptive text rather than internal codes.

Underlying Base Objects

Documented metadata for 12.2.2 identifies two referenced objects: the package HR_BIS and the synonym PAY_ELEMENT_ENTRIES_F. The synonym resolves to the element entries base table maintained by the Payroll application. The view aliases that base table as ELE within its defining query.

Every attribute exposed by the view is derived from columns of the element entries entity. No joins are introduced in the view definition; the transformation is limited to decoding selected lookup columns. HR_BIS is invoked as a reference object rather than a joined table, supplying the decode logic. This simple, single-source structure keeps the view performant and predictable, since all filtering, grouping, and ordering are pushed to the caller's SQL rather than embedded in the view.

Key Columns

• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-tracked validity range for the element entry record.
• CREATOR_TYPE — Decoded lookup value indicating the source that created the entry; the raw code is preserved separately as CREATOR_TYPE_CODE.
• ENTRY_TYPE — Decoded entry type, with the underlying code also exposed as a duplicate ENTRY_TYPE column at the end of the select list.
• REASON — Decoded element entry reason, resolved from the ELE_ENTRY_REASON lookup.
• UPDATING_ACTION_TYPE — The decoded action type representing how the entry was updated. This is the column most relevant to searches using the term "updating_action_type"; the raw stored value resides in UPDATING_ACTION_TYPE on the base table and is translated via the ACTION_TYPE lookup.
• SUBPRIORITY, DATE_EARNED, SOURCE_TRIGGER_ENTRY, SOURCE_PERIOD, SOURCE_RUN_TYPE, SOURCE_START_DATE, SOURCE_END_DATE — Contextual attributes describing the payroll run or period that generated or affected the entry.
• BALANCE_ADJ_COST_FLAG — Decoded YES_NO indicator governing balance adjustment cost treatment.
• ATTRIBUTE1–20 and ENTRY_INFORMATION1–30 — Descriptive flexfield and entry information flexfield segments.
• OBJECT_VERSION_NUMBER — Optimistic locking version identifier.

Common Use Cases and Queries

This view is typically queried to report element entries with readable action types, creator types, and reasons, and to trace entries back to their originating payroll run or adjustment context.

• Auditing entries by update action: SELECT effective_start_date, entry_type, updating_action_type, source_run_type FROM paybv_element_entry WHERE updating_action_type = 'Adjustment';
• Tracing balance adjustments: filter on BALANCE_ADJ_COST_FLAG and REASON to isolate costed adjustments.
• Extracting flexfield detail: select ATTRIBUTE1–20 and ENTRY_INFORMATION1–30 for interface or migration workbooks.
• Date-effective reporting: constrain EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to the required period.

Because the view exposes codes such as CREATOR_TYPE_CODE and the duplicated ENTRY_TYPE alongside decoded meanings, consumers can display friendly text while retaining the underlying values needed for programmatic joins back to Payroll base entities.