Search Results gl_concurrent_schedules_s

Overview

APPS.GL_SCHEDULER_PKG is a PL/SQL package body in the Oracle E-Business Suite General Ledger (GL) application, residing in the APPS schema and reported with a status of VALID under ETRM 12.2.2. Its principal business function is to automate the generation and maintenance of concurrent program scheduling definitions used when closing and reporting on GL accounting periods. Rather than requiring administrators to manually create every submission request for period-end and recurring concurrent processes, the package derives schedule records from the period definitions held in GL_PERIODS and the release definitions managed by the Oracle Concurrent Manager (FND) publication framework. In practical terms, it bridges GL period calendars with the FND concurrent release model, so that recurring activities—period close routines, reporting, allocations, and similar jobs—are submitted with the correct timing and release criteria. The package is classified as OTHER in the ETRM metadata, which indicates that it is an internal implementation unit rather than a documented open interface or public API; it is not referenced by any other database object, confirming that it is intended for internal consumption by GL period-management and scheduling routines rather than for direct third-party integration.

Key Procedures and Functions

The package exposes three documented procedures. As an implementation package, its internal structure should be treated as subject to change between releases, and the ETRM metadata does not publish parameter lists, so only the stated purposes are described here.

• CREATE_SCHEDULE — Establishes a concurrent schedule for a GL period or set of periods. It resolves the relevant period information and constructs the corresponding release or period definition records so that the associated concurrent programs execute at the intended time.
• CLEANUP_SCHEDULE — Removes or invalidates schedule definitions that are no longer required, typically after periods have been closed or when obsolete scheduling configurations must be purged to prevent redundant or conflicting concurrent submissions.
• UPDATE_SCHEDULES — Modifies existing schedule definitions to reflect changes in period status, release criteria, or scheduling attributes, keeping the active set of schedules synchronized with the current GL calendar and release configuration.

Tables Accessed

The package operates across both GL and FND tables, accessed through APPS synonyms. GL_CONCURRENT_SCHEDULES and GL_CONCURRENT_SCHEDULES_S are the primary GL tables holding the schedule definitions and their translation records; GL_PERIODS supplies the accounting period and calendar data that drive schedule timing. On the concurrent manager side, the package works with the FND concurrent release model: FND_CONC_RELEASE_CLASSES and FND_CONC_RELEASE_PERIODS define the release classes and period-based release windows, while FND_CONC_RELEASE_DISJS, FND_CONC_REL_CONJ_MEMBERS, and FND_CONC_REL_DISJ_MEMBERS store the disjunction and conjunction members that determine the logical conditions under which a release is triggered. FND_MESSAGE is used to raise or retrieve standardized messages during processing, and FNDCP_SCH is referenced for concurrent scheduling support. DUAL and STANDARD are used for basic SQL evaluation and PL/SQL operations.

Usage Notes

GL_SCHEDULER_PKG is normally invoked indirectly, from GL period-management and concurrent scheduling flows—for example, when schedules are generated or refreshed as periods are opened, closed, or redefined—rather than being called directly by end users. Because it is not referenced by any other database object per the ETRM metadata and is classified as OTHER, it should not be treated as a supported public API. Customizations and extensions should avoid calling these procedures directly and should instead rely on the standard GL concurrent program and period-management interfaces; any direct invocation risks incompatibility across EBS 12.1.1 and 12.2.2 patch levels, since the package is an internal component whose behavior and dependencies are tied to the concurrent release framework.