Search Results xla_amb_setup_errors_u1

Overview

XLA.XLA_AMB_SETUP_ERRORS is a transactional configuration-validation table within the Oracle E-Business Suite Subledger Accounting (XLA) schema. It stores error and warning messages generated when an Application Accounting Definition (AAD) is created, validated, or applied through the Accounting Methods Builder (AMB). Every row captures a discrete diagnostic condition raised against a specific subledger component — such as an entity, event class, event type, accounting line, description, analytical criterion, segment rule, or mapping set — so that implementers can identify and correct setup defects before the AAD is finalized and accounting is generated.

Per the ETRM documentation, the object resides in the APPS_TS_TX_DATA tablespace and carries the FND Design Data registration XLA.XLA_AMB_SETUP_ERRORS. Under an informal Data Vault classification, this table models as a hub for setup diagnostic events: it is a source-driven, insert-oriented record keyed by a surrogate identifier, with no foreign key dependencies to parent transactions. It is documented as standalone, meaning it neither enforces nor is referenced by other XLA tables through declared foreign keys in the physical schema.

The 12.2.2 documented schema contains 43 columns; the 12.1.1 footprint is substantially the same, with column additions occurring across releases. Access is restricted to standard Oracle Applications programs; direct DML is not supported.

Key Information Stored

The table's most significant columns map directly to the AMB configuration hierarchy being validated:

• AMB_ERROR_ID — Surrogate primary key, defined by unique index XLA_AMB_SETUP_ERRORS_U1 (APPS_TS_TX_IDX) and constraint XLA_AMB_SETUP_ERRORS_PK. In the context of a Data Vault model, this is the business-key candidate for the diagnostic hub.
• MESSAGE_NAME and MESSAGE_TYPE_FLAG — The message identifier and whether the condition is a warning or an error.
• MESSAGE_CATEGORY_CODE and CATEGORY_SEQUENCE_NUM — The functional grouping of the diagnostic and the display ordering of messages within that grouping.
• APPLICATION_ID and AMB_CONTEXT_CODE — The owning application and the AMB development context under which validation was performed.
• PRODUCT_RULE_TYPE_CODE, PRODUCT_RULE_CODE — Owner type and code of the Application Accounting Definition.
• ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE — The subledger event-model coordinates against which the error applies.
• ACCOUNTING_LINE_TYPE_CODE, ACCOUNTING_LINE_CODE, DESCRIPTION_TYPE_CODE, DESCRIPTION_CODE, ANALYTICAL_CRITERION_TYPE_CODE, ANALYTICAL_CRITERION_CODE, SEGMENT_RULE_TYPE_CODE, SEGMENT_RULE_CODE, MAPPING_SET_CODE — Fine-grained component references pinpointing which rule produced the diagnostic.
• SOURCE_TYPE_CODE, SOURCE_CODE, ACCOUNTING_SOURCE_CODE, EXTRACT_OBJECT_NAME, EXTRACT_COLUMN_NAME — Source and extract-object context for the failing component.
• MAPPING_GROUP_CODE, MPA_ACCOUNTING_LINE_TYPE_CODE, MPA_ACCOUNTING_LINE_CODE, LINE_DEFINITION_CODE — Mapping and multi-period accounting references.
• Standard WHO audit columns — PROGRAM_ID, REQUEST_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical uses centre on diagnosing why an AAD will not validate or why journal entries fail to generate. The most common reporting pattern isolates all errors raised for a given definition:

• Listing all errors against an Application Accounting Definition:

  SELECT AMB_ERROR_ID, MESSAGE_NAME, MESSAGE_CATEGORY_CODE, DESCRIPTION_CODE
  FROM   XLA.XLA_AMB_SETUP_ERRORS
  WHERE  PRODUCT_RULE_CODE = :product_rule_code
  AND    MESSAGE_TYPE_FLAG = 'E'
  ORDER BY CATEGORY_SEQUENCE_NUM;

• Ranking errors and warnings by category to prioritise remediation edits.
• Joining to subledger event and rule setup tables to display the affected rule components alongside each diagnostic.
• Auditing recent AAD validation runs by REQUEST_ID or PROGRAM_UPDATE_DATE.

Because the table is a diagnostic log rather than a transaction store, reports typically filter on MESSAGE_TYPE_FLAG and MESSAGE_CATEGORY_CODE, and are consumed after each AMB validation run.

Related Objects

The physical schema declares no foreign keys, so the table is documented as standalone; however, the AMB validation flow references it alongside the following logical peers:

• XLA_AMB_HEADERS / XLA_AMB_CONTEXTS — matched on AMB_CONTEXT_CODE, providing the AMB definition header.
• XLA_AAD_HEADERS — matched on PRODUCT_RULE_CODE, identifying the Application Accounting Definition owning the setup error.
• XLA_AAD_LINE_DEFNS — matched on LINE_DEFINITION_CODE, giving the accounting line definition referenced.
• XLA_MAPPING_SETS — matched on MAPPING_SET_CODE.
• FND_APPLICATION — matched on APPLICATION_ID to resolve the application short name.
• FND_MESSAGES / FND_MESSAGE_TL — matched on MESSAGE_NAME to render the rendered message text.
• FND_REQUESTS / FND_CONCURRENT_REQUESTS — matched on REQUEST_ID to tie diagnostics to the concurrent validation program that generated them.

These relationships are logical rather than enforced; joins are performed by the standard Subledger Accounting validation and reporting programs.