Search Results gl_transaction_calendar_v




Overview
Explore in AI Chat

Overview

GL_TRANSACTION_CALENDAR_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite. Its documented description is "10SC ONLY," indicating that in the delivered ETRM metadata it is scoped to a specific localization or reference configuration rather than a general-purpose, globally available object. The view exposes transaction calendar definitions alongside a computed privilege flag, making it useful for reporting on the calendars used to control which accounting dates accept journal entries and for enforcing row-level security in custom inquiries.

Unlike transactional GL views that join many tables, GL_TRANSACTION_CALENDAR_V is deliberately narrow: it projects selected columns from the transaction calendar entity and adds a single security-derived column. This makes it a lightweight, read-only presentation layer suitable for validation queries, personalizations, and lightweight integrations that need to confirm calendar availability without accessing the base table directly.

Underlying Base Objects

The view is defined over the synonym GL_TRANSACTION_CALENDAR, which resolves to the APPS base table holding transaction calendar definitions. Three underlying objects are documented: GL_TRANSACTION_CALENDAR (SYNONYM), FND_DATA_SECURITY (PACKAGE), and FND_GLOBAL (PACKAGE).

  • GL_TRANSACTION_CALENDAR — the driving synonym supplying TRANSACTION_CALENDAR_ID, NAME, and DESCRIPTION.
  • FND_DATA_SECURITY — invoked through FND_DATA_SECURITY.CHECK_FUNCTION to evaluate whether the current user may use a given calendar. The view passes the function group 'GL_DAS_TRANS_CAL_U' (with fallback 'GL_DAS_TRANS_CAL'), the calendar NAME, and the current user name obtained from FND_GLOBAL.USER_NAME.
  • FND_GLOBAL — the standard EBS package providing session context; here it supplies USER_NAME for the security check.

The DECODE wrapping returns 'Y' when CHECK_FUNCTION yields 'T' (true) and 'N' otherwise, materializing the security decision directly in the result set.

Key Columns

  • TRANSACTION_CALENDAR_ID — the unique identifier (foreign key) for the transaction calendar. Use this when joining to other GL objects or to calendar-day detail tables.
  • NAME — the user-facing calendar name, unique within the ledger context and referenced by the data security function.
  • DESCRIPTION — free-text description of the calendar's purpose.
  • USE_PRIVILEGE — a computed 'Y'/'N' flag reflecting the data-security evaluation for the current user. 'Y' indicates the signed-in user may use the calendar; 'N' indicates the calendar should be hidden or treated as unavailable.

Common Use Cases and Queries

The view is typically used in three ways: confirming that a calendar exists, filtering calendars by the current user's privileges, and driving dependent LOV or report logic.

List all calendars visible to the current user:

SELECT transaction_calendar_id,
       name,
       description
FROM   gl_transaction_calendar_v
WHERE  use_privilege = 'Y'
ORDER  BY name;

Look up a specific calendar by name:

SELECT transaction_calendar_id, name, use_privilege
FROM   gl_transaction_calendar_v
WHERE  name = :p_calendar_name;

Confirm the current user's privileges across all defined calendars:

SELECT name, use_privilege
FROM   gl_transaction_calendar_v
ORDER  BY name;

Because USE_PRIVILEGE depends on FND_GLOBAL.USER_NAME, results vary by session context; queries executed under a different responsibility or user may return different flag values. Integrations that cache results should therefore re-query per session rather than persisting the flag. The view performs no aggregation, so it is safe to join to journal-entry validation queries provided the standard GL access controls remain in force.

As the object is documented as "10SC ONLY," teams on EBS 12.1.1 or 12.2.2 should verify its presence in their instance via ALL_VIEWS before relying on it in custom code, and consider qualifying references as APPS.GL_TRANSACTION_CALENDAR_V.