Search Results tax_balance_id




Overview
Explore in AI Chat

Overview

The view PAYBV_US_TAX_REPORT_BALANCES_V is a read-only database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Payroll (PAY) product family and is classified as a business view, as indicated by the PAYBV_ naming convention. Its documented status is VALID.

The view presents a restricted projection of United States tax reporting balance information. It exposes only three columns of interest to downstream reporting and integration logic: REPORT_CODE, BALANCE_PRINT_SEQUENCE, and TAX_BALANCE_ID. Critically, the view text defines the source with a WITH READ ONLY clause, meaning the object cannot be used for DML operations; it exists purely for query and retrieval purposes. This makes it appropriate for reporting engines, extracts, and program logic that must reference US tax report balance identifiers without exposing the full underlying balance table.

Because the view is read-only and narrowly columned, it functions as a controlled access surface over US tax report balance configuration data maintained within the Payroll application, particularly in the context of statutory US tax reporting layouts and their associated balance definitions.

Underlying Base Objects

The view is defined over a single base object referenced in the ETRM metadata as the synonym PAY_US_TAX_REPORT_BALANCES. The view definition selects from this object, aliased as PUTRB, and projects the three columns identified in the view text.

At runtime, the synonym PAY_US_TAX_REPORT_BALANCES resolves to the corresponding base table in the APPS schema that stores US tax report balance records. Each row of that base table associates a tax report code with a balance definition and a sequencing attribute governing print order on the report. The view does not join additional tables, does not aggregate data, and does not apply filtering predicates beyond the read-only constraint. Consequently, the view is a direct, unfiltered projection: row cardinality matches the base table, and each view column maps one-to-one to a base table column.

Because only three columns are exposed, consumers of the view rely on the base table for all other attributes, such as descriptive text, effective dates, or tax reporting unit context. The TAX_BALANCE_ID serves as the linkage key back to the base table when broader attribute retrieval is required.

Key Columns

  • REPORT_CODE — Identifies the US tax report to which the balance belongs. It is the primary organizing attribute for grouping balance lines by report.
  • BALANCE_PRINT_SEQUENCE — A numeric ordering value that determines the position at which the associated balance prints on the tax report. It controls the presentation sequence of balance lines within a report code.
  • TAX_BALANCE_ID — The unique identifier for the tax balance record. This is the search key most commonly used to locate a specific balance entry, and it is the column users reference when searching for "tax_balance_id." It also functions as the join key to the base table for retrieving additional columns.

Common Use Cases and Queries

Typical scenarios include determining the print order of balances for a given US tax report, resolving a TAX_BALANCE_ID to its report context, and driving reporting extracts that require a stable, read-only source of balance identifiers.

To list all balances for a specific report in print order:

  • SELECT report_code, balance_print_sequence, tax_balance_id FROM apps.paybv_us_tax_report_balances_v WHERE report_code = :p_report_code ORDER BY balance_print_sequence;

To resolve a specific tax balance identifier:

  • SELECT report_code, balance_print_sequence FROM apps.paybv_us_tax_report_balances_v WHERE tax_balance_id = :p_tax_balance_id;

To enumerate report codes and their balance counts:

  • SELECT report_code, COUNT(*) balance_count FROM apps.paybv_us_tax_report_balances_v GROUP BY report_code;

Because the view is read-only, all three patterns are restricted to query use. Inserts, updates, and deletes must target the underlying PAY_US_TAX_REPORT_BALANCES table through supported Payroll maintenance processes.