Results for “gl_dynamic_summ_combinations”

34 results




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

Overview

GL_DYNAMIC_SUMM_COMBINATIONS is a General Ledger (GL) table in the Oracle E-Business Suite 12.1.1 and 12.2.2 schema (owner: GL). As stated in the ETRM metadata, its purpose is to store "newly created summary account combinations." In Oracle General Ledger, summary accounts aggregate balances from multiple detail accounts, and the Summary Account Templates feature allows dynamic expansion of those templates into concrete summary account combinations. This table captures those dynamically generated combinations, associating each one with the ledger and summary template that produced it. The table holds 36 documented columns and is classified as VALID in the ETRM repository.

From a Data Vault modeling perspective, the metadata's heuristic classification is link. This reflects the table's role as an associative construct: it resolves relationships between a ledger, a summary template, and a code combination, rather than acting as a standalone descriptive hub or a pure historical satellite. This classification is a modeling suggestion inferred from the foreign key structure, not a documented Oracle designation.

Key Information Stored

The table is structured around a surrogate identifier and the foreign keys that define each dynamic summary combination:

  • DYNAMIC_GROUP_ID — the surrogate primary key that uniquely identifies each dynamically created summary combination row. New rows are generated as templates expand.
  • LEDGER_ID — foreign key to GL_SETS_OF_BOOKS_11I; identifies the ledger for which the summary combination was created.
  • CODE_COMBINATION_ID — foreign key to GL_CODE_COMBINATIONS; links to the summary account combination generated by the template.
  • TEMPLATE_ID — foreign key to GL_SUMMARY_TEMPLATES; identifies the summary template that produced the row.
  • LAST_UPDATE_DATE and LAST_UPDATED_BY — standard EBS WHO-style audit columns recording when and by whom the row was last modified.
  • SEGMENT1 through SEGMENT30 — the individual accounting flexfield segment values that make up the summary combination. These denormalized segment columns allow the key flexfield values to be read directly without joining to GL_CODE_COMBINATIONS and support the template's segment-range rules.

Business-key candidates revolve around the combination of LEDGER_ID, TEMPLATE_ID, and CODE_COMBINATION_ID, which together identify a unique summary account per template and ledger. The surrogate DYNAMIC_GROUP_ID provides the stable primary reference.

Common Use Cases and Queries

Typical uses of this table center on diagnosing and reporting summary account generation:

  • Identifying which summary account combinations have been dynamically created for a given template or ledger.
  • Reconciling summary account balances against the detail accounts they aggregate.
  • Troubleshooting the Summary Account Templates concurrent program when combinations are missing or duplicated.

A representative query joining the table to resolve the ledger and combination:

  • SELECT d.DYNAMIC_GROUP_ID, d.LEDGER_ID, d.TEMPLATE_ID, c.CONCATENATED_SEGMENTS FROM GL_DYNAMIC_SUMM_COMBINATIONS d JOIN GL_CODE_COMBINATIONS c ON d.CODE_COMBINATION_ID = c.CODE_COMBINATION_ID WHERE d.TEMPLATE_ID = :template_id;

Reporting on template activity filters on LAST_UPDATE_DATE to isolate combinations generated during a specific period.

Related Objects

The foreign keys documented in ETRM establish the principal dependencies:

  • GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID; supplies the summary account and its concatenated flexfield values.
  • GL_SETS_OF_BOOKS_11I — joined on LEDGER_ID; identifies the ledger/ledger definition.
  • GL_SUMMARY_TEMPLATES — joined on TEMPLATE_ID; defines the template that generated the combination.

Downstream, GL summary balance and summary account interfaces consume these combinations when aggregating balances, while the Summary Account Templates concurrent program populates this table. Together these relationships make GL_DYNAMIC_SUMM_COMBINATIONS a pivotal link between template definitions, ledger context, and the resulting summary accounts in Oracle General Ledger.