Search Results psa_mf_trx_dist_all




Overview
Explore in AI Chat

Overview

PSA_MF_TRX_DIST_ALL is a Public Sector Financials (PSA) table owned by the PSA schema that stores accounts receivable distributions for a multiple-fund transaction. In Oracle EBS 12.1.1 and 12.2.2, it acts as the PSA extension layer that sits alongside the standard Receivables accounting distribution records, allowing a single AR transaction line to be distributed across multiple funds — a requirement common to public sector, government, and grant-funded organizations subject to fund accounting rules. Each row represents one distribution line tied to a Receivables line GL distribution, carrying the derived multiple-fund receivables account.

From a heuristic Data Vault modeling perspective, the metadata classification is standalone, with no parent or child links mined from its foreign key structure. This suggests it is best modeled as a satellite-like entity attached to the Receivables distribution it extends, rather than as a hub or link, though this is a modeling suggestion only and not a documented Data Vault design.

Key Information Stored

The table contains 25 documented columns. The most significant are:

Note that the documented metadata does not list fund, amount, or percentage columns; the fund association is carried via the CCID account segments rather than a discrete fund column.

Common Use Cases and Queries

Typical scenarios include reconciling multiple-fund receipts, auditing fund allocations, and verifying that posting runs captured the correct receivables accounts. A common pattern joins the table to Receivables distributions:

  • Query all multiple-fund distributions for a given posting control: SELECT * FROM PSA_MF_TRX_DIST_ALL WHERE POSTING_CONTROL_ID = :id;
  • Trace the fund account for a specific AR line distribution: SELECT MF_RECEIVABLES_CCID, PREV_MF_RECEIVABLES_CCID FROM PSA_MF_TRX_DIST_ALL WHERE CUST_TRX_LINE_GL_DIST_ID = :dist_id;
  • Audit changes by comparing MF_RECEIVABLES_CCID against PREV_MF_RECEIVABLES_CCID, and review the WHO columns for the last editor.
  • Reporting use cases include fund-level AR aging, grant revenue allocation, and DFF-driven client-specific fund reporting.

Related Objects

The metadata documents one foreign key relationship and several implicit dependencies:

Because the table is classified as standalone, integration is primarily through the AR distribution and posting control chain rather than through direct PSA child records.