Results for “xla_analytical_dtls_b”

50+ results




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

Overview

XLA_ANALYTICAL_DTLS_B is a Subledger Accounting (XLA) table in the Oracle E-Business Suite, owned by the XLA schema. In the ETRM metadata for release 12.2.2 the object is documented as VALID and is described as storing the translated header information — specifically the name and description — for Analytical Criteria. Analytical Criteria are the user-defined, account-determining conditions that Subledger Accounting applies when it derives the accounting for a subledger transaction. This table therefore holds the multilingual presentation layer for the analytical criteria definitions, allowing the same criterion to be displayed in the session language of each user.

Based on the foreign-key and primary-key structure mined from the dictionary, the metadata suggests a heuristic Data Vault classification of standalone. In Data Vault terms this behaves as a self-contained reference or descriptive structure rather than a classic hub, link, or satellite, because the documented schema exposes no outward foreign-key relationships to other XLA tables.

Key Information Stored

The physical schema is documented with 13 columns. The most significant are:

  • AMB_CONTEXT_CODE — the Application Message Builder context that scopes the analytical criterion to a particular subledger application or product.
  • ANALYTICAL_CRITERION_CODE — the identifier of the analytical criterion being described.
  • ANALYTICAL_CRITERION_TYPE_CODE — the classification of the criterion, distinguishing the kinds of conditions supported by the application.
  • ANALYTICAL_DETAIL_CODE — the identifier of the individual detail row within the criterion.
  • GROUPING_ORDER — the sequence in which detail elements are grouped or evaluated.
  • DATA_TYPE_CODE — the datatype of the value associated with the detail row.
  • VIEW_COLUMN_NUM — the column position used when the detail is rendered in the analytical criteria view.
  • ZD_EDITION_NAME — the edition name associated with the row, reflecting EBS edition-based redefinition.

Standard audit columns are also present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The documented surrogate primary key is XLA_ANALYTICAL_DTLS_B_PK, composed of AMB_CONTEXT_CODE, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, and ANALYTICAL_DETAIL_CODE. The documented unique index XLA_ANALYTICAL_DTLS_B_U1 overlaps these columns and adds ZD_EDITION_NAME, making it the strongest business-key candidate in the edition-aware model.

Common Use Cases and Queries

Typical usage is diagnostic and reporting-oriented: confirming which analytical criteria are defined for a subledger context, verifying grouping order, and reviewing the translated names and descriptions of criteria. A representative query pattern joins the header criterion to its application context:

  • SELECT analytical_criterion_code, analytical_criterion_type_code, analytical_detail_code, grouping_order, data_type_code FROM xla_analytical_dtls_b WHERE amb_context_code = :context AND zd_edition_name = :edition;
  • Aggregate detail rows per criterion to confirm grouping order and validate that each criterion exposes the expected number of details.
  • Audit reporting on CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE to trace configuration changes to analytical criteria over time.

Related Objects

Because the documented relationship classification is standalone, no foreign keys are exposed in the metadata. The most significant logical companions are therefore the corresponding XLA base and translation tables and the subledger accounting setup components that share the AMB_CONTEXT_CODE and ANALYTICAL_CRITERION_CODE keys. In practice, the translation rows in XLA_ANALYTICAL_DTLS_B are consumed together with the analytical criteria headers, the application message builder context definitions, and the accounting method and definition setup objects in the XLA schema. Join columns to rely on are AMB_CONTEXT_CODE, ANALYTICAL_CRITERION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, and ANALYTICAL_DETAIL_CODE, matched with ZD_EDITION_NAME to ensure edition-correct results under EBS 12.2.2 edition-based redefinition.