Search Results xla_aad_loader_logs_pk

Overview

XLA_AAD_LOADER_LOGS is a standalone table in the XLA (Subledger Accounting) schema of Oracle E-Business Suite. It stores the errors and log entries generated by the Application Accounting Definitions (AAD) loader — the utility that imports or migrates application accounting definitions, product rules, and their component hierarchies into the subledger accounting repository. Each row represents a discrete diagnostic event (message, warning, or error) produced during a loader run, tied to a specific loader request.

The ETRM metadata classifies this object heuristically as standalone under a Data Vault style model — it does not participate in a hub-link-satellite constellation as a dependent satellite. Modeling guidance would therefore treat it as an independent logging fact table rather than a satellite attached to an accounting-definition hub. Its physical schema in 12.2.2 documents 27 columns, with primary key XLA_AAD_LOADER_LOGS_PK on AAD_LOADER_LOG_ID, mirrored by unique index XLA_AAD_LOADER_LOGS_U1. It is present and valid in both 12.1.1 and 12.2.2.

Key Information Stored

The most significant columns fall into three functional groups:

• Identity: AAD_LOADER_LOG_ID is the surrogate primary key and the sole documented business-key candidate (via XLA_AAD_LOADER_LOGS_U1). OBJECT_VERSION_NUMBER supports optimistic locking.
• Diagnostic content: LOG_TYPE_CODE distinguishes severity/category; MESSAGE_NUM carries the message token; ENCODED_MESSAGE holds the message text (typically encoded for runtime substitution). AMB_CONTEXT_CODE identifies the subledger application context.
• Context of the loaded object: AAD_APPLICATION_ID, PRODUCT_RULE_TYPE_CODE, PRODUCT_RULE_CODE, COMPONENT_TYPE_CODE, COMPONENT_OWNER_CODE, COMPONENT_CODE, and the effective-dating pair VERSION_FROM / VERSION_TO identify which definition or component the log entry concerns.
• Original reference: ORIGINAL_CODE and ORIGINAL_NAME preserve the source naming prior to loading.
• Standard WHO/audit and request columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID. REQUEST_CODE links entries to the loader invocation.

Common Use Cases and Queries

Primary use is troubleshooting AAD loader runs — identifying which components failed and why. Typical pattern:

• Review all messages for a given concurrent request: SELECT AAD_LOADER_LOG_ID, LOG_TYPE_CODE, MESSAGE_NUM, ENCODED_MESSAGE FROM XLA.XLA_AAD_LOADER_LOGS WHERE REQUEST_ID = :req ORDER BY AAD_LOADER_LOG_ID;
• Isolate failures only: add WHERE LOG_TYPE_CODE = 'ERROR'.
• Trace a specific definition/component: filter on AAD_APPLICATION_ID, PRODUCT_RULE_CODE, COMPONENT_CODE.
• Report load activity over time using CREATION_DATE or PROGRAM_UPDATE_DATE ranges for audit and trend dashboards.

Because the table can accumulate entries across many loader executions, purge or archive strategies keyed on CREATION_DATE and age are commonly applied.

Related Objects

The metadata indicates this table is standalone (no enforced FK dependents documented). Conceptually it relates to the following:

• FND_CONCURRENT_REQUESTS via REQUEST_ID — the concurrent program run that executed the loader.
• XLA_AAD_APPLICATIONS / XLA_AAD_PRODUCT_RULES via AAD_APPLICATION_ID and PRODUCT_RULE_CODE — the definitions referenced in each log entry.
• XLA_AAD_COMPONENTS via COMPONENT_TYPE_CODE and COMPONENT_CODE.
• XLA_AAD_LOADER_TABLES and the loader staging objects consumed by the AAD loader utility.
• XLA_AAD_LOADER_LOGS is itself accessed through the Subledger Accounting concurrent programs (e.g., the Transfer/Upload Application Accounting Definitions processes) and standard diagnostics views.