Results for “xla_aad_groups”

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

Overview

XLA_AAD_GROUPS is a Subledger Accounting (XLA) repository table in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It stores the merge dependencies that the Subledger Accounting engine analyzes during the merge analysis phase of Application Accounting Definition (AAD) processing. The table is owned by the XLA schema and holds records that group application accounting definitions which must be merged together: every AAD sharing the same GROUP_NUM value is treated as a single merge unit. This grouping drives how the Accounting Methods Builder and the Create Accounting program reconcile and combine accounting definitions that share product rules and ambiguity context.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. Because the table contains no foreign key to a parent reference hub or link, it is best modeled as an independent structure rather than as a hub, link, or satellite. It is transactional reference data produced by the merge analysis routine, not a master entity.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• AMB_CONTEXT_CODE — the Accounting Methods Builder context code identifying the ambiguity or context under which merge analysis is performed.
• GROUP_NUM — the merge group number. All application accounting definitions sharing this value are merged together, making it the central grouping key and the term most often searched for by users.
• APPLICATION_ID — the application owning the product rule being analyzed.
• PRODUCT_RULE_TYPE_CODE — the type classification of the product rule participating in the merge.
• PRODUCT_RULE_CODE — the specific product rule code within the merge dependency.
• REQUIRED_FLAG — indicates whether the grouped definition is mandatory for the merge to proceed.
• OBJECT_VERSION_NUMBER — the optimistic locking column maintained by the framework.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.
• PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID — concurrent program and request metadata identifying the process that generated the row.

The surrogate primary key is XLA_AAD_GROUPS_PK, composed of AMB_CONTEXT_CODE, APPLICATION_ID, PRODUCT_RULE_TYPE_CODE, PRODUCT_RULE_CODE, and GROUP_NUM. A unique index, XLA_AAD_GROUPS_U1, covers the identical column set and therefore represents the same business key; the five columns together uniquely identify each merge dependency record.

Common Use Cases and Queries

Typical use cases include diagnosing merge conflicts during Create Accounting, verifying that accounting definitions were grouped as expected, and reporting on merge dependency scope. A frequent query retrieves all definitions belonging to one merge group:

• SELECT group_num, application_id, product_rule_type_code, product_rule_code, required_flag FROM xla.xla_aad_groups WHERE amb_context_code = :ctx ORDER BY group_num;
• To count definitions per merge group: SELECT group_num, COUNT(*) FROM xla.xla_aad_groups GROUP BY group_num;
• To trace generation source: SELECT group_num, program_id, request_id, creation_date FROM xla.xla_aad_groups WHERE request_id = :req;

Because the table is regenerated by merge analysis, extracted data should be treated as point-in-time and validated against the current accounting configuration.

Related Objects

This table is classified as standalone, so no explicit foreign keys are documented. Related structures that reference the same accounting configuration and merge context include:

• XLA_AAD_GROUPS links to merge analysis output objects through the shared columns AMB_CONTEXT_CODE, APPLICATION_ID, PRODUCT_RULE_TYPE_CODE, and PRODUCT_RULE_CODE.
• XLA_AMB_CONTEXTS — resolves AMB_CONTEXT_CODE to its ambiguity context definition.
• XLA_APPLICATION_ID references FND_APPLICATION — resolves APPLICATION_ID to the owning application.
• XLA_AAD_PRODUCT_RULES — the product rule definitions referenced by PRODUCT_RULE_CODE and PRODUCT_RULE_TYPE_CODE.
• XLA_AAD_MERGE_ANALYSIS or equivalent merge-analysis staging objects consuming GROUP_NUM results.
• FND_CONCURRENT_REQUESTS — joins on REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID to identify the generating concurrent request.