Results for “dist_code_combination_id”

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

Overview

FV.FV_REFUNDS_VOIDS_ALL is a Federal Financials (FV) transaction table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores refund, void, and chargeback invoice information consumed by the FMS Form 224 report, the U.S. Treasury reporting form used to reconcile federal agency disbursements and collections. The table acts as a staging and audit repository that consolidates payment-side events—refunds issued against vendor invoices, voided disbursements, and chargebacks recorded through cash receipts—into a single reporting structure.

In Data Vault modeling terms, the object is best classified as a link. The heuristic classification derives from the foreign-key structure: the table does not own the underlying business entities (invoices, payments, checks, receipts, vendors) but instead associates them, recording the intersection of an accounts payable invoice, an accounts receivable cash receipt, an AP payment or check, and a supplier. This link orientation makes the table a natural integration point for cross-module federal reporting, and it is populated by concurrent processes rather than entered directly by users.

Key Information Stored

The table contains 52 documented columns. The most consequential are:

• REFUNDS_VOIDS_ID — surrogate primary key uniquely identifying each refund, void, or chargeback record.
• TYPE — discriminator indicating whether the row represents a refund, a void, or a chargeback, driving Form 224 line classification.
• INVOICE_ID — reference to AP_INVOICES_ALL, identifying the invoice associated with the transaction.
• SET_OF_BOOKS_ID — ledger context, joining to GL_SETS_OF_BOOKS_11I.
• CASH_RECEIPT_ID — linkage to AR_CASH_RECEIPTS_ALL for chargeback and refund collections.
• CHECK_ID / CHECK_NUMBER — the disbursement instrument, joined to AP_CHECKS_ALL.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, VENDOR_NUMBER, VENDOR_SITE_CODE — supplier denormalization for reporting without repeated joins to PO_VENDORS.
• INVOICE_PAYMENT_ID — links the record to the specific payment applied against the invoice in AP_INVOICE_PAYMENTS_ALL.
• REFUND_AMOUNT, INVOICE_AMOUNT, DIST_AMOUNT — monetary measures used in Form 224 aggregation.
• OBLIGATION_NUMBER and OBLIGATION_DATE — federal budget execution attributes tying the transaction to an obligation.
• REFUND_GL_DATE, REFUND_GL_PERIOD, INVOICE_GL_DATE, PERIOD_REPORTED — accounting period attribution for reporting cutoff.
• PROCESSED_FLAG — process control indicating whether the row has been consumed by the Form 224 report run.
• ORG_ID — multi-org operating unit security key, supported by the fifteen ATTRIBUTE flex columns.

While the primary key is the surrogate REFUNDS_VOIDS_ID, business-key candidates typically combine INVOICE_ID, TYPE, SET_OF_BOOKS_ID, and ORG_ID in reporting queries, though no unique index on those columns is documented in the ETRM metadata.

Common Use Cases and Queries

The primary use case is FMS Form 224 preparation. Federal agencies extract unprocessed rows and aggregate them by ledger, period, and type. A representative query filters on PROCESSED_FLAG and joins to the ledger and supplier:

• Extract pending refund and void activity for a period: SELECT r.* FROM fv.fv_refunds_voids_all r WHERE r.processed_flag = 'N' AND r.set_of_books_id = :ledger AND r.refund_gl_period = :period.
• Report chargebacks tied to treasury collections: filter TYPE = 'CHARGEBACK' and join CASH_RECEIPT_ID to AR_CASH_RECEIPTS_ALL.
• Reconcile disbursement voids to checks: join CHECK_ID to AP_CHECKS_ALL and compare REFUND_AMOUNT against check amount.
• Supplier-level analysis: group by VENDOR_NUMBER, VENDOR_NAME, and OBLIGATION_NUMBER for trend reporting.

Because the table is populated by concurrent programs rather than manually, reporting queries should always scope by ORG_ID and SET_OF_BOOKS_ID to respect operating-unit and ledger security, and use the PROCESSED_FLAG and CONC_REQUEST_ID columns to trace each row to its originating request.

Related Objects

• AP_INVOICES_ALL — joined on FV_REFUNDS_VOIDS_ALL.INVOICE_ID = AP_INVOICES_ALL.INVOICE_ID; supplies invoice header detail.
• AP_CHECKS_ALL — joined on CHECK_ID; provides payment and void instrument context.
• AP_INVOICE_PAYMENTS_ALL — joined on INVOICE_PAYMENT_ID; identifies the specific payment applied.
• AR_CASH_RECEIPTS_ALL — joined on CASH_RECEIPT_ID; captures collection and chargeback receipts.
• GL_SETS_OF_BOOKS_11I — joined on SET_OF_BOOKS_ID; defines ledger and functional currency.
• PO_VENDORS — joined on VENDOR_ID; source of supplier master information.

Downstream, the FMS Form 224 concurrent program reads this table directly; no public APIs are documented for direct row creation, so integrations should rely on the delivered federal reporting processes.