Search Results gl_das_trans_cal

Overview

The APPS.GL_TRANSACTION_CALENDAR_V view is a data-security-aware reporting layer over the General Ledger transaction calendar definition table. In Oracle EBS 12.1.1 and 12.2.2, transaction calendars define the valid accounting dates on which journal entries may be entered and posted, and they are assigned to ledgers through the GL_LEDGERS table. This view exposes the transaction calendar identifier, its name, its description, and — critically — a computed privilege indicator that tells the calling application whether the currently connected user is authorized to use a given calendar.

Because the USE_PRIVILEGE column is derived at query time from the FND_DATA_SECURITY package rather than being stored, the view functions as a row-level authorization filter for any form, concurrent program, or custom integration that must respect General Ledger Data Access Sets (DAS). This makes it the preferred object for LOVs and validation queries where calendar visibility must match the security model.

Underlying Base Objects

The view is defined over the following documented objects:

• GL_TRANSACTION_CALENDAR (SYNONYM) — the driving table, supplying TRANSACTION_CALENDAR_ID, NAME, and DESCRIPTION for every transaction calendar defined in the instance.
• FND_DATA_SECURITY (PACKAGE) — invoked through FND_DATA_SECURITY.CHECK_FUNCTION to evaluate the current user's entitlement against the GL_DAS_TRANS_CAL_U privilege group and the GL_DAS_TRANS_CAL data access set object.
• FND_GLOBAL (PACKAGE) — supplies FND_GLOBAL.USER_NAME, the runtime identity passed into the security check.

The view is owned by APPS and is a simple, non-joining projection: one row is returned per transaction calendar row. All security logic is encapsulated in the DECODE expression, so no additional tables or outer joins are required to produce the privilege flag.

Key Columns

• TRANSACTION_CALENDAR_ID — the primary key of GL_TRANSACTION_CALENDAR; used to join to GL_PERIOD_STATUSES, GL_LEDGERS, and related period-close objects.
• NAME — the user-defined calendar name, for example "Standard Monthly Calendar"; also passed into the security check as the object instance argument.
• DESCRIPTION — free-text description stored on the calendar definition.
• USE_PRIVILEGE — a derived Y/N flag. FND_DATA_SECURITY.CHECK_FUNCTION returns 'T' when the user holds the required privilege for the named calendar, which the DECODE maps to 'Y'; any other return value is mapped to 'N'. Rows where the user lacks privilege are still returned, but flagged 'N'.

Common Use Cases and Queries

The most frequent use is filtering a calendar list of values to only those calendars the signed-on user may select. Note that a display-only query requires no WHERE clause on USE_PRIVILEGE; the flag itself is the presentation control.

SELECT transaction_calendar_id,
       name,
       description,
       use_privilege
  FROM apps.gl_transaction_calendar_v
 ORDER BY name;

To restrict output to authorized calendars only, filter on the flag:

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

A validation query confirms whether a specific user may post into a given calendar before a journal import or interface load proceeds:

SELECT v.name,
       v.use_privilege
  FROM apps.gl_transaction_calendar_v v
 WHERE v.transaction_calendar_id = :p_calendar_id;

Because USE_PRIVILEGE is evaluated in the session context, the view is also useful in diagnostic scripts that audit which calendars a responsibility can see. In integration scenarios, the view is typically joined back to GL_LEDGERS on TRANSACTION_CALENDAR_ID to confirm that every ledger configured for an interface is reachable by the service account executing the load.