Search Results fv_be_rpr_transactions




Overview
Explore in AI Chat

Overview

FV_BE_RPR_TRANSACTIONS is a Federal Financials (FV) product table within the Oracle E-Business Suite, residing in the FV schema. As the metadata description states, it "stores the details for the reprogramming transactions." Reprogramming is a government-specific budget execution activity in which an agency moves budgetary authority between programs, projects, or appropriations, typically within the limits defined by public law and congressional notification thresholds. This table therefore acts as the transaction-level ledger for reprogramming events processed by the Federal Financials budgeting engine.

Each row represents a single reprogramming transaction and carries the accounting distributions, amounts, approval routing, and dimension values required to move funds from a source to a target. The presence of both FUND_VALUE_FROM/FUND_VALUE_TO, the paired DISTRIBUTION_FROM and DISTRIBUTION_TO structures, and the three PUBLIC_LAW_CODE, ADVANCE_TYPE, and TRANSFER_DESCRIPTION columns reinforces this dual-sided transfer semantics.

Where the heuristic Data Vault classification is concerned, this object is categorized as satellite-leaning. Modelers should treat it as descriptive/event detail attached to a core reprogramming business key rather than as an intersection or hub, given the concentration of segment-level attributes and the single-column surrogate primary key.

Key Information Stored

The table contains 103 documented columns. The surrogate primary key is TRANSACTION_ID, enforced by index FV_BE_RPR_TRANSACTIONS_PK1 and duplicated in the U2 unique index. Two business-key candidates are documented: FV_BE_RPR_TRANSACTIONS_U1 (BUDGET_LEVEL_ID, DOC_NUMBER, SET_OF_BOOKS_ID) and FV_BE_RPR_TRANSACTIONS_U2 (TRANSACTION_ID). The most operationally significant columns include:

  • TRANSACTION_ID — surrogate primary key identifying the reprogramming transaction.
  • DOC_NUMBER — the user-facing reprogramming document number; a business-key component.
  • BUDGET_LEVEL_ID and SET_OF_BOOKS_ID — the budget level and ledger context of the transaction; both complete the U1 business key.
  • TRANSACTION_TYPE_ID, SUB_TYPE, and TRANSACTION_STATUS — classify and track the transaction through its lifecycle.
  • AMOUNT, FUND_VALUE_FROM, FUND_VALUE_TO — the monetary value of the reprogramming move.
  • GL_DATE — the accounting date.
  • DISTRIBUTION_FROM and DISTRIBUTION_TO — accounting flexfield distribution identifiers on each side.
  • SEGMENT1 through SEGMENT30 and the parallel SEGMENT1_FROM through SEGMENT30_FROM — the full "to" and "from" accounting segment strings.
  • APPROVAL_ID, APPROVED_BY_USER_ID — the approval record and the approver identity.
  • BU_GROUP_ID, PUBLIC_LAW_CODE, ADVANCE_TYPE, DEPT_ID, MAIN_ACCOUNT — linkage to budget user groups, statutory authority, and agency attribution.
  • Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN and ATTRIBUTE1..ATTRIBUTE15/ATTRIBUTE_CATEGORY.

Common Use Cases and Queries

Typical reporting needs include open reprogramming transactions awaiting approval, transaction history by document number, and cumulative reprogramming activity by public law or budget level.

  • Retrieve a transaction and its source/target segments by document number.
SELECT transaction_id, doc_number, amount, gl_date, transaction_status
FROM   fv.fv_be_rpr_transactions
WHERE  doc_number = :doc_number;
  • Track pending approvals against the JTF approval workflow.
SELECT t.transaction_id, t.doc_number, t.transaction_status, a.*
FROM   fv.fv_be_rpr_transactions t, jtf.jtf_um_approvals_b a
WHERE  t.approval_id = a.approval_id
AND    t.transaction_status = :pending_status;
  • Aggregate reprogramming value by statutory authority and budget level for congressional reporting.
  • Reconcile the from/to segment strings against GL balances for audit and funds-control purposes.

Related Objects

Foreign key and relationship metadata identify the following significant dependencies:

  • FV_BUDGET_USER_HDR — joined on FV_BE_RPR_TRANSACTIONS.BU_GROUP_ID = FV_BUDGET_USER_HDR.BU_GROUP_ID; owns the budget user group context.
  • JTF_UM_APPROVALS_B — joined on FV_BE_RPR_TRANSACTIONS.APPROVAL_ID = JTF_UM_APPROVALS_B.APPROVAL_ID; provides the approval definition backing the transaction.
  • FV_BE_RPR_TRANSACTIONS_PK1/_U1/_U2 — the primary and unique indexes that enforce identity and business key integrity.

Supplementary FV budgeting objects (e.g., budget level and transaction type validation tables) are referenced via BUDGET_LEVEL_ID and TRANSACTION_TYPE_ID, while SET_OF_BOOKS_ID links to the General Ledger ledger definition.