Search Results fun_trx_types_b_u1

Overview

FUN.FUN_TRX_TYPES_B is the foundational setup table in Oracle E-Business Suite that stores the Intercompany transaction types defined for the enterprise. It resides in the FUN schema, which owns the core Intercompany (formerly Global Accounting Engine / AGIS) functionality, and is registered in FND Design Data as FUN.FUN_TRX_TYPES_B. Every intercompany transaction processed through the Intercompany subsystem — whether flowing directly to the General Ledger or routed through Oracle Receivables and Oracle Payables for invoicing — must reference a valid row in this table. The table is stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is conventionally treated as a low-volume, reference-style configuration table whose contents are managed by the Intercompany setup administrator rather than by transactional runtime processes. Under a heuristic Data Vault classification mined from its foreign-key structure, this object models as a standalone hub: it carries a single, stable business concept (the intercompany transaction type), has no upward dependency on a parent entity, and is referenced by downstream transactional objects. Treating it as a hub — with a descriptive satellite carrying the flag columns and the ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield segments — is a reasonable warehouse modeling suggestion, though its modest size typically makes it viable as a simple dimension as well.

Key Information Stored

The table exposes 29 documented columns in the 12.2.2 physical schema. The most consequential are:

• TRX_TYPE_ID — a system-generated NUMBER(15) surrogate primary key, enforced by unique index FUN_TRX_TYPES_B_U1 (paired with ZD_EDITION_NAME in the 12.2.2 schema). It is the column referenced by all dependent transactional tables.
• TRX_TYPE_CODE — a mandatory-aligned VARCHAR2(15) business-key candidate carrying the human-readable transaction type code; it is enforced as the second unique business key by index FUN_TRX_TYPES_B_U2. A search for fun_trx_types_b_u2 therefore typically indicates a developer or DBA validating, dropping, or investigating this unique constraint.
• MANUAL_APPROVE_FLAG — indicates whether transactions of this type require manual approval; valid values are Y or N.
• ENABLED_FLAG — governs whether the transaction type is active and selectable; valid values are Y or N.
• ALLOW_INVOICING_FLAG — a critical behavioral switch: Y directs transactions to create AR and AP invoices, while N routes them straight to GL.
• VAT_TAXABLE_FLAG and ALLOW_INTEREST_ACCRUAL_FLAG — both documented as deprecated and retained for backward compatibility only.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — VARCHAR2(150) descriptive flexfield segments available for customer-specific extensibility.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, plus the 12.2.2-only ZD_EDITION_NAME used by the online patching (editioning) architecture.

Common Use Cases and Queries

Typical usage centres on validating setup configuration, driving conditional logic in intercompany processing, and feeding reporting extracts. A common lookup returns the enabled transaction types with their invoicing behaviour:

SELECT TRX_TYPE_ID, TRX_TYPE_CODE, ENABLED_FLAG, ALLOW_INVOICING_FLAG, MANUAL_APPROVE_FLAG FROM FUN.FUN_TRX_TYPES_B WHERE ENABLED_FLAG = 'Y';

A second frequent pattern resolves the surrogate key from the business key — effectively exercising FUN_TRX_TYPES_B_U2:

SELECT TRX_TYPE_ID FROM FUN.FUN_TRX_TYPES_B WHERE TRX_TYPE_CODE = :p_code;

Teams also mine the descriptive flexfield for custom reporting, filtering on ATTRIBUTE_CATEGORY and selected ATTRIBUTEn segments, and audit trailing uses LAST_UPDATED_BY and LAST_UPDATE_DATE to detect configuration drift between environments. Because the table is small and static, it is a natural candidate for caching in concurrent programs and for inclusion as a dimension in intercompany reconciliation extracts.

Related Objects

• IGI_EXP_TRX_TYPE — referenced from FUN_TRX_TYPES_B.TRX_TYPE_ID per the documented foreign-key relationship; join on the shared TRX_TYPE_ID.
• FUN_TRX_TYPES_TL — the translation table holding language-specific transaction type names, joined on TRX_TYPE_ID.
• FUN_TRX_HEADERS_ALL / FUN_TRX_LINES_ALL — intercompany transaction headers and lines that resolve their type via TRX_TYPE_ID.
• FUN_TRX_BATCHES_ALL — the batch grouping table used when intercompany transactions of a given type are processed together.
• Oracle Payables AP_INVOICES_ALL and Oracle Receivables RA_CUSTOMER_TRX_ALL — created when ALLOW_INVOICING_FLAG = 'Y', with the transaction type retained as the origin attribute.
• General Ledger interfaces GL_INTERFACE — receives the journal lines when ALLOW_INVOICING_FLAG = 'N'.
• The Intercompany setup form and associated concurrent programs, which maintain rows in this table through the standard FUN application APIs.