Results for “detail_code_combination_id”

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

Overview

The view APPS.PSBFV_GL_ACCOUNT_HIERARCHIES is a reporting and integration object owned by the APPS schema in Oracle E-Business Suite, and it is associated with the PSB (Public Sector Budgeting) product module. Its name follows the EBS convention for "flexfield value" (FV) views, which are public views that hide the complex underlying key-flexfield infrastructure and expose a simpler, human-readable or join-ready projection of general ledger data. In the context of EBS 12.1.1 and 12.2.2, this view presents summarized-to-detail account hierarchy relationships for general ledger code combinations, keyed by ledger.

The view exists to decouple downstream reports, forms, and interfaces from the physical structure of the account hierarchy and key flexfield tables. Rather than querying the code combination table and the hierarchy table directly, consumers can read a stable projection that already performs the necessary join. The view is defined with the WITH READ ONLY clause, confirming that it is intended purely for query access and cannot be the target of DML.

Underlying Base Objects

The documented view text is:

• SELECT A.LEDGER_ID, A.SUMMARY_CODE_COMBINATION_ID, A.DETAIL_CODE_COMBINATION_ID, A.TEMPLATE_ID, '_KF:SQLGL:GL#:GCC:_CO' FROM GL_ACCOUNT_HIERARCHIES A, GL_CODE_COMBINATIONS_KFV GCC WHERE A.SUMMARY_CODE_COMBINATION_ID = GCC.CODE_COMBINATION_ID WITH READ ONLY

Two base objects are therefore referenced:

• GL_ACCOUNT_HIERARCHIES — the driving table that stores the parent (summary) and child (detail) account relationships together with the operative ledger and the hierarchy template identifier.
• GL_CODE_COMBINATIONS_KFV — the key-flexfield view over GL code combinations, used here to validate and resolve the summary combination through its CODE_COMBINATION_ID. The join restricts returned rows to summary accounts that exist as valid code combinations.

Although the ETRM 12.2.2 metadata lists no referenced base objects explicitly, the embedded view text documents both objects above, and they should be treated as the authoritative dependency set.

Key Columns

• LEDGER_ID — identifies the ledger within which the hierarchy relationship is defined; required to scope the hierarchy to a specific accounting ledger.
• SUMMARY_CODE_COMBINATION_ID — the code combination identifier of the parent or summary account in the hierarchy.
• DETAIL_CODE_COMBINATION_ID — the code combination identifier of the child or detail account that rolls up into the summary account.
• TEMPLATE_ID — identifies the hierarchy template that governs the summarized account structure.
• "_KF:SQLGL:GL#:GCC:_CO" — a derived key-flexfield descriptor token used by EBS flexfield machinery to describe the SQLGL context of the GL code combination; it is a constant expression, not a stored business value.

Common Use Cases and Queries

This view is typically used to drive budget rollup reporting in Public Sector Budgeting, to resolve which detail accounts feed a summary account, and to reconcile summarized balances against their detail components.

• List all detail accounts for a given summary account in a ledger:
  SELECT detail_code_combination_id FROM psbfv_gl_account_hierarchies WHERE ledger_id = :ledger_id AND summary_code_combination_id = :summary_ccid;
• Identify all summary accounts within a template:
  SELECT DISTINCT summary_code_combination_id FROM psbfv_gl_account_hierarchies WHERE template_id = :template_id;
• Join to GL_CODE_COMBINATIONS_KFV to render concatenated account strings for reporting.

Because the view is read-only and joins through the key-flexfield view, it is safe for concurrent reporting use, and it should be preferred over direct queries against the underlying hierarchy table whenever summarized account relationships are required.