Search Results default_transaction_code

Overview

FV_TRANSACTION_EVENTS_V is a reporting and integration view within the Oracle E-Business Suite Federal Financials (FV) module. It presents transaction event definitions configured against transaction headers, exposing the accounting and transaction code attributes that govern how Federal Financials processes specific transaction events. In EBS 12.1.1 and 12.2.2, the view serves as a read interface for transaction event setup data, allowing reporting tools, extensions, and integration components to retrieve event-level configuration without directly querying the underlying base tables.

The view is relevant to users investigating default_transaction_code, a column exposed directly by the view. This column stores the transaction code that is applied by default when a transaction event is processed, and it is accompanied by flags that control whether the transaction code is mandatory, whether users may update it, and whether a list of values is available during entry. Together these attributes define the transaction code behavior for each event.

Underlying Base Objects

The view is defined over two Federal Financials base tables joined on the transaction header identifier:

• FV_TRANSACTION_EVENTS (aliased PSAE) — supplies the transaction event attributes, including the transaction code configuration columns.
• FV_TRANSACTION_HEADERS (aliased PSAH) — supplies header-level context such as application, activity name, and set of books.

The join condition is PSAE.TRANSACTION_HEADER_ID = PSAH.TRANSACTION_HEADER_ID, producing one row per transaction event associated with a transaction header. The view returns the row identifier (ROWID) of the event record along with descriptive and accounting attributes from the header. Documented metadata for this object does not list additional referenced base objects beyond these two tables.

Key Columns

• TRANSACTION_HEADER_ID / TRANSACTION_EVENT_ID — Primary identifying keys for the header and the event record.
• APPLICATION_ID — Identifies the owning application context for the transaction header.
• ACTIVITY_NAME — The activity associated with the transaction header.
• SET_OF_BOOKS_ID — The ledger or set of books context for the transaction event.
• TRANSACTION_EVENT / TRANSACTION_EVENT_DESC — The event code and its description.
• CHART_OF_ACCOUNTS_ID, CHARGE_ACCOUNT_CCID, RECEIVABLE_ACCOUNT_CCID, REVENUE_ACCOUNT_CCID — Accounting flexfield identifiers used to derive default accounting for the event.
• DEFAULT_TRANSACTION_CODE — The default transaction code applied for the event.
• TXN_CODE_REQUIRED, TXN_CODE_UPDATE_ALLOWED, TXN_CODE_LIST_ALLOWED — Flags controlling whether a transaction code must be supplied, may be changed, and whether a list of values is presented.
• ASSOC_COLLECTION_TXN_CODE, ASSOC_EXPENDITURE_TXN_CODE — Associated transaction codes for collection and expenditure processing.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE10 — Descriptive flexfield segments available for extensibility.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing transaction code configuration, validating required-code flags before data entry, and feeding downstream reporting with event-level defaults. The query below retrieves transaction code configuration for all events on a given header:

• SELECT transaction_event, transaction_event_desc, default_transaction_code, txn_code_required, txn_code_update_allowed FROM fv_transaction_events_v WHERE transaction_header_id = :header_id;

To identify events where a default transaction code is defined but is not mandatory:

• SELECT transaction_event, default_transaction_code FROM fv_transaction_events_v WHERE default_transaction_code IS NOT NULL AND txn_code_required = 'N';

To review event setup by ledger and activity:

• SELECT set_of_books_id, activity_name, transaction_event, default_transaction_code FROM fv_transaction_events_v ORDER BY set_of_books_id, activity_name;

Because the view is a simple two-table join, it is safe for read-only reporting and integration extraction. Any configuration changes must be performed against the underlying base tables through the standard Federal Financials setup forms, not through the view.