Search Results earn_run_val




Overview
Explore in AI Chat

Overview

APPS.PAY_MX_EMPLOYEE_EARNINGS_V is a valid Oracle E-Business Suite database view owned by the APPS schema and registered under FND Design Data as PAY.PAY_MX_EMPLOYEE_EARNINGS_V. It presents a denormalized, reporting-oriented projection of employee earnings and absence balances for Mexican payroll processing. The view consolidates payroll action context (assignment actions, payroll actions, run types, dates) with earning balance and days balance values, exposing run-to-date and year-to-date figures alongside the balance names and reporting names that users recognize in the application.

The view is particularly relevant to the search term earn_bal_name, since it exposes both EARN_BAL_NAME and EARN_REPORTING_NAME as VARCHAR2(4000) columns, allowing consumers to resolve an earning balance's system name and its user-facing reporting name without joining directly to PAY_BALANCE_TYPES. The view is documented with an Oracle Internal Use Only warning and is not supported for direct customer access except from standard Oracle Applications programs. Its View Type is recorded as Internal. In 12.1.1 and 12.2.2 the object remains VALID, and a public synonym PAY_MX_EMPLOYEE_EARNINGS_V is defined, so the view can be referenced unqualified by applications and custom reports.

Underlying Base Objects

The view is defined over the following documented base objects: PAY_AC_UTILITY (package), PAY_ASSIGNMENT_ACTIONS, PAY_BALANCE_ATTRIBUTES, PAY_BALANCE_TYPES, PAY_BAL_ATTRIBUTE_DEFINITIONS, PAY_DEFINED_BALANCES, PAY_MX_UTILITY (package), PAY_PAYROLL_ACTIONS, and PAY_RUN_BALANCES. The package references, PAY_AC_UTILITY and PAY_MX_UTILITY, supply the Mexican localization logic used to derive balance values and localization-specific attributes, while PAY_RUN_BALANCES holds the actual run and year-to-date balance amounts that are pivoted into the EARN_RUN_VAL, EARN_YTD_VAL, DAYS_RUN_VAL, and DAYS_YTD_VAL columns.

Balance definition and naming metadata originates from PAY_BALANCE_TYPES, PAY_BALANCE_ATTRIBUTES, PAY_BAL_ATTRIBUTE_DEFINITIONS, and PAY_DEFINED_BALANCES, which together determine the balance identifiers, names, reporting names, and unit of measure exposed by the view. Payroll action context is retrieved from PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS, providing the assignment, action, and run identifiers that tie each balance row to a specific payroll run. The view is referenced by the public synonym PAY_MX_EMPLOYEE_EARNINGS_V.

Key Columns

Common Use Cases and Queries

Typical usage covers Mexican payroll reporting and integration extracts where earning balances must be reported by balance name or reporting name alongside run and year-to-date values. A common pattern filters on the earning balance name:

SELECT assignment_id, date_earned, earn_bal_name, earn_reporting_name, earn_run_val, earn_ytd_val FROM apps.pay_mx_employee_earnings_v WHERE earn_bal_name = :p_balance_name ORDER BY assignment_id, date_earned;

Another frequent scenario retrieves all earnings for a given assignment and date range:

SELECT earn_bal_name, earn_reporting_name, earn_bal_uom, earn_run_val, earn_ytd_val FROM apps.pay_mx_employee_earnings_v WHERE assignment_id = :p_assignment_id AND date_earned BETWEEN :p_start AND :p_end;

Absence balances are queried through the days columns, using DAYS_BAL_NAME or DAYS_REPORTING_NAME. Because the view is documented as Oracle Internal Use Only, custom development should treat it as a read-only reporting convenience and validate behavior against the specific 12.1.1 or 12.2.2 patch level in use.