Results for “gl_concurrent_schedules”
34 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
GL_CONCURRENT_SCHEDULES is a General Ledger (GL) application table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the GL schema with VALID status. It stores Oracle General Ledger concurrent schedule definitions — the user-defined program schedules that control when background concurrent programs are launched against a particular accounting calendar. In EBS implementations, this table is central to automating recurring GL processes such as journal import, period close activities, revaluation, translation, consolidation, and recurring journal generation, ensuring that these operations fire on a predictable cadence tied to the accounting calendar rather than manual invocation.
From a modeling perspective, the mined foreign-key structure suggests a Data Vault classification of link. The table does not function as a pure hub of independent business entities; instead, it records a relationship between a schedule definition and the underlying calendar structures (period sets and period types). This link interpretation reflects the associative nature of the object: it binds a named schedule to a period set and period type, together with the execution attributes that govern timing.
Key Information Stored
The table is documented with 27 physical columns in the 12.2.2 schema. The most operationally significant columns are:
- SCHEDULE_NAME — the descriptive identifier of the concurrent schedule, and the column defined by the primary key GL_CONCURRENT_SCHEDULES_PK. A unique index, GL_CONCURRENT_SCHEDULES_U1 on SCHEDULE_NAME, identifies it as the primary business-key candidate.
- PERIOD_SET_NAME — the accounting period set the schedule is anchored to; a foreign key referencing GL_PERIOD_SETS.
- PERIOD_TYPE — the period type (for example, a monthly or weekly calendar type) used to determine period boundaries; a foreign key referencing GL_PERIOD_TYPES.
- RUN_DAY — the day within the period on which the scheduled program is intended to execute.
- RUN_TIME — the time of day at which the scheduled concurrent program runs.
- ENABLED_FLAG — indicates whether the schedule is currently active and eligible for submission.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing who last modified the schedule row and when.
- CREATION_DATE, CREATED_BY — standard audit columns recording initial row creation.
- ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the standard EBS descriptive flexfield (DFF) columns, allowing implementers to extend the schedule definition with site-specific information.
The surrogate primary key, GL_CONCURRENT_SCHEDULES_PK, is defined on SCHEDULE_NAME. In practice, SCHEDULE_NAME also serves as the business key, as reflected by the unique index GL_CONCURRENT_SCHEDULES_U1, meaning the surrogate and business identifiers converge on the same column.
Common Use Cases and Queries
Typical usage centers on auditing schedule configuration, troubleshooting why a recurring GL program did or did not run, and reporting on active schedules for change-management or SOX compliance purposes. A common query pattern lists all enabled schedules with their calendar binding:
- SELECT schedule_name, period_set_name, period_type, run_day, run_time FROM gl_concurrent_schedules WHERE enabled_flag = 'Y';
- Joining to gl_period_sets on period_set_name to validate that the referenced calendar is itself active and correct.
- Joining to gl_period_types on period_type to confirm the period type aligns with the intended calendar granularity.
- Filtering by last_update_date to identify schedules recently modified by administrators.
- Querying attribute columns (attribute1–attribute15, context) where DFF segments carry implementation-specific classification or ownership data.
These queries support reconciliations during period close, where verifying that revaluation, translation, or consolidation programs are scheduled against the correct calendar is essential to timely financial statement production.
Related Objects
The most significant related objects are those tied to this table through documented foreign-key relationships and the surrounding GL scheduling infrastructure:
- GL_PERIOD_SETS — referenced via GL_CONCURRENT_SCHEDULES.PERIOD_SET_NAME; defines the accounting calendar the schedule depends on.
- GL_PERIOD_TYPES — referenced via GL_CONCURRENT_SCHEDULES.PERIOD_TYPE; defines the period granularity used to compute run boundaries.
- Additionally, standard EBS concurrent manager objects such as FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUESTS, and FND_CONCURRENT_PROGRAM_SERIAL interact with schedules when programs are submitted, while GL_PERIODS supplies the concrete period rows against which RUN_DAY and RUN_TIME are ultimately interpreted. Together these objects form the scheduling and calendar context in which GL_CONCURRENT_SCHEDULES operates.
-
Oracle General Ledger concurrent schedule definitions
-
Oracle General Ledger concurrent schedule definitions
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
This table contains the tracking information that Golden Gate will use to launch Journal Import.
-
USSGL transaction codes
-
12.2.2 DBA Data 12.2.2
-
This table contains the tracking information that Golden Gate will use to launch Journal Import.
-
USSGL transaction codes
-
12.1.1 DBA Data 12.1.1