Search Results annual_salary




Overview
Explore in AI Chat

Overview

APPS.PAYBV_EMPLOYEE_ARCHIVE is a Business Intelligence System (BIS) view owned by the APPS schema and registered in Oracle EBS under the FND Design Data namespace PAY.PAYBV_EMPLOYEE_ARCHIVE. Its status is VALID. As a BIS view, it is not a transactional entity but a read-optimized, denormalized projection intended for reporting, data extraction, and downstream integration rather than for DML. In EBS 12.1.1 and 12.2.2 the "BV" naming convention identifies views delivered specifically for business intelligence and analytics consumption, typically exposing human-readable descriptive attributes alongside surrogate identifiers so that reporting tools can generate results without additional joins.

The view exposes payroll and HR assignment information at the employee/assignment level, including employer, tax unit, organization, job, grade, and compensation attributes. Because the user query referenced "annual_salary," the view is relevant to compensation analytics: ANNUAL_SALARY and PAY_RATE are numeric columns exposed directly, allowing salary reporting without navigating the underlying payroll action framework. The view reflects archive-oriented employee data, meaning it is suited to point-in-time or historical reporting of assignments and their associated pay attributes.

Underlying Base Objects

The ETRM dependency metadata documents that APPS.PAYBV_EMPLOYEE_ARCHIVE references the synonym PAY_ACTION_INFORMATION (base object PAY_ACTI) and the package PAY_AC_UTIL. PAY_ACTI stores the payload of payroll actions — the context and data generated when payroll processes execute. PAY_AC_UTIL is a PL/SQL utility package used across payroll action processing to derive, format, or validate the values written into action information. The BIS view therefore reads action-oriented data and presents it through a business-friendly column layout, with the package logic (further exposed through FND Design Data PAY.PAYBV_EMPLOYEE_ARCHIVE) shaping several of the descriptive VARCHAR2 columns. No additional base tables are documented; any reporting dependency should be traced through PAY_ACTI and the utility package rather than assumed from the view columns alone.

Key Columns

Common Use Cases and Queries

Typical uses include compensation analysis (distribution of ANNUAL_SALARY by organization, grade, or job), headcount and assignment reporting, and extraction of employee/pay data into an external warehouse using EFFECTIVE_DATE as the as-of control. The columns are exposed directly as a flat list, so reporting tools can select them without joining PAY_ACTI.

Salary distribution by organization:

SELECT ORGANIZATION_NAME, GRADE, COUNT(*) headcount, AVG(ANNUAL_SALARY) avg_salary FROM APPS.PAYBV_EMPLOYEE_ARCHIVE WHERE ANNUAL_SALARY IS NOT NULL GROUP BY ORGANIZATION_NAME, GRADE ORDER BY ORGANIZATION_NAME, GRADE;

Effective-dated employee salary extraction:

SELECT EMPLOYEE_NUMBER, FULL_NAME, ASSIGNMENT_NUMBER, JOB, PAY_RATE, ANNUAL_SALARY, EFFECTIVE_DATE FROM APPS.PAYBV_EMPLOYEE_ARCHIVE WHERE EFFECTIVE_DATE BETWEEN :start_date AND :end_date ORDER BY EMPLOYEE_NUMBER, EFFECTIVE_DATE;

Reporting should treat the view as read-only and validate duplicate rows per assignment and EFFECTIVE_DATE, since a single assignment may appear at multiple effective dates.