Search Results gl_concurrent_schedules




Overview
Explore in AI Chat

Overview

The GL_CONCURRENT_SCHEDULES table is a core repository for managing scheduled batch processing within the Oracle General Ledger module of Oracle E-Business Suite (EBS). It stores the master definitions for concurrent request schedules, which are used to automate and control the periodic submission of critical financial processes. These processes include, but are not limited to, recurring journal imports, mass allocations, and consolidation runs. The table's role is to provide a centralized, configurable framework that ensures financial operations execute consistently according to predefined calendars and business rules, thereby reducing manual intervention and enhancing operational reliability.

Key Information Stored

The table's primary key is the SCHEDULE_NAME, which uniquely identifies each schedule definition. As indicated by the foreign key relationships in the provided metadata, two critical columns link the schedule to the application's accounting calendar structure: PERIOD_SET_NAME and PERIOD_TYPE. These columns define the accounting calendar and period type (e.g., Month, Quarter) against which the schedule runs. While the exact full column list is not detailed in the excerpt, typical data stored includes parameters for the associated concurrent program, the effective start and end dates for the schedule, the frequency of execution (e.g., daily, period-end), and control flags for the schedule's status and processing rules.

Common Use Cases and Queries

A primary use case is the administration and audit of automated financial processes. System administrators and functional consultants query this table to verify schedule configurations, troubleshoot failed submissions, or document process flows. Common reporting queries involve joining with FND_CONCURRENT_REQUESTS to analyze the execution history of a specific schedule. A sample SQL pattern to list active schedules and their calendar dependencies is:

  • SELECT schedule_name, period_set_name, period_type
  • FROM gl.gl_concurrent_schedules
  • WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

Another critical use case is during period-close procedures, where teams validate that all necessary automated jobs are correctly scheduled for the upcoming accounting period.

Related Objects

As per the documented foreign keys, GL_CONCURRENT_SCHEDULES has a direct dependency on two fundamental calendar setup tables: GL_PERIOD_SETS and GL_PERIOD_TYPES. This ensures referential integrity, guaranteeing that a schedule cannot reference an invalid calendar or period type. The schedule definitions are utilized by the underlying concurrent manager infrastructure, interacting with tables such as FND_CONCURRENT_REQUESTS for execution instances. While not explicitly listed in the metadata, the schedules are typically accessed and managed via the Oracle EBS front-end forms and are integral to the setup of processes like the Journal Import scheduler.