Results for “balance_uom”

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

Overview

PAY_MX_TAX_BALANCES_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product, delivered as a reporting and integration layer for Mexican (MX) statutory tax balances. The view flattens payroll action, assignment action, balance type, and run balance data into a single row-per-action, per-tax-unit structure, allowing consumers to query State of Mexico (SOE) tax balance results without navigating the underlying balance engine directly. Because the view is defined with STATUS VALID and resides in the APPS schema, it is visible to any responsibility or concurrent program with the appropriate grants.

The view is particularly relevant to localization reporting. Its WHERE clause is hard-coded to PBAD.LEGISLATION_CODE = 'MX' and filtered through the balance attribute named 'SOE TAX BALANCES' whose business group is null (i.e., the seeded, legislation-level definition). Only balances with a corresponding PAY_RUN_BALANCES row effective between the start of the payroll action year and the action effective date are returned.

Underlying Base Objects

The view joins eight objects: PAY_PAYROLL_ACTIONS (PPA) and PAY_ASSIGNMENT_ACTIONS (PAA) supply the payroll/action lifecycle; PAY_BALANCE_TYPES (PBT), PAY_DEFINED_BALANCES (PDB), PAY_BALANCE_ATTRIBUTES (PBA), and PAY_BAL_ATTRIBUTE_DEFINITIONS (PBAD) supply balance metadata and the 'SOE TAX BALANCES' attribute linkage; PAY_RUN_BALANCES appears in an EXISTS subquery to restrict rows to assignments and tax units with actual computed run balances; and PAY_AC_UTILITY is invoked four times as a server-side API to resolve balance names, reporting names, and the GRE run and GRE YTD values.

Key Columns

The view exposes the following columns (as documented): ASSIGNMENT_ID, TAX_UNIT_ID, ASSIGNMENT_ACTION_ID, ACTION_STATUS, PAYROLL_ACTION_ID, ACTION_TYPE, DATE_PAID, DATE_EARNED, BUSINESS_GROUP_ID, RUN_TYPE_ID, BALANCE_TYPE_ID, BALANCE_NAME, REPORTING_NAME, BALANCE_UOM, RUN_VAL, and YTD_VAL. Reporting_NAME is derived via PAY_AC_UTILITY.GET_BAL_REPORTING_NAME(PBT.BALANCE_TYPE_ID) — the very attribute users search on when locating this object. RUN_VAL and YTD_VAL are computed through PAY_AC_UTILITY.GET_VALUE using the context keys '_ASG_GRE_RUN' and '_ASG_GRE_YTD', scoped by business group, legislation, assignment action, tax unit, and effective date. DATE_PAID is aliased from PPA.EFFECTIVE_DATE, and DATE_EARNED originates from the payroll action.

Common Use Cases and Queries

Typical usage includes MX payroll tax reporting, reconciliation of GRE balances against PAY_RUN_BALANCES, and integrations feeding tax filings. A representative query is:

SELECT assignment_id, tax_unit_id, date_earned, balance_name,
       reporting_name, run_val, ytd_val
FROM   apps.pay_mx_tax_balances_v
WHERE  business_group_id = :p_bg_id
AND    date_paid BETWEEN :p_start AND :p_end;

Aggregate reporting by tax unit is also common:

SELECT tax_unit_id, reporting_name, SUM(run_val), SUM(ytd_val)
FROM   apps.pay_mx_tax_balances_v
GROUP  BY tax_unit_id, reporting_name;

Because RUN_VAL and YTD_VAL are resolved per row through PAY_AC_UTILITY, performance-sensitive reports should filter aggressively by business group, date range, and tax unit.