Results for “validation_status_code”

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

Overview

XLA_LINE_DEFINITIONS_B is a Subledger Accounting (XLA) foundation table that stores the journal line definitions for an application. In Oracle E-Business Suite 12.1.1 and 12.2.2, journal line definitions are the configurable rules that determine which lines are generated when subledger transactions are accounted, how those lines are classified (for example, as receivables, payables, revenue, or tax lines), and which accounting attributes are derived for each line. The table therefore operates as the master definition repository for the Create Accounting process; the Accounting Program reads the definitions held here to decide which account derivation rules and line types apply to a given event class and event type.

The row's identity is scoped by subledger context: an application, an event class, an event type, a line definition owner, and a line definition code. Each record belongs to the AMB (Accounting Methods Builder) context identified by AMB_CONTEXT_CODE, which ties the definition to the accounting method and application context under which it was created and is valid. In Data Vault terms, the documented relationship classification for this object is standalone, which suggests modeling it as a hub-style reference table keyed on its business key rather than as a dependent link or satellite.

Key Information Stored

• Surrogate primary key: XLA_LINE_DEFINITIONS_B_PK is composed of AMB_CONTEXT_CODE, APPLICATION_ID, EVENT_CLASS_CODE, EVENT_TYPE_CODE, LINE_DEFINITION_OWNER_CODE, and LINE_DEFINITION_CODE. The unique index XLA_LINE_DEFINITIONS_B_U1 extends this list with ZD_EDITION_NAME, indicating that the business-key candidate includes the edition discriminator.
• AMB_CONTEXT_CODE — identifies the Accounting Methods Builder context in which the line definition was created; central to scoping any query against the table.
• APPLICATION_ID — the owning subledger application (for example, Payables, Receivables, or Assets).
• EVENT_CLASS_CODE and EVENT_TYPE_CODE — the transaction classification to which the line definition applies; together they determine when the definition is used during accounting.
• LINE_DEFINITION_OWNER_CODE and LINE_DEFINITION_CODE — the owner and unique code of the line definition, distinguishing definitions supplied by Oracle from those created by customers.
• VALIDATION_STATUS_CODE and ENABLED_FLAG — control whether the definition is active and valid for use in the accounting process.
• TRANSACTION_COA_ID and ACCOUNTING_COA_ID — chart of accounts contexts for the transaction side and the accounting side of the resulting lines.
• BUDGETARY_CONTROL_FLAG — indicates whether the line participates in budgetary control processing.
• OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle Applications who-columns supporting concurrency control and audit.
• ZD_EDITION_NAME — edition discriminator used by the edition-based redefinition architecture in 12.2.

Common Use Cases and Queries

Typical usage includes reviewing which line definitions are enabled for a subledger event class, auditing customer modifications to seeded definitions, and troubleshooting Create Accounting output where an expected line is missing. A representative query retrieves active definitions for a given application and event:

• SELECT line_definition_code, line_definition_owner_code, enabled_flag, validation_status_code FROM xla.xla_line_definitions_b WHERE application_id = :app_id AND event_class_code = :event_class AND enabled_flag = 'Y';
• SELECT ldb.line_definition_code, ldt.name, ldb.last_updated_by, ldb.last_update_date FROM xla.xla_line_definitions_b ldb, xla.xla_line_definitions_tl ldt WHERE ldb.line_definition_code = ldt.line_definition_code AND ldb.amb_context_code = ldt.amb_context_code AND ldt.language = USERENV('LANG');
• Reporting on validation issues: filter on VALIDATION_STATUS_CODE not equal to the valid value to surface incomplete Account Derivation Rule assignments.

Related Objects

• XLA_LINE_DEFINITIONS_TL — translated name and description for each definition, joined on AMB_CONTEXT_CODE, APPLICATION_ID, EVENT_CLASS_CODE, EVENT_TYPE_CODE, LINE_DEFINITION_OWNER_CODE, and LINE_DEFINITION_CODE.
• XLA_LINE_DEFINITION_DETAILS — the child rows holding the journal line rule details associated with each definition.
• XLA_ACCOUNTING_METHODS_B / XLA_AMB_CONTEXTS — the Accounting Methods Builder context and accounting method to which AMB_CONTEXT_CODE refers.
• XLA_EVENT_TYPES_B / XLA_EVENT_CLASSES_B — the event class and event type definitions referenced by EVENT_CLASS_CODE and EVENT_TYPE_CODE.
• XLA_AE_LINES and XLA_AE_HEADERS — the generated accounting entries produced using these line definitions.
• XLA_LINE_DEFINITIONS_B_U1 — the unique index enforcing the business-key candidate including ZD_EDITION_NAME.