Results for “tax_description”

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

Overview

PA_EVENT_TYPE_OUS_V is a reporting view owned by the APPS schema within the Oracle Projects (PA) module of Oracle E-Business Suite. It resides in the ETRM dictionary with a VALID status and is available in both 12.1.1 and 12.2.2 environments. The view consolidates project event type definitions with their associated output tax classifications and the operating unit (business unit) context in which those classifications are valid. Its principal purpose is to present, for each operating unit, the event types that carry an enabled tax classification, resolving the internal lookup code into a user-facing tax description and resolving the numerical ORG_ID into a meaningful operating unit name.

Because Projects event types can drive tax determination during billing and revenue recognition, this view serves as a reference for reporting, integration, and validation logic that must confirm which event types are legally usable for a given business unit on the current date.

Underlying Base Objects

The view is defined over three documented base objects and references one additional schema object:

• PA_EVENT_TYPE_OUS_ALL (SYNONYM) — the event type to output tax classification association table, keyed by EVENT_TYPE, ORG_ID, and OUTPUT_TAX_CLASSIFICATION_CODE. This drives the primary rows.
• ZX_OUTPUT_CLASSIFICATIONS_V (VIEW) — the E-Business Tax output classification lookup view, supplying MEANING (TAX_DESCRIPTION) and the enabled/date-effective attributes. It is joined on a global ORG_ID value of -99 as well as the specific operating unit.
• PA_OPERATING_UNITS_V (VIEW) — supplies the human-readable OPERATING_UNIT value for each ORG_ID.
• MO_GLOBAL (PACKAGE) — the multi-org initialization package noted in the metadata, typically invoked to populate the session Org_ID context used by the security predicate.

The joins require ENABLED_FLAG = 'Y' and restrict rows to those where SYSDATE falls between the effective start and end dates, so only currently valid tax classifications are exposed.

Key Columns

• ROW_ID — the ROWID of the underlying PA_EVENT_TYPE_OUS_ALL row; DISTINCT is applied because the tax lookup join can otherwise multiply rows.
• EVENT_TYPE — the Projects event type code.
• OUTPUT_TAX_CLASSIFICATION_CODE — the code linking the event type to the tax classification.
• TAX_DESCRIPTION — the display description of the classification, sourced from ZX_OUTPUT_CLASSIFICATIONS_V.
• ORG_ID — the operating unit identifier.
• OPERATING_UNIT — the resolved operating unit name from PA_OPERATING_UNITS_V.

Common Use Cases and Queries

Typical usage includes auditing which event types carry valid tax classifications, populating LOV or integration lookups, and comparing configuration across operating units. Note that MO_GLOBAL is used to establish the multi-org context before the view returns meaningful rows.

SELECT org_id, operating_unit, event_type,
       output_tax_classification_code, tax_description
FROM   apps.pa_event_type_ous_v
WHERE  org_id = :p_org_id
ORDER  BY event_type;

A second pattern checks coverage for a specific event type across business units:

SELECT operating_unit, tax_description
FROM   apps.pa_event_type_ous_v
WHERE  event_type = :p_event_type;