Results for “value_type_code”

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

Overview

The XLA.XLA_DESCRIPT_DETAILS_B table is a core configuration object within the Subledger Accounting (XLA) module of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. It stores the individual detail rows that collectively define a subledger journal entry description. Each row represents one component of a description string — either a literal text fragment or a source reference — together with the sequence in which that component should appear when the final description is assembled at accounting time.

A flexfield segment may be specified as a description component only when a valid TRANSACTION_COA_ID context exists, which is why accounting flexfield-based descriptions require chart-of-accounts context to be resolved before the description can be rendered. The table is registered in the ETRM 12.2.2 physical schema under the XLA schema and contains 16 documented columns.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone. It is not modelled as a classic hub, link, or satellite because it is a child configuration table whose numeric foreign key points to the description priorities table rather than to a shared business entity. In practice it behaves most like a satellite of the description-priority parent, carrying descriptive attributes keyed by sequence.

Key Information Stored

The table's surrogate primary key is DESCRIPTION_DETAIL_ID, defined by the XLA_DESCRIPT_DETAILS_B_PK constraint. Two unique indexes serve as business-key candidates: XLA_DESCRIPT_DETAILS_B_U1 on (DESCRIPTION_DETAIL_ID, ZD_EDITION_NAME) and XLA_DESCRIPT_DETAILS_B_U2 on (DESCRIPTION_PRIO_ID, USER_SEQUENCE, ZD_EDITION_NAME). The second is the more significant business key, since it enforces that each description detail occupies a unique position within its parent description priority.

The most important columns include:

• DESCRIPTION_DETAIL_ID — surrogate primary key identifying each detail row.
• DESCRIPTION_PRIO_ID — foreign key to XLA_DESC_PRIORITIES, tying the detail to its parent description definition.
• USER_SEQUENCE — ordinal position controlling the order in which components are concatenated.
• VALUE_TYPE_CODE — indicates whether the row is a literal text value or a source-derived value.
• SOURCE_APPLICATION_ID — identifies the application that owns the referenced source.
• SOURCE_TYPE_CODE — classifies the source (for example, a standard or system source).
• SOURCE_CODE — the specific source from which the runtime value is resolved.
• FLEXFIELD_SEGMENT_CODE — the accounting flexfield segment used when the component is a COA segment.
• DISPLAY_DESCRIPTION_FLAG — controls whether the resolved value is rendered in the output description.
• AMB_CONTEXT_CODE — the Application Management Bean context governing the detail.
• ZD_EDITION_NAME — editioning column supporting online patching (12.2.x).
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The principal use case is diagnostic: determining why a subledger journal entry description appears in a particular order or omits certain elements. A typical query joins the detail rows to their parent priority to reconstruct the intended description.

• Retrieve all detail components for a description priority, ordered by sequence:

  SELECT d.description_detail_id, d.user_sequence, d.value_type_code,
         d.source_code, d.flexfield_segment_code
  FROM   xla.xla_descript_details_b d
  WHERE  d.description_prio_id = :prio_id
  ORDER  BY d.user_sequence;

• Identify flexfield-segment components:

  SELECT detail_id, flexfield_segment_code
  FROM   xla_descript_details_b
  WHERE  flexfield_segment_code IS NOT NULL;

• Audit recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Reporting use cases include validating description definitions during implementation and troubleshooting descriptions produced by the Create Accounting process.

Related Objects

• XLA_DESC_PRIORITIES — parent table referenced by DESCRIPTION_PRIO_ID; joins to the primary key of this table.
• XLA_DESCRIPTIONS_B — holds the description header to which priorities belong.
• XLA_DESCRIPTIONS_TL — translated name and content of the description.
• XLA_ACCOUNTING_ERRORS — surfaced when a description cannot be resolved.
• XLA_EVENTS — event context used to supply source values at runtime.
• XLA_AE_HEADERS — final journal entry headers whose description field is derived.

Together these objects form the metadata chain from description definition through priority and detail to the assembled output rendered on subledger journal entries.