Results for “special_type”

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

Overview

FV_INTERIM_CASH_RECEIPTS_ALL is a Federal Financials (FV) staging table in Oracle E-Business Suite 12.1.1 and 12.2.2 that holds interim cash receipt records prior to their validation and transfer into the standard Receivables receipt tables. Despite the documented description stating that the table "contains payment batch information," the column inventory — receipt numbers, customer identifiers, receipt methods, amounts, GL dates, and bank account references — confirms that the object functions as an interim repository for cash receipts assembled in advance of posting. It sits between the receipt capture process and the final creation of AR_CASH_RECEIPTS_ALL records, allowing Federal agencies to review, correct, and validate receipt data before committing it to the subledger.

The ETRM metadata classifies this object heuristically as a link under Data Vault modeling principles. This classification is a modeling suggestion derived from the foreign-key topology: the table carries multiple outbound references to independent hubs (ledger, customer, receipt method, bank accounts) without acting as a hub itself. It is not a satellite, since it does not merely carry descriptive context for a single parent key.

Key Information Stored

The table spans 43 documented columns, with a composite unique index, FV_INTERIM_CASH_RECEIPTS_U1, defined over BATCH_ID, CUSTOMER_ID, CUSTOMER_TRX_ID, RECEIPT_NUMBER, CUSTOMER_TRX_LINE_ID, and RECEIPT_DESC_TYPE. This composite index is the business-key candidate that guarantees receipt uniqueness within a batch context; the table carries no documented single-column surrogate primary key. The most operationally significant columns include:

• BATCH_ID — Groups interim receipts into a processing batch.
• RECEIPT_NUMBER — The receipt identifier carried forward to the final AR receipt.
• CUSTOMER_ID and CUSTOMER_TRX_ID / CUSTOMER_TRX_LINE_ID — Link the receipt to the paying customer and the specific transaction or line being settled.
• AMOUNT and CURRENCY_CODE — The receipt value and its currency.
• RECEIPT_DATE and GL_DATE — Operational and accounting dates used for posting and reporting.
• RECEIPT_METHOD_ID — References AR_RECEIPT_METHODS to determine remittance channel.
• SET_OF_BOOKS_ID — The ledger to which the receipt will be posted.
• BANK_ACCOUNT_ID, CE_BANK_ACCOUNT_ID, and CE_BANK_ACCT_USE_ID — Bank account references spanning AP, Cash Management, and bank account use assignments.
• STATUS and SPECIAL_TYPE — Drive validation state and any special processing flags.
• SITE_USE_ID — The customer site associated with the receipt.
• ORG_ID — Multi-org operating unit partition.
• USSGL_TRANSACTION_CODE — Federal-specific code supporting USSGL accounting requirements.

Common Use Cases and Queries

The primary use case is pre-posting validation: identifying interim receipts that have not yet transferred to AR, detecting duplicates, or reconciling batch totals against expected deposits. A typical query filters by batch and status:

• SELECT batch_id, receipt_number, customer_id, amount, currency_code, status FROM fv_interim_cash_receipts_all WHERE batch_id = :batch_id ORDER BY receipt_number;
• SELECT receipt_method_id, COUNT(*), SUM(amount) FROM fv_interim_cash_receipts_all GROUP BY receipt_method_id;
• Joining to GL_SETS_OF_BOOKS_11I on SET_OF_BOOKS_ID to report receipts by ledger.
• Joining to AR_RECEIPT_METHODS on RECEIPT_METHOD_ID to summarize by remittance method.
• Federal reporting that aggregates AMOUNT by USSGL_TRANSACTION_CODE.

Related Objects

The documented foreign keys connect this table to several master and transaction objects:

• GL_SETS_OF_BOOKS_11I — via SET_OF_BOOKS_ID.
• AR_RECEIPT_METHODS — via RECEIPT_METHOD_ID.
• AP_BANK_ACCOUNTS_ALL — via BANK_ACCOUNT_ID.
• CE_BANK_ACCOUNTS — via CE_BANK_ACCOUNT_ID.
• CE_BANK_ACCT_USES_ALL — via CE_BANK_ACCT_USE_ID.

In practice, the table interfaces downstream with Oracle Receivables receipt creation and Cash Management reconciliation processes, and the interim rows are ultimately superseded by records in AR_CASH_RECEIPTS_ALL and AR_CASH_RECEIPT_HISTORY_ALL.