Results for “detail_code_combination_id”

2 results




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

Overview

GL_ACCOUNT_HIERARCHIES is a General Ledger table in the Oracle E-Business Suite (12.1.1 and 12.2.2) that stores the summary-to-detail account hierarchies used by the Summary Accounts feature. Each row establishes a parent/child relationship between a summary account (a roll-up code combination) and a detail account (a posting code combination) within a specific ledger and summary template. This structure allows Oracle General Ledger to aggregate balances and activity from detail accounts into summary accounts for reporting, inquiry, and allocation processing. The table resides in the GL schema and is classified as VALID in ETRM documentation.

Under the heuristic Data Vault classification derived from its foreign key structure, GL_ACCOUNT_HIERARCHIES is modeled as a link table. It does not carry descriptive attributes of its own; instead it connects several hubs — ledgers, code combinations, and summary templates — by resolving many-to-many relationships between summary and detail accounts.

Key Information Stored

The table comprises seven documented columns. The most significant are:

The surrogate primary key is GL_ACCOUNT_HIERARCHIES_PK, defined on (SUMMARY_CODE_COMBINATION_ID, DETAIL_CODE_COMBINATION_ID). Two unique indexes act as business-key candidates: GL_ACCOUNT_HIERARCHIES_U1 on (SUMMARY_CODE_COMBINATION_ID, DETAIL_CODE_COMBINATION_ID) and GL_ACCOUNT_HIERARCHIES_U2 on (LEDGER_ID, DETAIL_CODE_COMBINATION_ID, TEMPLATE_ID, SUMMARY_CODE_COMBINATION_ID). The U2 index enforces uniqueness across the ledger and template dimensions, ensuring a detail account maps to only one summary per template per ledger.

Common Use Cases and Queries

Typical usage includes verifying summary account roll-ups, reporting on hierarchy structure, and troubleshooting balance aggregation discrepancies. A common query retrieves all detail accounts feeding a given summary account:

  • Join GL_ACCOUNT_HIERARCHIES to GL_CODE_COMBINATIONS twice — once via SUMMARY_CODE_COMBINATION_ID and once via DETAIL_CODE_COMBINATION_ID — to display both account segments.
  • Filter by LEDGER_ID or SET_OF_BOOKS_ID to isolate a single ledger's hierarchy.
  • Join to GL_SUMMARY_TEMPLATES on TEMPLATE_ID to identify which template generated the hierarchy.
  • Order results by ORDERING_VALUE to reproduce the intended sequence of detail accounts.

Reporting scenarios include validating that all detail accounts are correctly mapped, auditing summary template changes, and reconciling summary account balances against their underlying detail accounts.

Related Objects

The table participates in a dense foreign key network:

  • GL_CODE_COMBINATIONS — referenced twice, through SUMMARY_CODE_COMBINATION_ID and DETAIL_CODE_COMBINATION_ID.
  • GL_LEDGERS — referenced via LEDGER_ID.
  • GL_SETS_OF_BOOKS — referenced via SET_OF_BOOKS_ID.
  • GL_SUMMARY_TEMPLATES — referenced via TEMPLATE_ID, defining the summary account structure.

These relationships make GL_ACCOUNT_HIERARCHIES a central link in the General Ledger summary account model, joining ledgers, summary templates, and code combinations.