Results for “fv_be_trx_dtls_u1”

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

Overview

The FV.FV_BE_TRX_DTLS table is the base transaction-detail table within the Oracle E-Business Suite Budget Execution (FV) module. It stores line-level details for all budget execution transactions and serves as the underlying data source for the detail block of the Define Appropriations and Define Fund Distributions forms. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are held in APPS_TS_TX_IDX. The object is documented as VALID under the FV schema in both EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone, indicating that it does not fit cleanly into a hub, link, or satellite pattern in the mined relationship structure. This is a modeling suggestion rather than a functional constraint; in practice, the table behaves as a transaction-detail entity anchored by a surrogate primary key.

Key Information Stored

The table contains 76 documented columns. The most operationally significant are:

• TRANSACTION_ID (NUMBER 15, mandatory) — the unique system-generated surrogate identifier and the physical primary key (FV_BE_TRX_DTLS_PK1). It is also the column behind the unique index FV_BE_TRX_DTLS_U1, making it the sole documented business-key candidate.
• DOC_ID (NUMBER 15) — the document identifier and foreign key to FV_BE_TRX_HDRS; indexed non-uniquely by FV_BE_TRX_DTLS_N1.
• REVISION_NUM — document revision number, supporting versioned transactions.
• TRANSACTION_STATUS (VARCHAR2 25) — current status of the transaction.
• GL_DATE — the General Ledger date for accounting recognition.
• QUARTER_NUM (NUMBER 15) — stored explicitly to permit quarter-level querying.
• TRANSACTION_TYPE_ID (NUMBER 15) — foreign key to FV_BE_TRANSACTION_TYPES.
• BUDGETING_SEGMENTS (VARCHAR2 2000) — concatenated accounting flexfield string giving distribution detail for lower budget level transactions.
• SEGMENT1 through SEGMENT30 (VARCHAR2 25 each) — individual key flexfield segments.
• INCREASE_DECREASE_FLAG and AMOUNT — the direction and value of the transaction line.
• SET_OF_BOOKS_ID, PUBLIC_LAW_CODE, GL_TRANSFER_FLAG, and TRANSFER_DESCRIPTION — supporting attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield storage columns.
• CORRECTED_FLAG, SOURCE, GROUP_ID, and EVENT_ID — audit, grouping, and event linkage fields.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include retrieving all detail lines for a given document, auditing transactions by GL date or period, and reconciling amount movements by increase/decrease direction. Representative query patterns include:

• Joining FV_BE_TRX_DTLS to FV_BE_TRX_HDRS on DOC_ID to report header-to-line detail.
• Filtering by SET_OF_BOOKS_ID and GL_DATE for ledger-level transaction reporting.
• Aggregating AMOUNT by INCREASE_DECREASE_FLAG and TRANSACTION_STATUS for budget movement analysis.
• Querying by BUDGETING_SEGMENTS or individual SEGMENTn columns for accounting distribution drill-down.
• Looking up a specific transaction via the unique index FV_BE_TRX_DTLS_U1 on TRANSACTION_ID for performance-critical single-row access.

Related Objects

• FV_BE_TRX_HDRS — header table; joined via FV_BE_TRX_DTLS.DOC_ID = FV_BE_TRX_HDRS.DOC_ID.
• FV_BE_TRANSACTION_TYPES — referenced via FV_BE_TRX_DTLS.TRANSACTION_TYPE_ID.
• FV_BE_TRX_DTLS_U1 — the unique index on TRANSACTION_ID, central to single-row lookups.
• FV_BE_TRX_DTLS_N1 — the non-unique index on DOC_ID supporting document-level queries.
• Define Appropriations form — consumes this table for its detail block.
• Define Fund Distributions form — likewise uses this table as its detail data source.
• GL_JE_LINES / GL interface objects — downstream accounting entries derived from transactions carrying GL_TRANSFER_FLAG and SET_OF_BOOKS_ID.