Results for “tax_group”

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

Overview

PAY_US_BALANCE_VALUES_V is an APPS-owned database view within the Oracle E-Business Suite Payroll (PAY) module. It exposes payroll balance values resolved at the assignment-action level for United States legislative requirements, joining payroll action, balance definition, assignment action, and US assignment reporting data. The view is documented with status VALID and is catalogued in ETRM for both 12.1.1 and 12.2.2 releases. Its documented description references a sales / ADS disco workbook requirement, indicating the view was created to satisfy a specific reporting deliverable rather than as a general-purpose seeded object. Functionally, it serves as a reporting and integration surface that presents computed balance amounts alongside the jurisdiction and tax group context in which those balances were evaluated.

Underlying Base Objects

The view is defined over a combination of payroll and HR tables accessible through APPS synonyms. The principal base objects recorded in the ETRM metadata are FF_CONTEXTS, FF_ROUTE_CONTEXT_USAGES, HR_ORGANIZATION_INFORMATION, PAY_ASSIGNMENT_ACTIONS, PAY_BALANCE_DIMENSIONS, PAY_BALANCE_FEEDS_F, PAY_BALANCE_TYPES, PAY_DEFINED_BALANCES, PAY_PAYROLL_ACTIONS, PAY_RUN_RESULTS, PAY_RUN_RESULT_VALUES, and PAY_US_ASG_REPORTING. It also invokes the PAY_BALANCE_PKG package.

The view text joins PAY_ASSIGNMENT_ACTIONS to PAY_PAYROLL_ACTIONS to obtain the effective date of the payroll action, then links PAY_DEFINED_BALANCES to PAY_BALANCE_TYPES and PAY_BALANCE_DIMENSIONS to resolve balance names and dimensions. US jurisdiction context is derived from PAY_US_ASG_REPORTING and HR_ORGANIZATION_INFORMATION filtered by the FEDERAL TAX RULES context. Balance amounts are resolved through PAY_BALANCE_PKG.GET_VALUE. A correlated subquery on PAY_US_ASG_REPORTING selects a single jurisdiction row per assignment, honouring the jurisdiction level defined on the balance type. An EXISTS clause against PAY_BALANCE_FEEDS_F, PAY_RUN_RESULTS, and PAY_RUN_RESULT_VALUES ensures that only balance types actually fed by run results within the payroll action effective date range are returned.

Key Columns

• ASSIGNMENT_ACTION_ID — Identifier of the assignment action row from PAY_ASSIGNMENT_ACTIONS, anchoring each balance value to a specific payroll processing action.
• ASSIGNMENT_ID — The assignment whose balance is being reported.
• PAYROLL_ACTION_ID — Identifier of the parent payroll action.
• EFFECTIVE_DATE — Effective date of the payroll action, used as the evaluation date for the balance value.
• BALANCE_TYPE_ID / BALANCE_NAME — Identifier and user-facing name of the balance type being evaluated.
• BALANCE_DIMENSION_ID / DIMENSION_NAME / DATABASE_ITEM_SUFFIX / DIMENSION_DESCRIPTION — Dimension metadata describing the balance definition.
• DEFINED_BALANCE_ID / ROUTE_ID — References to the defined balance and its associated route.
• VALUE — The computed balance amount returned by PAY_BALANCE_PKG.GET_VALUE for the defined balance, assignment action, tax unit, jurisdiction, tax group, and effective date.
• JURISDICTION_CODE — The US jurisdiction code applicable to the assignment action.
• TAX_GROUP — The federal tax rules organisation information value (ORG_INFORMATION5) identifying the tax group context.

Common Use Cases and Queries

The view is typically used to extract US payroll balance values for a given assignment action or payroll run, preserving jurisdiction and tax group context. A representative query retrieves balance values for a specific assignment action:

• SELECT assignment_action_id, assignment_id, balance_name, dimension_name, jurisdiction_code, tax_group, value FROM apps.pay_us_balance_values_v WHERE assignment_action_id = :p_assignment_action_id;
• SELECT balance_name, SUM(value) FROM apps.pay_us_balance_values_v WHERE effective_date BETWEEN :p_start AND :p_end GROUP BY balance_name;

Typical scenarios include reconciliation of US payroll balances against run results, feeding downstream tax reporting, and validating that balance feeds exist for the balance types returned. Because the view performs package-based value resolution and correlated subqueries, query performance benefits from filtering on ASSIGNMENT_ACTION_ID or PAYROLL_ACTION_ID rather than scanning the full result set.