Results for “pa_event_type_ous”

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

Overview

PA_EVENT_TYPE_OUS is an Oracle EBS Projects (PA) reporting view that exposes organizational unit security–filtered rows from the underlying PA_EVENT_TYPE_OUS_ALL table. In the Oracle E-Business Suite 12.1.1 and 12.2.2 releases, this view forms part of the multi-org (organization unit security) access layer used throughout the Projects module. Its primary role is to present event type definitions that are relevant to the organization unit currently set in the user's session, rather than returning every row stored in the underlying _ALL table.

The view is important for reporting and integration because it allows Project event type configuration, including tax identifiers associated with output VAT processing, to be queried in a manner that respects Oracle's MO: Operating Unit / MO: Security Profile access controls. For a user such as the one who searched for "output_vat_tax_id," this view is a natural query target when they need to retrieve the tax identifier assigned to a project event type, because OUTPUT_VAT_TAX_ID is exposed as a column.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over the PA_EVENT_TYPE_OUS_ALL table. The view text confirms a direct SELECT from that base object, selecting EVENT_TYPE, OUTPUT_VAT_TAX_ID, WHO (audit) columns, and ORG_ID. The metadata notes that referenced base objects are not otherwise documented, and that the object is "not implemented in this database" in the excerpt supplied — meaning it may be absent from certain instances or patches, and availability should be verified against the specific environment.

The critical behaviour of the view lies in its WHERE clause. It uses the USERENV('CLIENT_INFO') session value — which Oracle Applications populates with the current operating unit context — and applies NVL logic against ORG_ID so that rows matching the current organization context (or a sentinel value of -99) are returned. This is the standard Oracle multi-org view pattern, ensuring that queries against the view return only records the session is authorized to see.

• Base table: PA_EVENT_TYPE_OUS_ALL
• Filtering mechanism: USERENV('CLIENT_INFO') compared to ORG_ID
• Sentinel value: -99 (when no valid org context can be resolved)
• Documented referenced base objects: none beyond PA_EVENT_TYPE_OUS_ALL

Key Columns

• EVENT_TYPE — The identifier/name of the project event type. This is the primary business key exposed by the view.
• OUTPUT_VAT_TAX_ID — The tax identifier associated with output VAT for the event type. This is the column most relevant to the user's search, linking project events to VAT tax configuration.
• ORG_ID — The organization unit that owns the row; drives the multi-org security filtering.
• LAST_UPDATE_DATE — Timestamp of the most recent modification to the row.
• CREATION_DATE — Timestamp when the row was created.
• LAST_UPDATED_BY — The user ID of the last person to update the row.
• CREATED_BY — The user ID of the row creator.
• LAST_UPDATE_LOGIN — The login/session ID associated with the last update.

Common Use Cases and Queries

The most common use case is retrieving the output VAT tax identifier configured for a given project event type within the current operating unit. A simple query is:

SELECT event_type, output_vat_tax_id, org_id FROM pa_event_type_ous WHERE event_type = :p_event_type;

Because the view already applies the ORG_ID filter through the CLIENT_INFO session value, this query returns only rows accessible in the caller's operating unit context. A broader listing of configurations is equally straightforward:

SELECT event_type, output_vat_tax_id FROM pa_event_type_ous ORDER BY event_type;

Additional scenarios include validating that a tax identifier exists before creating project events, reconciling VAT tax setup across event types, and driving integrations that need event-to-tax mappings. Where the view returns no rows, verify the operating unit context and confirm the underlying _ALL table and view are actually implemented in the target instance, since the metadata indicates this object may not exist in every database.