Results for “location_code”

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

Overview

PAY_US_GTN_TAX_UNITS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered as part of the Oracle Payroll (PAY) product family and exposes a consolidated, reporting-friendly representation of tax units associated with United States payroll reporting data. The view is closely related to HR_TAX_UNITS_V, the base tax unit view that callers frequently reference when searching for tax unit information; PAY_US_GTN_TAX_UNITS_V extends that concept by joining assignment-level reporting data to produce a location-, organization-, and tax-unit-oriented result set.

Its primary purpose is to support extraction and reporting of "GTN" (Geographic Tax Nexus / tax-assignment) relationships between assignments, tax units, locations, and organizations. Because the underlying assignments are filtered by the current effective date, the view returns only currently active assignment rows, making it suitable for point-in-time payroll and tax reporting.

Underlying Base Objects

The documented referenced objects are FND_NUMBER (package), HR_ALL_ORGANIZATION_UNITS (synonym), HR_GENERAL (package), HR_LOCATIONS (view), HR_TAX_UNITS_V (view), PAY_US_ASG_REPORTING (synonym), and PER_ALL_ASSIGNMENTS_F (synonym). The view is defined as the UNION of three distinct component queries:

• Location-based component ('L'): Joins PAY_US_ASG_REPORTING, HR_TAX_UNITS_V, HR_LOCATIONS, and PER_ALL_ASSIGNMENTS_F to return tax units linked to an assignment's location.
• Organization-based component ('O'): Joins the same reporting and assignment objects with HR_ALL_ORGANIZATION_UNITS to return tax units linked to an assignment's organization.
• Generic component ('G'): Returns the tax unit directly from PAY_US_ASG_REPORTING and HR_TAX_UNITS_V, with location and organization columns nulled via the FND_NUMBER.CANONICAL_TO_NUMBER(NULL) conversion.

The three branches are combined with UNION (implicitly DISTINCT), so duplicate tax-unit rows are eliminated. The effective-dated predicate SYSDATE BETWEEN PAF.EFFECTIVE_START_DATE AND PAF.EFFECTIVE_END_DATE restricts results to assignments active as of the query date.

Key Columns

• TAX_UNIT_ID — Surrogate identifier of the tax unit.
• NAME — The tax unit name as sourced from HR_TAX_UNITS_V.
• LOCATION_ID / LOCATION_CODE — Location identifier and code where the assignment is associated; null for the 'G' branch.
• ORGANIZATION_ID / ORGANIZATION_NAME — Organization identifier and name; ORGANIZATION_NAME is null in the 'L' branch and both are null in the 'G' branch.
• TYPE — A discriminator indicating the source branch: 'L' for location, 'O' for organization, 'G' for generic tax-unit-only rows.

Common Use Cases and Queries

This view is typically consumed in US payroll tax reporting, interface extracts, and reconciliation where tax units must be correlated with locations or organizations. It supersedes direct querying of HR_TAX_UNITS_V for assignment-aware reporting.

Example — list active tax units by type:

• SELECT tax_unit_id, name, location_code, organization_name, type FROM apps.pay_us_gtn_tax_units_v WHERE type = 'O';

Example — locate tax units for a specific organization:

• SELECT tax_unit_id, name, location_code FROM apps.pay_us_gtn_tax_units_v WHERE organization_id = :p_org_id ORDER BY name;

Because the view is a UNION with DISTINCT semantics and date-filtered assignment joins, users should expect moderate performance cost on large assignment sets and should supply selective predicates where possible.