Search Results fv_ap_cash_pos_temp




Overview

The FV_AP_CASH_POS_TEMP table is a temporary staging table owned by the FV (Federal Financials) schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its documented purpose is to hold intermediate data used during the processing of the PMC-29 Cash Position report, a federal financials report that reconciles disbursement activity against the General Ledger cash balance for a given set of books. Rather than serving as a permanent transactional store, the table acts as a processing workspace: rows are populated by the report or concurrent program, consumed during report generation, and cleared or overwritten on subsequent runs.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table carries descriptive, run-scoped attributes (check date, invoice detail, cash balance, and amounts) attached to a driving business process keyed by CHECKRUN_ID, which points to the payment batch defined in AP_INV_SELECTION_CRITERIA_ALL. It is not a hub, since it holds no durable business key registry, and it is only weakly link-like because its only documented foreign key is a single parent reference.

Key Information Stored

The table is documented with 13 columns. The most operationally significant are:

  • CHECKRUN_ID — The foreign key to AP_INV_SELECTION_CRITERIA_ALL, identifying the payment batch (check run) being processed. This is the principal join and selection key.
  • CHECKRUN_NAME — The descriptive name of the check run, used in report headers and grouping.
  • CHECK_DATE — The date the payment was issued, central to cash timing and bank reconciliation.
  • ORG_ID — The operating unit, enabling multi-org secured reporting.
  • SET_OF_BOOKS_ID — The ledger context, matching the GL cash balance scope.
  • FUND — The federal fund code, used for Treasury and fund-balance reporting.
  • VENDOR_ID and VENDOR_SITE_ID — Payee and remit-to site identifiers.
  • INVOICE_NUM and INVOICE_DATE — Invoice identification and accounting date.
  • DISTRIBUTION_LINE_NUMBER — The invoice distribution line driving the cash impact.
  • AMOUNT — The disbursement amount for the row.
  • GL_CASH_BALANCE — The corresponding General Ledger cash balance used for reconciliation against the disbursed amount.

No surrogate primary key or unique index is documented in the supplied metadata. In practice, the natural business key for a row is the combination of the check run context plus the invoice distribution line, which distinguishes individual disbursement events within a batch.

Common Use Cases and Queries

The primary use case is generating and troubleshooting the PMC-29 Cash Position report, typically run as part of period-end or daily federal cash management. Consultants use the table to verify that the report selected the expected payments, to reconcile disbursement totals against GL cash, and to diagnose discrepancies or missing rows.

A representative query joins the staging rows back to the payment batch and projects fund and cash figures:

  • SELECT t.checkrun_name, t.check_date, t.fund, t.invoice_num, t.amount, t.gl_cash_balance FROM fv.fv_ap_cash_pos_temp t WHERE t.set_of_books_id = :ledger_id AND t.org_id = :org_id ORDER BY t.check_date;
  • Join pattern: SELECT t.*, c.checkrun_name FROM fv.fv_ap_cash_pos_temp t, ap.ap_inv_selection_criteria_all c WHERE t.checkrun_id = c.checkrun_id;

Because the table is transient, queries should be run immediately after the concurrent program populates it and before it is purged. Summarizing AMOUNT versus GL_CASH_BALANCE by FUND and CHECK_DATE provides a quick reconciliation view.

Related Objects

Oracle Proprietary, Confidential Information — Legal Notices apply.