Search Results xla_amb_setup_errors_pk

Overview

The XLA_AMB_SETUP_ERRORS table is a Subledger Accounting (XLA) repository owned by the XLA schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores errors reported by two core Subledger Accounting configuration utilities: the Create and Assign Source program and the Application Accounting Definition validation program. Because these programs operate across a large number of application accounting definitions, mapping sets, and source assignments, the table serves as a diagnostic log that surfaces configuration defects before they propagate into journal creation.

Each row captures a discrete error condition, tied to the specific subledger context — application, product rule, event class, event type, and accounting line — in which the error was detected. This makes the table an essential reference point during implementation, upgrade, and troubleshooting of Subledger Accounting setups.

From a data modeling perspective, the metadata heuristic classifies XLA_AMB_SETUP_ERRORS as standalone, suggesting it functions as an independent error-log entity rather than a hub or link within a Data Vault model. In practical terms, it behaves like a satellite-style log table keyed by a surrogate identifier, with no documented foreign key dependencies to other XLA configuration tables.

Key Information Stored

The primary key is defined by XLA_AMB_SETUP_ERRORS_PK on the AMB_ERROR_ID column. A unique index, XLA_AMB_SETUP_ERRORS_U1, also covers AMB_ERROR_ID, making it both the surrogate key and the sole documented business-key candidate. The table contains 43 columns; the most significant are:

• AMB_ERROR_ID — Surrogate primary key uniquely identifying each error record.
• MESSAGE_NAME and MESSAGE_TYPE_FLAG — Identify the error message and distinguish its severity or type.
• MESSAGE_CATEGORY_CODE and CATEGORY_SEQUENCE_NUM — Group errors by category and control ordering.
• APPLICATION_ID — The subledger application in which the error was raised.
• AMB_CONTEXT_CODE and PRODUCT_RULE_CODE / PRODUCT_RULE_TYPE_CODE — The subledger context and product rule involved.
• ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE — The transaction entity and event that triggered the error.
• ACCOUNTING_LINE_CODE and ACCOUNTING_LINE_TYPE_CODE — The accounting line definition affected.
• SOURCE_CODE and SOURCE_TYPE_CODE — The accounting source associated with the failure.
• MAPPING_SET_CODE and MAPPING_GROUP_CODE — The mapping configuration referenced during validation.
• REQUEST_ID and PROGRAM_ID — Trace the error to the concurrent request and program that produced it.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY — Standard audit columns.

Common Use Cases and Queries

Typical scenarios include diagnosing why an Application Accounting Definition fails validation, investigating why the Create and Assign Source program fails to complete, and auditing subledger setup before go-live. A common query filters errors by concurrent request:

• SELECT amb_error_id, message_name, message_category_code, application_id, program_id, request_id FROM xla_amb_setup_errors WHERE request_id = :req_id ORDER BY amb_error_id;
• Group by message_category_code to summarize recurring failure categories during implementation.
• Join to FND_CONCURRENT_REQUESTS on REQUEST_ID to correlate errors with program run history.

Related Objects

The metadata documents no foreign keys, positioning this table as standalone. Significant related objects include:

• XLA_AMB_SETUP_ERRORS_U1 / XLA_AMB_SETUP_ERRORS_PK — Unique and primary key constraints on AMB_ERROR_ID.
• FND_CONCURRENT_REQUESTS — Joins on REQUEST_ID to identify the originating concurrent request.
• FND_APPLICATION — Joins on APPLICATION_ID or PROGRAM_APPLICATION_ID.
• FND_CONCURRENT_PROGRAMS — Joins on PROGRAM_ID and PROGRAM_APPLICATION_ID.
• XLA_AMB_* configuration tables — Supply context for mapping sets, product rules, and sources referenced in error rows.