Search Results fv_be_rpr_transactions_u1




Overview
Explore in AI Chat

Overview

FV.FV_BE_RPR_TRANSACTIONS is the base transaction table in the Oracle E-Business Suite 12.1.1 / 12.2.2 Funds Reservation and Budget Execution (FV) module. It stores the detail records for reprogramming transactions — movements of budget authority from one balancing segment value to another — and serves as the underlying data store for the Enter Re-programming Transactions form. In the documented physical schema (ETRM 12.2.2), the table is owned by the FV schema and contains 103 columns, reflecting the wide accounting-flexfield and descriptive-flexfield structures typical of subledger transaction tables.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is satellite-leaning. This suggests the table behaves primarily as a descriptive satellite whose rows carry attributes and context around a business transaction key, supported by hub-like identifiers (TRANSACTION_ID) and link-like references to budget level, approval, and budgeting user hierarchy entities. The table resides in the APPS_TS_TX_DATA tablespace, while its unique indexes are placed in APPS_TS_TX_IDX.

Key Information Stored

The table's surrogate primary key, FV_BE_RPR_TRANSACTIONS_PK1, is defined on TRANSACTION_ID, a unique system-generated identifier. Two unique indexes act as business-key candidates:

The most significant columns include: DOC_NUMBER (the reprogramming document number); BUDGET_LEVEL_ID (foreign key to FV_BUDGET_LEVELS); FUND_VALUE_FROM and FUND_VALUE_TO (the balancing segment values between which funds move); TRANSACTION_TYPE_ID (foreign key to FV_BE_TRANSACTION_TYPES); AMOUNT; SUB_TYPE; GL_DATE (the General Ledger date); and TRANSACTION_STATUS. The FROM and TO accounting distributions are captured through DISTRIBUTION_FROM and DISTRIBUTION_TO, each paired with SEGMENT1_FROM through SEGMENT30_FROM and SEGMENT1 through SEGMENT30 respectively, allowing the full 30-segment Accounting Flexfield to be stored for each side of the transfer. SET_OF_BOOKS_ID identifies the ledger. The table also carries WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN), 15 developer ATTRIBUTE columns plus ATTRIBUTE_CATEGORY, and additional references such as APPROVAL_ID, BU_GROUP_ID, APPROVED_BY_USER_ID, EVENT_ID, PUBLIC_LAW_CODE, ADVANCE_TYPE, DEPT_ID, and MAIN_ACCOUNT.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include listing reprogramming transactions by ledger and budget level, tracing funds transferred between balancing segment values, and monitoring transaction status through approval workflows. A representative query joins to the budget level and transaction type dimensions:

  • Document listing: SELECT r.DOC_NUMBER, r.FUND_VALUE_FROM, r.FUND_VALUE_TO, r.AMOUNT, r.GL_DATE, r.TRANSACTION_STATUS FROM FV.FV_BE_RPR_TRANSACTIONS r WHERE r.SET_OF_BOOKS_ID = :ledger_id AND r.BUDGET_LEVEL_ID = :budget_level_id ORDER BY r.GL_DATE;
  • Funds movement summary: aggregate AMOUNT grouped by FUND_VALUE_FROM, FUND_VALUE_TO, and TRANSACTION_TYPE_ID.
  • Status tracking: filter on TRANSACTION_STATUS and APPROVAL_ID to identify transactions pending approval.
  • Distribution audit: select DISTRIBUTION_FROM and DISTRIBUTION_TO to verify the concatenated Accounting Flexfield on each side of the transfer.

Related Objects

The table participates in documented foreign-key relationships and is referenced by the following significant objects:

  • FV_BUDGET_LEVELS — joined via BUDGET_LEVEL_ID to resolve budget level context.
  • FV_BE_TRANSACTION_TYPES — joined via TRANSACTION_TYPE_ID to classify the reprogramming transaction.
  • FV_BUDGET_USER_HDR — referenced through BU_GROUP_ID, linking transactions to the budgeting user hierarchy.
  • JTF_UM_APPROVALS_B — referenced through APPROVAL_ID, tying transactions to the approval framework.
  • Enter Re-Programming Transactions form — the primary user interface that reads and writes these rows.