Results for “tax_code”

14 results




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

Overview

The PA_OUTPUT_TAX_CODE_SETUP_V view is a Projects (PA) module construct owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It exposes the set of output tax names and tax codes that are currently active for a given operating unit. The view is a filtered, de-duplicated projection over the transaction-level tax code view PA_OUTPUT_TAX_CODE_TXN_V, and it isolates only those tax codes whose effective date range encompasses the current system date.

Its role is that of a lightweight reference or lookup source. Rather than maintaining a dedicated tax code setup table for Projects, EBS derives the available output tax codes dynamically from the tax configuration, and this view presents that derived list in a consumable form. Reporting, concurrent programs, and integration layers can query it to obtain a valid, current list of tax codes without re-deriving the date logic themselves. Because the view returns only presently effective codes, it is well suited to validation and list-of-values use where stale or future-dated tax codes must be excluded.

Underlying Base Objects

Per the documented ETRM metadata, the view references a single base object:

  • PA_OUTPUT_TAX_CODE_TXN_V (VIEW) — the parent view from which tax name, tax code, and operating unit are sourced.

No base tables are listed directly; the table-level derivation is inherited from PA_OUTPUT_TAX_CODE_TXN_V, which in turn resolves against the tax setup and transaction data within the Projects schema. The dependency is therefore a view-over-view relationship, with PA_OUTPUT_TAX_CODE_SETUP_V adding a date-effectiveness filter and a DISTINCT operation on top of the parent result set.

Key Columns

The view exposes three columns:

  • TAX_NAME — the descriptive name of the output tax, used for display and selection in user-facing lists.
  • TAX_CODE — the tax code identifier, the value typically referenced by transactions and by downstream interfaces.
  • ORG_ID — the operating unit identifier, allowing the same tax code to be distinguished across organizations.

The DISTINCT clause ensures that duplicate rows arising in the parent view (for example, where the same tax name and code recur across effective records) collapse into a single entry per tax name, tax code, and operating unit combination.

Common Use Cases and Queries

The view is commonly used to populate lists of values, to validate user-entered tax codes, and to confirm which output tax codes are currently in force for an operating unit. A representative query returning all active output tax codes is shown below:

  • SELECT tax_name, tax_code, org_id FROM apps.pa_output_tax_code_setup_v ORDER BY org_id, tax_code;
  • SELECT tax_code FROM apps.pa_output_tax_code_setup_v WHERE org_id = :p_org_id AND tax_name = :p_tax_name;
  • SELECT COUNT(DISTINCT tax_code) FROM apps.pa_output_tax_code_setup_v WHERE org_id = :p_org_id;

Because the view is date-sensitive and non-deterministic over time, reports that require historical tax codes should reference PA_OUTPUT_TAX_CODE_TXN_V directly with explicit date predicates rather than reliance on the SYSDATE-driven filter embedded here. Where the operating unit is not supplied, callers should expect rows for multiple organizations and must constrain ORG_ID to enforce operating-unit security and correct context.