Search Results tax_domain




Overview

APPS.PAYBV_US_TAX_TYPES_V is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It is registered in the Applications Design Data repository under the design name PAY.PAYBV_US_TAX_TYPES_V and carries a VALID status in both 12.1.1 and 12.2.2 environments. The object is classified as a view rather than a table, meaning it presents no independent storage and derives every row it returns from underlying Oracle Payroll (PAY) objects.

The view exposes the set of United States payroll tax types configured for an enterprise, together with the tax domain they belong to, the employee/employer code that governs their classification, and limit tax flag information. Positions in the payroll run, costing, and statutory reporting all depend on tax types being correctly identified, which makes this view a natural reporting surface for tax configuration analysis. Because it is a BIS view, it is intended for read-only query access by reporting tools, custom concurrent programs, and integration extracts rather than for direct DML.

Underlying Base Objects

The documented dependency list for PAYBV_US_TAX_TYPES_V identifies two referenced objects:

  • APPS.PAY_US_TAX_TYPES — a synonym that resolves to the underlying payroll tax type definition table holding the US legislative tax type attributes.
  • APPS.HR_BIS — the Human Resources Business Intelligence System package, invoked at runtime to supply BIS-level security context and column translation logic for the view.

The view is not referenced by any other database object, confirming its position as a terminal reporting layer. No public or private synonyms beyond the APPS synonym are documented in the excerpt. The dependency on HR_BIS is significant: BIS views commonly call this package to enforce row-level security derived from the user's HR organization hierarchy, so results returned can vary by the responsibility or session under which they are queried.

Key Columns

The view projects six columns:

  • TAX_TYPE_ID (NUMBER) — the surrogate primary key of the tax type record; the most reliable join key to other PAY tables such as PAY_US_TAX_TYPES or tax type usages.
  • TAX_TYPE_CODE (VARCHAR2 30) — the short code that uniquely identifies the tax type in payroll processing logic.
  • TAX_DOMAIN_CODE (VARCHAR2 30) — the coded value of the tax domain, suitable for joins and equality predicates.
  • TAX_DOMAIN (VARCHAR2 4000) — the descriptive, translated form of the tax domain. Its wide datatype indicates a concatenated or flexfield-expanded description, making it appropriate for display but not for joining.
  • EE_ER_CODE (VARCHAR2 30) — indicates whether the tax type is characteristically employee-side, employer-side, or otherwise attributed.
  • LIMIT_TAX_FLAG (VARCHAR2 30) — flag identifying tax types subject to wage base or contribution limits.

All columns are nullable per the documented metadata; none is marked mandatory.

Common Use Cases and Queries

Typical applications of this view include validating the completeness of US tax type setup during implementation or upgrade, extracting tax type reference data for downstream analytics, and cross-checking domain assignment against legislative requirements. The following queries reflect common patterns:

  • List all tax types with descriptive domain: SELECT tax_type_id, tax_type_code, tax_domain_code, tax_domain, ee_er_code, limit_tax_flag FROM apps.paybv_us_tax_types_v ORDER BY tax_domain_code, tax_type_code;
  • Count tax types per domain: SELECT tax_domain_code, COUNT(*) FROM apps.paybv_us_tax_types_v GROUP BY tax_domain_code;
  • Isolate limited tax types: SELECT tax_type_code, tax_domain FROM apps.paybv_us_tax_types_v WHERE limit_tax_flag = 'Y';
  • Distinguish employee from employer taxes: SELECT tax_type_code, ee_er_code FROM apps.paybv_us_tax_types_v WHERE ee_er_code = 'ER';

Because BIS security may filter rows, cross-validate results against PAY_US_TAX_TYPES when preparing data reconciliation reports, and always join on TAX_TYPE_ID or TAX_TYPE_CODE rather than on the descriptive TAX_DOMAIN column.