Search Results xla_appli_amb_contexts




Overview
Explore in AI Chat

Overview

The XLA_APPLI_AMB_CONTEXTS table is a core configuration object within the XLA (Subledger Accounting) product of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. It resides in the XLA schema and is documented as VALID. Its stated purpose is to store the mapping between an Oracle application and its Application Accounting Definition (AAD) "AMB" contexts, i.e., the context codes that drive subledger accounting rule resolution. In practice, this table gates which accounting method, application accounting definition, and context set is applied when Subledger Accounting generates journal entries for a given source application.

From a heuristic Data Vault perspective, the metadata classifies this object as standalone. This classification implies the table can be modelled as an independent hub or reference satellite rather than a classic transactional link, since it exposes a stable composite business key (AMB_CONTEXT_CODE, APPLICATION_ID) with no documented outbound foreign key dependencies. The standalone designation is a modelling suggestion; it reflects that the object primarily holds reference or setup configuration rather than event-driven transactions.

Key Information Stored

The documented physical schema contains twelve columns. The most significant are:

  • AMB_CONTEXT_CODE — the application accounting definition context code; together with APPLICATION_ID it forms the primary key.
  • APPLICATION_ID — the Oracle application owning the context; the second half of the composite primary key.
  • STAGING_AMB_CONTEXT_CODE — the staging (pre-production or upgrade) counterpart of the context code, uniquely indexed.
  • UPDATED_FLAG — status indicator used during migration or concurrent processing to flag stale or refreshed rows.
  • LAST_ANALYZED_DATE — timestamp of the last statistics analysis performed on the context.
  • BATCH_NAME — identifier of the batch process that created or refreshed the row.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

The surrogate primary key is defined by XLA_APPLI_AMB_CONTEXTS_PK, while the unique indexes XLA_APPLI_AMB_CONTEXTS_U1 (AMB_CONTEXT_CODE, APPLICATION_ID) and XLA_APPLI_AMB_CONTEXTS_U2 (STAGING_AMB_CONTEXT_CODE) serve as business-key candidates.

Common Use Cases and Queries

Typical usage involves diagnosing why Subledger Accounting does not pick up an expected application accounting definition, verifying which AMB contexts are registered for an application, and reconciling staged contexts during upgrades.

  • Identifying all contexts registered for a specific application: 
    SELECT amb_context_code, staging_amb_context_code, updated_flag
FROM   xla.xla_appli_amb_contexts
WHERE  application_id = :app_id;
  • Detecting contexts that still await staging promotion: 
    SELECT application_id, amb_context_code
FROM   xla.xla_appli_amb_contexts
WHERE  updated_flag <> 'Y';
  • Reporting on last-analyzed and batch provenance for audit purposes.

Related Objects

Because the object is classified as standalone, no explicit FK relationships were mined. Nonetheless, it is functionally joined to the following XLA objects through the shared AMB_CONTEXT_CODE and APPLICATION_ID attributes: