Search Results create_schedule

Overview

APPS.GL_SCHEDULER_PKG is a server-side PL/SQL package in Oracle E-Business Suite that supports the General Ledger concurrent scheduling framework. Its core responsibility is the programmatic creation, maintenance, and synchronization of concurrent schedules that drive period-based GL processes, such as the period-end close, revaluation, and other recurring concurrent requests bound to GL calendar periods. The package is declared with AUTHID CURRENT_USER, meaning its unqualified references to database objects resolve through the calling user's schema and synonym context—in practice, the APPS schema—rather than through definer's rights. This is consistent with the standard EBS practice of granting broad execution privileges on APPS-owned packages to application responsibility users.

The package abstracts the underlying Oracle Concurrent Manager scheduling tables (the FND_CONC_RELEASE_* family) behind a small, transaction-safe API. Instead of requiring callers to insert directly into release-class, period, and conjunction/disjunction member tables, developers and internal GL code invoke a single function to register a schedule for a named calendar and period type.

Key Procedures and Functions

• CREATE_SCHEDULE — Creates a new concurrent schedule identified by a schedule name, and associates it with a calendar, period type, run day, run time, and a creation control flag. It returns a NUMBER status code indicating success or the nature of any failure. This is the primary entry point referenced by the search term "create_schedule." The create_flag BOOLEAN parameter governs whether the schedule is immediately materialized in the concurrent manager tables or only validated.
• CLEANUP_SCHEDULE — Removes or deactivates a previously created schedule by name, returning a NUMBER status. It is used to retire schedules that are no longer required, preventing orphaned rows in the FND concurrent release tables.
• UPDATE_SCHEDULES — Refreshes existing schedules when a period set changes. It accepts a period set name and returns a NUMBER status. This supports situations where period definitions in the GL calendar have been altered and dependent concurrent schedules must be regenerated to remain consistent.

All three functions return an integer status code; callers should check this value rather than assuming success, and must commit their own transaction boundaries, as the package does not commit internally per EBS API conventions.

Tables Accessed

The package reads and writes the following objects through APPS synonyms:

• GL_CONCURRENT_SCHEDULES and GL_CONCURRENT_SCHEDULES_S — the GL-specific schedule definition and its translation/sequence table, holding schedule metadata such as calendar and period type associations.
• GL_PERIODS — the GL calendar period definitions, used to resolve run dates and validate calendar/period type combinations.
• FND_CONC_RELEASE_CLASSES — the concurrent release class that groups scheduled requests.
• FND_CONC_RELEASE_PERIODS — the period-level entries that define recurring run windows for a release class.
• FND_CONC_RELEASE_DISJS, FND_CONC_REL_DISJ_MEMBERS, FND_CONC_REL_CONJ_MEMBERS — the disjunction/conjunction member tables that express the boolean run-date logic consumed by the Concurrent Manager.

Usage Notes

GL_SCHEDULER_PKG is typically invoked by internal GL close and calendar maintenance processes rather than directly by end users. It is not exposed through a standard GL form; instead, it is called by concurrent programs and by other PL/SQL logic during calendar and period-set maintenance. The UPDATE_SCHEDULES function is commonly triggered when a period set is regenerated, ensuring that dependent concurrent schedules remain aligned with the revised period definitions. Custom code should invoke the functions with fully qualified APPS object references, check the returned status code, and manage commits explicitly. The package is referenced by zero other documented packages, so callers must ensure their own error handling around its results.