Search Results paybv_employee_archive




Overview
Explore in AI Chat

Overview

PAYBV_EMPLOYEE_ARCHIVE is an APPS-owned read-only database view in the Oracle E-Business Suite Payroll (PAY) module. It exposes archived employee assignment details captured during the processing of payroll actions, specifically those recorded against the action context type AAP and the action information category EMPLOYEE DETAILS. The view presents a denormalised, human-readable projection of the PAY_ACTION_INFORMATION table, converting the generic ACTION_INFORMATION1 through ACTION_INFORMATION30 slots into named business columns such as FULL_NAME, NATIONAL_IDENTIFIER, JOB, and PAY_RATE.

Because the view carries a WITH READ ONLY clause, it is strictly a reporting and integration artefact. It plays a significant role wherever historical payroll/HR snapshots must be reproduced — for example, statutory reporting, audit trails, or interfaces that must reconstruct the state of an employee record at the time a payroll action was executed. In the context of the user search term national_identifier, this view is notable because it surfaces the NATIONAL_IDENTIFIER column directly, mapped from ACTION_INFORMATION4, allowing consumers to retrieve the employee national identifier without decoding the underlying generic information slots. This is directly relevant to 12.1.1 and 12.2.2 environments where legislative or payroll reports require a traceable national ID per assignment.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over two documented referenced objects:

The view therefore inherits the structure of the action information model, where each logical attribute is stored positionally in ACTION_INFORMATIONn columns. The view's SELECT list performs the semantic mapping of these positions to meaningful aliases, and the date conversion of selected slots into true date values.

Key Columns

Common Use Cases and Queries

Typical scenarios include reconstructing an employee's assignment state for a given action, producing national identifier reports, and feeding downstream interfaces with named employee attributes.

Retrieve the national identifier and key assignment details for a specific assignment:

  • SELECT assignment_id, employee_number, full_name, national_identifier, job, pay_rate
  • FROM apps.paybv_employee_archive
  • WHERE assignment_id = :p_assignment_id
  • ORDER BY effective_date DESC;

Search by national identifier across archived records:

  • SELECT employee_number, full_name, national_identifier, effective_date
  • FROM apps.paybv_employee_archive
  • WHERE national_identifier = :p_national_id;

Report all employee detail snapshots for a tax unit within a date range:

  • SELECT tax_unit_id, employee_number, organization_name, original_hire_date, payment_date
  • FROM apps.paybv_employee_archive
  • WHERE tax_unit_id = :p_tax_unit_id
  • AND payment_date BETWEEN :p_from AND :p_to;

Because the view is read-only and derived from PAY_ACTION_INFORMATION, query performance benefits from filtering on the indexed action context columns and from restricting by tax unit, date, or assignment. No DML should ever be attempted against this object.