Search Results fun_system_options_u1

Overview

FUN.FUN_SYSTEM_OPTIONS is a single-row configuration table in the Oracle E-Business Suite Financials (FUN) schema. It stores setup options that apply at the system level across all Oracle Payables, Receivables, and related financial transactions. As documented in the ETRM metadata, the table is guaranteed to contain only one row, making it a global control record rather than a transactional or historical store. Its role is to centralize defaults that drive currency handling, transaction thresholds, numbering behavior, batch processing modes, and calendar/period configuration for the entire financials application stack.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. It does not function as a hub, link, or satellite in the conventional sense, because it holds no business keys that fan out to other entities and has no foreign keys pointing into it from other tables. The classification is a modeling suggestion: the table is best treated as a reference/configuration object rather than a modeled entity in a dimensional or Data Vault warehouse.

Key Information Stored

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

• SYSTEM_OPTION_ID — The surrogate primary key, defined as a NUMBER(15). It serves as the row identifier and is the leading column of the unique index FUN_SYSTEM_OPTIONS_U1.
• ZD_EDITION_NAME — The second column of the unique business-key index, supporting the editioning model used in EBS 12.2.x.
• DEFAULT_CURRENCY and MIN_TRX_AMT_CURRENCY — Drive the default currency for transactions and the currency used when evaluating minimum transaction amounts.
• MIN_TRX_AMT — The minimum transaction amount threshold applied across financial transactions.
• EXCHG_RATE_TYPE — Specifies the default exchange rate type used for currency conversion.
• NUMBERING_TYPE — Determines whether document numbers are generated by the sequencing API ("SYS") or entered manually ("MAN").
• ALLOW_REJECT_FLAG — Controls whether rejection is permitted ("Y"/"N").
• GL_BATCH_FLAG and APAR_BATCH_FLAG — Control batch ("B") versus online ("O") processing for General Ledger and AP/AR respectively.
• INTECO_CALENDAR and INTECO_PERIOD_TYPE — Define the accounting calendar and period type used for interest/calendar computations.
• DEFAULT_AR_TRX_TYPE_ID, DEFAULT_CM_TRX_TYPE_ID, and DEFAULT_MEMO_LINE_ID — Reference default transaction types for receivables, credit memos, and memo lines.
• ALLOW_INTER_INTRA — Governs inter- and intra-company transaction behavior.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — Descriptive flexfield segments for extensible configuration.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard WHO audit columns.

The unique index FUN_SYSTEM_OPTIONS_U1 on (SYSTEM_OPTION_ID, ZD_EDITION_NAME) is the documented business-key candidate. The foreign key on SYSTEM_OPTION_ID references CS_SYSTEM_OPTIONS, indicating a relationship between the FUN and CS schemas.

Common Use Cases and Queries

Because the table holds exactly one row, queries are straightforward and typically retrieve all configuration values in a single read. Common patterns include:

• Retrieving the default currency and exchange rate type for reporting or validation logic.
• Checking batch versus online processing flags before initiating GL or AP/AR transactions.
• Reading the numbering type to determine document numbering behavior.
• Validating minimum transaction amounts against currency thresholds.
• Joining to CS_SYSTEM_OPTIONS to correlate configuration across schemas.

A representative query is:

• SELECT DEFAULT_CURRENCY, EXCHG_RATE_TYPE, NUMBERING_TYPE, GL_BATCH_FLAG, APAR_BATCH_FLAG FROM FUN.FUN_SYSTEM_OPTIONS;

For edition-aware environments, the query may filter on ZD_EDITION_NAME to target a specific edition. Reporting use cases include configuration audits, migration validation, and pre-upgrade verification of setup options.

Related Objects

The metadata documents the following significant relationships:

• CS_SYSTEM_OPTIONS — referenced via the foreign key on SYSTEM_OPTION_ID, linking FUN configuration to the CS schema.
• FUN_SYSTEM_OPTIONS_U1 — the unique index on (SYSTEM_OPTION_ID, ZD_EDITION_NAME), the primary access path.

Other dependent objects commonly encountered in EBS include Payables and Receivables transaction APIs that read these defaults at runtime, General Ledger journal entry programs that honor the batch flags, and the sequencing API referenced by NUMBERING_TYPE. These objects consume the configuration rather than referencing it through declared foreign keys, consistent with the standalone classification.