Results for “fv_be_rpr_hdr_v”

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

Overview

FV_BE_RPR_HDR_V is a Federal Financials (FV) view owned by the APPS schema and defined with VALID status in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented purpose is to serve as the RPR (Reimbursable Program Receivable) Transaction Extract header source for Subledger Accounting (SLA), allowing the accounting engine to identify the originating transaction records. The view is a thin projection layer: it joins the SLA event staging table XLA_EVENTS_GT to the RPR transaction table FV_BE_RPR_TRANSACTIONS and the GL_LEDGERS reference table, then aliases and renames several columns so the extract conforms to the header structure expected by the Create Accounting process and downstream SLA event modeling. The constant literal 'RPR' is emitted as the SOURCE column, which is how SLA determines the origin of an event when multiple Federal Financials sources coexist.

Users searching for "budget_level_id" land on this view because BUDGET_LEVEL_ID is exposed directly from FV_BE_RPR_TRANSACTIONS without transformation. Because the view is the documented extract boundary, BUDGET_LEVEL_ID here is the authoritative value flowing into SLA rather than a derived or display-only attribute.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, all reached through APPS synonyms:

• XLA_EVENTS_GT (SYNONYM) — the Subledger Accounting events global temporary table. The view is restricted to events currently staged in this table, which is why it is described as the SLA extract rather than a general-purpose report.
• FV_BE_RPR_TRANSACTIONS (SYNONYM) — the RPR transaction detail table and the source of BUDGET_LEVEL_ID, GL_DATE, TRANSACTION_ID, DOC_NUMBER, TRANSACTION_STATUS, APPROVED_BY_USER_ID, and SET_OF_BOOKS_ID.
• GL_LEDGERS (SYNONYM) — the General Ledger ledger definition, providing CURRENCY_CODE and validating the SET_OF_BOOKS_ID.

The join predicates are GT.EVENT_ID = RPR.EVENT_ID and RPR.SET_OF_BOOKS_ID = GL.LEDGER_ID. The view is therefore a driving-table join keyed on EVENT_ID, and it produces no rows for RPR transactions that lack a corresponding SLA event.

Key Columns

• EVENT_ID — the SLA event identifier; the extract join key and the value SLA uses to link the header to its event record.
• BUDGET_LEVEL_ID — the budget level associated with the RPR transaction, sourced unchanged from FV_BE_RPR_TRANSACTIONS. This is the column of interest for users tracing Federal budget-level accounting.
• GL_DATE — the accounting date carried into SLA for period and journal assignment.
• TRANSACTION_ID / DOC_NUMBER — the RPR transaction identifier and its document number for traceability back to the originating document.
• TRANSACTION_STATUS — the RPR transaction status at extraction time.
• RPR_APPROVED_BY_USER_ID — the view renames the base APPROVED_BY_USER_ID column with an RPR_ prefix to avoid ambiguity in the SLA extract context.
• SOURCE — a hard-coded literal 'RPR' identifying the Federal Financials source.
• LEDGER_ID — alias of RPR.SET_OF_BOOKS_ID, mapped to the SLA ledger identifier.
• CURRENCY_CODE — the ledger currency obtained from GL_LEDGERS.

Common Use Cases and Queries

Typical uses include diagnosing why an RPR transaction did not produce accounting, reconciling SLA events back to RPR transactions, and reviewing budget-level detail flowing into the accounting extract. Because the view depends on XLA_EVENTS_GT, its contents are transient and scoped to the accounting processing session.

To trace budget level and ledger context for staged RPR events:

• SELECT h.event_id, h.budget_level_id, h.gl_date, h.transaction_id, h.doc_number, h.transaction_status, h.ledger_id, h.currency_code FROM apps.fv_be_rpr_hdr_v h WHERE h.transaction_status = 'A';

To confirm the source tag and approval information for a specific transaction:

• SELECT h.event_id, h.source, h.budget_level_id, h.rpr_approved_by_user_id, h.gl_date FROM apps.fv_be_rpr_hdr_v h WHERE h.transaction_id = :transaction_id;

To group staged events by budget level for reconciliation against GL:

• SELECT h.budget_level_id, h.currency_code, COUNT(*) FROM apps.fv_be_rpr_hdr_v h GROUP BY h.budget_level_id, h.currency_code;

Queries should be issued against the APPS synonym and are most meaningful while SLA event staging is active.