Results for “gl_accounting_calendar”

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

Overview

APPS.GLBV_GL_ACCOUNTING_CALENDARS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It presents General Ledger accounting calendar definitions in a simplified, reporting-friendly form. In EBS terminology, an accounting calendar (also referred to as a period set) defines the fiscal years used by a ledger and consists of groups of General Ledger periods. Each accounting calendar record defines the naming convention, the number of periods per fiscal year, and the period type (such as Month, Quarter, or Year).

Because the view is registered as an FND Design Data object under the SQLGL product (SQLGL.GLBV_GL_ACCOUNTING_CALENDARS), it is intended as a stable interface for reporting, integration, and Business Intelligence tooling rather than for transactional maintenance. The "GLBV" naming prefix identifies it as a General Ledger business view, and the "V" suffix confirms that it is a read-only view. Administrators and developers consult it when they need to understand which accounting calendars exist in the instance, or when downstream systems require a lightweight lookup of calendar names and descriptions without navigating the full GL_PERIOD_SETS structure.

Underlying Base Objects

The ETRM metadata documents exactly one referenced base object: APPS.GL_PERIOD_SETS. The view abstracts that table, exposing only the calendar name and description while hiding the many technical columns required to define period sets, such as the period type, the number of periods per year, the start and end dates of the first period, and the accounting period type code.

Within GL_PERIOD_SETS, each row represents one period set. The view projects the period set name into the ACCOUNTING_CALENDAR column and the descriptive text into the DESCRIPTION column. The metadata further records that APPS.GLBV_GL_ACCOUNTING_CALENDARS is not referenced by any other database object, confirming it is a terminal, leaf-level view used only by external consumers such as reports or custom queries. Note that the "Referenced base objects" field in the 12.2.2 documented metadata is empty, whereas the dependency section of the source material explicitly lists GL_PERIOD_SETS; the dependency information should therefore be treated as authoritative.

Key Columns

• ACCOUNTING_CALENDAR (VARCHAR2, 15): The name of the accounting calendar, derived from the period set name in GL_PERIOD_SETS. This is the value typically entered when defining a ledger, and it is the key used to join to other calendar or period views.
• DESCRIPTION (VARCHAR2, 240): The free-text description associated with the calendar, used to convey its purpose, the fiscal year convention, or administrative notes.

No mandatory flags are documented for either column, and the view exposes no primary key, date, or numeric columns. Consequently, joins to period-level views must be performed on the calendar name rather than a surrogate identifier.

Common Use Cases and Queries

A frequent requirement is simply to list all accounting calendars defined in an instance, which supports the user search "Calendar — Go to calendar." The following query returns the complete calendar listing:

• SELECT ACCOUNTING_CALENDAR, DESCRIPTION FROM APPS.GLBV_GL_ACCOUNTING_CALENDARS ORDER BY ACCOUNTING_CALENDAR;
• Filtering for a specific calendar: SELECT ACCOUNTING_CALENDAR, DESCRIPTION FROM APPS.GLBV_GL_ACCOUNTING_CALENDARS WHERE ACCOUNTING_CALENDAR = :calendar_name;
• Validating calendar assignment before ledger setup by joining the view to ledger configuration tables on ACCOUNTING_CALENDAR.
• Feeding BI Publisher reports or analytics dashboards that require a dropdown of available calendars.

Because the view is read-only and thin, it imposes negligible query overhead and is safe for high-frequency integration calls. For period-level detail, consumers must query complementary views such as the GL period views built over GL_PERIODS.