Results for “function_transaction_code”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_FUNCTION_TRANSACTIONS_ALL is a Projects (PA) module reference table that stores the system-defined operations available within Oracle EBS AutoAccounting functions. AutoAccounting drives the derivation of General Ledger account combinations for subledger accounting events, and each function defines a specific derivation context (for example, revenue distribution, cost distribution, or invoice account generation). The table enumerates, per function, the discrete transactions that the function recognizes, allowing the application and its configuration layer to distinguish between different accounting events handled by the same function.

The object is owned by the PA schema, carries a VALID status in the EBS 12.1.1 and 12.2.2 data dictionary, and is documented in the ETRM repository with thirteen physical columns. Under the heuristic Data Vault classification mined from its foreign key structure, the table is hub-leaning: its composite primary key identifies a business concept (a function and its associated transaction) rather than an event or a descriptive history, which suggests a natural hub candidate in a vaulted model.

Key Information Stored

The documented primary key is PA_FUNCTION_TRANSACTIONS_PK, comprising FUNCTION_CODE, FUNCTION_TRANSACTION_CODE, APPLICATION_ID, and ORG_ID. This composite key is a business key rather than a surrogate identifier; there is no sequence-generated single-column surrogate in the documented schema. Two unique indexes reinforce this design: PA_FUNCTION_TRANSACTIONS_U1 on FUNCTION_CODE, FUNCTION_TRANSACTION_CODE, APPLICATION_ID, ORG_ID, and ZD_EDITION_NAME; and PA_FUNCTION_TRANSACTIONS_U2 on FUNCTION_CODE, FUNCTION_TRANSACTION_NAME, APPLICATION_ID, ORG_ID, and ZD_EDITION_NAME. Together these enforce uniqueness of a transaction both by code and by name within a function, application, and operating unit.

  • FUNCTION_CODE — identifies the AutoAccounting function to which the transaction belongs; foreign key to PA_FUNCTIONS.
  • FUNCTION_TRANSACTION_CODE — the system-defined operation code that uniquely distinguishes the transaction within a function.
  • FUNCTION_TRANSACTION_NAME — the user-facing name of the transaction, constrained by the second unique index.
  • APPLICATION_ID — the application owning the function and transaction, part of both unique keys and the primary key.
  • ORG_ID — the operating unit context, enabling the same function and transaction definitions to exist across organizations.
  • ENABLED_FLAG — controls whether the transaction is active for AutoAccounting processing.
  • DESCRIPTION — optional descriptive text for the transaction.
  • ZD_EDITION_NAME — the editioning column supporting Online Patching in EBS 12.2.x.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard WHO-style change tracking.

Common Use Cases and Queries

Typical usage centers on validating AutoAccounting configuration, driving distribution line generation, and reporting on the transactions enabled for a given function. Because PA_CUST_REV_DIST_LINES_ALL and PA_SEGMENT_RULE_PAIRINGS_ALL both reference this table, the most frequent query pattern is a lookup join, filtering by FUNCTION_CODE, FUNCTION_TRANSACTION_CODE, APPLICATION_ID, and ORG_ID to resolve the transaction identity or description.

  • Listing enabled transactions for a function: SELECT FUNCTION_TRANSACTION_CODE, FUNCTION_TRANSACTION_NAME, ENABLED_FLAG FROM PA_FUNCTION_TRANSACTIONS_ALL WHERE FUNCTION_CODE = :function_code AND ORG_ID = :org_id AND ENABLED_FLAG = 'Y';
  • Resolving transaction names on revenue distribution lines by joining PA_CUST_REV_DIST_LINES_ALL to this table on FUNCTION_CODE, FUNCTION_TRANSACTION_CODE, PROGRAM_APPLICATION_ID/APPLICATION_ID, and ORG_ID.
  • Reviewing segment rule pairings alongside the transactions they govern, joining PA_SEGMENT_RULE_PAIRINGS_ALL on the same four columns.
  • Validating configuration completeness by comparing PA_FUNCTIONS entries against the transactions defined here, ensuring every function has the expected operations.

Related Objects

The documented relationships identify the parent function and the two principal dependent tables. The foreign key to PA_FUNCTIONS anchors the function definition; the inbound references from PA_CUST_REV_DIST_LINES_ALL and PA_SEGMENT_RULE_PAIRINGS_ALL establish this table as a hub for AutoAccounting configuration and distribution processing.

  • PA_FUNCTIONS — parent function definition; joined on PA_FUNCTION_TRANSACTIONS_ALL.FUNCTION_CODE = PA_FUNCTIONS.FUNCTION_CODE and APPLICATION_ID.
  • PA_CUST_REV_DIST_LINES_ALL — customer revenue distribution lines referencing function and transaction on FUNCTION_CODE, FUNCTION_TRANSACTION_CODE, PROGRAM_APPLICATION_ID, and ORG_ID.
  • PA_SEGMENT_RULE_PAIRINGS_ALL — segment rule pairings referencing function and transaction on FUNCTION_CODE, FUNCTION_TRANSACTION_CODE, APPLICATION_ID, and ORG_ID.
  • PA_FUNCTION_TRANSACTIONS_PK / U1 / U2 — the primary key and unique indexes enforcing the documented business keys.