Search Results entry_start_date

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

Overview

PAYBV_ELEMENT_ENTRY_DET is an APPS-owned reporting view in the Oracle E-Business Suite Payroll (PAY) module, documented as VALID and exposed for both 12.1.1 and 12.2.2. It presents a denormalized, business-friendly projection of element entries — the individual payroll elements (earnings, deductions, contributions, and similar) assigned to an assignment for a given payroll period. Rather than requiring report authors to join the base element entry, assignment, people, payroll, time period, and location objects manually, the view pre-resolves descriptive attributes such as employee name, assignment number, payroll and GRE names, and the input values attached to each entry.

The view is intended primarily for ad hoc reporting, BI Publisher datasets, and downstream integration extracts. Its most distinctive characteristic is the heavy reliance on the PAY_ADHOC_UTILS_PKG.GET_INPUT_NAME function, which dynamically resolves element input names and values by passing the element entry identifier, an input ordinal, the requested attribute, and the effective date boundaries of the assignment, payroll period, and element entry itself. This function-driven design allows the view to surface input values that are date-effectively correct for the period in question, an important consideration in payroll reporting.

Underlying Base Objects

ETRM documentation records the following referenced objects: PAY_ADHOC_UTILS_PKG, PAY_COSTING_DETAIL_REP_PKG, HR_BIS, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY (packages); HR_LOCATIONS, HR_ORGANIZATION_UNITS, PAY_PAYROLLS_F, PER_ASSIGNMENTS_F, and PER_PEOPLE_F (views); and PAY_ELEMENT_ENTRIES_F, PER_TIME_PERIODS, and HR_SOFT_CODING_KEYFLEX (synonyms).

The transactional core is PAY_ELEMENT_ENTRIES_F, which supplies the element entry identifier and its effective start and end dates. PER_ASSIGNMENTS_F and PER_PEOPLE_F provide assignment number, employee number, and person identifiers, while HR_PERSON_NAME resolves the last, first, and middle names. PAY_PAYROLLS_F supplies the payroll name, and PER_TIME_PERIODS supplies the payroll period start and end dates used as function parameters. HR_LOCATIONS and HR_ORGANIZATION_UNITS contribute location and organization names. HR_SOFT_CODING_KEYFLEX supplies the segment used as the tax unit identifier, with PAY_COSTING_DETAIL_REP_PKG deriving the GRE name. HR_BIS performs lookup decoding, and HR_SECURITY and HR_GENERAL enforce row-level access and session context.

Key Columns

• LAST_NAME, FIRST_NAME, MIDDLE_NAMES, EMPLOYEE_NUMBER, ASSIGNMENT_NUMBER, NATIONAL_IDENTIFIER — employee and assignment identification.
• PAYROLL_NAME, ORGANIZATION_NAME, TAX_UNIT_ID, GRE_NAME, LOCATION_CODE — payroll, organization, tax unit, GRE, and location context.
• ELEMENT_NAME, CLASSIFICATION, RECURRING, SOURCE — element identity and classification; SOURCE is decoded from CREATOR_TYPE via HR_BIS.BIS_DECODE_LOOKUP.
• INPUT_VALUE1_NAME / VALUE1 through INPUT_VALUE3_NAME / VALUE3 — the first three element input names and their values, resolved by GET_INPUT_NAME.
• Effective dates — the view passes PEE.EFFECTIVE_START_DATE and PEE.EFFECTIVE_END_DATE, together with the time period boundaries, into each function call; the element entry end date governs whether an entry is considered active for the reported period.

Common Use Cases and Queries

Typical scenarios include auditing recurring versus non-recurring element entries, reconciling payroll input values for a period, and extracting earnings and deduction detail for interface files. Because the view is function-driven and returns limited input columns (three), high-volume extractions may perform better against PAY_ELEMENT_ENTRIES_F and PAY_ELEMENT_ENTRY_VALUES_F directly.

Sample query pattern:

• SELECT employee_number, assignment_number, payroll_name, element_name, classification, recurring, input_value1_name, value1 FROM apps.paybv_element_entry_det WHERE payroll_name = :p_payroll AND element_name = :p_element ORDER BY employee_number;
• Filter by SOURCE = 'Payroll' to isolate entries created by the payroll run, or by ORGANIZATION_NAME to scope results to a business group or GRE.

As with all HR-secured views, results are constrained by the HR_SECURITY predicate for the connected user, so the query returns only assignments the user is authorized to view.