Search Results xla_aad_loader_logs_u1

Overview

XLA.XLA_AAD_LOADER_LOGS is a transactional logging table in the Subledger Accounting (XLA) module of Oracle E-Business Suite. It records the outcome of Application Accounting Definition (AAD) loader operations — the import, export, overwrite, and merge processing performed when AAD content is moved between environments or upgraded. Each row represents a discrete log entry generated during an AAD loader request, capturing the request context, the specific accounting definition component involved, and any error message produced.

The object is owned by the XLA schema and resides in the APPS_TS_TX_DATA tablespace, with its unique index in APPS_TS_TX_IDX. Oracle designates this object for internal use only; supported access is limited to standard Oracle Applications programs rather than direct customer SQL or DML. The heuristic Data Vault classification mined from the foreign-key structure is standalone, suggesting that in a dimensional or Data Vault model the table can be treated as an independent entity rather than a hub, link, or satellite, since no explicit parent-child dependencies are documented within the EBS schema itself.

Key Information Stored

The table's surrogate primary key is AAD_LOADER_LOG_ID, which is also the single column of the unique index XLA_AAD_LOADER_LOGS_U1. This column is documented as the internal identifier of the log and serves as the business-key candidate for the unique index. The remaining columns describe the loader operation and its context:

• AMB_CONTEXT_CODE — the AMB (Application Message Builder) context code associated with the load.
• APPLICATION_ID and AAD_APPLICATION_ID — the internal application identifier and the application to which the application accounting definition belongs.
• REQUEST_CODE — the request type, with documented values IMPORT, EXPORT, OVERWRITE, MERGE, and MERGE_ANALYSIS.
• LOG_TYPE_CODE and MESSAGE_NUM — the log classification and the numeric message identifier.
• ENCODED_MESSAGE — the encoded error message text (up to 2000 characters), the primary diagnostic payload.
• PRODUCT_RULE_TYPE_CODE and PRODUCT_RULE_CODE — the owner code (documented values S for Oracle, C for Customer) and the code of the application accounting definition product rule.
• COMPONENT_TYPE_CODE, COMPONENT_OWNER_CODE, and COMPONENT_CODE — the component type, its owner (S or C), and its code.
• VERSION_FROM and VERSION_TO — the version range involved in the merge or overwrite operation.
• ORIGINAL_CODE and ORIGINAL_NAME — the pre-merge or pre-overwrite component identity.
• Standard WHO and program columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and the request audit columns PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The dominant use case is troubleshooting failed AAD import, export, or merge operations. Support and implementation teams query this table to surface the encoded error message and the specific product rule or component that caused the failure. A typical diagnostic query filters on the concurrent request identifier:

• SELECT AAD_LOADER_LOG_ID, REQUEST_CODE, LOG_TYPE_CODE, MESSAGE_NUM, ENCODED_MESSAGE FROM XLA.XLA_AAD_LOADER_LOGS WHERE REQUEST_ID = :request_id ORDER BY AAD_LOADER_LOG_ID;

Other common patterns include aggregating failures by request type or application, tracing version transitions for a given product rule (filtering on PRODUCT_RULE_CODE, VERSION_FROM, and VERSION_TO), and auditing which components were replaced during a merge by examining ORIGINAL_CODE and ORIGINAL_NAME. Because the object is flagged internal-use-only, read access is normally exercised indirectly through Subledger Accounting diagnostics and standard concurrent program output rather than through custom application code.

Related Objects

The FK/PK relationship data classifies this object as standalone, so no parent or child foreign keys are documented within the EBS schema. Related investigation paths are therefore driven by the descriptive columns rather than referential constraints:

• FND_USER — join on CREATED_BY and LAST_UPDATED_BY to identify the user who generated the log entry.
• FND_CONCURRENT_REQUESTS — join on REQUEST_ID to relate log rows to the concurrent request that ran the AAD loader.
• FND_APPLICATION — join on APPLICATION_ID and AAD_APPLICATION_ID to resolve application names.
• XLA_AAD_HEADERS and XLA_AAD_DETAILS — the application accounting definition content being loaded, referenced logically through PRODUCT_RULE_CODE and COMPONENT_CODE.
• XLA_AAD_LOADER_LOGS_PK and XLA_AAD_LOADER_LOGS_U1 — the primary key constraint and unique index defined on AAD_LOADER_LOG_ID.