Search Results pa_function_transactions_all




Overview
Explore in AI Chat

Overview

The PA_FUNCTION_TRANSACTIONS_ALL table is a core reference table within the Oracle E-Business Suite Projects module (PA). It defines the system-level operations, or specific transaction types, that are associated with AutoAccounting functions. In the context of Oracle Projects, AutoAccounting is a critical engine that automatically determines the General Ledger (GL) account combinations for various project transactions, such as cost accruals, revenue recognition, and invoice generation. This table, therefore, serves as a master catalog of permissible transaction codes that can be linked to these accounting functions, enabling the precise and rule-based mapping of project activities to financial accounts. Its ALL suffix indicates it is a multi-organization table, storing data partitioned by the ORG_ID (Operating Unit).

Key Information Stored

The table's structure centers on uniquely identifying a valid function-transaction combination within a specific organizational and application context. The primary key columns are FUNCTION_CODE, FUNCTION_TRANSACTION_CODE, APPLICATION_ID, and ORG_ID. The FUNCTION_CODE links to the PA_FUNCTIONS table, identifying the specific AutoAccounting function (e.g., for labor costs, revenue). The FUNCTION_TRANSACTION_CODE defines the discrete operation within that function, such as 'REVENUE' or 'UNBILLED_RECEIVABLE'. The APPLICATION_ID denotes the EBS product (like Projects) that owns the function, and ORG_ID scopes the record to an operating unit. This design ensures that accounting rules can be finely tuned per transaction type and organization.

Common Use Cases and Queries

This table is primarily referenced during the setup and execution of AutoAccounting rules and when analyzing accounting distributions. Common scenarios include validating setup integrity and troubleshooting account generation. A typical query might join to PA_FUNCTIONS to list all available transactions for a specific function, which is useful for setup audits or documentation.

SELECT pft.function_code,
       pf.function_name,
       pft.function_transaction_code,
       pft.application_id
  FROM pa_function_transactions_all pft,
       pa_functions pf
 WHERE pft.function_code = pf.function_code
   AND pft.org_id = 123
 ORDER BY pft.function_code;

Another critical use case is tracing the source of generated accounting entries. When a GL account for a customer revenue distribution line seems incorrect, one would examine the PA_CUST_REV_DIST_LINES_ALL table, which stores the FUNCTION_CODE and FUNCTION_TRANSACTION_CODE used for that line, and then reference PA_FUNCTION_TRANSACTIONS_ALL to understand the configured operation.

Related Objects

  • PA_FUNCTIONS: The parent table, defining the AutoAccounting functions to which the transactions belong. Linked via FOREIGN_CODE and APPLICATION_ID.
  • PA_CUST_REV_DIST_LINES_ALL: A key transactional table that stores the function and transaction codes used for revenue distribution lines, creating a direct foreign key relationship to this table.
  • PA_SEGMENT_RULE_PAIRINGS_ALL: A setup table that defines specific accounting segment rules (like which natural account to use) for a given function and transaction code combination, also linked via foreign key.
  • AutoAccounting Engine: The core PL/SQL logic (within various PA packages) that queries this table as part of its validation and account derivation processes.