Search Results transfer_to_gl_mode_code

Overview

XLA_SUBLEDGER_OPTIONS_V is a reporting and integration view owned by the APPS schema within the Subledger Accounting (XLA) product of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It consolidates Subledger Accounting configuration for ledgers and their associated subledgers into a single relational projection, surfacing accounting method, ledger options, launch options, and ledger relationship attributes. The view is intended for diagnostics, setup verification, and downstream reporting rather than transactional posting. Because it exposes the flag ENABLE_AVERAGE_BALANCES_FLAG (the attribute users typically search for as "enable_average_balances_flag"), it is a common reference point when validating whether average balance processing is enabled at the ledger level before period-end or GL transfer execution. It also carries the subledger application identifier, journal source name, control account type, and the SLA enablement flag, making it suitable for cross-ledger comparisons of Subledger Accounting readiness.

Underlying Base Objects

The view is defined over five referenced objects, all accessed through APPS synonyms:

• GL_LEDGERS — supplies ledger identity and ledger-level attributes, including LEDGER_ID, LEDGER_CATEGORY_CODE, CURRENCY_CODE, SHORT_NAME, CHART_OF_ACCOUNTS_ID, PERIOD_SET_NAME, SLA_ACCOUNTING_METHOD_CODE, and ENABLE_AVERAGE_BALANCES_FLAG.
• GL_LEDGER_RELATIONSHIPS — supplies the primary/secondary relationship context (PRIMARY_LEDGER_ID, SLA_LEDGER_ID, SL_COA_MAPPING_ID, RELATIONSHIP_ENABLED_FLAG) and the account-level conversion (ALC) options.
• XLA_SUBLEDGERS — supplies subledger-level attributes such as APPLICATION_ID, JE_SOURCE_NAME, CONTROL_ACCOUNT_TYPE_CODE, and ALC_ENABLED, joining each ledger-subledger combination.
• XLA_LEDGER_OPTIONS — supplies ledger-level SLA options, including TRANSFER_TO_GL_MODE_CODE, ACCT_REVERSAL_OPTION_CODE, ENABLED_FLAG, CAPTURE_EVENT_FLAG, and ROUNDING_RULE_CODE.
• XLA_LAUNCH_OPTIONS — supplies accounting program launch behavior, including ACCOUNTING_MODE_CODE, SUMMARY_REPORT_FLAG, SUBMIT_TRANSFER_TO_GL_FLAG, SUBMIT_GL_POST_FLAG, ERROR_LIMIT, PROCESSES, and PROCESSING_UNIT_SIZE.

Rows are produced by combining the ledger record with its subledger, ledger option, and launch option configuration, so a single ledger may appear multiple times when more than one subledger is defined for it.

Key Columns

LEDGER_ID / PRIMARY_LEDGER_ID / SLA_LEDGER_ID identify the reporting ledger, its primary ledger, and the SLA ledger respectively. APPLICATION_ID and JE_SOURCE_NAME identify the subledger and journal source. SLA_ACCOUNTING_METHOD_CODE and SLA_ACCOUNTING_METHOD_TYPE describe the accounting method applied. ENABLE_AVERAGE_BALANCES_FLAG indicates whether average balance processing is active for the ledger. ENABLE_BUDGETARY_CONTROL_FLAG, ALLOW_INTERCOMPANY_POST_FLAG, and SLA_BAL_BY_LEDGER_CURR_FLAG govern budgetary control, intercompany posting, and balancing currency behavior. BAL_SEG_COLUMN_NAME, MGT_SEG_COLUMN_NAME, and the related *_VALUE_OPTION_CODE columns define the balancing and management segment sources. The launch/ledger option columns control transfer-to-GL behavior, reversal, and processing limits.

Common Use Cases and Queries

The view is used to audit Subledger Accounting setup across ledgers and subledgers, and to confirm configuration such as average balances, transfer-to-GL mode, and accounting method before running accounting or transfer programs.

SELECT ledger_id, name, enable_average_balances_flag
FROM   apps.xla_sublger_options_v;

A typical query to inspect average balance enablement by ledger:

SELECT l.ledger_id,
       l.short_name,
       l.enable_average_balances_flag
FROM   apps.xla_sublger_options_v l
WHERE  l.enable_average_balances_flag = 'Y';

To review SLA transfer and launch settings for a specific subledger application:

SELECT application_id, ledger_id, je_source_name,
       transfer_to_gl_mode_code, submit_transfer_to_gl_flag,
       accounting_mode_code, enable_average_balances_flag
FROM   apps.xla_sublger_options_v
WHERE  application_id = 200;

Given that the view spans ledger relationships and per-subledger SLA options, results are best filtered by LEDGER_ID or APPLICATION_ID to avoid producing a Cartesian-style expansion across unrelated subledger combinations.