Search Results date_vehicle_returned

Overview

APPS.PAY_IE_BIK_COMPANY_VEHICLES_V is a reporting view in the Oracle E-Business Suite Applications schema (APPS) that consolidates company vehicle benefit-in-kind (BIK) data for Irish payroll processing. The object is classified as an internal view (View Type: Internal) and carries the Oracle warning that it is for internal use only and that access is not supported except through standard Oracle Applications programs. Its purpose is to expose, in a single denormalised row per assignment, the vehicle allocation details required to assess and report the taxable benefit arising from an employer-provided vehicle under Irish Revenue rules administered through the Irish BIK functionality in Oracle Payroll.

Because the view joins person, assignment, payroll, payroll run result and vehicle repository data, it is most naturally consumed by extract, reporting and reconciliation processes rather than by transactional screens. It presents a flattened, ready-to-query result set aligned to the Irish BIK payroll element structure, and is typically used by statutory reporting, year-end processing and audit activities.

Underlying Base Objects

The view is defined over a set of base objects spanning the Payroll (PAY), Human Resources (PER/HR) and Advanced Procurement/Vehicle (PQP) product families. Documented dependencies are:

• PAY_IE_BIK (package) — the Irish BIK calculation package, which supplies the business rules and derived values.
• PAY_RUN_RESULTS, PAY_RUN_RESULT_VALUES, PAY_INPUT_VALUES_F, PAY_ELEMENT_TYPES_F, PAY_ASSIGNMENT_ACTIONS — payroll run and element data used to derive the BIK amounts and reporting attributes.
• PAY_PAYROLLS_F, PAY_PAYROLL_ACTIONS — payroll and action context, supporting the PAYROLL_ID column.
• PQP_VEHICLE_ALLOCATIONS_F, PQP_VEHICLE_REPOSITORY_F — the vehicle allocation and vehicle master records (registration number, market value).
• PER_ASSIGNMENTS_F, PER_PEOPLE_F — assignment and person records.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY — person name formatting and row-level security enforcement.

Note that PAY_PAYROLLS_F, PER_ASSIGNMENTS_F and PER_PEOPLE_F are views, while the remaining PAY, PQP and HR objects are resolved through synonyms or packages. The view is not referenced by any other database object, so it sits at the leaf of the dependency chain.

Key Columns

• PPS_NO — the Irish Personal Public Service Number, the unique individual identifier used in Irish payroll reporting.
• SURNAME, FIRST_NAME — formatted person name (from HR_PERSON_NAME).
• ASSIGNMENT_NUMBER, ASSIGNMENT_ID, ASSIGNMENT_SET_ID — assignment identity and set context.
• DATE_VEHICLE_PROVIDED, DATE_VEHICLE_RETURNED — the period during which the vehicle was made available, used to pro-rate the benefit.
• ORIG_MARKET_VALUE_OF_VEHICLE, VEHICLE_REGISTRATION_NUMBER — vehicle valuation and identification from the PQP repository and allocation records.
• CALCULATION_METHOD, DECLARED_BUSINESS_MILEAGE — method of BIK computation and declared business mileage.
• CUMULATIVE_BUSINESS_MILEAGE, CUMULATIVE_TOTAL_MILEAGE — mileage accumulators supporting the business/private mileage split.
• PAYROLL_ID, CONSOLIDATION_SET_ID — payroll and consolidation grouping identifiers for aggregation and reporting.

Common Use Cases and Queries

Typical scenarios include producing Irish BIK summaries for revenue reporting, reconciling vehicle allocations against payroll deductions, and auditing declared versus cumulative mileage. A basic extract follows:

• Point lookup: SELECT * FROM APPS.PAY_IE_BIK_COMPANY_VEHICLES_V WHERE PPS_NO = :pps_no;
• Payroll extract: SELECT pps_no, surname, first_name, vehicle_registration_number, orig_market_value_of_vehicle, cumulative_business_mileage, cumulative_total_mileage FROM APPS.PAY_IE_BIK_COMPANY_VEHICLES_V WHERE payroll_id = :payroll_id;
• Period analysis: SELECT assignment_number, date_vehicle_provided, date_vehicle_returned FROM APPS.PAY_IE_BIK_COMPANY_VEHICLES_V WHERE date_vehicle_provided BETWEEN :from_date AND :to_date;

Because row-level security is applied via HR_SECURITY, results are restricted to assignments visible to the querying user. Given the Oracle Internal Use Only designation, production usage should follow supported payroll reporting paths rather than direct ad-hoc access.