Results for “alc_enabled_flag”

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

Overview

XLA_SUBLEDGERS is a configuration and registration table in the Oracle Subledger Accounting (XLA) product, owned by the XLA schema. It is supported in Oracle E-Business Suite releases 12.1.1 and 12.2.2. As described in the ETRM metadata, the table stores information that depends on the application, and it includes one row for each application — standard or non-standard — that is supported by Subledger Accounting.

In practice, XLA_SUBLEDGERS acts as the registry of subledger applications known to the accounting engine. Each entry identifies a source application, associates it with an application type and journal entry source, and controls whether key accounting features such as control accounts and the Accounting Library Check (ALC) are enabled for that application. The unique index XLA_SUBLEDGERS_U1 on (APPLICATION_ID, ZD_EDITION_NAME) provides a business-key candidate for identifying a row within an edition, while XLA_SUBLEDGERS_PK on APPLICATION_ID serves as the surrogate identifier for the core record.

From a heuristic Data Vault modeling perspective, the metadata classifies this table as standalone, meaning it has no mined foreign-key relationships to other tables. It is best treated as a reference or hub-like table for subledger applications rather than as a transactional link or satellite.

Key Information Stored

The most significant columns in XLA_SUBLEDGERS include:

• APPLICATION_ID — the primary key (XLA_SUBLEDGERS_PK) and the identifier of the subledger application registered with XLA.
• JE_SOURCE_NAME — the journal entry source name associated with the application, used when generating accounting entries.
• APPLICATION_TYPE_CODE — the classification of the application, distinguishing standard from non-standard application support.
• VALUATION_METHOD_FLAG — indicates whether valuation method processing applies to the application.
• ALC_ENABLED_FLAG — controls whether the Accounting Library Check is enabled for the application.
• CONTROL_ACCOUNT_ENABLED_FLAG — indicates whether control account processing is enabled.
• CONTROL_ACCOUNT_TYPE_CODE — the type of control account behavior applied.
• CONTROL_ACCOUNT_SOURCE_CODE — the source from which control account values are derived.
• DEFAULT_PARTY_TYPE_CODE — the default party type used by the application's accounting.
• DRILLDOWN_PROCEDURE_NAME — the drilldown procedure used to navigate from subledger accounting output back to source transactions.
• SECURITY_FUNCTION_NAME — the security function linked to the application.
• ZD_EDITION_NAME — the edition identifier used for edition-based redefinition, forming part of the unique business key XLA_SUBLEDGERS_U1.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard Who-column tracking.

Common Use Cases and Queries

Subledger Accounting administrators and developers query XLA_SUBLEDGERS to determine which applications are registered with XLA and which accounting features are active. A typical query lists the registered applications and their feature flags:

• SELECT application_id, je_source_name, application_type_code, alc_enabled_flag, control_account_enabled_flag FROM xla.xla_subledgers;
• To filter for applications where control account processing is enabled: SELECT application_id, control_account_type_code FROM xla.xla_subledgers WHERE control_account_enabled_flag = 'Y';
• To resolve drilldown and security configuration for a specific application: SELECT application_id, drilldown_procedure_name, security_function_name FROM xla.xla_subledgers WHERE application_id = :app_id;

These queries support troubleshooting of accounting generation failures, validation of setup during implementation, and reporting on subledger configuration across the EBS instance.

Related Objects

Although the mined relationship data classifies XLA_SUBLEDGERS as standalone, it participates logically with several core Subledger Accounting objects through APPLICATION_ID and related configuration columns:

• XLA_APPLICATIONS — joins on APPLICATION_ID to provide application-level definitions.
• XLA_ENTITY_MAPPINGS — joins on APPLICATION_ID to map application entities to accounting.
• XLA_EVENTS — references the application via APPLICATION_ID for event processing.
• XLA_ACCOUNTING_EVENTS — uses APPLICATION_ID to associate accounting entries with the registered subledger.
• XLA_JE_SOURCES — relates through JE_SOURCE_NAME to define journal entry sources.
• XLA_LOOKUPS — provides the valid values behind the various _CODE and _FLAG columns.
• XLA_DESCRIPTIONS and XLA_SOURCES — depend on the application registration to support descriptive and source configuration.
• FND_APPLICATION — join on APPLICATION_ID to resolve the application's display name and base path.