Results for “gl_transaction_calendar”

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

Overview

GL_TRANSACTION_CALENDAR is a General Ledger reference table that stores transaction calendar definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. A transaction calendar specifies which days of the week are treated as business days for a given accounting configuration, and it is assigned to a ledger or set of books to govern how General Ledger processes transactions, performs foreign currency revaluation, and calculates effective dates for accounting entries. The table resides in the GL schema and is classified as VALID in the ETRM repository.

From a dimensional modeling perspective, the mined foreign-key structure suggests treating GL_TRANSACTION_CALENDAR as a hub. A hub represents a core business concept whose identity is held in a single surrogate key and referenced by many dependent entities. Here, TRANSACTION_CALENDAR_ID serves as that stable identity, and multiple operational tables across General Ledger, Cash Management, and other modules reference it, which is consistent with hub-style integration behavior.

Key Information Stored

The table contains 32 documented columns. The most significant are:

• TRANSACTION_CALENDAR_ID — surrogate primary key, enforced by GL_TRANSACTION_CALENDAR_PK and by the unique index GL_TRANSACTION_CALENDAR_U1. This is the value propagated to all dependent tables.
• NAME — the user-visible calendar name; a business-key candidate protected by the unique index GL_TRANSACTION_CALENDAR_U2.
• MON_BUSINESS_DAY_FLAG through SUN_BUSINESS_DAY_FLAG — seven flags, one per weekday, indicating whether that day is a business day for the calendar.
• DESCRIPTION — free-form description of the calendar definition.
• SECURITY_FLAG — controls security-related behavior for the calendar definition.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns maintained by the application.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns used to capture customer-specific extension data.

The distinction between TRANSACTION_CALENDAR_ID and NAME matters for integration: foreign keys always carry the surrogate ID, while reports and interfaces typically resolve the NAME for user-facing output.

Common Use Cases and Queries

Typical scenarios include validating ledger calendar assignments, auditing which calendars define which business days, and joining calendar attributes to ledgers or transaction dates for period-close reporting. A common pattern resolves ledger assignments to calendar names:

• Select ledgers and their calendars: SELECT l.ledger_id, l.name, c.name FROM gl_ledgers l, gl_transaction_calendar c WHERE l.transaction_calendar_id = c.transaction_calendar_id;
• Inspect business-day definitions: SELECT name, mon_business_day_flag, tue_business_day_flag, ... FROM gl_transaction_calendar;
• Analyze transaction dates by calendar: join GL_TRANSACTION_DATES to GL_TRANSACTION_CALENDAR on TRANSACTION_CALENDAR_ID to see which dates are flagged as business days.
• Trace Cash Management forecasting: join CE_FORECAST_HEADERS to GL_TRANSACTION_CALENDAR on TRANSACTION_CALENDAR_ID to determine the calendar driving forecast generation.

Because the table is small and relatively static, it is well suited to being loaded into reporting extracts or used as a lookup in BI Publisher and OTBI custom reports.

Related Objects

The following objects reference GL_TRANSACTION_CALENDAR through documented foreign keys:

• GL_LEDGERS — join on GL_LEDGERS.TRANSACTION_CALENDAR_ID = GL_TRANSACTION_CALENDAR.TRANSACTION_CALENDAR_ID; assigns a calendar to each ledger.
• GL_SETS_OF_BOOKS and GL_SETS_OF_BOOKS_11I — legacy set-of-books views referencing the same column.
• GL_TRANSACTION_DATES — child table holding individual dated entries for each calendar.
• CE_FORECAST_HEADERS — Cash Management forecasting headers linked via TRANSACTION_CALENDAR_ID.
• QRM_ANALYSIS_SETTINGS — references the calendar through GL_CALENDAR_ID.
• CN_SF_REPOSITORIES_ALL — additional dependent entity joined on TRANSACTION_CALENDAR_ID.

Together these relationships confirm the hub role of GL_TRANSACTION_CALENDAR as the central definition point for business-day rules across Oracle EBS financial modules.