Results for “xla_seg_rules_fvl”

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

Overview

XLA_SEG_RULES_FVL is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the Subledger Accounting (XLA) product family. It presents segment rule definitions maintained in Subledger Accounting, which govern how individual segments of the Transaction Chart of Accounts are derived, defaulted, or mapped to the Accounting Chart of Accounts during subledger journal entry creation. The view combines the base segment rule definition, its translated name and description, lookup-decoded rule type meaning, and flexfield structure names for both the transaction and accounting charts of accounts.

The "FVL" suffix denotes a flexfield validation view intended for value-list or descriptive display purposes, exposing friendly descriptive names (such as TRANSACTION_COA_NAME and ACCOUNTING_COA_NAME) rather than raw identifiers. This makes the view suitable for reporting, BI Publisher data sources, and integration lookups where business-friendly labels are required. The view applies USERENV('LANG') filtering throughout, ensuring that application, flexfield structure, and segment rule translations are returned in the session language.

Underlying Base Objects

The documented base objects for this view in release 12.2.2 are FND_APPLICATION_TL (synonym), FND_FLEX_VALUE_SETS (synonym), FND_ID_FLEX_SEGMENTS_VL (view), FND_ID_FLEX_STRUCTURES_TL (synonym), FND_SEGMENT_ATTRIBUTE_TYPES (synonym), XLA_LOOKUPS (view), XLA_SEG_RULES_B (synonym), and XLA_SEG_RULES_TL (synonym). The primary driving table is XLA_SEG_RULES_B, which stores the segment rule header and assignment specification. XLA_SEG_RULES_TL supplies the language-dependent NAME and DESCRIPTION. XLA_LOOKUPS, restricted to LOOKUP_TYPE = 'XLA_OWNER_TYPE', decodes the SEGMENT_RULE_TYPE_CODE into a display meaning. FND_APPLICATION_TL provides the APPLICATION_NAME, while FND_ID_FLEX_STRUCTURES_TL is joined twice — once as FLX1 for the transaction chart of accounts and once as FLX2 for the accounting chart of accounts — both filtered on ID_FLEX_CODE = 'GL#' and APPLICATION_ID = 101 (General Ledger). The joins to the flexfield structure translations are outer joins, so segment rules with no assigned chart of accounts still appear. The remaining documented objects, FND_ID_FLEX_SEGMENTS_VL, FND_FLEX_VALUE_SETS, and FND_SEGMENT_ATTRIBUTE_TYPES, support the second half of the union view, which resolves the flexfield segment name and value set name referenced by segment rules, and determines whether the assignment mode is a specific value. A UNION ALL combines the assignment-mode records, matching on APPLICATION_ID, AMB_CONTEXT_CODE, SEGMENT_RULE_TYPE_CODE, and SEGMENT_RULE_CODE.

Key Columns

• APPLICATION_ID / APPLICATION_NAME — the owning subledger application and its translated name.
• AMB_CONTEXT_CODE — the accounting methods builder context in which the segment rule is defined.
• SEGMENT_RULE_TYPE_CODE / SEGMENT_RULE_TYPE_DSP — the rule type code and its decoded meaning from XLA_LOOKUPS.
• SEGMENT_RULE_CODE / NAME / DESCRIPTION — the rule identifier plus translated name and description.
• TRANSACTION_COA_ID / TRANSACTION_COA_NAME — the source chart of accounts structure identifier and its flexfield structure name.
• ACCOUNTING_COA_ID / ACCOUNTING_COA_NAME — the target chart of accounts identifier and its flexfield structure name.
• FLEXFIELD_SEGMENT_CODE / FLEXFIELD_SEGMENT_NAME — the segment being assigned and its resolved name.
• FLEXFIELD_ASSIGN_MODE_CODE — the assignment mode (for example, 'A' for direct assignment).
• FLEX_VALUE_SET_ID / FLEX_VALUE_SET_NAME — the value set from which permitted segment values derive.
• ENABLED_FLAG — whether the segment rule is currently active.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The most frequent requirement is resolving TRANSACTION_COA_NAME from a known chart of accounts identifier — the exact term the user searched. A typical query selects the rule and both chart names for a given application and context:

• Listing all enabled segment rules for a subledger application with their transaction and accounting chart of accounts names.
• Identifying which segment rules reference a particular value set (FLEX_VALUE_SET_NAME) before making value set changes.
• Auditing segment rules by creation or last update date to support change control and period-end reviews.
• Building a reporting extract that maps segment rule codes to descriptive names for user documentation.

Sample query:

SELECT segment_rule_code, name, segment_rule_type_dsp, transaction_coa_name, accounting_coa_name, flexfield_segment_code, flex_value_set_name, enabled_flag FROM apps.xla_seg_rules_fvl WHERE application_id = 200 AND amb_context_code = 'DEFAULT' AND enabled_flag = 'Y' ORDER BY segment_rule_code;

Because the view filters on USERENV('LANG'), results reflect the language of the connected session, and joins to the flexfield structures are outer joins, so records without an assigned chart of accounts return a null TRANSACTION_COA_NAME or ACCOUNTING_COA_NAME rather than being excluded.