Search Results pa_expenditure_type_ous_all




Overview
Explore in AI Chat

Overview

The PA_EXPENDITURE_TYPE_OUS_ALL table is a core data object within the Oracle E-Business Suite (EBS) Projects module (PA). It serves as a critical junction table that enables the configuration of tax codes at the operating unit level for specific expenditure types. Its primary role is to store operating unit-specific tax overrides, allowing organizations to define distinct tax rules (specifically for Output VAT) for the same expenditure type across different legal entities or business units within a multi-org implementation. This table is essential for ensuring accurate tax calculations on project-related expenditures, which is a fundamental requirement for financial compliance and reporting.

Key Information Stored

The table's structure is designed to link expenditure types, operating units, and tax codes. While the full column list is not detailed in the provided metadata, the documented foreign key relationships reveal its most critical columns. The key identifier columns are EXPENDITURE_TYPE and ORG_ID, which together form a unique constraint linking to the master expenditure type and the operating unit setup, respectively. The most significant data column is OUTPUT_VAT_TAX_ID, which stores the specific tax code identifier from the Receivables (AR) tax repository. This ID points to the detailed tax rate and rules defined in AR_VAT_TAX_ALL_B, applying them to the given expenditure type for the specified operating unit.

Common Use Cases and Queries

A primary use case is the setup and maintenance of project-specific taxation during implementation or when adding new operating units. Financial analysts and project accountants query this table to audit or report on the tax codes applied to project costs. A common reporting query involves joining to related master tables to produce a human-readable list. For example:

  • Identifying the configured tax codes for all expenditure types in a specific operating unit.
  • Validating that all active expenditure types have an appropriate tax assignment.
  • Troubleshooting discrepancies in tax amounts on project invoices or cost distributions by verifying the assigned OUTPUT_VAT_TAX_ID.

A typical SQL pattern retrieves the expenditure type name and tax code:
SELECT pet.expenditure_type, pet.description, arv.tax_code
FROM pa_expenditure_type_ous_all petou,
pa_expenditure_types pet,
ar_vat_tax_all_b arv
WHERE petou.expenditure_type = pet.expenditure_type
AND petou.output_vat_tax_id = arv.vat_tax_id
AND petou.org_id = :p_org_id;

Related Objects

The table maintains strict referential integrity through its foreign key constraints, linking it to master data across the Projects and Financials modules. The documented relationships are:

  • PA_EXPENDITURE_TYPES: References via PA_EXPENDITURE_TYPE_OUS_ALL.EXPENDITURE_TYPE. This is the master definition table for all expenditure categories in Projects.
  • PA_IMPLEMENTATIONS_ALL: References via PA_EXPENDITURE_TYPE_OUS_ALL.ORG_ID. This table defines the operating unit context for the Projects module.
  • AR_VAT_TAX_ALL_B: References via PA_EXPENDITURE_TYPE_OUS_ALL.OUTPUT_VAT_TAX_ID. This is the central Receivables table storing all Value-Added Tax (VAT) and sales tax codes, rates, and rules.

These relationships position PA_EXPENDITURE_TYPE_OUS_ALL as a vital integration point between project costing (PA) and financial tax engine (AR) data, governed by the operating unit structure.