Search Results fvfv_status_obligations

Overview

FVFV_STATUS_OBLIGATIONS is a read-only reporting view within the Oracle E-Business Suite Federal Financials (FV) module. It presents a consolidated picture of obligation and commitment activity by joining accounts payable invoice distribution data with the corresponding purchasing and requisition records. The view correlates invoice lines to their originating purchase order distributions, purchase order lines, and requisition lines, exposing the funding document references and the amounts recorded against each. Its principal purpose is to support the reporting of obligations and commitments required in a federal accounting environment, where funds control and the tracking of commitments, obligations, and expenditures are mandatory.

The view is defined with the WITH READ ONLY clause, confirming that it is intended exclusively for query and reporting access rather than transactional maintenance. It is documented as not implemented in the reference database, meaning that the underlying object may not exist in all environments and must be validated against the specific instance before use.

Underlying Base Objects

The view is constructed over eleven base tables spanning the Payables, General Ledger, and Purchasing schemas. These are AP_INVOICES, AP_INVOICE_DISTRIBUTIONS, GL_CODE_COMBINATIONS, GL_SETS_OF_BOOKS, PO_DISTRIBUTIONS, PO_LINE_LOCATIONS, PO_LINES, PO_HEADERS, PO_REQ_DISTRIBUTIONS, PO_REQUISITION_LINES, and PO_REQUISITION_HEADERS.

The driving relationship is between AP_INVOICES and AP_INVOICE_DISTRIBUTIONS on INVOICE_ID, with each distribution linked to a code combination through GL_CODE_COMBINATIONS and to a set of books through GL_SETS_OF_BOOKS. The purchasing chain is connected through the PO_DISTRIBUTION_ID on the invoice distribution, which links to PO_DISTRIBUTIONS, and then outward through PO_LINE_LOCATIONS, PO_LINES, and PO_HEADERS. The requisition chain is reached through PO_DISTRIBUTIONS.REQ_DISTRIBUTION_ID to PO_REQ_DISTRIBUTIONS, PO_REQUISITION_LINES, and PO_REQUISITION_HEADERS.

All purchasing and requisition joins are outer joins (marked with the plus sign), which preserves invoice distribution rows even when no downstream purchasing or requisition record exists. This design allows the view to report invoice-only activity alongside fully documented obligation chains.

Key Columns

• SET_OF_BOOKS_ID / SET_OF_BOOKS_NAME — Identifies the ledger under which the transaction is recorded.
• INVOICE_NUMBER / INVOICE_DATE / INVOICE_AMOUNT — The invoice header identifier, transaction date, and distributed amount.
• OBLIGATION_NUMBER — Derived from the purchase order header segment (PH.SEGMENT1), representing the obligation document.
• OBLIGATION_DATE — Populated from PD.GL_ENCUMBERED_DATE, the date on which the purchase order distribution was encumbered.
• OBLIGATION_AMOUNT — Computed as (QUANTITY_ORDERED − QUANTITY_CANCELLED) × UNIT_PRICE for the purchase line.
• OBLIGATION_STATUS — Corresponds to PL.CLOSED_CODE, indicating the open or closed state of the obligation.
• COMMITMENT_NUMBER — Derived from the requisition header segment (PRH.SEGMENT1).
• COMMITMENT_DATE — Populated from PRD.GL_ENCUMBERED_DATE.
• COMMITMENT_AMOUNT — Computed as (QUANTITY − QUANTITY_CANCELLED) × UNIT_PRICE for the requisition line.
• _KF:ACCOUNT_NUM — A key flexfield placeholder (referencing '_KF:SQLGL:GL#:GCC') that resolves to the accounting flexfield combination on the invoice distribution.

Common Use Cases and Queries

The most frequent use case is reconciling obligations to their funding documents, particularly when a user searches on OBLIGATION_DATE to isolate activity within a fiscal period. A representative query follows:

• SELECT obligation_number, obligation_date, obligation_amount, obligation_status, invoice_number, invoice_amount FROM FVFV_STATUS_OBLIGATIONS WHERE obligation_date BETWEEN :start_date AND :end_date ORDER BY obligation_date;
• SELECT set_of_books_name, obligation_status, SUM(obligation_amount), SUM(commitment_amount) FROM FVFV_STATUS_OBLIGATIONS GROUP BY set_of_books_name, obligation_status;
• SELECT invoice_number, commitment_number, commitment_date, commitment_amount FROM FVFV_STATUS_OBLIGATIONS WHERE obligation_number = :po_number;

These patterns support period-end obligation reporting, commitment roll-forward analysis, and drill-down from an invoice to its purchase order and requisition lineage. Analysts should note that because the purchasing and requisition joins are outer joins, rows with null obligation or commitment values represent invoices not yet tied to a funding document.