Results for “consolidation_name”

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

Overview

GL_CONSOLIDATION_AUDIT_V is a reporting view owned by the APPS schema in Oracle E-Business Suite General Ledger. It exposes a consolidated, de-normalized read model of consolidation activity by joining consolidation definitions, their audit records, and the corresponding accounting period status rows. The view is marked VALID and is shipped as part of the General Ledger (GL) product, version-tagged internally by the header directive $HEADER: GLGVWREG.LDT 120.16.12010000.5.

The view answers a recurring operational question: which consolidations ran, into which target period, and in what accounting period sequence did that target period fall? Because it surfaces CONSOLIDATION_NAME directly, it is the natural access point for users and downstream processes searching on consolidation name rather than internal numeric consolidation identifiers. It is intended for inquiry, audit, and integration reporting rather than transactional maintenance; consolidation definitions and audit rows are created and maintained by the consolidation concurrent programs, not by this view.

Underlying Base Objects

The documented view text references three base objects, all resolved through APPS synonyms:

• GL_CONSOLIDATION — the consolidation definition (parent/subsidiary mapping, target ledger, and name). Aliased as C and the source of CONSOLIDATION_ID and NAME.
• GL_CONSOLIDATION_AUDIT — the audit trail of consolidation executions, holding the target period name for each run. Aliased as CA.
• GL_PERIOD_STATUSES — the period calendar/status table, filtered to APPLICATION_ID = 101 (General Ledger) and matched on the consolidation's target ledger and the audit row's target period. Aliased as PS.

Joins are equi-joins on C.CONSOLIDATION_ID = CA.CONSOLIDATION_ID, PS.LEDGER_ID = C.TO_LEDGER_ID, and PS.PERIOD_NAME = CA.TO_PERIOD_NAME. The query applies DISTINCT, which suppresses duplicate combinations arising from multiple audit rows or overlapping period status rows.

Key Columns

• CONSOLIDATION_ID — surrogate identifier of the consolidation definition; the join key back to GL_CONSOLIDATION.
• CONSOLIDATION_NAME — the user-defined consolidation name from GL_CONSOLIDATION. This is the column most frequently used as a search filter and display value.
• PERIOD_NAME — the target period name from the consolidation audit record, validated against GL_PERIOD_STATUSES for the target ledger.
• PERIOD_YEAR — the fiscal/calendar year of that target period, sourced from GL_PERIOD_STATUSES.
• PERIOD_NUM — the numeric period sequence within the year, enabling chronological ordering of consolidation runs independently of period-name formatting.

Common Use Cases and Queries

Typical scenarios include auditing which periods have been consolidated into a given target ledger, listing all periods touched by a named consolidation, and feeding downstream extracts that require year/period sequencing. A representative lookup by consolidation name:

• SELECT consolidation_id, consolidation_name, period_name, period_year, period_num FROM apps.gl_consolidation_audit_v WHERE consolidation_name = :name ORDER BY period_year, period_num;
• SELECT consolidation_name, COUNT(DISTINCT period_name) FROM apps.gl_consolidation_audit_v GROUP BY consolidation_name; — to gauge consolidation coverage per definition.
• SELECT * FROM apps.gl_consolidation_audit_v WHERE period_year = :year AND period_num = :period; — to enumerate all consolidations hitting a specific target period.

Because the view is read-only and joins only three objects, it performs efficiently for targeted predicates on CONSOLIDATION_NAME and period columns; large unfiltered extracts should still be constrained by ledger or period for best performance.