Search Results psa_receivables_trx_all




Overview
Explore in AI Chat

Overview

PSA_RECEIVABLES_TRX_ALL is a table owned by the PSA schema, delivered as part of the Public Sector Financials (PSA) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store information indicating whether a receivable activity is of the multi-fund type. In public sector accounting, a single receivable transaction may need to be distributed across multiple funds; this table persists the configuration flag that drives that behavior for each receivable activity definition.

The object carries a documented status of VALID, with 22 columns in the ETRM 12.2.2 physical schema. The primary key is PK_RECV_TRX_ID, defined on the surrogate column PSA_RECEIVABLES_TRX_ID. Under the heuristic Data Vault classification mined from the foreign key structure, this object is identified as standalone, meaning it has no documented foreign key relationships to parent or child objects. As a modeling suggestion, a standalone classification is most consistent with a reference or lookup-style table, though it could also be treated as a hub if a natural business key were identified and integrated with dependent satellites.

Key Information Stored

The table's most significant column is PSA_RECEIVABLES_TRX_ID, the surrogate primary key that uniquely identifies each row. This is the column referenced by PK_RECV_TRX_ID and is the identifier used by any consuming application or report.

The remainder of the documented column set is dominated by standard EBS audit and descriptive attribute columns:

  • PSA_RECEIVABLES_TRX_ID — surrogate primary key; the sole documented unique identifier for a multi-fund receivable activity record.
  • LAST_UPDATE_DATE — timestamp of the most recent change to the row; the standard WHO column used for incremental extraction and change detection.
  • LAST_UPDATED_BY — the application user who performed the last update.
  • CREATION_DATE — timestamp when the record was first inserted.
  • CREATED_BY — the user or process that created the record.
  • LAST_UPDATE_LOGIN — the login session associated with the last update.
  • ATTRIBUTE_CATEGORY — the descriptive flexfield context, if a DFF is enabled on this table.
  • ATTRIBUTE1 through ATTRIBUTE15 — the fifteen standard descriptive flexfield segment columns used for customer-specific extensions of the receivable activity definition.

No business-key unique index is documented beyond the surrogate primary key, so no alternate natural key can be asserted from the metadata. Note that the documented column list is entirely composed of the key, WHO audit columns, and the DFF columns; the operational flag distinguishing multi-fund from single-fund activities is not enumerated in the ETRM excerpt, so its physical column name should be confirmed against the deployed schema at the target release.

Common Use Cases and Queries

Because this object is a PSA configuration table, the principal reporting use case is validating which receivable activities are configured for multi-fund treatment before period close or before migrating public sector setups. A typical query pattern selects the identifier and audit columns for recently changed configuration rows:

  • Configuration audit: SELECT psa_receivables_trx_id, creation_date, last_update_date, last_updated_by FROM psa.psa_receivables_trx_all ORDER BY last_update_date DESC — supports change tracking and setup review.
  • Incremental extract for a data warehouse: filter on last_update_date >= :last_run_date to pull only rows modified since the previous load.
  • DFF inspection: select ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 to report on customer-defined extensions.
  • Setup comparison across environments: extract the identifier set from each instance and reconcile counts to detect configuration drift.

Because the table is classified as standalone, queries should not assume join predicates to other PSA tables beyond the identifier column semantics.

Related Objects

The supplied metadata documents no foreign key relationships for this table; therefore related objects cannot be enumerated from FK/PK evidence. Join relationships to application modules that consume the multi-fund flag should be validated against the deployed data model. Practically, the adjacent objects for investigation are other PSA public sector tables that carry a PSA_RECEIVABLES_TRX_ID column and reference this identifier, and standard EBS audit infrastructure objects such as FND_USER and FND_LOGINS, which resolve CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. Any reporting join to those metadata tables should be performed on user_id and login_id respectively, but no such relationship is asserted as documented here.