Search Results pa_function_transactions




Overview
Explore in AI Chat

Overview

PA_FUNCTION_TRANSACTIONS is a Projects (PA) module view that exposes function transaction definitions used by Oracle Projects to classify and control the transactions that can be entered, costed, billed, or interfaced against project functionality. In Oracle EBS 12.1.1 and 12.2.2, this object is documented as a Single-Org (single organization) view, meaning that it is intended to present data for one operating unit or organization at a time rather than exposing all organizations simultaneously. It serves as the reporting and integration-facing layer over the multi-org base table, filtering rows by the organization identifier associated with the current session.

The view is primarily used for validation, setup review, and reference lookups. It allows reports, forms, and custom integrations to retrieve the list of enabled function codes and their associated transaction codes and names without directly querying the underlying _ALL table. Because it is a view rather than a table, no physical storage is created; the definition is stored in the data dictionary and is resolved at runtime. The ETRM documentation notes that the object is not implemented in the reference database, which indicates that availability depends on whether the relevant Projects setup and database objects have been created in a given environment.

Underlying Base Objects

The documented definition of PA_FUNCTION_TRANSACTIONS is a SELECT from PA_FUNCTION_TRANSACTIONS_ALL. The base table is the multi-organization (_ALL) table that stores function transaction definitions across all organizations, including the ORG_ID column that identifies the owning organization. The view applies a WHERE clause that compares the ORG_ID on the base row against the organization identifier derived from the session context, using USERENV('CLIENT_INFO') to retrieve the current organization.

The filter logic uses NVL and TO_NUMBER with a sentinel value of -99, and it also handles blank or single-space client information by treating such values as NULL. This is the standard Oracle multi-org view pattern (also known as a secured or org-striped view) that restricts visible rows to the current operating unit. The ETRM metadata lists no other referenced base objects, so PA_FUNCTION_TRANSACTIONS_ALL is the sole documented source object.

Key Columns

The view exposes the following columns, each derived directly from PA_FUNCTION_TRANSACTIONS_ALL:

  • APPLICATION_ID — Identifier of the application that owns the function transaction definition, used to scope the setup to the correct product.
  • FUNCTION_CODE — The functional area or business function to which the transaction belongs.
  • FUNCTION_TRANSACTION_CODE — The code that uniquely identifies the transaction type within its function.
  • FUNCTION_TRANSACTION_NAME — The user-facing name of the function transaction.
  • ENABLED_FLAG — Indicates whether the function transaction is active and available for use.
  • DESCRIPTION — Free-text description providing additional context for the function transaction.
  • ORG_ID — The organization identifier used by the multi-org filter; rows are returned only when this matches the session organization.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture standard who-column audit information.

Common Use Cases and Queries

Typical use cases include reviewing which function transactions are enabled for a given organization, joining the view to transaction or setup tables to resolve codes to names, and driving custom reports or interfaces that must respect the current operating unit.

A basic query lists all enabled function transactions visible to the session:

  • SELECT function_code, function_transaction_code, function_transaction_name FROM pa_function_transactions WHERE enabled_flag = 'Y';

To resolve a specific transaction name by code:

  • SELECT function_transaction_name FROM pa_function_transactions WHERE function_transaction_code = :code;

Because the view is organization-filtered, results depend on the active org context. When querying from a tool that does not set CLIENT_INFO, the organization filter may not resolve as expected, and querying the base table PA_FUNCTION_TRANSACTIONS_ALL with an explicit ORG_ID predicate is often preferred for administrative or cross-organization reporting.